diff --git a/docs/_images/Tenant_manager_01_3Engines.png b/docs/_images/Tenant_manager_01_connectVM.png similarity index 100% rename from docs/_images/Tenant_manager_01_3Engines.png rename to docs/_images/Tenant_manager_01_connectVM.png diff --git a/docs/_images/Tenant_manager_02_3Engines.png b/docs/_images/Tenant_manager_02_connectVM.png similarity index 100% rename from docs/_images/Tenant_manager_02_3Engines.png rename to docs/_images/Tenant_manager_02_connectVM.png diff --git a/docs/_images/Tenant_manager_03_3Engines.png b/docs/_images/Tenant_manager_03_connectVM.png similarity index 100% rename from docs/_images/Tenant_manager_03_3Engines.png rename to docs/_images/Tenant_manager_03_connectVM.png diff --git a/docs/_images/Tenant_manager_04_3Engines.png b/docs/_images/Tenant_manager_04_connectVM.png similarity index 100% rename from docs/_images/Tenant_manager_04_3Engines.png rename to docs/_images/Tenant_manager_04_connectVM.png diff --git a/docs/_images/Tenant_manager_05_3Engines.png b/docs/_images/Tenant_manager_05_connectVM.png similarity index 100% rename from docs/_images/Tenant_manager_05_3Engines.png rename to docs/_images/Tenant_manager_05_connectVM.png diff --git a/docs/_images/add_ticket_3Enginescloud.png b/docs/_images/add_ticket_connectVMcloud.png similarity index 100% rename from docs/_images/add_ticket_3Enginescloud.png rename to docs/_images/add_ticket_connectVMcloud.png diff --git a/docs/_images/3Engines-logo.png b/docs/_images/connectVM-logo.png similarity index 100% rename from docs/_images/3Engines-logo.png rename to docs/_images/connectVM-logo.png diff --git a/docs/_images/3Engines-user-roles-create-4.png b/docs/_images/connectVM-user-roles-create-4.png similarity index 100% rename from docs/_images/3Engines-user-roles-create-4.png rename to docs/_images/connectVM-user-roles-create-4.png diff --git a/docs/_images/3Engines_cli.png b/docs/_images/connectVM_cli.png similarity index 100% rename from docs/_images/3Engines_cli.png rename to docs/_images/connectVM_cli.png diff --git a/docs/_images/3Engines_cli_install_linux_help.png b/docs/_images/connectVM_cli_install_linux_help.png similarity index 100% rename from docs/_images/3Engines_cli_install_linux_help.png rename to docs/_images/connectVM_cli_install_linux_help.png diff --git a/docs/_images/3Engines_cloud_1.png b/docs/_images/connectVM_cloud_1.png similarity index 100% rename from docs/_images/3Engines_cloud_1.png rename to docs/_images/connectVM_cloud_1.png diff --git a/docs/_images/3Engines_cloud_10.png b/docs/_images/connectVM_cloud_10.png similarity index 100% rename from docs/_images/3Engines_cloud_10.png rename to docs/_images/connectVM_cloud_10.png diff --git a/docs/_images/3Engines_cloud_11.png b/docs/_images/connectVM_cloud_11.png similarity index 100% rename from docs/_images/3Engines_cloud_11.png rename to docs/_images/connectVM_cloud_11.png diff --git a/docs/_images/3Engines_cloud_2.png b/docs/_images/connectVM_cloud_2.png similarity index 100% rename from docs/_images/3Engines_cloud_2.png rename to docs/_images/connectVM_cloud_2.png diff --git a/docs/_images/3Engines_cloud_3.png b/docs/_images/connectVM_cloud_3.png similarity index 100% rename from docs/_images/3Engines_cloud_3.png rename to docs/_images/connectVM_cloud_3.png diff --git a/docs/_images/3Engines_cloud_5.png b/docs/_images/connectVM_cloud_5.png similarity index 100% rename from docs/_images/3Engines_cloud_5.png rename to docs/_images/connectVM_cloud_5.png diff --git a/docs/_images/3Engines_cloud_6.png b/docs/_images/connectVM_cloud_6.png similarity index 100% rename from docs/_images/3Engines_cloud_6.png rename to docs/_images/connectVM_cloud_6.png diff --git a/docs/_images/3Engines_cloud_7.png b/docs/_images/connectVM_cloud_7.png similarity index 100% rename from docs/_images/3Engines_cloud_7.png rename to docs/_images/connectVM_cloud_7.png diff --git a/docs/_images/3Engines_cloud_8.png b/docs/_images/connectVM_cloud_8.png similarity index 100% rename from docs/_images/3Engines_cloud_8.png rename to docs/_images/connectVM_cloud_8.png diff --git a/docs/_images/3Engines_cloud_9.png b/docs/_images/connectVM_cloud_9.png similarity index 100% rename from docs/_images/3Engines_cloud_9.png rename to docs/_images/connectVM_cloud_9.png diff --git a/docs/_images/3Engines_coe.png b/docs/_images/connectVM_coe.png similarity index 100% rename from docs/_images/3Engines_coe.png rename to docs/_images/connectVM_coe.png diff --git a/docs/_images/3Engines_coe_cluster_list.png b/docs/_images/connectVM_coe_cluster_list.png similarity index 100% rename from docs/_images/3Engines_coe_cluster_list.png rename to docs/_images/connectVM_coe_cluster_list.png diff --git a/docs/_images/3Engines_container_create_help.png b/docs/_images/connectVM_container_create_help.png similarity index 100% rename from docs/_images/3Engines_container_create_help.png rename to docs/_images/connectVM_container_create_help.png diff --git a/docs/_images/3Engines_help.png b/docs/_images/connectVM_help.png similarity index 100% rename from docs/_images/3Engines_help.png rename to docs/_images/connectVM_help.png diff --git a/docs/_images/3Engines_server_create_help.png b/docs/_images/connectVM_server_create_help.png similarity index 100% rename from docs/_images/3Engines_server_create_help.png rename to docs/_images/connectVM_server_create_help.png diff --git a/docs/_images/3Engines_vim.png b/docs/_images/connectVM_vim.png similarity index 100% rename from docs/_images/3Engines_vim.png rename to docs/_images/connectVM_vim.png diff --git a/docs/_images/3Enginescli_flavor_list.png b/docs/_images/connectVMcli_flavor_list.png similarity index 100% rename from docs/_images/3Enginescli_flavor_list.png rename to docs/_images/connectVMcli_flavor_list.png diff --git a/docs/_images/cookie-consent-3Engines-cloud-1.png b/docs/_images/cookie-consent-connectVM-cloud-1.png similarity index 100% rename from docs/_images/cookie-consent-3Engines-cloud-1.png rename to docs/_images/cookie-consent-connectVM-cloud-1.png diff --git a/docs/_images/cookie-consent-3Engines-cloud-11.png b/docs/_images/cookie-consent-connectVM-cloud-11.png similarity index 100% rename from docs/_images/cookie-consent-3Engines-cloud-11.png rename to docs/_images/cookie-consent-connectVM-cloud-11.png diff --git a/docs/_images/cookie-consent-3Engines-cloud-12.png b/docs/_images/cookie-consent-connectVM-cloud-12.png similarity index 100% rename from docs/_images/cookie-consent-3Engines-cloud-12.png rename to docs/_images/cookie-consent-connectVM-cloud-12.png diff --git a/docs/_images/cookie-consent-3Engines-cloud-13.png b/docs/_images/cookie-consent-connectVM-cloud-13.png similarity index 100% rename from docs/_images/cookie-consent-3Engines-cloud-13.png rename to docs/_images/cookie-consent-connectVM-cloud-13.png diff --git a/docs/_images/cookie-consent-3Engines-cloud-15.png b/docs/_images/cookie-consent-connectVM-cloud-15.png similarity index 100% rename from docs/_images/cookie-consent-3Engines-cloud-15.png rename to docs/_images/cookie-consent-connectVM-cloud-15.png diff --git a/docs/_images/cookie-consent-3Engines-cloud-2.png b/docs/_images/cookie-consent-connectVM-cloud-2.png similarity index 100% rename from docs/_images/cookie-consent-3Engines-cloud-2.png rename to docs/_images/cookie-consent-connectVM-cloud-2.png diff --git a/docs/_images/cookie-consent-3Engines-cloud-4.png b/docs/_images/cookie-consent-connectVM-cloud-4.png similarity index 100% rename from docs/_images/cookie-consent-3Engines-cloud-4.png rename to docs/_images/cookie-consent-connectVM-cloud-4.png diff --git a/docs/_images/cookie-consent-3Engines-cloud-5.png b/docs/_images/cookie-consent-connectVM-cloud-5.png similarity index 100% rename from docs/_images/cookie-consent-3Engines-cloud-5.png rename to docs/_images/cookie-consent-connectVM-cloud-5.png diff --git a/docs/_images/cookie-consent-3Engines-cloud-6.png b/docs/_images/cookie-consent-connectVM-cloud-6.png similarity index 100% rename from docs/_images/cookie-consent-3Engines-cloud-6.png rename to docs/_images/cookie-consent-connectVM-cloud-6.png diff --git a/docs/_images/cookie-consent-3Engines-cloud-7.png b/docs/_images/cookie-consent-connectVM-cloud-7.png similarity index 100% rename from docs/_images/cookie-consent-3Engines-cloud-7.png rename to docs/_images/cookie-consent-connectVM-cloud-7.png diff --git a/docs/_images/cookie-consent-3Engines-cloud-8.png b/docs/_images/cookie-consent-connectVM-cloud-8.png similarity index 100% rename from docs/_images/cookie-consent-3Engines-cloud-8.png rename to docs/_images/cookie-consent-connectVM-cloud-8.png diff --git a/docs/_images/cookie-consent-3Engines-cloud-9.png b/docs/_images/cookie-consent-connectVM-cloud-9.png similarity index 100% rename from docs/_images/cookie-consent-3Engines-cloud-9.png rename to docs/_images/cookie-consent-connectVM-cloud-9.png diff --git a/docs/_images/create_account_3Enginescloud.png b/docs/_images/create_account_connectVMcloud.png similarity index 100% rename from docs/_images/create_account_3Enginescloud.png rename to docs/_images/create_account_connectVMcloud.png diff --git a/docs/_images/dashboard-services-10-3Engines-cloud.png b/docs/_images/dashboard-services-10-connectVM-cloud.png similarity index 100% rename from docs/_images/dashboard-services-10-3Engines-cloud.png rename to docs/_images/dashboard-services-10-connectVM-cloud.png diff --git a/docs/_images/dashboard-services-2-3Engines-cloud.png b/docs/_images/dashboard-services-2-connectVM-cloud.png similarity index 100% rename from docs/_images/dashboard-services-2-3Engines-cloud.png rename to docs/_images/dashboard-services-2-connectVM-cloud.png diff --git a/docs/_images/dashboard-services-3-3Engines-cloud.png b/docs/_images/dashboard-services-3-connectVM-cloud.png similarity index 100% rename from docs/_images/dashboard-services-3-3Engines-cloud.png rename to docs/_images/dashboard-services-3-connectVM-cloud.png diff --git a/docs/_images/dashboard-services-4-3Engines-cloud.png b/docs/_images/dashboard-services-4-connectVM-cloud.png similarity index 100% rename from docs/_images/dashboard-services-4-3Engines-cloud.png rename to docs/_images/dashboard-services-4-connectVM-cloud.png diff --git a/docs/_images/dashboard-services-5-3Engines-cloud.png b/docs/_images/dashboard-services-5-connectVM-cloud.png similarity index 100% rename from docs/_images/dashboard-services-5-3Engines-cloud.png rename to docs/_images/dashboard-services-5-connectVM-cloud.png diff --git a/docs/_images/dashboard-services-6-3Engines-cloud.png b/docs/_images/dashboard-services-6-connectVM-cloud.png similarity index 100% rename from docs/_images/dashboard-services-6-3Engines-cloud.png rename to docs/_images/dashboard-services-6-connectVM-cloud.png diff --git a/docs/_images/dashboard-services-7-3Engines-cloud.png b/docs/_images/dashboard-services-7-connectVM-cloud.png similarity index 100% rename from docs/_images/dashboard-services-7-3Engines-cloud.png rename to docs/_images/dashboard-services-7-connectVM-cloud.png diff --git a/docs/_images/dashboard-services-9-3Engines-cloud.png b/docs/_images/dashboard-services-9-connectVM-cloud.png similarity index 100% rename from docs/_images/dashboard-services-9-3Engines-cloud.png rename to docs/_images/dashboard-services-9-connectVM-cloud.png diff --git a/docs/_images/editing_profile_3Enginescloud.png b/docs/_images/editing_profile_connectVMcloud.png similarity index 100% rename from docs/_images/editing_profile_3Enginescloud.png rename to docs/_images/editing_profile_connectVMcloud.png diff --git a/docs/_images/enter_new_password_3Enginescloud.png b/docs/_images/enter_new_password_connectVMcloud.png similarity index 100% rename from docs/_images/enter_new_password_3Enginescloud.png rename to docs/_images/enter_new_password_connectVMcloud.png diff --git a/docs/_images/forgot_your_password_3Enginescloud.png b/docs/_images/forgot_your_password_connectVMcloud.png similarity index 100% rename from docs/_images/forgot_your_password_3Enginescloud.png rename to docs/_images/forgot_your_password_connectVMcloud.png diff --git a/docs/_images/inv_01_3Enginescloud.png b/docs/_images/inv_01_connectVMcloud.png similarity index 100% rename from docs/_images/inv_01_3Enginescloud.png rename to docs/_images/inv_01_connectVMcloud.png diff --git a/docs/_images/inv_02_3Enginescloud.png b/docs/_images/inv_02_connectVMcloud.png similarity index 100% rename from docs/_images/inv_02_3Enginescloud.png rename to docs/_images/inv_02_connectVMcloud.png diff --git a/docs/_images/ku_3Engines_line_entry.png b/docs/_images/ku_connectVM_line_entry.png similarity index 100% rename from docs/_images/ku_3Engines_line_entry.png rename to docs/_images/ku_connectVM_line_entry.png diff --git a/docs/_images/login_3Enginescloud.png b/docs/_images/login_connectVMcloud.png similarity index 100% rename from docs/_images/login_3Enginescloud.png rename to docs/_images/login_connectVMcloud.png diff --git a/docs/_images/manage-totp-05_3Enginescloud.png b/docs/_images/manage-totp-05_connectVMcloud.png similarity index 100% rename from docs/_images/manage-totp-05_3Enginescloud.png rename to docs/_images/manage-totp-05_connectVMcloud.png diff --git a/docs/_images/nvidia_chosen_3Engines_cloud.png b/docs/_images/nvidia_chosen_connectVM_cloud.png similarity index 100% rename from docs/_images/nvidia_chosen_3Engines_cloud.png rename to docs/_images/nvidia_chosen_connectVM_cloud.png diff --git a/docs/_images/register_3Enginescloud.png b/docs/_images/register_connectVMcloud.png similarity index 100% rename from docs/_images/register_3Enginescloud.png rename to docs/_images/register_connectVMcloud.png diff --git a/docs/_images/register_3Enginescloud1.png b/docs/_images/register_connectVMcloud1.png similarity index 100% rename from docs/_images/register_3Enginescloud1.png rename to docs/_images/register_connectVMcloud1.png diff --git a/docs/_images/register_3Enginescloud1.png.md b/docs/_images/register_connectVMcloud1.png.md similarity index 100% rename from docs/_images/register_3Enginescloud1.png.md rename to docs/_images/register_connectVMcloud1.png.md diff --git a/docs/_images/register_organization_3Enginescloud.png b/docs/_images/register_organization_connectVMcloud.png similarity index 100% rename from docs/_images/register_organization_3Enginescloud.png rename to docs/_images/register_organization_connectVMcloud.png diff --git a/docs/_images/registration_successful_3Enginescloud.png b/docs/_images/registration_successful_connectVMcloud.png similarity index 100% rename from docs/_images/registration_successful_3Enginescloud.png rename to docs/_images/registration_successful_connectVMcloud.png diff --git a/docs/_images/saml_3Engines_cloud.png b/docs/_images/saml_connectVM_cloud.png similarity index 100% rename from docs/_images/saml_3Engines_cloud.png rename to docs/_images/saml_connectVM_cloud.png diff --git a/docs/_images/services_3Enginescloud.png b/docs/_images/services_connectVMcloud.png similarity index 100% rename from docs/_images/services_3Enginescloud.png rename to docs/_images/services_connectVMcloud.png diff --git a/docs/_images/tickets_3Enginescloud.png b/docs/_images/tickets_connectVMcloud.png similarity index 100% rename from docs/_images/tickets_3Enginescloud.png rename to docs/_images/tickets_connectVMcloud.png diff --git a/docs/_images/users_roles_01_3Enginescloud.png b/docs/_images/users_roles_01_connectVMcloud.png similarity index 100% rename from docs/_images/users_roles_01_3Enginescloud.png rename to docs/_images/users_roles_01_connectVMcloud.png diff --git a/docs/_images/wallets_contracts_3Enginescloud.png b/docs/_images/wallets_contracts_connectVMcloud.png similarity index 100% rename from docs/_images/wallets_contracts_3Enginescloud.png rename to docs/_images/wallets_contracts_connectVMcloud.png diff --git a/docs/accountmanagement/Adding-Editing-Organizations.html.md b/docs/accountmanagement/Adding-Editing-Organizations.html.md index 523f651..05abff7 100644 --- a/docs/accountmanagement/Adding-Editing-Organizations.html.md +++ b/docs/accountmanagement/Adding-Editing-Organizations.html.md @@ -5,9 +5,9 @@ search: false Adding and editing Organization[🔗](#adding-and-editing-organization "Permalink to this headline") ================================================================================================= -After logging into press **Organization** button on the left bar menu. +After logging into press **Organization** button on the left bar menu. -![register_organization_3Enginescloud.png](../_images/register_organization_3Enginescloud.png) +![register_organization_connectVMcloud.png](../_images/register_organization_connectVMcloud.png) In **My Organization** tab you can register an organization and become its administrator or join an organization if you have invitation code provided by it’s administrator. diff --git a/docs/accountmanagement/Contracts-Wallets.html.md b/docs/accountmanagement/Contracts-Wallets.html.md index aa27ac4..0a92fc0 100644 --- a/docs/accountmanagement/Contracts-Wallets.html.md +++ b/docs/accountmanagement/Contracts-Wallets.html.md @@ -5,9 +5,9 @@ search: false Wallets and Contracts Management[🔗](#wallets-and-contracts-management "Permalink to this headline") =================================================================================================== -After logging into press **Wallets/Contracts** button on the left menu bar: +After logging into press **Wallets/Contracts** button on the left menu bar: -![wallets_contracts_3Enginescloud.png](../_images/wallets_contracts_3Enginescloud.png) +![wallets_contracts_connectVMcloud.png](../_images/wallets_contracts_connectVMcloud.png) you will see the following 3 billing modes: diff --git a/docs/accountmanagement/Cookie-consent-on-3Engines-Cloud.html.md b/docs/accountmanagement/Cookie-consent-on-connectVM-Cloud.html.md similarity index 78% rename from docs/accountmanagement/Cookie-consent-on-3Engines-Cloud.html.md rename to docs/accountmanagement/Cookie-consent-on-connectVM-Cloud.html.md index 2fe68a6..5f61d11 100644 --- a/docs/accountmanagement/Cookie-consent-on-3Engines-Cloud.html.md +++ b/docs/accountmanagement/Cookie-consent-on-connectVM-Cloud.html.md @@ -2,7 +2,7 @@ search: false --- -Cookie consent on 3Engines Cloud[🔗](#cookie-consent-on-brand-name "Permalink to this headline") +Cookie consent on connectVM Cloud[🔗](#cookie-consent-on-brand-name "Permalink to this headline") ================================================================================================= A *cookie* is a small text file that your browser stores in local environment and later uses to track or recognize your activities on the site. @@ -15,7 +15,7 @@ Cookies are an essential tool for the remote site to deliver the best possible u Introducing Cookiebot site[🔗](#introducing-cookiebot-site "Permalink to this headline") --------------------------------------------------------------------------------------- -3Engines Cloud is using [Cookiebot](https://www.cookiebot.com/) software to manage **cookies consent** from the user. It will show you all of the cookies that your browser is storing and you will be able to choose which types of cookies should 3Engines Cloud take into account. Both Cookiebot and 3Engines Cloud site are [GDPR compliant](https://gdpr-info.eu/), however, 3Engines Cloud also has its own [Privacy Policy](https://3Engines.com/privacy-policy/) in effect. +connectVM Cloud is using [Cookiebot](https://www.cookiebot.com/) software to manage **cookies consent** from the user. It will show you all of the cookies that your browser is storing and you will be able to choose which types of cookies should connectVM Cloud take into account. Both Cookiebot and connectVM Cloud site are [GDPR compliant](https://gdpr-info.eu/), however, connectVM Cloud also has its own [Privacy Policy](https://connectVM.com/privacy-policy/) in effect. Of particular relevance is Cookiebot page [Logging and demonstration of user consents](https://support.cookiebot.com/hc/en-us/articles/360003782654-Logging-and-demonstration-of-user-consents). @@ -26,16 +26,16 @@ You can directly interfere with cookies from your browser, operating system, net Cookiebot window[🔗](#cookiebot-window "Permalink to this headline") ------------------------------------------------------------------- -This is the Cookiebot window on 3Engines Cloud: +This is the Cookiebot window on connectVM Cloud: -![cookie-consent-3Engines-cloud-1.png](../_images/cookie-consent-3Engines-cloud-1.png) +![cookie-consent-connectVM-cloud-1.png](../_images/cookie-consent-connectVM-cloud-1.png) You will see it when visiting one of these sites for the first time: -* the **main site** itself, , -* in **AI platform** , -* on **ecommerce page**, , or in -* the **dashboard**, . +* the **main site** itself, , +* in **AI platform** , +* on **ecommerce page**, , or in +* the **dashboard**, . Cookiebot is interactive and you can change your cookies preferences while using the site. If the consent for using cookies was withdrawn, you are also going to see the same starting Cookiebot window when visiting these sites after the change. @@ -49,7 +49,7 @@ Details view of available cookies[🔗](#details-view-of-available-cookies "Perm To see the cookies that you can give your consent to, click on **Details**. -![cookie-consent-3Engines-cloud-2.png](../_images/cookie-consent-3Engines-cloud-2.png) +![cookie-consent-connectVM-cloud-2.png](../_images/cookie-consent-connectVM-cloud-2.png) There are five types of cookies and you may need to scroll down to see them all. @@ -59,11 +59,11 @@ When shown for the first time, the left button will contain label **Deny**. Choo This is the most basic type of cookie and the site presumes you have already given consent to it. That is why the check button to the right of the row, ![COOKIE-BUTTON](_images/cookie-consent-for-site-1.png), is already set to “ON”. Technically, you can try to remove the consent by clicking on that button, but you will be met with a message like this: -![cookie-consent-3Engines-cloud-13.png](../_images/cookie-consent-3Engines-cloud-13.png) +![cookie-consent-connectVM-cloud-13.png](../_images/cookie-consent-connectVM-cloud-13.png) You can also see additional details about that cookie type and the cookies it contains. By clicking on the name of the cookie, you will be able to see from which company it is, what it looks like and so on. -![cookie-consent-3Engines-cloud-15.png](../_images/cookie-consent-3Engines-cloud-15.png) +![cookie-consent-connectVM-cloud-15.png](../_images/cookie-consent-connectVM-cloud-15.png) ### The number of cookies shown per category[🔗](#the-number-of-cookies-shown-per-category "Permalink to this headline") @@ -106,22 +106,22 @@ Click on toggle button on the right side of the form window and when you finish ### About cookie consent[🔗](#about-cookie-consent "Permalink to this headline") -This option explains what cookies are and also provides links to [Privacy Policy](https://3Engines.com/privacy-policy/) and, more specifically, to [Cookie Policy](https://3Engines.com/cookie-policy/). +This option explains what cookies are and also provides links to [Privacy Policy](https://connectVM.com/privacy-policy/) and, more specifically, to [Cookie Policy](https://connectVM.com/cookie-policy/). -![cookie-consent-3Engines-cloud-4.png](../_images/cookie-consent-3Engines-cloud-4.png) +![cookie-consent-connectVM-cloud-4.png](../_images/cookie-consent-connectVM-cloud-4.png) You can still change cookie consent by clicking on **Customize**, which will lead you back to **Details** tab (already explained above). Selecting the cookies preferences[🔗](#selecting-the-cookies-preferences "Permalink to this headline") ----------------------------------------------------------------------------------------------------- -Once you click either **Allow selection** or **Allow all** buttons, the form will disappear and your selection will be fixed. To change it, click on icon ![COORANGE](_images/cookie-consent-3Engines-cloud-12.png) in the lower left browser window corner. +Once you click either **Allow selection** or **Allow all** buttons, the form will disappear and your selection will be fixed. To change it, click on icon ![COORANGE](_images/cookie-consent-connectVM-cloud-12.png) in the lower left browser window corner. -![cookie-consent-3Engines-cloud-5.png](../_images/cookie-consent-3Engines-cloud-5.png) +![cookie-consent-connectVM-cloud-5.png](../_images/cookie-consent-connectVM-cloud-5.png) A smaller window will appear: -![cookie-consent-3Engines-cloud-6.png](../_images/cookie-consent-3Engines-cloud-6.png) +![cookie-consent-connectVM-cloud-6.png](../_images/cookie-consent-connectVM-cloud-6.png) Clicking on **Withdraw your consent**, all types of cookies will be annulled except the necessary one. @@ -131,7 +131,7 @@ Button **Change your consent** will lead to the **Details** tab we already discu To see what your consent data look like, click on **Show details**: -![cookie-consent-3Engines-cloud-7.png](../_images/cookie-consent-3Engines-cloud-7.png) +![cookie-consent-connectVM-cloud-7.png](../_images/cookie-consent-connectVM-cloud-7.png) Each consent you give to the site, generates a unique consent ID, which, together with the time and date, you can see in the image above. Consent ID is random, anonymous, encrypted and unique. In that way, user anonymity is preserved while the site is still in a position to conclude whether the consent was actually provided or not. @@ -142,15 +142,15 @@ Troubleshooting[🔗](#troubleshooting "Permalink to this headline") You can see the contents of the cookie file through various browser options and also through a file viewer on your desktop computer. It is quite possible (but not at all advisable) to delete the cookie file outside of the browser. In particular, deleting the entire cookie by force will also delete the **necessary** part of the cookie. You may, then, lose access to the site, be forced to contact [Helpdesk and Support](Help-Desk-And-Support.html.md) and so on. -Setting up cookies on 3Engines Cloud subdomains[🔗](#setting-up-cookies-on-brand-name-subdomains "Permalink to this headline") +Setting up cookies on connectVM Cloud subdomains[🔗](#setting-up-cookies-on-brand-name-subdomains "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------------------- Cookiebot procedures are exactly the same on subdomains or the dashboard. -Here is what cookie consent window will look like, for example, on : +Here is what cookie consent window will look like, for example, on : -![cookie-consent-3Engines-cloud-8.png](../_images/cookie-consent-3Engines-cloud-8.png) +![cookie-consent-connectVM-cloud-8.png](../_images/cookie-consent-connectVM-cloud-8.png) -Set the cookies up by clicking on ![CO](_images/cookie-consent-3Engines-cloud-11.png) icon in the lover left part of the browser window. +Set the cookies up by clicking on ![CO](_images/cookie-consent-connectVM-cloud-11.png) icon in the lover left part of the browser window. -![cookie-consent-3Engines-cloud-9.png](../_images/cookie-consent-3Engines-cloud-9.png) \ No newline at end of file +![cookie-consent-connectVM-cloud-9.png](../_images/cookie-consent-connectVM-cloud-9.png) \ No newline at end of file diff --git a/docs/accountmanagement/Editing-Profile.html.md b/docs/accountmanagement/Editing-Profile.html.md index c51772f..d54b056 100644 --- a/docs/accountmanagement/Editing-Profile.html.md +++ b/docs/accountmanagement/Editing-Profile.html.md @@ -5,9 +5,9 @@ search: false Editing profile[🔗](#editing-profile "Permalink to this headline") ================================================================= -After logging into press **My Profile** button on the left bar menu. +After logging into press **My Profile** button on the left bar menu. -![editing_profile_3Enginescloud.png](../_images/editing_profile_3Enginescloud.png) +![editing_profile_connectVMcloud.png](../_images/editing_profile_connectVMcloud.png) In **My Profile** tab you will be able to: diff --git a/docs/accountmanagement/Forgotten-Password.html.md b/docs/accountmanagement/Forgotten-Password.html.md index 7f9c8fa..825b5da 100644 --- a/docs/accountmanagement/Forgotten-Password.html.md +++ b/docs/accountmanagement/Forgotten-Password.html.md @@ -7,7 +7,7 @@ Forgotten Password[🔗](#forgotten-password "Permalink to this headline") Go to the login page and click on **Forgot Password** button. -![forgot_your_password_3Enginescloud.png](../_images/forgot_your_password_3Enginescloud.png) +![forgot_your_password_connectVMcloud.png](../_images/forgot_your_password_connectVMcloud.png) Enter your email address into the field and press **Submit** button. Check your mailbox for further steps. @@ -15,7 +15,7 @@ Open the link from email and set up a new password. After that, click **Submit** button. -![enter_new_password_3Enginescloud.png](../_images/enter_new_password_3Enginescloud.png) +![enter_new_password_connectVMcloud.png](../_images/enter_new_password_connectVMcloud.png) If you haven’t received a message, check your SPAM folder. If you forgot the email address or the message can’t be delivered successfully, please contact our Support Team. \ No newline at end of file diff --git a/docs/accountmanagement/Help-Desk-And-Support.html.md b/docs/accountmanagement/Help-Desk-And-Support.html.md index ba96c73..d483ffd 100644 --- a/docs/accountmanagement/Help-Desk-And-Support.html.md +++ b/docs/accountmanagement/Help-Desk-And-Support.html.md @@ -5,9 +5,9 @@ search: false Helpdesk and Support[🔗](#helpdesk-and-support "Permalink to this headline") =========================================================================== -After logging into press the **Tickets** button on the left menu bar to create or manage your tickets. +After logging into press the **Tickets** button on the left menu bar to create or manage your tickets. -![tickets_3Enginescloud.png](../_images/tickets_3Enginescloud.png) +![tickets_connectVMcloud.png](../_images/tickets_connectVMcloud.png) There are few tabs available in Tickets menu: @@ -21,7 +21,7 @@ To check details or add a comment to existing tickets, please use **Show details If you want to create a new ticket, press **Add ticket** button on the top of the side. -![add_ticket_3Enginescloud.png](../_images/add_ticket_3Enginescloud.png) +![add_ticket_connectVMcloud.png](../_images/add_ticket_connectVMcloud.png) Choose proper category, add **Summary**, describe the issue and press **Create request** button. Once you press the button ticket will be visible in the **OPEN** tab. \ No newline at end of file diff --git a/docs/accountmanagement/How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md b/docs/accountmanagement/How-to-activate-connectVM-CLI-access-to-connectVM-Cloud-cloud-using-one-or-two-factor-authentication.html.md similarity index 72% rename from docs/accountmanagement/How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md rename to docs/accountmanagement/How-to-activate-connectVM-CLI-access-to-connectVM-Cloud-cloud-using-one-or-two-factor-authentication.html.md index 51758e3..24786e3 100644 --- a/docs/accountmanagement/How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md +++ b/docs/accountmanagement/How-to-activate-connectVM-CLI-access-to-connectVM-Cloud-cloud-using-one-or-two-factor-authentication.html.md @@ -2,18 +2,18 @@ search: false --- -How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication[🔗](#how-to-activate-3Engines-cli-access-to-brand-name-cloud-using-one-or-two-factor-authentication "Permalink to this headline") +How to activate connectVM CLI access to connectVM Cloud cloud using one- or two-factor authentication[🔗](#how-to-activate-connectVM-cli-access-to-brand-name-cloud-using-one-or-two-factor-authentication "Permalink to this headline") ======================================================================================================================================================================================================================================== One-factor and two-factor authentication for activating command line access to the cloud[🔗](#one-factor-and-two-factor-authentication-for-activating-command-line-access-to-the-cloud "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -To log into a site, you usually provide user name and email address during the creation of the account and then you use those same data to enter the site. You provide that data once and that is why it is called “one-factor” authentication. Two-factor authentication requires the same but considers it to be only the first step; on 3Engines Cloud cloud, the second step is +To log into a site, you usually provide user name and email address during the creation of the account and then you use those same data to enter the site. You provide that data once and that is why it is called “one-factor” authentication. Two-factor authentication requires the same but considers it to be only the first step; on connectVM Cloud cloud, the second step is > * to generate six-digit code using the appropriate software and then to > * send it to the cloud as a means of additional certification. -Cloud parameters for authentication and, later, 3Engines CLI access, are found in a so-called *RC file*. This article will help you download and use it to first authenticate and then access the cloud using 3Engines CLI commands. +Cloud parameters for authentication and, later, connectVM CLI access, are found in a so-called *RC file*. This article will help you download and use it to first authenticate and then access the cloud using connectVM CLI commands. What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -32,27 +32,27 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **2FA** If your account has 2FA enabled (which you will recognize from the respective prompt when authenticating), you need to install and configure a piece of software which generates six-digit codes used for 2FA. To set that up, follow one of these articles, depending on the type of device you are using: -* Mobile device (Android, iOS): [Two-Factor Authentication to 3Engines Cloud site using mobile application](Two-Factor-Authentication-for-3Engines-Cloud-Site.html.md) -* Computer [Two-Factor Authentication to 3Engines Cloud site using KeePassXC on desktop](Using-KeePassXC-for-Two-Factor-Authentication-on-3Engines-Cloud.html.md) +* Mobile device (Android, iOS): [Two-Factor Authentication to connectVM Cloud site using mobile application](Two-Factor-Authentication-for-connectVM-Cloud-Site.html.md) +* Computer [Two-Factor Authentication to connectVM Cloud site using KeePassXC on desktop](Using-KeePassXC-for-Two-Factor-Authentication-on-connectVM-Cloud.html.md) -No. 3 **3EnginesClient installed and available** +No. 3 **connectVMClient installed and available** -Installing 3EnginesClient on various platforms will also install the ability to run the **.sh** files. Since 3Engines is written in Python, it is recommended to use a dedicated virtual environment for the rest of this article. +Installing connectVMClient on various platforms will also install the ability to run the **.sh** files. Since connectVM is written in Python, it is recommended to use a dedicated virtual environment for the rest of this article. Install GitBash on Windows -: Run **.sh** files and install 3EnginesClient from a GitBash window under Windows. [How to install 3EnginesClient GitBash for Windows on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-GitBash-or-Cygwin-for-Windows-on-3Engines-Cloud.html.md). +: Run **.sh** files and install connectVMClient from a GitBash window under Windows. [How to install connectVMClient GitBash for Windows on connectVM Cloud](../connectVMcli/How-to-install-connectVMClient-GitBash-or-Cygwin-for-Windows-on-connectVM-Cloud.html.md). Install and run WSL (Linux under Windows) -: Run **.sh** files and install 3EnginesClient from a Ubuntu window under Windows. [How to install 3EnginesClient on Windows using Windows Subsystem for Linux on 3Engines Cloud 3Engines Hosting](../3Enginescli/How-to-install-3EnginesClient-on-Windows-using-Windows-Subsystem-for-Linux-on-3Engines-Cloud-3Engines-Hosting.html.md). +: Run **.sh** files and install connectVMClient from a Ubuntu window under Windows. [How to install connectVMClient on Windows using Windows Subsystem for Linux on connectVM Cloud connectVM Hosting](../connectVMcli/How-to-install-connectVMClient-on-Windows-using-Windows-Subsystem-for-Linux-on-connectVM-Cloud-connectVM-Hosting.html.md). -Install 3EnginesClient on Linux -: [How to install 3EnginesClient for Linux on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md). +Install connectVMClient on Linux +: [How to install connectVMClient for Linux on connectVM Cloud](../connectVMcli/How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md). How to download the RC file[🔗](#how-to-download-the-rc-file "Permalink to this headline") ----------------------------------------------------------------------------------------- @@ -70,24 +70,24 @@ Top right corner of the Horizon screen contains the account name. Depending on t **Click on API Access** -Navigate to **API Access** -> **Download 3Engines RC File**. Depending on the cloud you are using, you will see a menu like this: +Navigate to **API Access** -> **Download connectVM RC File**. Depending on the cloud you are using, you will see a menu like this: | | | --- | | **WAW3-1, WAW3-2, FRA1-1** | | ../_images/download_rc_file_2fa.png | -Option **3Engines clouds.yaml File** is out of scope of this article. +Option **connectVM clouds.yaml File** is out of scope of this article. -### Which 3Engines RC file to download[🔗](#which-3Engines-rc-file-to-download "Permalink to this headline") +### Which connectVM RC file to download[🔗](#which-connectVM-rc-file-to-download "Permalink to this headline") Choose the appropriate option, depending on the type of account: 2FA *not* active on the account -: For clouds **WAW3-1, WAW3-2, FRA1-1**, select option **3Engines RC File**. +: For clouds **WAW3-1, WAW3-2, FRA1-1**, select option **connectVM RC File**. 2FA active on the account -: Download file **3Engines RC File (2FA)**. +: Download file **connectVM RC File (2FA)**. You only need one copy of the RC file at any time. If you downloaded more than one copy of the file to the same folder without moving or renaming them, your operating system may differentiate amongst the downloaded files by adding additional characters at the end of the file name. @@ -99,7 +99,7 @@ By way of example, let the downloaded RC file name be **cloud\_00734\_1-openrc-2 The contents of the downloaded RC file[🔗](#the-contents-of-the-downloaded-rc-file "Permalink to this headline") --------------------------------------------------------------------------------------------------------------- -RC file sets up *environment variables* which are used by the 3Engines CLI client to authenticate to the cloud. By convention, these variables are in upper case and start with **OS\_**: **OS\_TENANT\_ID**, **OS\_PROJECT\_NAME** etc. For example, in case of one-factor authentication, the RC file will ask for password and store it into a variable called **OS\_PASSWORD**. +RC file sets up *environment variables* which are used by the connectVM CLI client to authenticate to the cloud. By convention, these variables are in upper case and start with **OS\_**: **OS\_TENANT\_ID**, **OS\_PROJECT\_NAME** etc. For example, in case of one-factor authentication, the RC file will ask for password and store it into a variable called **OS\_PASSWORD**. Below is an example content of an RC file which does not use 2FA: @@ -175,15 +175,15 @@ Duration of life for environment variables set by sourcing the RC file[🔗](#du When you source the file, environment variables are set for your current shell. To prove it, open two terminal windows, source the RC file in one of them but not in the other and you won’t be able to authenticate from that second terminal window. -That is why you will need to activate your RC file each time you start a new terminal session. Once authenticated and while that terminal window is open, you can use it to issue 3Engines CLI commands at will. +That is why you will need to activate your RC file each time you start a new terminal session. Once authenticated and while that terminal window is open, you can use it to issue connectVM CLI commands at will. Testing the connection[🔗](#testing-the-connection "Permalink to this headline") ------------------------------------------------------------------------------- -If not already, install 3Engines client using one of the links in Prerequisite No 3. To verify access, execute the following command which lists flavors available in 3Engines Cloud cloud: +If not already, install connectVM client using one of the links in Prerequisite No 3. To verify access, execute the following command which lists flavors available in connectVM Cloud cloud: ``` -3Engines flavor list +connectVM flavor list ``` @@ -221,7 +221,7 @@ If that is the case, simply activate the RC file again as previously and type th ### 2FA accounts: lost Internet connection[🔗](#fa-accounts-lost-internet-connection "Permalink to this headline") -Activating a 2FA RC file requires access to 3Engines Cloud account service because it involves not only setting variables, but also obtaining an appropriate token. +Activating a 2FA RC file requires access to connectVM Cloud account service because it involves not only setting variables, but also obtaining an appropriate token. If you do not have an Internet connection, you will receive the following output after having entered a six-digit code: @@ -232,11 +232,11 @@ Call to Keycloak failed with code 000 and message It will be followed by an empty line and you will be returned to your command prompt. -To resolve this issue, please connect to the Internet and try to activate the RC file again. If you are certain that you have Internet connection, it could mean that 3Engines Cloud account service is down. If no downtime was announced for it, please contact 3Engines Cloud customer support: [Helpdesk and Support](Help-Desk-And-Support.html.md) +To resolve this issue, please connect to the Internet and try to activate the RC file again. If you are certain that you have Internet connection, it could mean that connectVM Cloud account service is down. If no downtime was announced for it, please contact connectVM Cloud customer support: [Helpdesk and Support](Help-Desk-And-Support.html.md) ### Non-2FA accounts: entering a wrong password[🔗](#non-2fa-accounts-entering-a-wrong-password "Permalink to this headline") -If your account does not have two-factor authentication and you entered a wrong password, you will **not** get an error. However, if you try to execute a command like **3Engines flavor list**, you will get the error similar to this: +If your account does not have two-factor authentication and you entered a wrong password, you will **not** get an error. However, if you try to execute a command like **connectVM flavor list**, you will get the error similar to this: ``` The request you have made requires authentication. (HTTP 401) (Request-ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx) @@ -249,7 +249,7 @@ To resolve, activate your file again and enter the correct password. ### Using the wrong file[🔗](#using-the-wrong-file "Permalink to this headline") -If you have a 2FA authentication enabled for your account but have tried to activate the non-2FA version of the RC file, executing, say, command **3Engines flavor list**, will give you the following error: +If you have a 2FA authentication enabled for your account but have tried to activate the non-2FA version of the RC file, executing, say, command **connectVM flavor list**, will give you the following error: ``` Unrecognized schema in response body. (HTTP 401) @@ -268,12 +268,12 @@ With the appropriate version of RC file activated, you should be able to create > * networks, > * Kubernetes clusters -and, in general, use all 3Engines CLI commands. +and, in general, use all connectVM CLI commands. For example, if you want to create a new virtual machine, you can follow this article: -[How to create a VM using the 3Engines CLI client on 3Engines Cloud cloud](../cloud/How-to-create-a-VM-using-the-3Engines-CLI-client-on-3Engines-Cloud-cloud.html.md) +[How to create a VM using the connectVM CLI client on connectVM Cloud cloud](../cloud/How-to-create-a-VM-using-the-connectVM-CLI-client-on-connectVM-Cloud-cloud.html.md) -If you want your new virtual machine to be based on an image which is not available on 3Engines Cloud cloud, you will need to upload it. The following article contains instructions how to do it: +If you want your new virtual machine to be based on an image which is not available on connectVM Cloud cloud, you will need to upload it. The following article contains instructions how to do it: -[How to upload your custom image using 3Engines CLI on 3Engines Cloud](../cloud/How-to-upload-your-custom-image-using-3Engines-CLI-on-3Engines-Cloud.html.md) \ No newline at end of file +[How to upload your custom image using connectVM CLI on connectVM Cloud](../cloud/How-to-upload-your-custom-image-using-connectVM-CLI-on-connectVM-Cloud.html.md) \ No newline at end of file diff --git a/docs/accountmanagement/How-to-buy-credits-using-pay-per-use-wallet-on-3Engines-Cloud.html.md b/docs/accountmanagement/How-to-buy-credits-using-pay-per-use-wallet-on-connectVM-Cloud.html.md similarity index 75% rename from docs/accountmanagement/How-to-buy-credits-using-pay-per-use-wallet-on-3Engines-Cloud.html.md rename to docs/accountmanagement/How-to-buy-credits-using-pay-per-use-wallet-on-connectVM-Cloud.html.md index 71cd25b..ce9f3c0 100644 --- a/docs/accountmanagement/How-to-buy-credits-using-pay-per-use-wallet-on-3Engines-Cloud.html.md +++ b/docs/accountmanagement/How-to-buy-credits-using-pay-per-use-wallet-on-connectVM-Cloud.html.md @@ -2,10 +2,10 @@ search: false --- -How to buy credits using Pay Per Use wallet on 3Engines Cloud[🔗](#how-to-buy-credits-using-pay-per-use-wallet-on-brand-name "Permalink to this headline") +How to buy credits using Pay Per Use wallet on connectVM Cloud[🔗](#how-to-buy-credits-using-pay-per-use-wallet-on-brand-name "Permalink to this headline") =========================================================================================================================================================== -In this article you will learn how to use PPU (Pay Per Use) wallet in order to cover expenses of your account at 3Engines Cloud. +In this article you will learn how to use PPU (Pay Per Use) wallet in order to cover expenses of your account at connectVM Cloud. What Are We Going To Cover[🔗](#what-are-we-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -21,7 +21,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Have payment details ready** @@ -33,7 +33,7 @@ You are going to pay with the data you enter for the organization. Be sure that No. 3 **Useful articles** -As explained in [Wallets and Contracts Management](Contracts-Wallets.html.md), there are **three ways of paying for the services** on 3Engines Cloud platform: +As explained in [Wallets and Contracts Management](Contracts-Wallets.html.md), there are **three ways of paying for the services** on connectVM Cloud platform: PPUSE (Pay Per Use Wallet) : Billing according to the usage. @@ -51,33 +51,33 @@ Step 1 Check for the correct tax ID or VAT number[🔗](#step-1-check-for-the-co Field **Company tax ID / VAT number** must be filled in with correct data. -![3Engines_cloud_1.png](../_images/3Engines_cloud_1.png) +![connectVM_cloud_1.png](../_images/connectVM_cloud_1.png) -You can check it by going to: +You can check it by going to: Without it, you won’t be able to make an order. An error like this one will appear: -![3Engines_cloud_11.png](../_images/3Engines_cloud_11.png) +![connectVM_cloud_11.png](../_images/connectVM_cloud_11.png) Step 2 Select PPU as your way of payment[🔗](#step-2-select-ppu-as-your-way-of-payment "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------- -On this link, you choose the actual contract type: +On this link, you choose the actual contract type: -![3Engines_cloud_2.png](../_images/3Engines_cloud_2.png) +![connectVM_cloud_2.png](../_images/connectVM_cloud_2.png) Click on **Buy now** (assuming you will choose Pay Per Use), otherwise, click on **Choose Fixed term** to opt for **Fixed term payments**. Step 3 Define how many credits for PPU service[🔗](#step-3-define-how-many-credits-for-ppu-service "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------------------- -Either by clicking button **Buy now** or by visiting the following link directly: , you will start the process of paying for PPU. +Either by clicking button **Buy now** or by visiting the following link directly: , you will start the process of paying for PPU. -![3Engines_cloud_3.png](../_images/3Engines_cloud_3.png) +![connectVM_cloud_3.png](../_images/connectVM_cloud_3.png) Let’s say that you want to buy for 250 units, where each unit costs 1 Euro. -![3Engines_cloud_5.png](../_images/3Engines_cloud_5.png) +![connectVM_cloud_5.png](../_images/connectVM_cloud_5.png) If you have only one wallet, the **default wallet** will be automatically offered. If you, however, have several wallets, choose the proper one for this order. @@ -86,7 +86,7 @@ Step 4 Choose payment method[🔗](#step-4-choose-payment-method "Permalink to t Check whether the information about your organization is correct and proceed to payment. -![3Engines_cloud_6.png](../_images/3Engines_cloud_6.png) +![connectVM_cloud_6.png](../_images/connectVM_cloud_6.png) There are two different ways of payment: @@ -102,22 +102,22 @@ You will see a summary with a new invoice on the bottom of the page. If you chose direct bank transfer, scroll down to the payment section and click Pay: -![3Engines_cloud_7.png](../_images/3Engines_cloud_7.png) +![connectVM_cloud_7.png](../_images/connectVM_cloud_7.png) Step 5 Check payment reports[🔗](#step-5-check-payment-reports "Permalink to this headline") ------------------------------------------------------------------------------------------- Check whether the invoice amount matches the actual balance. The invoice in the upper right corner next to the eye icon marked with red line. -![3Engines_cloud_9.png](../_images/3Engines_cloud_9.png) +![connectVM_cloud_9.png](../_images/connectVM_cloud_9.png) -Check on status of the invoice by going to this link: +Check on status of the invoice by going to this link: -![3Engines_cloud_8.png](../_images/3Engines_cloud_8.png) +![connectVM_cloud_8.png](../_images/connectVM_cloud_8.png) -Check your wallet as well: +Check your wallet as well: -![3Engines_cloud_10.png](../_images/3Engines_cloud_10.png) +![connectVM_cloud_10.png](../_images/connectVM_cloud_10.png) What To Do Next[🔗](#what-to-do-next "Permalink to this headline") ----------------------------------------------------------------- @@ -125,7 +125,7 @@ What To Do Next[🔗](#what-to-do-next "Permalink to this headline") There are two ways of reaching to us in case of any problems: Dashboard ticket -: From the browser, use link or click on option **Support** –> **Tickets** in the Dashboard. +: From the browser, use link or click on option **Support** –> **Tickets** in the Dashboard. -Standard 3Engines Cloud support -: The link is \ No newline at end of file +Standard connectVM Cloud support +: The link is \ No newline at end of file diff --git a/docs/accountmanagement/How-to-manage-TOTP-authentication-on-3Engines-Cloud.html.md b/docs/accountmanagement/How-to-manage-TOTP-authentication-on-connectVM-Cloud.html.md similarity index 65% rename from docs/accountmanagement/How-to-manage-TOTP-authentication-on-3Engines-Cloud.html.md rename to docs/accountmanagement/How-to-manage-TOTP-authentication-on-connectVM-Cloud.html.md index 20044b8..8c0c5dd 100644 --- a/docs/accountmanagement/How-to-manage-TOTP-authentication-on-3Engines-Cloud.html.md +++ b/docs/accountmanagement/How-to-manage-TOTP-authentication-on-connectVM-Cloud.html.md @@ -2,10 +2,10 @@ search: false --- -How to manage TOTP authentication on 3Engines Cloud[🔗](#how-to-manage-totp-authentication-on-brand-name "Permalink to this headline") +How to manage TOTP authentication on connectVM Cloud[🔗](#how-to-manage-totp-authentication-on-brand-name "Permalink to this headline") ======================================================================================================================================= -In order to use your 3Engines Cloud account, you need to set a password, and an additional factor of authentication. For the latter, the TOTP algorithm is being used. In this article you will learn how to manage your TOTP configuration. +In order to use your connectVM Cloud account, you need to set a password, and an additional factor of authentication. For the latter, the TOTP algorithm is being used. In this article you will learn how to manage your TOTP configuration. What Are We Going To Cover[🔗](#what-are-we-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -21,7 +21,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud account: +You need a connectVM Cloud account: No. 2 **2FA set on your account** diff --git a/docs/accountmanagement/How-to-start-using-dashboard-services-on-3Engines-Cloud.html.md b/docs/accountmanagement/How-to-start-using-dashboard-services-on-connectVM-Cloud.html.md similarity index 56% rename from docs/accountmanagement/How-to-start-using-dashboard-services-on-3Engines-Cloud.html.md rename to docs/accountmanagement/How-to-start-using-dashboard-services-on-connectVM-Cloud.html.md index 21efb18..eae774c 100644 --- a/docs/accountmanagement/How-to-start-using-dashboard-services-on-3Engines-Cloud.html.md +++ b/docs/accountmanagement/How-to-start-using-dashboard-services-on-connectVM-Cloud.html.md @@ -2,12 +2,12 @@ search: false --- -How to start using dashboard services on 3Engines Cloud[🔗](#how-to-start-using-dashboard-services-on-brand-name "Permalink to this headline") +How to start using dashboard services on connectVM Cloud[🔗](#how-to-start-using-dashboard-services-on-brand-name "Permalink to this headline") =============================================================================================================================================== -When you try to use 3Engines Cloud dashboard at , you will see an advice on the order of operations to start using the dashboard properly. +When you try to use connectVM Cloud dashboard at , you will see an advice on the order of operations to start using the dashboard properly. -![dashboard-services-2-3Engines-cloud.png](../_images/dashboard-services-2-3Engines-cloud.png) +![dashboard-services-2-connectVM-cloud.png](../_images/dashboard-services-2-connectVM-cloud.png) Step 1 Set up the organization[🔗](#step-1-set-up-the-organization "Permalink to this headline") ----------------------------------------------------------------------------------------------- @@ -16,27 +16,27 @@ Step 1 Set up the organization[🔗](#step-1-set-up-the-organization "Permalink The option to use is **Configuration** -> **Organization**. -![dashboard-services-4-3Engines-cloud.png](../_images/dashboard-services-4-3Engines-cloud.png) +![dashboard-services-4-connectVM-cloud.png](../_images/dashboard-services-4-connectVM-cloud.png) See article [Adding and editing Organization](Adding-Editing-Organizations.html.md). Step 2 Enable payment options[🔗](#step-2-enable-payment-options "Permalink to this headline") --------------------------------------------------------------------------------------------- -Go to the [eCommerce site](https://ecommerce.3Engines.com/) and top up your wallet with the required funds. +Go to the [eCommerce site](https://ecommerce.connectVM.com/) and top up your wallet with the required funds. -![dashboard-services-3-3Engines-cloud.png](../_images/dashboard-services-3-3Engines-cloud.png) +![dashboard-services-3-connectVM-cloud.png](../_images/dashboard-services-3-connectVM-cloud.png) -See article [How to buy credits using Pay Per Use wallet on 3Engines Cloud](How-to-buy-credits-using-pay-per-use-wallet-on-3Engines-Cloud.html.md). +See article [How to buy credits using Pay Per Use wallet on connectVM Cloud](How-to-buy-credits-using-pay-per-use-wallet-on-connectVM-Cloud.html.md). Step 3 Activate the project[🔗](#step-3-activate-the-project "Permalink to this headline") ----------------------------------------------------------------------------------------- Go to “Cloud projects” and activate the project in the cloud/region you are interested in. The options to choose are **Billing and Reporting** -> **Cloud projects/Wallets**. -![dashboard-services-5-3Engines-cloud.png](../_images/dashboard-services-5-3Engines-cloud.png) +![dashboard-services-5-connectVM-cloud.png](../_images/dashboard-services-5-connectVM-cloud.png) -At the moment of this writing, there were four different regions to choose from: WAW3-1, WAW3-2, WAW4-1, FRA1-2. These regions are actually clouds running under 3Engines and in each you can have your own virtual machines, access to EO data, create Kubernetes clusters and so on. Although all clouds are running under 3Engines, there are differences in available software, hardware, resources and so on, so it pays to learn which cloud is best for you. +At the moment of this writing, there were four different regions to choose from: WAW3-1, WAW3-2, WAW4-1, FRA1-2. These regions are actually clouds running under connectVM and in each you can have your own virtual machines, access to EO data, create Kubernetes clusters and so on. Although all clouds are running under connectVM, there are differences in available software, hardware, resources and so on, so it pays to learn which cloud is best for you. You may want to work with all these clouds at the same time, maybe with different groups of people working on different projects and so on. @@ -47,16 +47,16 @@ Step 4 Start using the chosen cloud in Horizon[🔗](#step-4-start-using-the-cho To start using the services, choose proper **Cloud Panel** from the **Management Interfaces**. -![dashboard-services-6-3Engines-cloud.png](../_images/dashboard-services-6-3Engines-cloud.png) +![dashboard-services-6-connectVM-cloud.png](../_images/dashboard-services-6-connectVM-cloud.png) -It will lead you to page : +It will lead you to page : -![dashboard-services-7-3Engines-cloud.png](../_images/dashboard-services-7-3Engines-cloud.png) +![dashboard-services-7-connectVM-cloud.png](../_images/dashboard-services-7-connectVM-cloud.png) Let’s say we want to work with cloud WAW3-1. -![dashboard-services-10-3Engines-cloud.png](../_images/dashboard-services-10-3Engines-cloud.png) +![dashboard-services-10-connectVM-cloud.png](../_images/dashboard-services-10-connectVM-cloud.png) Click on **Sign In** and the Horizon will show up. Horizon will remember which project and cloud were active previously and will return to them automatically. If you want to work with another cloud, select it manually. -![dashboard-services-9-3Engines-cloud.png](../_images/dashboard-services-9-3Engines-cloud.png) \ No newline at end of file +![dashboard-services-9-connectVM-cloud.png](../_images/dashboard-services-9-connectVM-cloud.png) \ No newline at end of file diff --git a/docs/accountmanagement/Inviting-New-User.html.md b/docs/accountmanagement/Inviting-New-User.html.md index 0d4a1dc..3f9f54e 100644 --- a/docs/accountmanagement/Inviting-New-User.html.md +++ b/docs/accountmanagement/Inviting-New-User.html.md @@ -11,9 +11,9 @@ One user can only be assigned to one organization at a time. To invite a new user to your organization you need to share an **invitation code**. -After logging into press **Invitations** button on the left bar menu. +After logging into press **Invitations** button on the left bar menu. -![inv_01_3Enginescloud.png](../_images/inv_01_3Enginescloud.png) +![inv_01_connectVMcloud.png](../_images/inv_01_connectVMcloud.png) Now you can copy an invitation code by clicking on **Copy to clipboard** button and send it to a new user by email. @@ -26,6 +26,6 @@ As an organization admin, you need to accept the invitation first. Go to the **Invitations** tab and choose an invitation that you want to accept or – in other case – reject. -![inv_02_3Enginescloud.png](../_images/inv_02_3Enginescloud.png) +![inv_02_connectVMcloud.png](../_images/inv_02_connectVMcloud.png) -After accepting the invitation you will be able to add/edit roles. For more details please check [Tenant manager users and roles on 3Engines Cloud](Tenant-Manager-Users-And-Roles-On-3Engines-Cloud.html.md). \ No newline at end of file +After accepting the invitation you will be able to add/edit roles. For more details please check [Tenant manager users and roles on connectVM Cloud](Tenant-Manager-Users-And-Roles-On-connectVM-Cloud.html.md). \ No newline at end of file diff --git a/docs/accountmanagement/Privacy-Policy.html.md b/docs/accountmanagement/Privacy-Policy.html.md index 6e6b1cb..b05c7a0 100644 --- a/docs/accountmanagement/Privacy-Policy.html.md +++ b/docs/accountmanagement/Privacy-Policy.html.md @@ -5,4 +5,4 @@ search: false Privacy policy for clients[🔗](#privacy-policy-for-clients "Permalink to this headline") ======================================================================================= -If you are not redirected, [click here](https://3Engines.com/3Engines-privacy-policy-for-clients/). \ No newline at end of file +If you are not redirected, [click here](https://connectVM.com/connectVM-privacy-policy-for-clients/). \ No newline at end of file diff --git a/docs/accountmanagement/Registration-And-Account.html.md b/docs/accountmanagement/Registration-And-Account.html.md index 5cec7e7..b604fcb 100644 --- a/docs/accountmanagement/Registration-And-Account.html.md +++ b/docs/accountmanagement/Registration-And-Account.html.md @@ -5,21 +5,21 @@ search: false Registration and Setting up an Account[🔗](#registration-and-setting-up-an-account "Permalink to this headline") =============================================================================================================== -Go to the site and press **CREATE ACCOUNT** button. +Go to the site and press **CREATE ACCOUNT** button. -![register_3Enginescloud.png](../_images/register_3Enginescloud.png) +![register_connectVMcloud.png](../_images/register_connectVMcloud.png) Fill up all fields marked with **\*** including accepting mandatory terms and conditions and press **Create Account** button. Please note that marketing consents are not mandatory and can be changed at any time. -![create_account_3Enginescloud.png](../_images/create_account_3Enginescloud.png) +![create_account_connectVMcloud.png](../_images/create_account_connectVMcloud.png) Once you create account below screen will appear. Please check your mail box and verify mail. After that you will be able to log in. -![registration_successful_3Enginescloud.png](../_images/registration_successful_3Enginescloud.png) +![registration_successful_connectVMcloud.png](../_images/registration_successful_connectVMcloud.png) -For general information about types of account and user roles you may have in Dashboard, see [Tenant manager users and roles on 3Engines Cloud](Tenant-Manager-Users-And-Roles-On-3Engines-Cloud.html.md) +For general information about types of account and user roles you may have in Dashboard, see [Tenant manager users and roles on connectVM Cloud](Tenant-Manager-Users-And-Roles-On-connectVM-Cloud.html.md) After creating personal account you can either create new company account or join an existing account. See articles: @@ -29,4 +29,4 @@ After creating personal account you can either create new company account or joi If you are a single user you can only access a limited number of services. -See article [How to start using dashboard services on 3Engines Cloud](How-to-start-using-dashboard-services-on-3Engines-Cloud.html.md) \ No newline at end of file +See article [How to start using dashboard services on connectVM Cloud](How-to-start-using-dashboard-services-on-connectVM-Cloud.html.md) \ No newline at end of file diff --git a/docs/accountmanagement/Removing-User-From-Organization.html.md b/docs/accountmanagement/Removing-User-From-Organization.html.md index 1091a87..8fbbd51 100644 --- a/docs/accountmanagement/Removing-User-From-Organization.html.md +++ b/docs/accountmanagement/Removing-User-From-Organization.html.md @@ -5,9 +5,9 @@ search: false Removing user from Organization[🔗](#removing-user-from-organization "Permalink to this headline") ================================================================================================= -After logging into press **Sub-accounts** button on the left bar menu to check the list of members of your Organization. +After logging into press **Sub-accounts** button on the left bar menu to check the list of members of your Organization. -![users_roles_01_3Enginescloud.png](../_images/users_roles_01_3Enginescloud.png) +![users_roles_01_connectVMcloud.png](../_images/users_roles_01_connectVMcloud.png) Select user that you want to be removed and press **Unassign** button on the right side and after that press **Confirm** button. diff --git a/docs/accountmanagement/Services.html.md b/docs/accountmanagement/Services.html.md index da1bdd0..5672c46 100644 --- a/docs/accountmanagement/Services.html.md +++ b/docs/accountmanagement/Services.html.md @@ -5,9 +5,9 @@ search: false Services[🔗](#services "Permalink to this headline") =================================================== -After logging into press **Active services** button on the left bar menu. +After logging into press **Active services** button on the left bar menu. -![services_3Enginescloud.png](../_images/services_3Enginescloud.png) +![services_connectVMcloud.png](../_images/services_connectVMcloud.png) In this tab you are able to filter your services by Project or by Product. @@ -20,6 +20,6 @@ How to change assigned contract[🔗](#how-to-change-assigned-contract "Permalin **PAY AS YOU GO** - user can assign wallet to specific project in the **Accounts** tab -**FIXED TERM** - is assigned by 3Engines Support Team during the contract creation +**FIXED TERM** - is assigned by connectVM Support Team during the contract creation Please note that **PPU/PAYG** assignment status is visible in the **Accounts** tab. \ No newline at end of file diff --git a/docs/accountmanagement/Tenant-Manager-Users-And-Roles-On-3Engines-Cloud.html.md b/docs/accountmanagement/Tenant-Manager-Users-And-Roles-On-connectVM-Cloud.html.md similarity index 56% rename from docs/accountmanagement/Tenant-Manager-Users-And-Roles-On-3Engines-Cloud.html.md rename to docs/accountmanagement/Tenant-Manager-Users-And-Roles-On-connectVM-Cloud.html.md index d1ce807..0b73dd2 100644 --- a/docs/accountmanagement/Tenant-Manager-Users-And-Roles-On-3Engines-Cloud.html.md +++ b/docs/accountmanagement/Tenant-Manager-Users-And-Roles-On-connectVM-Cloud.html.md @@ -2,29 +2,29 @@ search: false --- -Tenant manager users and roles on 3Engines Cloud[](#tenant-manager-users-and-roles-on-3Engines-cloud "Permalink to this headline")enant manager users and roles on 3Engines Cloud[🔗](#tenant-manager-users-and-roles-on-brand-name "Permalink to this headline") +Tenant manager users and roles on connectVM Cloud[](#tenant-manager-users-and-roles-on-connectVM-cloud "Permalink to this headline")enant manager users and roles on connectVM Cloud[🔗](#tenant-manager-users-and-roles-on-brand-name "Permalink to this headline") ================================================================================================================================= -Differences between 3Engines User Roles and Tenant Manager’s Roles[🔗](#differences-between-3Engines-user-roles-and-tenant-manager-s-roles "Permalink to this headline") +Differences between connectVM User Roles and Tenant Manager’s Roles[🔗](#differences-between-connectVM-user-roles-and-tenant-manager-s-roles "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -An 3Engines role is a personality that a user assumes to perform a specific set of operations. A role includes a set of rights and privileges. A user assuming that role inherits those rights and privileges. 3Engines roles are defined for each user and each project independently. +An connectVM role is a personality that a user assumes to perform a specific set of operations. A role includes a set of rights and privileges. A user assuming that role inherits those rights and privileges. connectVM roles are defined for each user and each project independently. -A Tenant Manager role, on the other hand, defines whether a user should have the ability to manage an organization via the Tenant Manager or have access to 3Engines. +A Tenant Manager role, on the other hand, defines whether a user should have the ability to manage an organization via the Tenant Manager or have access to connectVM. What Are We Going To Cover[🔗](#what-are-we-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- > * The difference between User Roles and Tenant Manager Role > * List three basic roles an organization administrator you can assign -> * Show how to add a **member+** role, which can have access to 3Engines and be used for managing projects +> * Show how to add a **member+** role, which can have access to connectVM and be used for managing projects Users and Roles in the Tenant Manager[🔗](#users-and-roles-in-the-tenant-manager "Permalink to this headline") ------------------------------------------------------------------------------------------------------------- -After logging into click on the **Sub-accounts** button on the left bar menu. +After logging into click on the **Sub-accounts** button on the left bar menu. -![Tenant_manager_01_3Engines.png](../_images/Tenant_manager_01_3Engines.png) +![Tenant_manager_01_connectVM.png](../_images/Tenant_manager_01_connectVM.png) Here you are able to: @@ -33,38 +33,38 @@ Here you are able to: As an *organization administrator* you can assign one of the following roles to a user: -> * **admin** - user with highest privileges, can manage whole organizations and has access to 3Engines. +> * **admin** - user with highest privileges, can manage whole organizations and has access to connectVM. > * **member** - default user with basic privileges. -> * **member+** - the same as **member** but has 3Engines access and can manage projects. +> * **member+** - the same as **member** but has connectVM access and can manage projects. -Adding member+ user to your project in 3Engines using Horizon interface[🔗](#adding-member-user-to-your-project-in-3Engines-using-horizon-interface "Permalink to this headline") +Adding member+ user to your project in connectVM using Horizon interface[🔗](#adding-member-user-to-your-project-in-connectVM-using-horizon-interface "Permalink to this headline") ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -Users with the role of **member+** have access to 3Engines and can be enabled to manage your organization projects. They cannot however, manage the organization itself. +Users with the role of **member+** have access to connectVM and can be enabled to manage your organization projects. They cannot however, manage the organization itself. To add a **member+** user to the project, follow these steps: **1.** Check if your user has a **member+** role in Tenant Manager. -**2.** Log into as an admin. +**2.** Log into as an admin. **3.** Select **Identity** → **Projects** -![Tenant_manager_02_3Engines.png](../_images/Tenant_manager_02_3Engines.png) +![Tenant_manager_02_connectVM.png](../_images/Tenant_manager_02_connectVM.png) **4.** Select the project you want to add a user to and select **Manage members** -![Tenant_manager_03_3Engines.png](../_images/Tenant_manager_03_3Engines.png) +![Tenant_manager_03_connectVM.png](../_images/Tenant_manager_03_connectVM.png) **5.** Add the desired user(s) to the project by clicking on the “+” button next to them. -![Tenant_manager_04_3Engines.png](../_images/Tenant_manager_04_3Engines.png) +![Tenant_manager_04_connectVM.png](../_images/Tenant_manager_04_connectVM.png) **6.** Choose a suitable project role for the user and confirm by clicking **Save** in the lower-right corner. -![Tenant_manager_05_3Engines.png](../_images/Tenant_manager_05_3Engines.png) +![Tenant_manager_05_connectVM.png](../_images/Tenant_manager_05_connectVM.png) -**7.** Next time the user will log into 3Engines Horizon, the suitable access to the project will be granted. +**7.** Next time the user will log into connectVM Horizon, the suitable access to the project will be granted. What To Do Next[🔗](#what-to-do-next "Permalink to this headline") ----------------------------------------------------------------- @@ -73,4 +73,4 @@ The article [Inviting new user to your Organization](Inviting-New-User.html.md) To the contrary, article [Removing user from Organization](Removing-User-From-Organization.html.md) shows how to remove a user from the organization. -The article /accountmanagement/Accounts-and-Projects-Management is a general guidance to creating and managing accounts and projects on 3Engines Cloud. \ No newline at end of file +The article /accountmanagement/Accounts-and-Projects-Management is a general guidance to creating and managing accounts and projects on connectVM Cloud. \ No newline at end of file diff --git a/docs/accountmanagement/Two-Factor-Authentication-for-3Engines-Cloud-Site.html.md b/docs/accountmanagement/Two-Factor-Authentication-for-connectVM-Cloud-Site.html.md similarity index 80% rename from docs/accountmanagement/Two-Factor-Authentication-for-3Engines-Cloud-Site.html.md rename to docs/accountmanagement/Two-Factor-Authentication-for-connectVM-Cloud-Site.html.md index b698274..b0751fd 100644 --- a/docs/accountmanagement/Two-Factor-Authentication-for-3Engines-Cloud-Site.html.md +++ b/docs/accountmanagement/Two-Factor-Authentication-for-connectVM-Cloud-Site.html.md @@ -2,12 +2,12 @@ search: false --- -Two-Factor Authentication to 3Engines Cloud site using mobile application[🔗](#two-factor-authentication-to-brand-name-site-using-mobile-application "Permalink to this headline") +Two-Factor Authentication to connectVM Cloud site using mobile application[🔗](#two-factor-authentication-to-brand-name-site-using-mobile-application "Permalink to this headline") =================================================================================================================================================================================== Warning -Two-Factor Authentication is required for all 3Engines Cloud users. The only exception are accounts which log in using Keystone credentials. +Two-Factor Authentication is required for all connectVM Cloud users. The only exception are accounts which log in using Keystone credentials. Traditionally, the most basic way to implement security online was to authenticate users and companies with a pair of usernames/passwords. Most usernames are email addresses and if email address is breached, the bad actor can probably learn your password too. What once used to be secure enough is not secure now because of easy access to refined brute force methods, availability of computing power at scale, social engineering methods, identity theft and so on. @@ -17,12 +17,12 @@ The way to overcome this limitation is to introduce two or more factors or types > * something the user has (token generator, smartphone, credit card etc.) or > * biometric information such as fingerprint, iris, retina, voice, face and so on. -Logging into the 3Engines Cloud site uses two-factor authentication, meaning you will have to supply two independent types of data: +Logging into the connectVM Cloud site uses two-factor authentication, meaning you will have to supply two independent types of data: > * the “classical” username and password, as well as > * the numeric code supplied by a concrete mobile app. -This article is about using mobile devices to authenticate to the cloud. If you want to use your computer to do that, see [Two-Factor Authentication to 3Engines Cloud site using KeePassXC on desktop](Using-KeePassXC-for-Two-Factor-Authentication-on-3Engines-Cloud.html.md). +This article is about using mobile devices to authenticate to the cloud. If you want to use your computer to do that, see [Two-Factor Authentication to connectVM Cloud site using KeePassXC on desktop](Using-KeePassXC-for-Two-Factor-Authentication-on-connectVM-Cloud.html.md). You will first have to install one of the following two mobile applications, for Android or iOS mobile operating systems: @@ -46,14 +46,14 @@ In this tutorial, you are going to use the FreeOTP app. Warning -If you lose access to QR codes and cannot log into the Horizon site for 3Engines Cloud, ask Support service to help you by sending email to the following address [support@3Engines.com](/cdn-cgi/l/email-protection#80f3f5f0f0eff2f4a6a3b3b7bba6a3b5b2bba6a3b4b8bbe3eceff5e4e6e5f2f2efa6a3b4b6bbe3efed). +If you lose access to QR codes and cannot log into the Horizon site for connectVM Cloud, ask Support service to help you by sending email to the following address [support@connectVM.com](/cdn-cgi/l/email-protection#80f3f5f0f0eff2f4a6a3b3b7bba6a3b5b2bba6a3b4b8bbe3eceff5e4e6e5f2f2efa6a3b4b6bbe3efed). What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- > * How to start using the mobile authenticator > * How to locate, download and install FreeOTP app on your mobile device -> * How to set up FreeOTP app and connect it to your 3Engines Cloud account +> * How to set up FreeOTP app and connect it to your connectVM Cloud account > * How to get new code each time you want to enter the site Prerequisites[🔗](#prerequisites "Permalink to this headline") @@ -79,9 +79,9 @@ Download [Google Authenticator in iOS App Store using this link](https://apps.ap Warning -You should install the authenticator app **before** trying to log into the 3Engines Cloud site. +You should install the authenticator app **before** trying to log into the connectVM Cloud site. -You are now going to download, install and use the FreeOTP app to authenticate to 3Engines Cloud site. +You are now going to download, install and use the FreeOTP app to authenticate to connectVM Cloud site. Step 1 Download and Install FreeOTP from the App Store[🔗](#step-1-download-and-install-freeotp-from-the-app-store "Permalink to this headline") ----------------------------------------------------------------------------------------------------------------------------------------------- @@ -104,16 +104,16 @@ Once installed, type on **Open** and the app will run. At first, there will be n Note -FreeOTP can also use tokens to secure access to the remote site. The 3Engines Cloud site uses QR code, so that is what you will use in this tutorial. (Both “token” and “QR scan” denote a secure connection to the site, but use different techniques in the process.) +FreeOTP can also use tokens to secure access to the remote site. The connectVM Cloud site uses QR code, so that is what you will use in this tutorial. (Both “token” and “QR scan” denote a secure connection to the site, but use different techniques in the process.) Step 2 Scan QR and Create Brand[🔗](#step-2-scan-qr-and-create-brand "Permalink to this headline") ------------------------------------------------------------------------------------------------- -Select a brand, which means select an icon that will make your tokens stand out graphically. If you will employ this app only to get access to 3Engines Cloud, you may select whichever icon you want. +Select a brand, which means select an icon that will make your tokens stand out graphically. If you will employ this app only to get access to connectVM Cloud, you may select whichever icon you want. [![otp05.png](../_images/otp05.png)](../_images/otp05.png) -In the next step, you may require that the phone is unlocked when the token is to be activated. Choose that if you are afraid someone might steal your phone and get access to your 3Engines Cloud data that way. +In the next step, you may require that the phone is unlocked when the token is to be activated. Choose that if you are afraid someone might steal your phone and get access to your connectVM Cloud data that way. [![otp07.png](../_images/otp07.png)](../_images/otp07.png) @@ -129,7 +129,7 @@ Click on it to get to the scanner part of the application and read the QR code f Note -The QR code will appear on screen when you first try to log into the 3Engines Cloud site (see below). +The QR code will appear on screen when you first try to log into the connectVM Cloud site (see below). [![eefa_qr_screen_creodias.png](../_images/eefa_qr_screen_creodias.png)](../_images/eefa_qr_screen_creodias.png) @@ -144,16 +144,16 @@ If you created several tokens or repeatedly scanned QR code from the screen, you [![eefa_several_rows.png](../_images/eefa_several_rows.png)](../_images/eefa_several_rows.png) -Tapping on any of these will produce the six-digit code that you have to type into the entry form to get logged in. Only one of these will be the right one, in this case, the first row produces the correct six-digits code for 3Engines Cloud site. +Tapping on any of these will produce the six-digit code that you have to type into the entry form to get logged in. Only one of these will be the right one, in this case, the first row produces the correct six-digits code for connectVM Cloud site. [![eefa_tapped.png](../_images/eefa_tapped.png)](../_images/eefa_tapped.png) -You are now ready to log into the 3Engines Cloud site using the two-factor authentication. +You are now ready to log into the connectVM Cloud site using the two-factor authentication. How to Start Using the Mobile Authenticator With Your Account[🔗](#how-to-start-using-the-mobile-authenticator-with-your-account "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------------------------------------------------- -Use the usual link to log into your 3Engines Cloud account and choose 3Engines Cloud in the input menu. +Use the usual link to log into your connectVM Cloud account and choose connectVM Cloud in the input menu. [![eefa_start_creodias.png](../_images/eefa_start_creodias.png)](../_images/eefa_start_creodias.png) @@ -180,7 +180,7 @@ Logging Into the Site Once the Two-Factor Authentication is Installed[🔗](#log Here is the workflow in one place, with all of the screens repeated for easy reference. -Use the usual link to log into your 3Engines Cloud account and choose 3Engines Cloud in the input menu. +Use the usual link to log into your connectVM Cloud account and choose connectVM Cloud in the input menu. [![eefa_start_creodias.png](../_images/eefa_start_creodias.png)](../_images/eefa_start_creodias.png) @@ -206,8 +206,8 @@ If the FreeOTP app is in the foreground on the mobile device while you are submi ### What To Do Next[🔗](#what-to-do-next "Permalink to this headline") -As mentioned in the beginning, you can use your computer for two-factor authentication – see article [Two-Factor Authentication to 3Engines Cloud site using KeePassXC on desktop](Using-KeePassXC-for-Two-Factor-Authentication-on-3Engines-Cloud.html.md). +As mentioned in the beginning, you can use your computer for two-factor authentication – see article [Two-Factor Authentication to connectVM Cloud site using KeePassXC on desktop](Using-KeePassXC-for-Two-Factor-Authentication-on-connectVM-Cloud.html.md). -Either using mobile device or computer to authenticate, you will be logged into Horizon. You will then need to activate access to 3Engines Cloud cloud API functions and be able to run **3Engines** command. Please see article [How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication](How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md). +Either using mobile device or computer to authenticate, you will be logged into Horizon. You will then need to activate access to connectVM Cloud cloud API functions and be able to run **connectVM** command. Please see article [How to activate connectVM CLI access to connectVM Cloud cloud using one- or two-factor authentication](How-to-activate-connectVM-CLI-access-to-connectVM-Cloud-cloud-using-one-or-two-factor-authentication.html.md). -To learn how to manage your TOTP secret key, visit the following article: [How to manage TOTP authentication on 3Engines Cloud](How-to-manage-TOTP-authentication-on-3Engines-Cloud.html.md) - it can be useful if you, for instance, want to use a different method of authentication, are unable to extract your secret key from currently used piece of software such as FreeOTP and do not have your secret key backed up in a readable way. \ No newline at end of file +To learn how to manage your TOTP secret key, visit the following article: [How to manage TOTP authentication on connectVM Cloud](How-to-manage-TOTP-authentication-on-connectVM-Cloud.html.md) - it can be useful if you, for instance, want to use a different method of authentication, are unable to extract your secret key from currently used piece of software such as FreeOTP and do not have your secret key backed up in a readable way. \ No newline at end of file diff --git a/docs/accountmanagement/Using-KeePassXC-for-Two-Factor-Authentication-on-3Engines-Cloud.html.md b/docs/accountmanagement/Using-KeePassXC-for-Two-Factor-Authentication-on-connectVM-Cloud.html.md similarity index 85% rename from docs/accountmanagement/Using-KeePassXC-for-Two-Factor-Authentication-on-3Engines-Cloud.html.md rename to docs/accountmanagement/Using-KeePassXC-for-Two-Factor-Authentication-on-connectVM-Cloud.html.md index 9bd274a..283a3cf 100644 --- a/docs/accountmanagement/Using-KeePassXC-for-Two-Factor-Authentication-on-3Engines-Cloud.html.md +++ b/docs/accountmanagement/Using-KeePassXC-for-Two-Factor-Authentication-on-connectVM-Cloud.html.md @@ -2,10 +2,10 @@ search: false --- -Two-Factor Authentication to 3Engines Cloud site using KeePassXC on desktop[🔗](#two-factor-authentication-to-brand-name-site-using-keepassxc-on-desktop "Permalink to this headline") +Two-Factor Authentication to connectVM Cloud site using KeePassXC on desktop[🔗](#two-factor-authentication-to-brand-name-site-using-keepassxc-on-desktop "Permalink to this headline") ======================================================================================================================================================================================= -Please see article [Two-Factor Authentication to 3Engines Cloud site using mobile application](Two-Factor-Authentication-for-3Engines-Cloud-Site.html.md) if you want to use a smartphone app for the TOTP two-factor authentication. +Please see article [Two-Factor Authentication to connectVM Cloud site using mobile application](Two-Factor-Authentication-for-connectVM-Cloud-Site.html.md) if you want to use a smartphone app for the TOTP two-factor authentication. If you, however, want to use your desktop or laptop computer instead, KeePassXC is probably a good choice for you. It is a free and open source graphical password manager. It stores passwords, TOTP keys and other secrets in a file on your computer. You can later, for example, move that file manually to a different computer to use that device instead of the current one. @@ -22,7 +22,7 @@ The following instructions are for Ubuntu. If you use a different operating syst Step 1 Install KeePassXC[🔗](#step-1-install-keepassxc "Permalink to this headline") ----------------------------------------------------------------------------------- -Install KeePassXC before logging in to the 3Engines Cloud website. Open the terminal, type the following command and press Enter: +Install KeePassXC before logging in to the connectVM Cloud website. Open the terminal, type the following command and press Enter: ``` sudo apt update && sudo apt upgrade -y && sudo apt install -y keepassxc @@ -61,7 +61,7 @@ Choose the name for the file containing your secrets and its location. Click **S Step 3 Add the entry for your account[🔗](#step-3-add-the-entry-for-your-account "Permalink to this headline") ------------------------------------------------------------------------------------------------------------- -Your database should now be operational. Let’s create the entry containing your username, password and TOTP for the 3Engines Cloud cloud. Click **Add a new entry** (the fourth button on the toolbar, marked with the red rectangle on the screenshot below. +Your database should now be operational. Let’s create the entry containing your username, password and TOTP for the connectVM Cloud cloud. Click **Add a new entry** (the fourth button on the toolbar, marked with the red rectangle on the screenshot below. ![keepassxc_05_creodias.png](../_images/keepassxc_05_creodias.png) @@ -69,7 +69,7 @@ The following window will appear: ![keepassxc_06_creodias.png](../_images/keepassxc_06_creodias.png) -In the **Title** field enter the name under which your entry should be identified in your database, for example 3Engines Cloud. Then, type your username and password. +In the **Title** field enter the name under which your entry should be identified in your database, for example connectVM Cloud. Then, type your username and password. Click **OK** to save the entry. @@ -82,7 +82,7 @@ Now we need to obtain your TOTP key. ### Method 1: During account creation[🔗](#method-1-during-account-creation "Permalink to this headline") -After having created an account on but before first login, you will receive the **Mobile Authenticator Setup** prompt, as in the following image: +After having created an account on but before first login, you will receive the **Mobile Authenticator Setup** prompt, as in the following image: ![keepassxc_07_creodias.png](../_images/keepassxc_07_creodias.png) @@ -115,13 +115,13 @@ The window with the code will look like this: ![keepassxc_10_creodias.png](../_images/keepassxc_10_creodias.png) -Type your 6-digit code from the above window to the text field **One-time-code** on the 3Engines Cloud website and choose how you would like to call your device containing the TOTP key. Please make sure that you do it before that key expires. If the key expires, you will get another one and you should type it instead. Click **Submit**. You should now be able to proceed with your login process. +Type your 6-digit code from the above window to the text field **One-time-code** on the connectVM Cloud website and choose how you would like to call your device containing the TOTP key. Please make sure that you do it before that key expires. If the key expires, you will get another one and you should type it instead. Click **Submit**. You should now be able to proceed with your login process. ### Method 2: After another method of TOTP has already been configured[🔗](#method-2-after-another-method-of-totp-has-already-been-configured "Permalink to this headline") If the method of TOTP authentication you are currently using allows you to extract the **secret** key(or you have it backed up somewhere), you should be able to use that same **secret key** which you are currently using for KeePassXC as well. -If no other options remain, contact 3Engines Cloud customer support for assistance. +If no other options remain, contact connectVM Cloud customer support for assistance. Either way, eventually you should get your secret key. Enter it in KeePassXC the same way as explained in **Method 1** above - to the **Key:** text field. If that secret key is already added and configured for your account, no further action should be necessary. If not and you are in the process of configuring it, paste the 6-digit TOTP code from KeePassXC in the same way as you entered the code from your other device during account setup. diff --git a/docs/accountmanagement/accountmanagement.html.md b/docs/accountmanagement/accountmanagement.html.md index 96f4ece..1cf259a 100644 --- a/docs/accountmanagement/accountmanagement.html.md +++ b/docs/accountmanagement/accountmanagement.html.md @@ -6,20 +6,20 @@ ACCOUNT MANAGEMENT[](#account-management "Permalink to this headline") ======================================================================= * [Registration and Setting up an Account](Registration-And-Account.html.md) -* [How to start using dashboard services on 3Engines Cloud](How-to-start-using-dashboard-services-on-3Engines-Cloud.html.md) -* [Two-Factor Authentication to 3Engines Cloud site using mobile application](Two-Factor-Authentication-for-3Engines-Cloud-Site.html.md) -* [Two-Factor Authentication to 3Engines Cloud site using KeePassXC on desktop](Using-KeePassXC-for-Two-Factor-Authentication-on-3Engines-Cloud.html.md) -* [How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication](How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md) -* [How to manage TOTP authentication on 3Engines Cloud](How-to-manage-TOTP-authentication-on-3Engines-Cloud.html.md) +* [How to start using dashboard services on connectVM Cloud](How-to-start-using-dashboard-services-on-connectVM-Cloud.html.md) +* [Two-Factor Authentication to connectVM Cloud site using mobile application](Two-Factor-Authentication-for-connectVM-Cloud-Site.html.md) +* [Two-Factor Authentication to connectVM Cloud site using KeePassXC on desktop](Using-KeePassXC-for-Two-Factor-Authentication-on-connectVM-Cloud.html.md) +* [How to activate connectVM CLI access to connectVM Cloud cloud using one- or two-factor authentication](How-to-activate-connectVM-CLI-access-to-connectVM-Cloud-cloud-using-one-or-two-factor-authentication.html.md) +* [How to manage TOTP authentication on connectVM Cloud](How-to-manage-TOTP-authentication-on-connectVM-Cloud.html.md) * [Adding and editing Organization](Adding-Editing-Organizations.html.md) -* [How to buy credits using Pay Per Use wallet on 3Engines Cloud](How-to-buy-credits-using-pay-per-use-wallet-on-3Engines-Cloud.html.md) +* [How to buy credits using Pay Per Use wallet on connectVM Cloud](How-to-buy-credits-using-pay-per-use-wallet-on-connectVM-Cloud.html.md) * [Forgotten Password](Forgotten-Password.html.md) * [Editing profile](Editing-Profile.html.md) * [Wallets and Contracts Management](Contracts-Wallets.html.md) * [Services](Services.html.md) * [Inviting new user to your Organization](Inviting-New-User.html.md) * [Removing user from Organization](Removing-User-From-Organization.html.md) -* [Tenant manager users and roles on 3Engines Cloud](Tenant-Manager-Users-And-Roles-On-3Engines-Cloud.html.md) +* [Tenant manager users and roles on connectVM Cloud](Tenant-Manager-Users-And-Roles-On-connectVM-Cloud.html.md) * [Helpdesk and Support](Help-Desk-And-Support.html.md) * [Privacy policy for clients](Privacy-Policy.html.md) -* [Cookie consent on 3Engines Cloud](Cookie-consent-on-3Engines-Cloud.html.md) \ No newline at end of file +* [Cookie consent on connectVM Cloud](Cookie-consent-on-connectVM-Cloud.html.md) \ No newline at end of file diff --git a/docs/cloud/Block-storage-and-object-storage-performance-limits-on-3Engines-Cloud.html.md b/docs/cloud/Block-storage-and-object-storage-performance-limits-on-connectVM-Cloud.html.md similarity index 66% rename from docs/cloud/Block-storage-and-object-storage-performance-limits-on-3Engines-Cloud.html.md rename to docs/cloud/Block-storage-and-object-storage-performance-limits-on-connectVM-Cloud.html.md index cb9ff80..87ae84e 100644 --- a/docs/cloud/Block-storage-and-object-storage-performance-limits-on-3Engines-Cloud.html.md +++ b/docs/cloud/Block-storage-and-object-storage-performance-limits-on-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -Block storage and object storage performance limits on 3Engines Cloud[🔗](#block-storage-and-object-storage-performance-limits-on-brand-name "Permalink to this headline") +Block storage and object storage performance limits on connectVM Cloud[🔗](#block-storage-and-object-storage-performance-limits-on-brand-name "Permalink to this headline") =========================================================================================================================================================================== -On 3Engines Cloud, there are performance limits for **HDD**, **NVMe (SSD)**, and **Object Storage** to ensure stable operation and protect against accidental DDoS attacks. +On connectVM Cloud, there are performance limits for **HDD**, **NVMe (SSD)**, and **Object Storage** to ensure stable operation and protect against accidental DDoS attacks. Current limits[🔗](#current-limits "Permalink to this headline") --------------------------------------------------------------- @@ -12,7 +12,7 @@ Block HDD Block SSD/NVMe : **3000** IOPS (read and write) - **NOTE**: On 3Engines Cloud, *all* SSD storage is NVMe-based. + **NOTE**: On connectVM Cloud, *all* SSD storage is NVMe-based. S3 Object Storage (General Tier) : **2000** operations per second with a diff --git a/docs/cloud/DNS-as-a-Service-on-3Engines-Cloud-Hosting.html.md b/docs/cloud/DNS-as-a-Service-on-connectVM-Cloud-Hosting.html.md similarity index 73% rename from docs/cloud/DNS-as-a-Service-on-3Engines-Cloud-Hosting.html.md rename to docs/cloud/DNS-as-a-Service-on-connectVM-Cloud-Hosting.html.md index ff5e6ea..abe8042 100644 --- a/docs/cloud/DNS-as-a-Service-on-3Engines-Cloud-Hosting.html.md +++ b/docs/cloud/DNS-as-a-Service-on-connectVM-Cloud-Hosting.html.md @@ -1,4 +1,4 @@ -DNS as a Service on 3Engines Cloud Hosting[🔗](#dns-as-a-service-on-brand-name-cloud-name-hosting "Permalink to this headline") +DNS as a Service on connectVM Cloud Hosting[🔗](#dns-as-a-service-on-brand-name-cloud-name-hosting "Permalink to this headline") ================================================================================================================================ DNS as a Service (DNSaaS) provides functionality of managing configuration of user’s domains. Managing configuration means that the user is capable of creating, updating and deleting the following DNS records: @@ -16,9 +16,9 @@ DNS as a Service (DNSaaS) provides functionality of managing configuration of us | SSHFP | SSH Public Key Fingerprint | | TXT | Text record | -DNS configuration management is available via 3Engines web dashboard (Horizon), 3Engines command line interface as well as via the API. +DNS configuration management is available via connectVM web dashboard (Horizon), connectVM command line interface as well as via the API. -DNS records management is performed on the level of an 3Engines project. +DNS records management is performed on the level of an connectVM project. Since DNSaaS purpose is to deal with external domain names, the internal name resolution (name resolution for private IP addresses within user’s projects) is not covered by this documentation. @@ -31,16 +31,16 @@ What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this > * Adding new record for the domain > * Adding records for subdomains > * Managing records -> * Limitations in 3Engines DNSaaS +> * Limitations in connectVM DNSaaS Prerequisites[🔗](#prerequisites "Permalink to this headline") ------------------------------------------------------------- No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . -No. 2 **Must have access to a project in 3Engines Cloud 3Engines account** +No. 2 **Must have access to a project in connectVM Cloud connectVM account** If you are a tenant manager, you will be able to either use the existing basic project or create new projects for yourself or your users. @@ -53,7 +53,7 @@ We assume you already have a > * basic knowledge of Domain Name Service principles as well as > * understanding of the purpose of DNS records. -If not, please see [DNS article on Wikipedia](https://en.wikipedia.org/wiki/Domain_Name_System) or [3Engines DNSaaS command line reference](https://docs.3Engines.org/python-designateclient/latest/user/shell-v2.html.md) +If not, please see [DNS article on Wikipedia](https://en.wikipedia.org/wiki/Domain_Name_System) or [connectVM DNSaaS command line reference](https://docs.connectVM.org/python-designateclient/latest/user/shell-v2.html.md) No. 4 **Must have domain purchased from a registrar** @@ -61,31 +61,31 @@ You also must own a domain purchased from any registrar (domain reseller). Obtai No. 5 **Must have a Linux server with an assigned IP address** -To verify DNS creation and propagation, you shall use the **dig** command from Linux. You will also need an IP address to point the domain name to. You may have already created one such VM in your 3Engines Cloud server and if not, here is how to create a virtual machine, assign a floating IP to it and access it from Windows desktop computer: +To verify DNS creation and propagation, you shall use the **dig** command from Linux. You will also need an IP address to point the domain name to. You may have already created one such VM in your connectVM Cloud server and if not, here is how to create a virtual machine, assign a floating IP to it and access it from Windows desktop computer: -[How to create a Linux VM and access it from Windows desktop on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md) +[How to create a Linux VM and access it from Windows desktop on connectVM Cloud](How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-connectVM-Cloud.html.md) Or, you might connect from a Linux based computer to the cloud: -[How to create a Linux VM and access it from Linux command line on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md) +[How to create a Linux VM and access it from Linux command line on connectVM Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md) In both cases, the article will contain a section to connect floating IP to the newly created VM. The generated IP address will vary, but for the sake of concreteness we shall assume that it is **64.225.133.254**. You will enter that value later in this article, to create record set for the site or service you are making. Step 1 Delegate domain to your registrar’s system[🔗](#step-1-delegate-domain-to-your-registrar-s-system "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------------------------- -The configuration of domain name in your registrar’s system must point to the NS records of 3Engines name servers. It can be achieved in two ways: +The configuration of domain name in your registrar’s system must point to the NS records of connectVM name servers. It can be achieved in two ways: -**Option 1 - Use 3Engines name servers (recommended)** +**Option 1 - Use connectVM name servers (recommended)** -Configure NS records for your domain to the following 3Engines name servers: +Configure NS records for your domain to the following connectVM name servers: | | | | | --- | --- | --- | | Purpose | Name Server | IP | -| primary name server | cloud-dns1.3Engines.com | 91.212.141.94 | -| secondary name server | cloud-dns2.3Engines.com | 91.212.141.102 | -| secondary name server | cloud-dns3.3Engines.com | 91.212.141.86 | +| primary name server | cloud-dns1.connectVM.com | 91.212.141.94 | +| secondary name server | cloud-dns2.connectVM.com | 91.212.141.102 | +| secondary name server | cloud-dns3.connectVM.com | 91.212.141.86 | **Option 2 - Set up your own glue records (not recommended)** @@ -107,7 +107,7 @@ Step 2 Zone configuration[🔗](#step-2-zone-configuration "Permalink to this he Zone configuration is defining parameters for the main domain name you have purchased. -To manage domain *exampledomain.com* in 3Engines, login to 3Engines dashboard, choose the right project if different than default, go to **Project** → **DNS** → **Zones**, click **Create Zone** and fill in the required fields: +To manage domain *exampledomain.com* in connectVM, login to connectVM dashboard, choose the right project if different than default, go to **Project** → **DNS** → **Zones**, click **Create Zone** and fill in the required fields: ![dns1.png](../_images/dns1.png) @@ -117,9 +117,9 @@ Here is what the parameters mean: > * **Description**: free text description > * **Email Address**: an administrative e-mail address associated with the domain > * **TTL**: *Time To Live* in seconds - a period of time between refreshing cache in DNS servers. Please note that the longer time, the faster will be name recognition for your domain by external DNS servers but also if you introduce changes, they will propagate slower. The default value of 3600 seconds is a reasonable compromise. -> * **Type**: You may choose if 3Engines name servers will be primary or secondary for your domain. Default: Primary. In case you want to setup secondary name servers, you just define IP addresses or master DNS servers for the domain. +> * **Type**: You may choose if connectVM name servers will be primary or secondary for your domain. Default: Primary. In case you want to setup secondary name servers, you just define IP addresses or master DNS servers for the domain. -After submitting, your domain should be served by 3Engines. +After submitting, your domain should be served by connectVM. Step 3 Checking the presence of the domain on the Internet[🔗](#step-3-checking-the-presence-of-the-domain-on-the-internet "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------------------------------------------- @@ -137,11 +137,11 @@ There are several ways of checking whether the domain name has propagated. : The **dig** command has several parameters. The following combination will show the presence of the name servers in the global DNS system: > ``` - > dig -t any +noall +answer exampledomain.com @cloud-dns1.3Engines.com - > exampledomain.com. 3600 IN SOA cloud-dns2.3Engines.com. [email protected]. 1675003306 3588 600 86400 3600 - > exampledomain.com. 3600 IN NS cloud-dns1.3Engines.com. - > exampledomain.com. 3600 IN NS cloud-dns3.3Engines.com. - > exampledomain.com. 3600 IN NS cloud-dns2.3Engines.com. + > dig -t any +noall +answer exampledomain.com @cloud-dns1.connectVM.com + > exampledomain.com. 3600 IN SOA cloud-dns2.connectVM.com. [email protected]. 1675003306 3588 600 86400 3600 + > exampledomain.com. 3600 IN NS cloud-dns1.connectVM.com. + > exampledomain.com. 3600 IN NS cloud-dns3.connectVM.com. + > exampledomain.com. 3600 IN NS cloud-dns2.connectVM.com. > > ``` @@ -192,12 +192,12 @@ The parameters are: Submit the form and check whether your configuration works: ``` -dig -t any +noall +answer exampledomain.com @cloud-dns1.3Engines.com -exampledomain.com. 3600 IN SOA cloud-dns2.3Engines.com. XXXXXXXXX.YYYYYYYY.com. 1675325538 3530 600 86400 3600 +dig -t any +noall +answer exampledomain.com @cloud-dns1.connectVM.com +exampledomain.com. 3600 IN SOA cloud-dns2.connectVM.com. XXXXXXXXX.YYYYYYYY.com. 1675325538 3530 600 86400 3600 exampledomain.com. 3600 IN A 64.225.133.254 -exampledomain.com. 3600 IN NS cloud-dns1.3Engines.com. -exampledomain.com. 3600 IN NS cloud-dns2.3Engines.com. -exampledomain.com. 3600 IN NS cloud-dns3.3Engines.com. +exampledomain.com. 3600 IN NS cloud-dns1.connectVM.com. +exampledomain.com. 3600 IN NS cloud-dns2.connectVM.com. +exampledomain.com. 3600 IN NS cloud-dns3.connectVM.com. ``` @@ -220,7 +220,7 @@ To configure an address of web server in **exampledomain.com**, so that **www.ex Submit the form and check whether your configuration works: ``` -dig -t any +noall +answer www.exampledomain.com @cloud-dns1.3Engines.com +dig -t any +noall +answer www.exampledomain.com @cloud-dns1.connectVM.com www.exampledomain.com. 3600 IN A 64.225.133.254 ``` @@ -228,7 +228,7 @@ www.exampledomain.com. 3600 IN A 64.225.133.254 Step 6 Managing records[🔗](#step-6-managing-records "Permalink to this headline") --------------------------------------------------------------------------------- -Anytime you want to review, edit or delete records in your domain, visit 3Engines dashboard, **Project** → **DNS** → **Zones**. After clicking the domain name of your interest, choose **Record Sets** tab and see the list of all records: +Anytime you want to review, edit or delete records in your domain, visit connectVM dashboard, **Project** → **DNS** → **Zones**. After clicking the domain name of your interest, choose **Record Sets** tab and see the list of all records: ![show_example_domain_record_sets.png](../_images/show_example_domain_record_sets.png) @@ -237,21 +237,21 @@ From this screen you can update or delete records. Limitations[🔗](#limitations "Permalink to this headline") --------------------------------------------------------- -There are the following limitations in 3Engines DNSaaS: +There are the following limitations in connectVM DNSaaS: > * You cannot manage NS records for your domain. Therefore > > > + you cannot add additional secondary name servers > > + you are unable to delegate subdomains to external servers -> * Even though you are able to configure reverse DNS for your domain, this configuration will have no effect since reverse DNS for 3Engines Cloud IP pools are managed on DNS servers other than 3Engines DNSaaS. +> * Even though you are able to configure reverse DNS for your domain, this configuration will have no effect since reverse DNS for connectVM Cloud IP pools are managed on DNS servers other than connectVM DNSaaS. What To Do Next[🔗](#what-to-do-next "Permalink to this headline") ----------------------------------------------------------------- -Once an 3Engines object has floating IP address, you can use the DNS service to propagate a domain name and, thus, create a service or a site. There are several situations in which you can create a floating IP address: +Once an connectVM object has floating IP address, you can use the DNS service to propagate a domain name and, thus, create a service or a site. There are several situations in which you can create a floating IP address: You already have an existing VM -: Follow the procedure in article [How to Add or Remove Floating IP’s to your VM on 3Engines Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md) to assign a new floating IP to it. +: Follow the procedure in article [How to Add or Remove Floating IP’s to your VM on connectVM Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md) to assign a new floating IP to it. Assign floating IP while creating a new VM from scratch : That is the approach in articles from Prerequisite No. 5. @@ -259,4 +259,4 @@ Assign floating IP while creating a new VM from scratch **Kubernetes services can have an automatically assigned floating IP** : The following article shows how to deploy an HTTPS service on Kubernetes: -[Deploying HTTPS Services on Magnum Kubernetes in 3Engines Cloud Cloud](../kubernetes/Deploying-HTTPS-Services-on-Magnum-Kubernetes-in-3Engines-Cloud-Cloud.html.md) \ No newline at end of file +[Deploying HTTPS Services on Magnum Kubernetes in connectVM Cloud Cloud](../kubernetes/Deploying-HTTPS-Services-on-Magnum-Kubernetes-in-connectVM-Cloud-Cloud.html.md) \ No newline at end of file diff --git a/docs/cloud/Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-3Engines-Cloud.html.md b/docs/cloud/Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-connectVM-Cloud.html.md similarity index 78% rename from docs/cloud/Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-3Engines-Cloud.html.md rename to docs/cloud/Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-connectVM-Cloud.html.md index b79a17e..0e6cf0d 100644 --- a/docs/cloud/Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-3Engines-Cloud.html.md +++ b/docs/cloud/Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -Dashboard Overview – Project Quotas And Flavors Limits on 3Engines Cloud[🔗](#dashboard-overview-project-quotas-and-flavors-limits-on-brand-name "Permalink to this headline") +Dashboard Overview – Project Quotas And Flavors Limits on connectVM Cloud[🔗](#dashboard-overview-project-quotas-and-flavors-limits-on-brand-name "Permalink to this headline") =============================================================================================================================================================================== -While using 3Engines Cloud platform, one of the first things you will spot is the “Limit Summary”. Each project is restricted by preset quotas. This is preventing system capacities from being exhausted without notification and guaranteeing free resources. +While using connectVM Cloud platform, one of the first things you will spot is the “Limit Summary”. Each project is restricted by preset quotas. This is preventing system capacities from being exhausted without notification and guaranteeing free resources. On the first screen after logging into Horizon Dashboard you will see seven charts reflecting limits most essential to the stability of the platform. You can always show this screen with command **Compute** -> **Overview**. @@ -34,4 +34,4 @@ During the VM creation process, while choosing flavor, you may spot a yellow exc You can expand the flavor summary by clicking the arrow on the left. The charts will show the current free resources as well as the resources that will remain after creating a new instance. -If the quota would be exceeded, 3Engines will non allow to choose this particular flavor. \ No newline at end of file +If the quota would be exceeded, connectVM will non allow to choose this particular flavor. \ No newline at end of file diff --git a/docs/cloud/How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md b/docs/cloud/How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md similarity index 88% rename from docs/cloud/How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md rename to docs/cloud/How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md index ddaa972..de9946b 100644 --- a/docs/cloud/How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md +++ b/docs/cloud/How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How To Create a New Linux VM With NVIDIA Virtual GPU in the 3Engines Dashboard Horizon on 3Engines Cloud[🔗](#how-to-create-a-new-linux-vm-with-nvidia-virtual-gpu-in-the-3Engines-dashboard-horizon-on-brand-name "Permalink to this headline") +How To Create a New Linux VM With NVIDIA Virtual GPU in the connectVM Dashboard Horizon on connectVM Cloud[🔗](#how-to-create-a-new-linux-vm-with-nvidia-virtual-gpu-in-the-connectVM-dashboard-horizon-on-brand-name "Permalink to this headline") =================================================================================================================================================================================================================================================== You can create Linux virtual machine with NVIDIA RTX A6000 as the additional graphics card. The card contains @@ -38,7 +38,7 @@ Insert the name of the instance (eg. “vm\_with\_vgpu”) and click Next button Your goal is to use an image with predefinced NVIDIA support. To list all such images, click on field **Available** and enter ‘NVIDIA’ into it. Only the images with NVIDIA in their names will be listed: -![nvidia_chosen_3Engines_cloud.png](../_images/nvidia_chosen_3Engines_cloud.png) +![nvidia_chosen_connectVM_cloud.png](../_images/nvidia_chosen_connectVM_cloud.png) Select Instance Boot Source (eg. “Image”), and choose desired image (eg. “Ubuntu 20.04 NVIDIA”) by clicking on arrow. @@ -88,7 +88,7 @@ Open “Security Groups” After that, choose “allow\_ping\_ssh\_icmp\_rdp” ![createnew6.png](../_images/createnew6.png) -Choose or generate SSH keypair, as explained in article [How to create key pair in 3Engines Dashboard on 3Engines Cloud](How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md) for your VM. Next, launch your instance by clicking on blue button. +Choose or generate SSH keypair, as explained in article [How to create key pair in connectVM Dashboard on connectVM Cloud](How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md) for your VM. Next, launch your instance by clicking on blue button. ![createnew7.png](../_images/createnew7.png) @@ -98,7 +98,7 @@ You will see “Instances” menu with your newly created VM. Note -If you want to make your VM accessible from the Internet, see this article: [How to Add or Remove Floating IP’s to your VM on 3Engines Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md) +If you want to make your VM accessible from the Internet, see this article: [How to Add or Remove Floating IP’s to your VM on connectVM Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md) Step 4 Issue Commands from the Console[🔗](#step-4-issue-commands-from-the-console "Permalink to this headline") --------------------------------------------------------------------------------------------------------------- @@ -107,9 +107,9 @@ Open the drop-down menu and choose “Console”. ![createnew9.png](../_images/createnew9.png) -You can connect to your virtual machine using SSH, see this article: [How to connect to your virtual machine via SSH in Linux on 3Engines Cloud](../networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-3Engines-Cloud.html.md) +You can connect to your virtual machine using SSH, see this article: [How to connect to your virtual machine via SSH in Linux on connectVM Cloud](../networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-connectVM-Cloud.html.md) -You can also use the SPICE console using the 3Engines Dashboard. +You can also use the SPICE console using the connectVM Dashboard. Click on the black terminal area (to activate access to the console). Type: diff --git a/docs/cloud/How-to-access-the-VM-from-3Engines-console-on-3Engines-Cloud.html.md b/docs/cloud/How-to-access-the-VM-from-connectVM-console-on-connectVM-Cloud.html.md similarity index 85% rename from docs/cloud/How-to-access-the-VM-from-3Engines-console-on-3Engines-Cloud.html.md rename to docs/cloud/How-to-access-the-VM-from-connectVM-console-on-connectVM-Cloud.html.md index d3db5c9..19f235f 100644 --- a/docs/cloud/How-to-access-the-VM-from-3Engines-console-on-3Engines-Cloud.html.md +++ b/docs/cloud/How-to-access-the-VM-from-connectVM-console-on-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -How to access the VM from 3Engines console on 3Engines Cloud[🔗](#how-to-access-the-vm-from-3Engines-console-on-brand-name "Permalink to this headline") +How to access the VM from connectVM console on connectVM Cloud[🔗](#how-to-access-the-vm-from-connectVM-console-on-brand-name "Permalink to this headline") =========================================================================================================================================================== -Once you have created a virtual machine in 3Engines, you will need to perform various administrative tasks such as: +Once you have created a virtual machine in connectVM, you will need to perform various administrative tasks such as: > * installing and uninstalling software, > * uploading and downloading files, @@ -32,14 +32,14 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . Using console for administrative tasks within Linux based VMs[🔗](#using-console-for-administrative-tasks-within-linux-based-vms "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------------------------------------------------- -1. Go to and select your authentication method: +1. Go to and select your authentication method: -![login_3Enginescloud.png](../_images/login_3Enginescloud.png) +![login_connectVMcloud.png](../_images/login_connectVMcloud.png) You will enter the Horizon main screen. @@ -72,7 +72,7 @@ You will then use the console as a predefined user called **eouser**. Attention -Google Chrome seems to work slowly while using the 3Engines console. Firefox works well. +Google Chrome seems to work slowly while using the connectVM console. Firefox works well. Using console to perform administrative tasks within Fedora VMs[🔗](#using-console-to-perform-administrative-tasks-within-fedora-vms "Permalink to this headline") ----------------------------------------------------------------------------------------------------------------------------------------------------------------- @@ -96,11 +96,11 @@ where *vault* is the namespace within which the pod *vault-0* will be found and Further explanations of **exec** command are out of scope of this article. The following article will show you how to activate the **kubectl** command after the cluster has been created: -[How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](../kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md) +[How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](../kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md) This article shows an example of an **exec** command to enter the VM and, later, save the data within it: -[Volume-based vs Ephemeral-based Storage for Kubernetes Clusters on 3Engines Cloud 3Engines Magnum](../kubernetes/Volume-based-vs-Ephemeral-based-Storage-for-Kubernetes-Clusters-on-3Engines-Cloud-3Engines-Magnum.html.md) +[Volume-based vs Ephemeral-based Storage for Kubernetes Clusters on connectVM Cloud connectVM Magnum](../kubernetes/Volume-based-vs-Ephemeral-based-Storage-for-Kubernetes-Clusters-on-connectVM-Cloud-connectVM-Magnum.html.md) ### Performing administrative tasks within Windows based VMs[🔗](#performing-administrative-tasks-within-windows-based-vms "Permalink to this headline") diff --git a/docs/cloud/How-to-clone-existing-and-configured-VMs-on-3Engines-Cloud.html.md b/docs/cloud/How-to-clone-existing-and-configured-VMs-on-connectVM-Cloud.html.md similarity index 69% rename from docs/cloud/How-to-clone-existing-and-configured-VMs-on-3Engines-Cloud.html.md rename to docs/cloud/How-to-clone-existing-and-configured-VMs-on-connectVM-Cloud.html.md index deadaeb..74b425f 100644 --- a/docs/cloud/How-to-clone-existing-and-configured-VMs-on-3Engines-Cloud.html.md +++ b/docs/cloud/How-to-clone-existing-and-configured-VMs-on-connectVM-Cloud.html.md @@ -1,16 +1,16 @@ -How to clone existing and configured VMs on 3Engines Cloud[🔗](#how-to-clone-existing-and-configured-vms-on-brand-name "Permalink to this headline") +How to clone existing and configured VMs on connectVM Cloud[🔗](#how-to-clone-existing-and-configured-vms-on-brand-name "Permalink to this headline") ===================================================================================================================================================== -The simplest way to create the snapshot of your machine is using “Horizon” - graphical interface of 3Engines dashboard. +The simplest way to create the snapshot of your machine is using “Horizon” - graphical interface of connectVM dashboard. In summary, there will be 2 operations: 1. Creating snapshot 2. Restoring snapshot to newly created VM. -To start, please visit our website and login. +To start, please visit our website and login. -![saml_3Engines_cloud.png](../_images/saml_3Engines_cloud.png) +![saml_connectVM_cloud.png](../_images/saml_connectVM_cloud.png) After logon, in **“Instances”** menu select VM to be cloned, and create its snapshot by clicking “Actions” Menu @@ -22,7 +22,7 @@ Once the snapshot is ready, you may see it on **“Images”** page of Horizon. Now, you may click **“Launch”** in right upper corner of the window or just go back to **“Instances”** menu and launch new instance. -Full manual is here: [How to create new Linux VM in 3Engines Dashboard Horizon on 3Engines Cloud](How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md) +Full manual is here: [How to create new Linux VM in connectVM Dashboard Horizon on connectVM Cloud](How-to-create-new-Linux-VM-in-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md) But if this process is familiar to you, there is only one difference. Chose as the source **“boot from snapshot”** instead of **“boot from image”** and select your snapshot from the list below. In next steps select parameters (flavour, size), at least the same as the original one. (“Launch instance” button will be unavailable until all necessary settings were completed). @@ -32,4 +32,4 @@ Caution If the original machine had any additional volumes attached to it, they should also be cloned. -You may also want to read: [Volume snapshot inheritance and its consequences on 3Engines Cloud](../datavolume/Volume-snapshot-inheritance-and-its-consequences-on-3Engines-Cloud.html.md). \ No newline at end of file +You may also want to read: [Volume snapshot inheritance and its consequences on connectVM Cloud](../datavolume/Volume-snapshot-inheritance-and-its-consequences-on-connectVM-Cloud.html.md). \ No newline at end of file diff --git a/docs/cloud/How-to-create-Windows-VM-on-3Engines-Horizon-and-access-it-via-web-console-on-3Engines-Cloud.html.md b/docs/cloud/How-to-create-Windows-VM-on-connectVM-Horizon-and-access-it-via-web-console-on-connectVM-Cloud.html.md similarity index 94% rename from docs/cloud/How-to-create-Windows-VM-on-3Engines-Horizon-and-access-it-via-web-console-on-3Engines-Cloud.html.md rename to docs/cloud/How-to-create-Windows-VM-on-connectVM-Horizon-and-access-it-via-web-console-on-connectVM-Cloud.html.md index 6f38c78..284f0b9 100644 --- a/docs/cloud/How-to-create-Windows-VM-on-3Engines-Horizon-and-access-it-via-web-console-on-3Engines-Cloud.html.md +++ b/docs/cloud/How-to-create-Windows-VM-on-connectVM-Horizon-and-access-it-via-web-console-on-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -How to create Windows VM on 3Engines Horizon and access it via web console on 3Engines Cloud[🔗](#how-to-create-windows-vm-on-3Engines-horizon-and-access-it-via-web-console-on-brand-name "Permalink to this headline") +How to create Windows VM on connectVM Horizon and access it via web console on connectVM Cloud[🔗](#how-to-create-windows-vm-on-connectVM-horizon-and-access-it-via-web-console-on-brand-name "Permalink to this headline") =========================================================================================================================================================================================================================== -This article provides a straightforward way of creating a functional Windows VM on 3Engines Cloud cloud, using the Horizon graphical interface. +This article provides a straightforward way of creating a functional Windows VM on connectVM Cloud cloud, using the Horizon graphical interface. The idea is to @@ -27,7 +27,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . Step 1: Access the Launch Instance menu[🔗](#step-1-access-the-launch-instance-menu "Permalink to this headline") ---------------------------------------------------------------------------------------------------------------- @@ -214,6 +214,6 @@ Follow the appropriate prompts to update your operating system. What To Do Next[🔗](#what-to-do-next "Permalink to this headline") ----------------------------------------------------------------- -If you want to access your virtual machine remotely using RDP (Remote Desktop Protocol), you should consider increasing its security by using a bastion host. The following article contains more information: [Connecting to a Windows VM via RDP through a Linux bastion host port forwarding on 3Engines Cloud](../windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-3Engines-Cloud.html.md) +If you want to access your virtual machine remotely using RDP (Remote Desktop Protocol), you should consider increasing its security by using a bastion host. The following article contains more information: [Connecting to a Windows VM via RDP through a Linux bastion host port forwarding on connectVM Cloud](../windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-connectVM-Cloud.html.md) -To learn more about security groups, you can check this article: [How to use Security Groups in Horizon on 3Engines Cloud](How-to-use-Security-Groups-in-Horizon-on-3Engines-Cloud.html.md) \ No newline at end of file +To learn more about security groups, you can check this article: [How to use Security Groups in Horizon on connectVM Cloud](How-to-use-Security-Groups-in-Horizon-on-connectVM-Cloud.html.md) \ No newline at end of file diff --git a/docs/cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md b/docs/cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md similarity index 81% rename from docs/cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md rename to docs/cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md index 94ee22c..cb9e408 100644 --- a/docs/cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md +++ b/docs/cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md @@ -1,9 +1,9 @@ -How to create a Linux VM and access it from Linux command line on 3Engines Cloud[🔗](#how-to-create-a-linux-vm-and-access-it-from-linux-command-line-on-brand-name "Permalink to this headline") +How to create a Linux VM and access it from Linux command line on connectVM Cloud[🔗](#how-to-create-a-linux-vm-and-access-it-from-linux-command-line-on-brand-name "Permalink to this headline") ================================================================================================================================================================================================= -Creating a virtual machine in a 3Engines Cloud cloud allows you to perform computations without having to engage your own infrastructure. In this article you shall create a Linux based virtual machine and access it remotely from a Linux command line on a desktop or laptop. +Creating a virtual machine in a connectVM Cloud cloud allows you to perform computations without having to engage your own infrastructure. In this article you shall create a Linux based virtual machine and access it remotely from a Linux command line on a desktop or laptop. -If you want to access Linux VM from a Windows based command line, follow this article instead: [How to create a Linux VM and access it from Windows desktop on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md). +If you want to access Linux VM from a Windows based command line, follow this article instead: [How to create a Linux VM and access it from Windows desktop on connectVM Cloud](How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-connectVM-Cloud.html.md). Note @@ -12,7 +12,7 @@ This article only covers the basics of creating a VM - it does not cover topics What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- -> * Creating a Linux virtual machine in 3Engines Cloud cloud using command **Launch Instance** from Horizon Dashboard +> * Creating a Linux virtual machine in connectVM Cloud cloud using command **Launch Instance** from Horizon Dashboard You will enter the following required data into that window: @@ -36,7 +36,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . No. 2 **Basic knowledge of Linux terminal** @@ -48,13 +48,13 @@ A Linux distribution running on your computer. This article was written for Ubun No. 4 **SSH client installed and configured on your local Linux computer** -The SSH client must be installed and configured on your local Linux computer. Please see [Generating an SSH keypair in Linux on 3Engines Cloud](../networking/Generating-a-SSH-keypair-in-Linux-on-3Engines-Cloud.html.md). +The SSH client must be installed and configured on your local Linux computer. Please see [Generating an SSH keypair in Linux on connectVM Cloud](../networking/Generating-a-SSH-keypair-in-Linux-on-connectVM-Cloud.html.md). -If you already have an SSH key pair and an SSH client configured, you should import your public key to the Horizon dashboard. The following article contains information how to do it: [How to import SSH public key to 3Engines Horizon on 3Engines Cloud](../networking/How-to-Import-SSH-Public-Key-to-3Engines-Horizon-on-3Engines-Cloud.html.md). +If you already have an SSH key pair and an SSH client configured, you should import your public key to the Horizon dashboard. The following article contains information how to do it: [How to import SSH public key to connectVM Horizon on connectVM Cloud](../networking/How-to-Import-SSH-Public-Key-to-connectVM-Horizon-on-connectVM-Cloud.html.md). Alternatively, you can also create a key pair directly in the Horizon: -[How to create key pair in 3Engines Dashboard on 3Engines Cloud](How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md). +[How to create key pair in connectVM Dashboard on connectVM Cloud](How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md). Options for creation of a Virtual Machine (VM)[🔗](#options-for-creation-of-a-virtual-machine-vm "Permalink to this headline") ----------------------------------------------------------------------------------------------------------------------------- @@ -63,7 +63,7 @@ Creation of a virtual machine is divided into 11 sections, four of which are man Note -In 3Engines terminology, a *virtual machine* is also an *instance*. *Instance* is a broader term as not all instances need be virtual machines, it is also possible to use real hardware as an instance. +In connectVM terminology, a *virtual machine* is also an *instance*. *Instance* is a broader term as not all instances need be virtual machines, it is also possible to use real hardware as an instance. The window to create a virtual machine is called **Launch Instance**. You will enter all the data about an instance into that window and its options. @@ -110,7 +110,7 @@ You should now see the following form: ![create-linux-linux-07_creodias.png](../_images/create-linux-linux-07_creodias.png) -The standard definition of 3Engines *flavor* is the amount of resources available to the instance - like VCPU, memory and storage capacity. +The standard definition of connectVM *flavor* is the amount of resources available to the instance - like VCPU, memory and storage capacity. Choose the one which suits you best and click **↑** next to it. @@ -130,7 +130,7 @@ To solve this issue, choose a flavor that supports your chosen source instead. I Another possible explanation might be that your quota is too low for creating a VM with your chosen flavor. You can see your quota in the **Compute -> Overview** section of your Horizon dashboard. If that is the case, you can either: * choose a different flavor or -* contact the 3Engines Cloud Support to request quota increase - [Helpdesk and Support](../accountmanagement/Help-Desk-And-Support.html.md). +* contact the connectVM Cloud Support to request quota increase - [Helpdesk and Support](../accountmanagement/Help-Desk-And-Support.html.md). Click **Next** or click **Networks** to define networks. @@ -178,7 +178,7 @@ In the image above, the key is called **test-key**. There are three ways to ente > * using option **Create Key Pair** – create it on the spot, > * using option **Import Key Pair** – take the keys you already have and upload them to the cloud, -> * using one of the key pairs that were already existing within 3Engines cloud. +> * using one of the key pairs that were already existing within connectVM cloud. If you haven’t created your key pair yet, please follow Prerequisite No. 4. @@ -208,7 +208,7 @@ Just like on the above screenshot, under header **IP Address**, you will see net Step 8 Attach a Floating IP to the instance[🔗](#step-8-attach-a-floating-ip-to-the-instance "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------------- -Here is how to create and attach a floating IP to your instance: [How to Add or Remove Floating IP’s to your VM on 3Engines Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md). +Here is how to create and attach a floating IP to your instance: [How to Add or Remove Floating IP’s to your VM on connectVM Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md). Once you have added the floating IP, you will see it in the Horizon dashboard under header **IP Address** - just like in the last image from that article: @@ -219,7 +219,7 @@ The floating IP address in that article is **64.225.132.0**. Your address will v Step 9 Connecting to your virtual machine using SSH[🔗](#step-9-connecting-to-your-virtual-machine-using-ssh "Permalink to this headline") ----------------------------------------------------------------------------------------------------------------------------------------- -The following article has information about connecting to a virtual machine using SSH: [How to connect to your virtual machine via SSH in Linux on 3Engines Cloud](../networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-3Engines-Cloud.html.md). +The following article has information about connecting to a virtual machine using SSH: [How to connect to your virtual machine via SSH in Linux on connectVM Cloud](../networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-connectVM-Cloud.html.md). The last command in that article was: @@ -233,7 +233,7 @@ The IP address in that article is **64.225.132.99** and is different from the ad What To Do Next[🔗](#what-to-do-next "Permalink to this headline") ----------------------------------------------------------------- -3Engines Cloud cloud can be used for general hosting needs, such as +connectVM Cloud cloud can be used for general hosting needs, such as > * installing LAMP servers, > * installing and using WordPress servers, @@ -242,20 +242,20 @@ What To Do Next[🔗](#what-to-do-next "Permalink to this headline") To create a *cluster* of instances, see the series of articles on Kubernetes: -[How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](../kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md). +[How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](../kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md). If you find yourself unable to connect to your virtual machine using SSH, you can use the web console for troubleshooting and other purposes. Here’s how to do it: -[How to access the VM from 3Engines console on 3Engines Cloud](How-to-access-the-VM-from-3Engines-console-on-3Engines-Cloud.html.md) +[How to access the VM from connectVM console on connectVM Cloud](How-to-access-the-VM-from-connectVM-console-on-connectVM-Cloud.html.md) If you don’t want the storage of your instance to be deleted while the VM is removed, you can choose to use a volume during instance creation. Please see the following articles: -[VM created with option Create New Volume No on 3Engines Cloud](VM-created-with-option-Create-New-Volume-No-on-3Engines-Cloud.html.md) +[VM created with option Create New Volume No on connectVM Cloud](VM-created-with-option-Create-New-Volume-No-on-connectVM-Cloud.html.md) -[VM created with option Create New Volume Yes on 3Engines Cloud](VM-created-with-option-Create-New-Volume-Yes-on-3Engines-Cloud.html.md). +[VM created with option Create New Volume Yes on connectVM Cloud](VM-created-with-option-Create-New-Volume-Yes-on-connectVM-Cloud.html.md). You can’t apply the SSH keys uploaded to the Horizon dashboard directly to a VM after its creation. The following article presents a walkaround to this problem: -[How to add SSH key from Horizon web console on 3Engines Cloud](../networking/How-to-add-SSH-key-from-Horizon-web-console-on-3Engines-Cloud.html.md). +[How to add SSH key from Horizon web console on connectVM Cloud](../networking/How-to-add-SSH-key-from-Horizon-web-console-on-connectVM-Cloud.html.md). -If you find that the storage of your VM is insufficient for your needs, you can attach the volume to it after its creation. The following articles contain appropriate instructions: [How to attach a volume to VM less than 2TB on Linux on 3Engines Cloud](../datavolume/How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-3Engines-Cloud.html.md) and [How to attach a volume to VM more than 2TB on Linux on 3Engines Cloud](../datavolume/How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-3Engines-Cloud.html.md). \ No newline at end of file +If you find that the storage of your VM is insufficient for your needs, you can attach the volume to it after its creation. The following articles contain appropriate instructions: [How to attach a volume to VM less than 2TB on Linux on connectVM Cloud](../datavolume/How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-connectVM-Cloud.html.md) and [How to attach a volume to VM more than 2TB on Linux on connectVM Cloud](../datavolume/How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-connectVM-Cloud.html.md). \ No newline at end of file diff --git a/docs/cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md b/docs/cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-connectVM-Cloud.html.md similarity index 84% rename from docs/cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md rename to docs/cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-connectVM-Cloud.html.md index 94251d1..0efb08c 100644 --- a/docs/cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md +++ b/docs/cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-connectVM-Cloud.html.md @@ -1,9 +1,9 @@ -How to create a Linux VM and access it from Windows desktop on 3Engines Cloud[🔗](#how-to-create-a-linux-vm-and-access-it-from-windows-desktop-on-brand-name "Permalink to this headline") +How to create a Linux VM and access it from Windows desktop on connectVM Cloud[🔗](#how-to-create-a-linux-vm-and-access-it-from-windows-desktop-on-brand-name "Permalink to this headline") =========================================================================================================================================================================================== -Creating a virtual machine in a 3Engines Cloud cloud allows you to perform computations without having to engage your own infrastructure. In this article you shall create a Linux based virtual machine and access it remotely using PuTTY on Windows. +Creating a virtual machine in a connectVM Cloud cloud allows you to perform computations without having to engage your own infrastructure. In this article you shall create a Linux based virtual machine and access it remotely using PuTTY on Windows. -If you want to access Linux VM from a Linux command line, follow this article instead: [How to create a Linux VM and access it from Linux command line on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md). +If you want to access Linux VM from a Linux command line, follow this article instead: [How to create a Linux VM and access it from Linux command line on connectVM Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md). Note @@ -12,7 +12,7 @@ This article only covers the basics of creating a VM - it does not cover topics What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- -> * Creating a Linux virtual machine in 3Engines Cloud cloud using command **Launch Instance** from Horizon Dashboard +> * Creating a Linux virtual machine in connectVM Cloud cloud using command **Launch Instance** from Horizon Dashboard You will enter the following data into that window: @@ -42,7 +42,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . No. 2 **Basic knowledge of Linux terminal** @@ -60,9 +60,9 @@ No. 5 **SSH key** You need to have an SSH key pair. It consists of a public and private key. You can use your existing pair in this workflow or create a new one. If you do not have one, you have several options, such as: -* Generate them directly using the Horizon dashboard: [How to create key pair in 3Engines Dashboard on 3Engines Cloud](How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md). +* Generate them directly using the Horizon dashboard: [How to create key pair in connectVM Dashboard on connectVM Cloud](How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md). -* Generate your key pair using the Windows command line. Please check this article: [How to Create SSH Key Pair in Windows 10 On 3Engines Cloud](../windows/How-To-Create-SSH-Key-Pair-In-Windows-On-3Engines-Cloud.html.md). If you choose that option, make sure that you upload your public key to the Horizon dashboard: [How to import SSH public key to 3Engines Horizon on 3Engines Cloud](../networking/How-to-Import-SSH-Public-Key-to-3Engines-Horizon-on-3Engines-Cloud.html.md). +* Generate your key pair using the Windows command line. Please check this article: [How to Create SSH Key Pair in Windows 10 On connectVM Cloud](../windows/How-To-Create-SSH-Key-Pair-In-Windows-On-connectVM-Cloud.html.md). If you choose that option, make sure that you upload your public key to the Horizon dashboard: [How to import SSH public key to connectVM Horizon on connectVM Cloud](../networking/How-to-Import-SSH-Public-Key-to-connectVM-Horizon-on-connectVM-Cloud.html.md). This article contains information about configuring PuTTY using one such key pair. @@ -73,7 +73,7 @@ Creation of a virtual machine is divided into 11 sections, four of which are man Note -In 3Engines terminology, a *virtual machine* is also an *instance*. *Instance* is a broader term as not all instances need be virtual machines, it is also possible to use real hardware as an instance. +In connectVM terminology, a *virtual machine* is also an *instance*. *Instance* is a broader term as not all instances need be virtual machines, it is also possible to use real hardware as an instance. The window to create a virtual machine is called **Launch Instance**. You will enter all the data about an instance into that window. @@ -120,7 +120,7 @@ You should now see the following form: ![create-linux-linux-07_creodias.png](../_images/create-linux-linux-07_creodias.png) -The standard definition of 3Engines *flavor* is the amount of resources available to the instance - like VCPU, memory and storage capacity. +The standard definition of connectVM *flavor* is the amount of resources available to the instance - like VCPU, memory and storage capacity. Choose the one which suits you best and click **↑** next to it. @@ -142,7 +142,7 @@ To solve this issue, choose a flavor that supports your chosen source instead. I Another possible cause might be that your quota is too low for creating a VM with your chosen flavor. You can see your quota in the **Compute -> Overview** section of your Horizon dashboard. If that is the case, you can either: * choose a different flavor or -* contact the 3Engines Cloud Support to request quota increase - [Helpdesk and Support](../accountmanagement/Help-Desk-And-Support.html.md). +* contact the connectVM Cloud Support to request quota increase - [Helpdesk and Support](../accountmanagement/Help-Desk-And-Support.html.md). Click **Next** or click **Networks** to define networks. @@ -193,7 +193,7 @@ In the image above, the key is called **test-key**. There are three ways to ente > * using option **Create Key Pair** – create it on the spot, > * using option **Import Key Pair** – take the keys you already have and upload them to the cloud, -> * using one of the key pairs that were already existing within 3Engines cloud. +> * using one of the key pairs that were already existing within connectVM cloud. If you haven’t created your key pair yet, please follow Prerequisite No. 5. @@ -223,7 +223,7 @@ Just like on the above screenshot, under header **IP Address**, you will see net Step 8 Attach a Floating IP to the instance[🔗](#step-8-attach-a-floating-ip-to-the-instance "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------------- -Here is how to create and attach a floating IP to your instance: [How to Add or Remove Floating IP’s to your VM on 3Engines Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md). +Here is how to create and attach a floating IP to your instance: [How to Add or Remove Floating IP’s to your VM on connectVM Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md). Once you have added the floating IP, you will see it in the Horizon dashboard under header **IP Address** - just like in the last image from that article: @@ -325,7 +325,7 @@ Type **eouser** and press Enter. Note -User **eouser** is the predefined Linux user name on default images on 3Engines Cloud hosting. +User **eouser** is the predefined Linux user name on default images on connectVM Cloud hosting. You should now be connected to your virtual machine and be able to execute commands: @@ -345,7 +345,7 @@ You can now start your session as explained in Step 12 above. What To Do Next[🔗](#what-to-do-next "Permalink to this headline") ----------------------------------------------------------------- -3Engines Cloud cloud can be used for general hosting needs, such as +connectVM Cloud cloud can be used for general hosting needs, such as > * installing LAMP servers, > * installing and using WordPress servers, @@ -354,20 +354,20 @@ What To Do Next[🔗](#what-to-do-next "Permalink to this headline") To create a *cluster* of instances, see the series of articles on Kubernetes: -[How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](../kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md). +[How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](../kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md). If you find yourself unable to connect to your virtual machine using SSH, you can use the web console for troubleshooting and other purposes. Here’s how to do it: -[How to access the VM from 3Engines console on 3Engines Cloud](How-to-access-the-VM-from-3Engines-console-on-3Engines-Cloud.html.md) +[How to access the VM from connectVM console on connectVM Cloud](How-to-access-the-VM-from-connectVM-console-on-connectVM-Cloud.html.md) If you don’t want the storage of your instance to be deleted while the VM is removed, you can choose to use a volume during instance creation. Please see the following articles: -[VM created with option Create New Volume No on 3Engines Cloud](VM-created-with-option-Create-New-Volume-No-on-3Engines-Cloud.html.md) +[VM created with option Create New Volume No on connectVM Cloud](VM-created-with-option-Create-New-Volume-No-on-connectVM-Cloud.html.md) -[VM created with option Create New Volume Yes on 3Engines Cloud](VM-created-with-option-Create-New-Volume-Yes-on-3Engines-Cloud.html.md). +[VM created with option Create New Volume Yes on connectVM Cloud](VM-created-with-option-Create-New-Volume-Yes-on-connectVM-Cloud.html.md). You can’t apply the SSH keys uploaded to the Horizon dashboard directly to a VM after its creation. The following article presents a walkaround to this problem: -[How to add SSH key from Horizon web console on 3Engines Cloud](../networking/How-to-add-SSH-key-from-Horizon-web-console-on-3Engines-Cloud.html.md). +[How to add SSH key from Horizon web console on connectVM Cloud](../networking/How-to-add-SSH-key-from-Horizon-web-console-on-connectVM-Cloud.html.md). -If you find that the storage of your VM is insufficient for your needs, you can attach the volume to it after its creation. The following articles contain appropriate instructions: [How to attach a volume to VM less than 2TB on Linux on 3Engines Cloud](../datavolume/How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-3Engines-Cloud.html.md) and [How to attach a volume to VM more than 2TB on Linux on 3Engines Cloud](../datavolume/How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-3Engines-Cloud.html.md). \ No newline at end of file +If you find that the storage of your VM is insufficient for your needs, you can attach the volume to it after its creation. The following articles contain appropriate instructions: [How to attach a volume to VM less than 2TB on Linux on connectVM Cloud](../datavolume/How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-connectVM-Cloud.html.md) and [How to attach a volume to VM more than 2TB on Linux on connectVM Cloud](../datavolume/How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-connectVM-Cloud.html.md). \ No newline at end of file diff --git a/docs/cloud/How-to-create-a-VM-using-the-3Engines-CLI-client-on-3Engines-Cloud-cloud.html.md b/docs/cloud/How-to-create-a-VM-using-the-connectVM-CLI-client-on-connectVM-Cloud-cloud.html.md similarity index 59% rename from docs/cloud/How-to-create-a-VM-using-the-3Engines-CLI-client-on-3Engines-Cloud-cloud.html.md rename to docs/cloud/How-to-create-a-VM-using-the-connectVM-CLI-client-on-connectVM-Cloud-cloud.html.md index 206f572..f2ebc0e 100644 --- a/docs/cloud/How-to-create-a-VM-using-the-3Engines-CLI-client-on-3Engines-Cloud-cloud.html.md +++ b/docs/cloud/How-to-create-a-VM-using-the-connectVM-CLI-client-on-connectVM-Cloud-cloud.html.md @@ -1,12 +1,12 @@ -How to create a VM using the 3Engines CLI client on 3Engines Cloud cloud[🔗](#how-to-create-a-vm-using-the-3Engines-cli-client-on-brand-name-cloud "Permalink to this headline") +How to create a VM using the connectVM CLI client on connectVM Cloud cloud[🔗](#how-to-create-a-vm-using-the-connectVM-cli-client-on-brand-name-cloud "Permalink to this headline") =================================================================================================================================================================================== -This article will cover creating a virtual machine on 3Engines Cloud cloud using the 3Engines CLI client exclusively. It contains basic information to get you started. +This article will cover creating a virtual machine on connectVM Cloud cloud using the connectVM CLI client exclusively. It contains basic information to get you started. What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- -> * The **3Engines** command to create a VM +> * The **connectVM** command to create a VM > * Selecting parameters of the new virtual machine > > > * Image @@ -24,20 +24,20 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . -No. 2 **3Engines CLI client configured** +No. 2 **connectVM CLI client configured** -To have the 3Engines CLI client configured and operational, see article: [How to install 3EnginesClient for Linux on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md). +To have the connectVM CLI client configured and operational, see article: [How to install connectVMClient for Linux on connectVM Cloud](../connectVMcli/How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md). If the command ``` -3Engines flavor list +connectVM flavor list ``` -shows a list of flavors, the **3Engines** command is operational. +shows a list of flavors, the **connectVM** command is operational. No. 3 **Available image to create a new VM from** @@ -50,18 +50,18 @@ In general, you can create a new virtual machine from these four sources: In this article, we will use the first option, an operating system image, as a source of a new virtual machine. There are three ways you can obtain an image: -Images that are automatically included on 3Engines Cloud cloud +Images that are automatically included on connectVM Cloud cloud : There is a set of images that come predefined with the cloud. Typically, that default list of images will contain Ubuntu, CentOS, and Windows 2019/22 images, with various flavors. Other default images could be available as well, say, for AlmaLinux, OPNSense, OSGeolive, Rocky Linux and so on. Images shared from other projects -: Under 3Engines, images can be shared between the projects. To have an alien image available in your project, you have to accept it first. +: Under connectVM, images can be shared between the projects. To have an alien image available in your project, you have to accept it first. Images uploaded within your account : Finally, you can upload an image by yourself. Once uploaded, the image will be a first class citizen but it may not be automatically available on other accounts you might have. See this article - [How to upload your custom image using 3Engines CLI on 3Engines Cloud](How-to-upload-your-custom-image-using-3Engines-CLI-on-3Engines-Cloud.html.md) + [How to upload your custom image using connectVM CLI on connectVM Cloud](How-to-upload-your-custom-image-using-connectVM-CLI-on-connectVM-Cloud.html.md) for an example of uploading a new Debian image to the cloud. @@ -69,4 +69,4 @@ No. 4 **Available SSH key pair** These two articles should help generate and import the SSH key into the cloud: -* /networking/Generating-a-sshkeypair-in-Linux-on-3Engines-Cloud and \ No newline at end of file +* /networking/Generating-a-sshkeypair-in-Linux-on-connectVM-Cloud and \ No newline at end of file diff --git a/docs/cloud/How-to-create-instance-snapshot-using-Horizon-on-3Engines-Cloud.html.md b/docs/cloud/How-to-create-instance-snapshot-using-Horizon-on-connectVM-Cloud.html.md similarity index 81% rename from docs/cloud/How-to-create-instance-snapshot-using-Horizon-on-3Engines-Cloud.html.md rename to docs/cloud/How-to-create-instance-snapshot-using-Horizon-on-connectVM-Cloud.html.md index cbb7e49..0f4a524 100644 --- a/docs/cloud/How-to-create-instance-snapshot-using-Horizon-on-3Engines-Cloud.html.md +++ b/docs/cloud/How-to-create-instance-snapshot-using-Horizon-on-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -How to create instance snapshot using Horizon on 3Engines Cloud[🔗](#how-to-create-instance-snapshot-using-horizon-on-brand-name "Permalink to this headline") +How to create instance snapshot using Horizon on connectVM Cloud[🔗](#how-to-create-instance-snapshot-using-horizon-on-brand-name "Permalink to this headline") =============================================================================================================================================================== -In this article, you will learn how to create instance snapshot on 3Engines Cloud cloud, using Horizon dashboard. +In this article, you will learn how to create instance snapshot on connectVM Cloud cloud, using Horizon dashboard. Instance snapshots allow you to archive the state of the virtual machine. You can, then, use them for @@ -49,14 +49,14 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Ephemeral storage vs. persistent storage** -Please see article [Ephemeral vs Persistent storage option Create New Volume on 3Engines Cloud](../datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-3Engines-Cloud.html.md) to understand the basic difference between ephemeral and persistent types of storage in 3Engines. +Please see article [Ephemeral vs Persistent storage option Create New Volume on connectVM Cloud](../datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-connectVM-Cloud.html.md) to understand the basic difference between ephemeral and persistent types of storage in connectVM. No. 3 **Instance with ephemeral storage** -You need a virtual machine hosted on 3Engines Cloud cloud. +You need a virtual machine hosted on connectVM Cloud cloud. Using any of the following articles will produce an instance with ephemeral storage: \ No newline at end of file diff --git a/docs/cloud/How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md b/docs/cloud/How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md similarity index 72% rename from docs/cloud/How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md rename to docs/cloud/How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md index 0eaff8a..5e341b6 100644 --- a/docs/cloud/How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md +++ b/docs/cloud/How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How to create key pair in 3Engines Dashboard on 3Engines Cloud[🔗](#how-to-create-key-pair-in-3Engines-dashboard-on-brand-name "Permalink to this headline") +How to create key pair in connectVM Dashboard on connectVM Cloud[🔗](#how-to-create-key-pair-in-connectVM-dashboard-on-brand-name "Permalink to this headline") =============================================================================================================================================================== Open **Compute -> Key Pairs** @@ -30,8 +30,8 @@ Click key name in **Key Pairs** menu and read your **public key**. You can also * To connect via SSH to your Virtual Machine using Linux, follow the steps in this FAQ: -[How to connect to your virtual machine via SSH in Linux on 3Engines Cloud](../networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-3Engines-Cloud.html.md) +[How to connect to your virtual machine via SSH in Linux on connectVM Cloud](../networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-connectVM-Cloud.html.md) * To connect via SSH to your Virtual Machine using Windows (Command Prompt), follow the steps in this FAQ: -[How to connect to a virtual machine via SSH from Windows 10 Command Prompt on 3Engines Cloud](../windows/How-to-connect-to-a-virtual-machine-via-SSH-from-Windows-10-Command-Prompt-on-3Engines-Cloud.html.md) \ No newline at end of file +[How to connect to a virtual machine via SSH from Windows 10 Command Prompt on connectVM Cloud](../windows/How-to-connect-to-a-virtual-machine-via-SSH-from-Windows-10-Command-Prompt-on-connectVM-Cloud.html.md) \ No newline at end of file diff --git a/docs/cloud/How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md b/docs/cloud/How-to-create-new-Linux-VM-in-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md similarity index 75% rename from docs/cloud/How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md rename to docs/cloud/How-to-create-new-Linux-VM-in-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md index 60f89d5..b947abd 100644 --- a/docs/cloud/How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md +++ b/docs/cloud/How-to-create-new-Linux-VM-in-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How to create new Linux VM in 3Engines Dashboard Horizon on 3Engines Cloud[🔗](#how-to-create-new-linux-vm-in-3Engines-dashboard-horizon-on-brand-name "Permalink to this headline") +How to create new Linux VM in connectVM Dashboard Horizon on connectVM Cloud[🔗](#how-to-create-new-linux-vm-in-connectVM-dashboard-horizon-on-brand-name "Permalink to this headline") ======================================================================================================================================================================================= Go to **Project → Compute → Instances**. @@ -31,7 +31,7 @@ Open **“Security Groups”** After that, choose “default” and “allow\_pi ![newvm6.png](../_images/newvm6.png) -Choose or generate SSH keypair [How to create key pair in 3Engines Dashboard on 3Engines Cloud](How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md) for your VM. Next, launch your instance by clicking on blue button. +Choose or generate SSH keypair [How to create key pair in connectVM Dashboard on connectVM Cloud](How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md) for your VM. Next, launch your instance by clicking on blue button. ![newvm7.png](../_images/newvm7.png) @@ -61,4 +61,4 @@ After you finish, type “exit”. This will close the session. -If you want to make your VM accessible from the Internet check [How to Add or Remove Floating IP’s to your VM on 3Engines Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md). \ No newline at end of file +If you want to make your VM accessible from the Internet check [How to Add or Remove Floating IP’s to your VM on connectVM Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md). \ No newline at end of file diff --git a/docs/cloud/How-to-fix-unresponsive-console-issue-on-3Engines-Cloud.html.md b/docs/cloud/How-to-fix-unresponsive-console-issue-on-connectVM-Cloud.html.md similarity index 78% rename from docs/cloud/How-to-fix-unresponsive-console-issue-on-3Engines-Cloud.html.md rename to docs/cloud/How-to-fix-unresponsive-console-issue-on-connectVM-Cloud.html.md index 2f44b54..ee3cccf 100644 --- a/docs/cloud/How-to-fix-unresponsive-console-issue-on-3Engines-Cloud.html.md +++ b/docs/cloud/How-to-fix-unresponsive-console-issue-on-connectVM-Cloud.html.md @@ -1,9 +1,9 @@ -How to fix unresponsive console issue on 3Engines Cloud[🔗](#how-to-fix-unresponsive-console-issue-on-brand-name "Permalink to this headline") +How to fix unresponsive console issue on connectVM Cloud[🔗](#how-to-fix-unresponsive-console-issue-on-brand-name "Permalink to this headline") =============================================================================================================================================== When you create a new virtual machine, the first thing you might want to do is to have a look at the console panel and check whether the instance has booted correctly. -After opening up the console in 3Engines you might encounter this error: +After opening up the console in connectVM you might encounter this error: * unresponsive grey screen * document icon in the down-right corner which informs about the issue on client side diff --git a/docs/cloud/How-to-generate-ec2-credentials-on-3Engines-Cloud.html.md b/docs/cloud/How-to-generate-ec2-credentials-on-3Engines-Cloud.html.md deleted file mode 100644 index 9fcbab7..0000000 --- a/docs/cloud/How-to-generate-ec2-credentials-on-3Engines-Cloud.html.md +++ /dev/null @@ -1,24 +0,0 @@ -How to generate and manage EC2 credentials on 3Engines Cloud[🔗](#how-to-generate-and-manage-ec2-credentials-on-brand-name "Permalink to this headline") -========================================================================================================================================================= - -EC2 credentials are used for accessing private S3 buckets on 3Engines Cloud cloud. This article covers how to generate and manage a pair of EC2 credentials so that you will be able to mount those buckets both - -> * on your virtual machines and -> * on your local computers. - -Warning - -A pair of EC2 credentials usually provides access to secret data so share it only with trusted individuals. - -Prerequisites[🔗](#prerequisites "Permalink to this headline") -------------------------------------------------------------- - -No. 1 **Hosting** - -You need a 3Engines Cloud hosting account with access to Horizon interface: - -No. 2 **3Engines CLI client installed and configured** - -You need to have the 3Engines CLI operational. - -First, it must be installed. You have several options, such as: \ No newline at end of file diff --git a/docs/cloud/How-to-generate-ec2-credentials-on-connectVM-Cloud.html.md b/docs/cloud/How-to-generate-ec2-credentials-on-connectVM-Cloud.html.md new file mode 100644 index 0000000..13f4f98 --- /dev/null +++ b/docs/cloud/How-to-generate-ec2-credentials-on-connectVM-Cloud.html.md @@ -0,0 +1,24 @@ +How to generate and manage EC2 credentials on connectVM Cloud[🔗](#how-to-generate-and-manage-ec2-credentials-on-brand-name "Permalink to this headline") +========================================================================================================================================================= + +EC2 credentials are used for accessing private S3 buckets on connectVM Cloud cloud. This article covers how to generate and manage a pair of EC2 credentials so that you will be able to mount those buckets both + +> * on your virtual machines and +> * on your local computers. + +Warning + +A pair of EC2 credentials usually provides access to secret data so share it only with trusted individuals. + +Prerequisites[🔗](#prerequisites "Permalink to this headline") +------------------------------------------------------------- + +No. 1 **Hosting** + +You need a connectVM Cloud hosting account with access to Horizon interface: + +No. 2 **connectVM CLI client installed and configured** + +You need to have the connectVM CLI operational. + +First, it must be installed. You have several options, such as: \ No newline at end of file diff --git a/docs/cloud/How-to-generate-or-use-Application-Credentials-via-CLI-on-3Engines-Cloud.html.md b/docs/cloud/How-to-generate-or-use-Application-Credentials-via-CLI-on-connectVM-Cloud.html.md similarity index 76% rename from docs/cloud/How-to-generate-or-use-Application-Credentials-via-CLI-on-3Engines-Cloud.html.md rename to docs/cloud/How-to-generate-or-use-Application-Credentials-via-CLI-on-connectVM-Cloud.html.md index f8df9be..93bcd7f 100644 --- a/docs/cloud/How-to-generate-or-use-Application-Credentials-via-CLI-on-3Engines-Cloud.html.md +++ b/docs/cloud/How-to-generate-or-use-Application-Credentials-via-CLI-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How to generate or use Application Credentials via CLI on 3Engines Cloud[🔗](#how-to-generate-or-use-application-credentials-via-cli-on-brand-name "Permalink to this headline") +How to generate or use Application Credentials via CLI on connectVM Cloud[🔗](#how-to-generate-or-use-application-credentials-via-cli-on-brand-name "Permalink to this headline") ================================================================================================================================================================================= You can authenticate your applications to *keystone* by creating application credentials for them. It is also possible to delegate a subset of role assignments on a project to an application credential, granting the same or restricted authorization to a project for the app. @@ -10,24 +10,24 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . No. 2 **Authenticate** -Once you have installed this piece of software, you need to authenticate to start using it: [How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md) +Once you have installed this piece of software, you need to authenticate to start using it: [How to activate connectVM CLI access to connectVM Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-connectVM-CLI-access-to-connectVM-Cloud-cloud-using-one-or-two-factor-authentication.html.md) -No. 3 **3EnginesClient installed and available** +No. 3 **connectVMClient installed and available** -3Engines is written in Python, it is recommended to use a dedicated virtual environment for the rest of this article. +connectVM is written in Python, it is recommended to use a dedicated virtual environment for the rest of this article. Install GitBash on Windows -: [How to install 3EnginesClient GitBash for Windows on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-GitBash-or-Cygwin-for-Windows-on-3Engines-Cloud.html.md). +: [How to install connectVMClient GitBash for Windows on connectVM Cloud](../connectVMcli/How-to-install-connectVMClient-GitBash-or-Cygwin-for-Windows-on-connectVM-Cloud.html.md). Install and run WSL (Linux under Windows) -: [How to install 3EnginesClient on Windows using Windows Subsystem for Linux on 3Engines Cloud 3Engines Hosting](../3Enginescli/How-to-install-3EnginesClient-on-Windows-using-Windows-Subsystem-for-Linux-on-3Engines-Cloud-3Engines-Hosting.html.md). +: [How to install connectVMClient on Windows using Windows Subsystem for Linux on connectVM Cloud connectVM Hosting](../connectVMcli/How-to-install-connectVMClient-on-Windows-using-Windows-Subsystem-for-Linux-on-connectVM-Cloud-connectVM-Hosting.html.md). -Install 3EnginesClient on Linux -: [How to install 3EnginesClient for Linux on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md). +Install connectVMClient on Linux +: [How to install connectVMClient for Linux on connectVM Cloud](../connectVMcli/How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md). No. 4 **jq installed and running** @@ -46,7 +46,7 @@ Step 1 CLI Commands for Application Credentials[🔗](#step-1-cli-commands-for-a Command ``` -3Engines application credential +connectVM application credential ``` @@ -63,7 +63,7 @@ application credential show To see the parameters for these commands, end them with **--help**, like this: ``` -3Engines application credential create --help +connectVM application credential create --help ``` @@ -81,7 +81,7 @@ Step 2 The Simplest Way to Create a New Application Credential[🔗](#step-2-the The simplest way to generate a new application credential is just to define the name – the rest of the parameters will be defined automatically for you. The following command uses name **cred2**: ``` -3Engines application credential create cred2 +connectVM application credential create cred2 ``` @@ -109,7 +109,7 @@ _member_ magnum_user load-balancer_member heat_stack_owner creator k8s_admin Note -Role **\_member\_** is the most basic role and should always be present. Beware however, as in some variations of 3Engines it can be called **member** instead of **\_member\_**. +Role **\_member\_** is the most basic role and should always be present. Beware however, as in some variations of connectVM it can be called **member** instead of **\_member\_**. **--expiration** @@ -134,7 +134,7 @@ By default, for security reasons, application credentials are forbidden from bei Here is a complete example, using all of the available parameters to create a new application credential: ``` -3Engines application credential create foo-dev-member4 --role _member_ --expiration $(date +"%Y-11-%dT%H:%M:%S") --description "Test application credentials" --unrestricted -c id -c secret -f json | jq -r '"application_credential_id: \"" + .id + "\"", "application_credential_secret: \"" + .secret + "\""' +connectVM application credential create foo-dev-member4 --role _member_ --expiration $(date +"%Y-11-%dT%H:%M:%S") --description "Test application credentials" --unrestricted -c id -c secret -f json | jq -r '"application_credential_id: \"" + .id + "\"", "application_credential_secret: \"" + .secret + "\""' ``` @@ -147,7 +147,7 @@ The name of the new application credential will be **foo-dev-member4**, will be Step 4 Enter id and secret into clouds.yml[🔗](#step-4-enter-id-and-secret-into-clouds-yml "Permalink to this headline") ----------------------------------------------------------------------------------------------------------------------- -You are now going to store the values of **id** and **secret** that the cloud has sent to you. Once stored, future **3Engines** commands will use these value to authenticate to the cloud without using any kind of password. +You are now going to store the values of **id** and **secret** that the cloud has sent to you. Once stored, future **connectVM** commands will use these value to authenticate to the cloud without using any kind of password. The place to store *id* and *secret* is a file called *clouds.yml*. It may reside on your local computer in one of these three locations: @@ -159,14 +159,14 @@ Current directory The current directory is searched first. User configuration directory -: **$HOME/.config/3Engines/clouds.yml** +: **$HOME/.config/connectVM/clouds.yml** The most common default location for individual users. Searched after the current directory. System-wide configuration directory -: **/etc/3Engines/clouds.yml** +: **/etc/connectVM/clouds.yml** Searches that location as the last resort. @@ -181,7 +181,7 @@ The contents of the *clouds.yml* file will be in *yaml* format. It is customary Let us create a new application credential called *trial-member\_creatornew*. ``` -3Engines application credential create trial-member_creatornew --unrestricted -c id -c secret -f json | jq -r '"application_credential_id: \"" + .id + "\"", "application_credential_secret: \"" + .secret + "\""' +connectVM application credential create trial-member_creatornew --unrestricted -c id -c secret -f json | jq -r '"application_credential_id: \"" + .id + "\"", "application_credential_secret: \"" + .secret + "\""' ``` @@ -192,7 +192,7 @@ This is the result: Now create the *clouds.yml* file using your preferred editor of choice. Here it is *nano*: ``` -nano $HOME/.config/3Engines/clouds.yml +nano $HOME/.config/connectVM/clouds.yml ``` @@ -205,7 +205,7 @@ clouds: trial-member_creatornew: auth_type: "v3applicationcredential" auth: - auth_url: https://keystone.3Engines.com:5000/v3 + auth_url: https://keystone.connectVM.com:5000/v3 application_credential_id: "a582edb593644106baeaa75fd706feb2" application_credential_secret: "mPKQort71xi7Ros7BHb1sG4753wvN_tmJMBd1aRBBGzgFZM7AoUkLWzCutQuh-dAyac86-rkikYqqYaT1_f0hA" @@ -217,7 +217,7 @@ Let us dissect that file line by line: > * **trial-member\_creatornew** is the name of the application credential used in the previous *credential create* command. > * **v3applicationcredential** is the type of auth connection (it is always the same) > * **auth** start of *auth* parameters -> * **auth\_url** the address to call on the 3Engines Cloud 3Engines server (it always the same) +> * **auth\_url** the address to call on the connectVM Cloud connectVM server (it always the same) > * **application\_credential\_id** the value from the previous call of *credential create* command > * **credential create** command the value from the previous call of *credential create* command @@ -254,7 +254,7 @@ It works. You can also use that parameter in the command line, like this: ``` -3Engines --os-cloud=trial-member_creatornew flavor list +connectVM --os-cloud=trial-member_creatornew flavor list ``` @@ -262,7 +262,7 @@ It works as well: ![cli_os_cloud.png](../_images/cli_os_cloud.png) -You have to set up **OS\_CLOUD** once per opening a new terminal window and then you can use **3Engines** command without interpolating **--os-cloud** parameter all the time. +You have to set up **OS\_CLOUD** once per opening a new terminal window and then you can use **connectVM** command without interpolating **--os-cloud** parameter all the time. If you had two or more clouds defined in the *clouds.yml* file, then using **--os-cloud** in the command line would be more flexible. @@ -299,8 +299,8 @@ What To Do Next[🔗](#what-to-do-next "Permalink to this headline") Here are some articles that use application credentials: -[How to install Rancher RKE2 Kubernetes on 3Engines Cloud](../kubernetes/How-to-install-Rancher-RKE2-Kubernetes-on-3Engines-Cloud-cloud.html.md) +[How to install Rancher RKE2 Kubernetes on connectVM Cloud](../kubernetes/How-to-install-Rancher-RKE2-Kubernetes-on-connectVM-Cloud-cloud.html.md) -[Configuring IP Whitelisting for 3Engines Load Balancer using Terraform on 3Engines Cloud](../kubernetes/Configuring-IP-Whitelisting-for-3Engines-Load-Balancer-using-Terraform-on-3Engines-Cloud.html.md) +[Configuring IP Whitelisting for connectVM Load Balancer using Terraform on connectVM Cloud](../kubernetes/Configuring-IP-Whitelisting-for-connectVM-Load-Balancer-using-Terraform-on-connectVM-Cloud.html.md) -[3Engines User Roles on 3Engines Cloud](3Engines-user-roles-on-3Engines-Cloud.html.md) \ No newline at end of file +[connectVM User Roles on connectVM Cloud](connectVM-user-roles-on-connectVM-Cloud.html.md) \ No newline at end of file diff --git a/docs/cloud/How-to-install-Python-virtualenv-or-virtualenvwrapper-on-3Engines-Cloud.html.md b/docs/cloud/How-to-install-Python-virtualenv-or-virtualenvwrapper-on-connectVM-Cloud.html.md similarity index 96% rename from docs/cloud/How-to-install-Python-virtualenv-or-virtualenvwrapper-on-3Engines-Cloud.html.md rename to docs/cloud/How-to-install-Python-virtualenv-or-virtualenvwrapper-on-connectVM-Cloud.html.md index 79cefda..3adcdb2 100644 --- a/docs/cloud/How-to-install-Python-virtualenv-or-virtualenvwrapper-on-3Engines-Cloud.html.md +++ b/docs/cloud/How-to-install-Python-virtualenv-or-virtualenvwrapper-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How to install Python virtualenv or virtualenvwrapper on 3Engines Cloud[🔗](#how-to-install-python-virtualenv-or-virtualenvwrapper-on-brand-name "Permalink to this headline") +How to install Python virtualenv or virtualenvwrapper on connectVM Cloud[🔗](#how-to-install-python-virtualenv-or-virtualenvwrapper-on-brand-name "Permalink to this headline") =============================================================================================================================================================================== Virtualenv is a tool with which you are able to create isolated Python environments. It is mainly used to get rid of problems with dependencies and versions. diff --git a/docs/cloud/How-to-start-a-VM-from-a-snapshot-on-3Engines-Cloud.html.md b/docs/cloud/How-to-start-a-VM-from-a-snapshot-on-connectVM-Cloud.html.md similarity index 86% rename from docs/cloud/How-to-start-a-VM-from-a-snapshot-on-3Engines-Cloud.html.md rename to docs/cloud/How-to-start-a-VM-from-a-snapshot-on-connectVM-Cloud.html.md index d8d15ea..3148e3b 100644 --- a/docs/cloud/How-to-start-a-VM-from-a-snapshot-on-3Engines-Cloud.html.md +++ b/docs/cloud/How-to-start-a-VM-from-a-snapshot-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How to start a VM from a snapshot on 3Engines Cloud[🔗](#how-to-start-a-vm-from-a-snapshot-on-brand-name "Permalink to this headline") +How to start a VM from a snapshot on connectVM Cloud[🔗](#how-to-start-a-vm-from-a-snapshot-on-brand-name "Permalink to this headline") ======================================================================================================================================= a) Volume Snapshot[🔗](#a-volume-snapshot "Permalink to this headline") @@ -32,7 +32,7 @@ a) Volume Snapshot[🔗](#a-volume-snapshot "Permalink to this headline") ![snap7.png](../_images/snap7.png) -8. The rest of procedure is the same: [How to create new Linux VM in 3Engines Dashboard Horizon on 3Engines Cloud](How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md). +8. The rest of procedure is the same: [How to create new Linux VM in connectVM Dashboard Horizon on connectVM Cloud](How-to-create-new-Linux-VM-in-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md). 9. Newly created machine is visible in the Instances list. @@ -66,7 +66,7 @@ In the “Images” you may also find symbolic links to the volume snapshots.(i. ![snap5.png](../_images/snap5.png) -6. The rest of procedure is the same: [How to create new Linux VM in 3Engines Dashboard Horizon on 3Engines Cloud](How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md). +6. The rest of procedure is the same: [How to create new Linux VM in connectVM Dashboard Horizon on connectVM Cloud](How-to-create-new-Linux-VM-in-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md). 7. Virtual machine has been created. diff --git a/docs/cloud/How-to-start-a-VM-from-instance-snapshot-using-Horizon-dashboard-on-3Engines-Cloud.html.md b/docs/cloud/How-to-start-a-VM-from-instance-snapshot-using-Horizon-dashboard-on-connectVM-Cloud.html.md similarity index 70% rename from docs/cloud/How-to-start-a-VM-from-instance-snapshot-using-Horizon-dashboard-on-3Engines-Cloud.html.md rename to docs/cloud/How-to-start-a-VM-from-instance-snapshot-using-Horizon-dashboard-on-connectVM-Cloud.html.md index c9feee7..24d1f39 100644 --- a/docs/cloud/How-to-start-a-VM-from-instance-snapshot-using-Horizon-dashboard-on-3Engines-Cloud.html.md +++ b/docs/cloud/How-to-start-a-VM-from-instance-snapshot-using-Horizon-dashboard-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How to start a VM from instance snapshot using Horizon dashboard on 3Engines Cloud[🔗](#how-to-start-a-vm-from-instance-snapshot-using-horizon-dashboard-on-brand-name "Permalink to this headline") +How to start a VM from instance snapshot using Horizon dashboard on connectVM Cloud[🔗](#how-to-start-a-vm-from-instance-snapshot-using-horizon-dashboard-on-brand-name "Permalink to this headline") ===================================================================================================================================================================================================== In this article, you will learn how to create a virtual machine from an instance snapshot using Horizon dashboard. @@ -8,11 +8,11 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Ephemeral storage vs. persistent storage** -Please see article [Ephemeral vs Persistent storage option Create New Volume on 3Engines Cloud](../datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-3Engines-Cloud.html.md) to understand the basic difference between ephemeral and persistent types of storage in 3Engines. +Please see article [Ephemeral vs Persistent storage option Create New Volume on connectVM Cloud](../datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-connectVM-Cloud.html.md) to understand the basic difference between ephemeral and persistent types of storage in connectVM. No. 3 **Instance snapshot** diff --git a/docs/cloud/How-to-transfer-volumes-between-domains-and-projects-using-Horizon-dashboard-on-3Engines-Cloud.html.md b/docs/cloud/How-to-transfer-volumes-between-domains-and-projects-using-Horizon-dashboard-on-connectVM-Cloud.html.md similarity index 89% rename from docs/cloud/How-to-transfer-volumes-between-domains-and-projects-using-Horizon-dashboard-on-3Engines-Cloud.html.md rename to docs/cloud/How-to-transfer-volumes-between-domains-and-projects-using-Horizon-dashboard-on-connectVM-Cloud.html.md index f32e4b2..6b9c4ba 100644 --- a/docs/cloud/How-to-transfer-volumes-between-domains-and-projects-using-Horizon-dashboard-on-3Engines-Cloud.html.md +++ b/docs/cloud/How-to-transfer-volumes-between-domains-and-projects-using-Horizon-dashboard-on-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -How to transfer volumes between domains and projects using Horizon dashboard on 3Engines Cloud[🔗](#how-to-transfer-volumes-between-domains-and-projects-using-horizon-dashboard-on-brand-name "Permalink to this headline") +How to transfer volumes between domains and projects using Horizon dashboard on connectVM Cloud[🔗](#how-to-transfer-volumes-between-domains-and-projects-using-horizon-dashboard-on-brand-name "Permalink to this headline") ============================================================================================================================================================================================================================= -Volumes in 3Engines can be used to store data. They are visible to virtual machines like drives. +Volumes in connectVM can be used to store data. They are visible to virtual machines like drives. Such a volume is usually available to just the project in which it was created. Transferring data stored on it between projects might take a long time, especially if such a volume contains lots of data, like, say, hundreds or thousands of gigabytes (or even more). @@ -21,7 +21,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: +You need a connectVM Cloud hosting account with access to the Horizon interface: No. 2 **Volume** @@ -33,7 +33,7 @@ You can check the status of your volume in the **Volumes -> Volumes** section of ![transfer-volume-between-projects-horizon-32_creodias.png](../_images/transfer-volume-between-projects-horizon-32_creodias.png) -The following article includes information how to disconnect a volume from a virtual machine: [How to move data volume between two VMs using 3Engines Horizon on 3Engines Cloud](../datavolume/How-to-move-data-volume-between-two-VMs-using-3Engines-Horizon-on-3Engines-Cloud.html.md) +The following article includes information how to disconnect a volume from a virtual machine: [How to move data volume between two VMs using connectVM Horizon on connectVM Cloud](../datavolume/How-to-move-data-volume-between-two-VMs-using-connectVM-Horizon-on-connectVM-Cloud.html.md) No. 4 **Ability to perform operations on both the source project and the destination project** @@ -141,6 +141,6 @@ After cancelling, your volume should now once again have status **Available**: What To Do Next[🔗](#what-to-do-next "Permalink to this headline") ----------------------------------------------------------------- -Now that the volume has been transferred, you might want to connect it to a virtual machine. This article includes information how to do that: [How to move data volume between two VMs using 3Engines Horizon on 3Engines Cloud](../datavolume/How-to-move-data-volume-between-two-VMs-using-3Engines-Horizon-on-3Engines-Cloud.html.md) +Now that the volume has been transferred, you might want to connect it to a virtual machine. This article includes information how to do that: [How to move data volume between two VMs using connectVM Horizon on connectVM Cloud](../datavolume/How-to-move-data-volume-between-two-VMs-using-connectVM-Horizon-on-connectVM-Cloud.html.md) -The workflow described in this article can also be done using the 3Engines CLI. Learn more here: [How to transfer volumes between domains and projects using 3Engines CLI client on 3Engines Cloud](../3Enginescli/How-to-transfer-volumes-between-domains-and-projects-using-3Engines-CLI-client-on-3Engines-Cloud.html.md) \ No newline at end of file +The workflow described in this article can also be done using the connectVM CLI. Learn more here: [How to transfer volumes between domains and projects using connectVM CLI client on connectVM Cloud](../connectVMcli/How-to-transfer-volumes-between-domains-and-projects-using-connectVM-CLI-client-on-connectVM-Cloud.html.md) \ No newline at end of file diff --git a/docs/cloud/How-to-upload-custom-image-to-3Engines-Cloud-cloud-using-3Engines-Horizon-dashboard.html.md b/docs/cloud/How-to-upload-custom-image-to-connectVM-Cloud-cloud-using-connectVM-Horizon-dashboard.html.md similarity index 63% rename from docs/cloud/How-to-upload-custom-image-to-3Engines-Cloud-cloud-using-3Engines-Horizon-dashboard.html.md rename to docs/cloud/How-to-upload-custom-image-to-connectVM-Cloud-cloud-using-connectVM-Horizon-dashboard.html.md index 8217956..653a6f8 100644 --- a/docs/cloud/How-to-upload-custom-image-to-3Engines-Cloud-cloud-using-3Engines-Horizon-dashboard.html.md +++ b/docs/cloud/How-to-upload-custom-image-to-connectVM-Cloud-cloud-using-connectVM-Horizon-dashboard.html.md @@ -1,12 +1,12 @@ -How to upload custom image to 3Engines Cloud cloud using 3Engines Horizon dashboard[🔗](#how-to-upload-custom-image-to-brand-name-cloud-using-3Engines-horizon-dashboard "Permalink to this headline") +How to upload custom image to connectVM Cloud cloud using connectVM Horizon dashboard[🔗](#how-to-upload-custom-image-to-brand-name-cloud-using-connectVM-horizon-dashboard "Permalink to this headline") ========================================================================================================================================================================================================= -In this tutorial, you will upload custom image stored on your local computer to 3Engines Cloud cloud, using the Horizon Dashboard. The uploaded image will be available within your project alongside default images from 3Engines Cloud cloud and you will be able to create virtual machines using it. +In this tutorial, you will upload custom image stored on your local computer to connectVM Cloud cloud, using the Horizon Dashboard. The uploaded image will be available within your project alongside default images from connectVM Cloud cloud and you will be able to create virtual machines using it. What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- -> * How to check for the presence of image in 3Engines Cloud cloud +> * How to check for the presence of image in connectVM Cloud cloud > * How different images might behave > * How to upload an image using Horizon dashboard > * Example: how to upload image for Debian 11 @@ -17,7 +17,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Custom image you wish to upload** @@ -35,8 +35,8 @@ The following container formats are supported: > | aki | ami | ari | bare | > | docker | ova | ovf | | -For the explanation of these formats, see article [What Image Formats are Available in 3Engines 3Engines Cloud cloud](What-Image-Formats-are-available-in-3Engines-3Engines-Cloud-Cloud.html.md). +For the explanation of these formats, see article [What Image Formats are Available in connectVM connectVM Cloud cloud](What-Image-Formats-are-available-in-connectVM-connectVM-Cloud-Cloud.html.md). No. 3 **Uploaded public SSH key** -If the image you wish to upload requires you to attach an SSH public key while creating the virtual machine, the key will need to be uploaded to 3Engines Cloud cloud. One of these articles should help: \ No newline at end of file +If the image you wish to upload requires you to attach an SSH public key while creating the virtual machine, the key will need to be uploaded to connectVM Cloud cloud. One of these articles should help: \ No newline at end of file diff --git a/docs/cloud/How-to-upload-your-custom-image-using-3Engines-CLI-on-3Engines-Cloud.html.md b/docs/cloud/How-to-upload-your-custom-image-using-connectVM-CLI-on-connectVM-Cloud.html.md similarity index 52% rename from docs/cloud/How-to-upload-your-custom-image-using-3Engines-CLI-on-3Engines-Cloud.html.md rename to docs/cloud/How-to-upload-your-custom-image-using-connectVM-CLI-on-connectVM-Cloud.html.md index 474b6ef..d109e08 100644 --- a/docs/cloud/How-to-upload-your-custom-image-using-3Engines-CLI-on-3Engines-Cloud.html.md +++ b/docs/cloud/How-to-upload-your-custom-image-using-connectVM-CLI-on-connectVM-Cloud.html.md @@ -1,12 +1,12 @@ -How to upload your custom image using 3Engines CLI on 3Engines Cloud[🔗](#how-to-upload-your-custom-image-using-3Engines-cli-on-brand-name "Permalink to this headline") +How to upload your custom image using connectVM CLI on connectVM Cloud[🔗](#how-to-upload-your-custom-image-using-connectVM-cli-on-brand-name "Permalink to this headline") =========================================================================================================================================================================== -In this tutorial, you will upload custom image stored on your local computer to 3Engines Cloud cloud, using the 3Engines CLI client. The uploaded image will be available within your project alongside default images from 3Engines Cloud cloud and you will be able to create virtual machines using it. +In this tutorial, you will upload custom image stored on your local computer to connectVM Cloud cloud, using the connectVM CLI client. The uploaded image will be available within your project alongside default images from connectVM Cloud cloud and you will be able to create virtual machines using it. What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- -> * How to check for the presence of the image in your 3Engines cloud +> * How to check for the presence of the image in your connectVM cloud > * How different images might behave > * How to upload the image using only CLI commands > * Example: how to upload image for Debian 11 @@ -17,11 +17,11 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . -No. 2 **3Engines CLI configured** +No. 2 **connectVM CLI configured** -You need to have the 3Engines CLI client configured and operational. See [How to install 3EnginesClient for Linux on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md). You can test whether your 3Engines CLI is properly activated by executing the **3Engines server list** command mentioned in the end of that article - it should return the list of your virtual machines. +You need to have the connectVM CLI client configured and operational. See [How to install connectVMClient for Linux on connectVM Cloud](../connectVMcli/How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md). You can test whether your connectVM CLI is properly activated by executing the **connectVM server list** command mentioned in the end of that article - it should return the list of your virtual machines. No. 3 **Custom image you wish to upload** @@ -39,8 +39,8 @@ The following container formats are supported: > | aki | ami | ari | bare | > | docker | ova | ovf | | -For the explanation of these formats, see article [What Image Formats are Available in 3Engines 3Engines Cloud cloud](What-Image-Formats-are-available-in-3Engines-3Engines-Cloud-Cloud.html.md). +For the explanation of these formats, see article [What Image Formats are Available in connectVM connectVM Cloud cloud](What-Image-Formats-are-available-in-connectVM-connectVM-Cloud-Cloud.html.md). No. 4 **Uploaded public SSH key** -If the image you wish to upload requires you to attach an SSH public key while creating the virtual machine, the key will need to be uploaded to 3Engines Cloud cloud. One of these articles should help: \ No newline at end of file +If the image you wish to upload requires you to attach an SSH public key while creating the virtual machine, the key will need to be uploaded to connectVM Cloud cloud. One of these articles should help: \ No newline at end of file diff --git a/docs/cloud/How-to-use-Docker-on-3Engines-Cloud.html.md b/docs/cloud/How-to-use-Docker-on-connectVM-Cloud.html.md similarity index 100% rename from docs/cloud/How-to-use-Docker-on-3Engines-Cloud.html.md rename to docs/cloud/How-to-use-Docker-on-connectVM-Cloud.html.md diff --git a/docs/cloud/How-to-use-GUI-in-Linux-VM-on-3Engines-Cloud-and-access-it-from-local-Linux-computer.html.md b/docs/cloud/How-to-use-GUI-in-Linux-VM-on-connectVM-Cloud-and-access-it-from-local-Linux-computer.html.md similarity index 92% rename from docs/cloud/How-to-use-GUI-in-Linux-VM-on-3Engines-Cloud-and-access-it-from-local-Linux-computer.html.md rename to docs/cloud/How-to-use-GUI-in-Linux-VM-on-connectVM-Cloud-and-access-it-from-local-Linux-computer.html.md index f6b2d5d..8cdda78 100644 --- a/docs/cloud/How-to-use-GUI-in-Linux-VM-on-3Engines-Cloud-and-access-it-from-local-Linux-computer.html.md +++ b/docs/cloud/How-to-use-GUI-in-Linux-VM-on-connectVM-Cloud-and-access-it-from-local-Linux-computer.html.md @@ -1,7 +1,7 @@ -How to Use GUI in Linux VM on 3Engines Cloud and access it From Local Linux Computer[🔗](#how-to-use-gui-in-linux-vm-on-brand-name-and-access-it-from-local-linux-computer "Permalink to this headline") +How to Use GUI in Linux VM on connectVM Cloud and access it From Local Linux Computer[🔗](#how-to-use-gui-in-linux-vm-on-brand-name-and-access-it-from-local-linux-computer "Permalink to this headline") ========================================================================================================================================================================================================= -In this article you will learn how to use GUI (graphical user interface) on a Linux virtual machine running on 3Engines Cloud cloud. +In this article you will learn how to use GUI (graphical user interface) on a Linux virtual machine running on connectVM Cloud cloud. For this purpose, you will install and use **X2Go** on your local Linux computer. @@ -20,7 +20,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Linux installed on your local computer** @@ -28,9 +28,9 @@ You need to have a local computer with Linux installed. This article was written No. 3 **Linux virtual machine** -You need a Linux virtual machine running on 3Engines Cloud cloud. You need to able to access it via SSH. The following article explains how to create one such virtual machine: +You need a Linux virtual machine running on connectVM Cloud cloud. You need to able to access it via SSH. The following article explains how to create one such virtual machine: -[How to create a Linux VM and access it from Linux command line on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md) +[How to create a Linux VM and access it from Linux command line on connectVM Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md) This article was written for virtual machines using a default Ubuntu 20.04 image on cloud. Adjust the instructions from this article accordingly if your virtual machine has a different Linux distribution. diff --git a/docs/cloud/How-to-use-Security-Groups-in-Horizon-on-3Engines-Cloud.html.md b/docs/cloud/How-to-use-Security-Groups-in-Horizon-on-connectVM-Cloud.html.md similarity index 94% rename from docs/cloud/How-to-use-Security-Groups-in-Horizon-on-3Engines-Cloud.html.md rename to docs/cloud/How-to-use-Security-Groups-in-Horizon-on-connectVM-Cloud.html.md index 4868eb0..f863933 100644 --- a/docs/cloud/How-to-use-Security-Groups-in-Horizon-on-3Engines-Cloud.html.md +++ b/docs/cloud/How-to-use-Security-Groups-in-Horizon-on-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -How to use Security Groups in Horizon on 3Engines Cloud[🔗](#how-to-use-security-groups-in-horizon-on-brand-name "Permalink to this headline") +How to use Security Groups in Horizon on connectVM Cloud[🔗](#how-to-use-security-groups-in-horizon-on-brand-name "Permalink to this headline") =============================================================================================================================================== -Security groups in **3Engines** are used to filter the Internet traffic coming **to** and **from** your virtual machines. They consist of security rules and can be attached to your virtual machines during and after the creation of the machines. +Security groups in **connectVM** are used to filter the Internet traffic coming **to** and **from** your virtual machines. They consist of security rules and can be attached to your virtual machines during and after the creation of the machines. By default, each instance has a rule which blocks all incoming Internet traffic and allows all outgoing traffic. To modify those settings, you can apply other security groups to it. @@ -10,7 +10,7 @@ Viewing the security groups[🔗](#viewing-the-security-groups "Permalink to thi To check your current security groups, please follow these steps: -Log in to your 3Engines Cloud account: . +Log in to your connectVM Cloud account: . In the panel on the left choose **Network** and then **Security Groups**. diff --git a/docs/cloud/Resizing-a-virtual-machine-using-3Engines-Horizon-on-3Engines-Cloud.html.md b/docs/cloud/Resizing-a-virtual-machine-using-connectVM-Horizon-on-connectVM-Cloud.html.md similarity index 78% rename from docs/cloud/Resizing-a-virtual-machine-using-3Engines-Horizon-on-3Engines-Cloud.html.md rename to docs/cloud/Resizing-a-virtual-machine-using-connectVM-Horizon-on-connectVM-Cloud.html.md index d9b0f2f..c34c05c 100644 --- a/docs/cloud/Resizing-a-virtual-machine-using-3Engines-Horizon-on-3Engines-Cloud.html.md +++ b/docs/cloud/Resizing-a-virtual-machine-using-connectVM-Horizon-on-connectVM-Cloud.html.md @@ -1,10 +1,10 @@ -Resizing a virtual machine using 3Engines Horizon on 3Engines Cloud[🔗](#resizing-a-virtual-machine-using-3Engines-horizon-on-brand-name "Permalink to this headline") +Resizing a virtual machine using connectVM Horizon on connectVM Cloud[🔗](#resizing-a-virtual-machine-using-connectVM-horizon-on-brand-name "Permalink to this headline") ========================================================================================================================================================================= Introduction[🔗](#introduction "Permalink to this headline") ----------------------------------------------------------- -When creating a new virtual machine under 3Engines, one of the options you choose is the *flavor*. A flavor is a predefined combination of CPU, memory and disk size and there usually is a number of such flavors for you to choose from. +When creating a new virtual machine under connectVM, one of the options you choose is the *flavor*. A flavor is a predefined combination of CPU, memory and disk size and there usually is a number of such flavors for you to choose from. After the instance is spawned, it is possible to change one flavor for another, and that process is called *resizing*. You might want to resize an already existing VM in order to: @@ -14,32 +14,32 @@ After the instance is spawned, it is possible to change one flavor for another, > * seamlessly transition from testing to production environment, > * change application workload byt scaling the VM up or down. -In this article, we are going to resize VMs using commands in 3Engines Horizon. +In this article, we are going to resize VMs using commands in connectVM Horizon. Prerequisites[🔗](#prerequisites "Permalink to this headline") ------------------------------------------------------------- No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **How to create a new VM** -If you are a normal user of 3Engines Cloud hosting, you will have all prerogatives needed to resize the VM. Make sure that the VM you are about to resize belongs to a project you have access to. Here are the basics of creating a Linux VM in Horizon: +If you are a normal user of connectVM Cloud hosting, you will have all prerogatives needed to resize the VM. Make sure that the VM you are about to resize belongs to a project you have access to. Here are the basics of creating a Linux VM in Horizon: -[How to create a Linux VM and access it from Linux command line on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md) +[How to create a Linux VM and access it from Linux command line on connectVM Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md) -[How to create a Linux VM and access it from Windows desktop on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md) +[How to create a Linux VM and access it from Windows desktop on connectVM Cloud](How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-connectVM-Cloud.html.md) No. 3 **Awareness of existing quotas and flavors limits** -For general introduction to quotas and flavors, see [Dashboard Overview – Project Quotas And Flavors Limits on 3Engines Cloud](Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-3Engines-Cloud.html.md). +For general introduction to quotas and flavors, see [Dashboard Overview – Project Quotas And Flavors Limits on connectVM Cloud](Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-connectVM-Cloud.html.md). Also: > * The VM you want to resize is in an active or shut down state. > * A flavor with the desired resource configuration exists. -> * Adequate resources are available in your 3Engines environment to accommodate the resize. +> * Adequate resources are available in your connectVM environment to accommodate the resize. Creating a new VM[🔗](#creating-a-new-vm "Permalink to this headline") --------------------------------------------------------------------- @@ -131,4 +131,4 @@ In this case, the sizes of the disk before and after the resizing do not match. What To Do Next[🔗](#what-to-do-next "Permalink to this headline") ----------------------------------------------------------------- -You can also resize the virtual machine using only 3Engines CLI. More details here: [Resizing a virtual machine using 3Engines CLI on 3Engines Cloud](../3Enginescli/Resizing-a-virtual-machine-using-3Engines-CLI-on-3Engines-Cloud.html.md) \ No newline at end of file +You can also resize the virtual machine using only connectVM CLI. More details here: [Resizing a virtual machine using connectVM CLI on connectVM Cloud](../connectVMcli/Resizing-a-virtual-machine-using-connectVM-CLI-on-connectVM-Cloud.html.md) \ No newline at end of file diff --git a/docs/cloud/Spot-instances-on-3Engines-Cloud.html.md b/docs/cloud/Spot-instances-on-connectVM-Cloud.html.md similarity index 71% rename from docs/cloud/Spot-instances-on-3Engines-Cloud.html.md rename to docs/cloud/Spot-instances-on-connectVM-Cloud.html.md index e3ebe06..6c874d0 100644 --- a/docs/cloud/Spot-instances-on-3Engines-Cloud.html.md +++ b/docs/cloud/Spot-instances-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -Spot instances on 3Engines Cloud[🔗](#spot-instances-on-brand-name "Permalink to this headline") +Spot instances on connectVM Cloud[🔗](#spot-instances-on-brand-name "Permalink to this headline") ================================================================================================= Spot instance is resource similar to Amazon EC2 Spot Instances or Google Spot VMs. In short, user is provided with unused computational resources for a discounted price but those resources can be terminated on a short time notice whenever on-demand usage increases. The main use case are ephemeral workflows which can deal with being terminated unexpectedly and/or orchestration platforms which can deal with forced scaling down of available resources e.g. Kubernetes clusters. @@ -15,7 +15,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: +You need a connectVM Cloud hosting account with access to the Horizon interface: No. 2 **Available exclusively on WAW3-2 cloud** @@ -25,8 +25,8 @@ When using spot instances, be sure to work only on WAW3-2 cloud: No. 3 **Using quotas and flavors** -For quotas, see this article: [Dashboard Overview – Project Quotas And Flavors Limits on 3Engines Cloud](Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-3Engines-Cloud.html.md) +For quotas, see this article: [Dashboard Overview – Project Quotas And Flavors Limits on connectVM Cloud](Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-connectVM-Cloud.html.md) -No. 3 **3Engines CLI client** +No. 3 **connectVM CLI client** -If you want to interact with 3Engines Cloud cloud using 3Engines CLI client, you need to have it installed. Check one of these articles: \ No newline at end of file +If you want to interact with connectVM Cloud cloud using connectVM CLI client, you need to have it installed. Check one of these articles: \ No newline at end of file diff --git a/docs/cloud/Status-Power-State-and-dependences-in-billing-of-instances-VMs-on-3Engines-Cloud.html.md b/docs/cloud/Status-Power-State-and-dependences-in-billing-of-instances-VMs-on-connectVM-Cloud.html.md similarity index 93% rename from docs/cloud/Status-Power-State-and-dependences-in-billing-of-instances-VMs-on-3Engines-Cloud.html.md rename to docs/cloud/Status-Power-State-and-dependences-in-billing-of-instances-VMs-on-connectVM-Cloud.html.md index 700d9c4..27542d1 100644 --- a/docs/cloud/Status-Power-State-and-dependences-in-billing-of-instances-VMs-on-3Engines-Cloud.html.md +++ b/docs/cloud/Status-Power-State-and-dependences-in-billing-of-instances-VMs-on-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -Status Power State and dependencies in billing of instance VMs on 3Engines Cloud[🔗](#status-power-state-and-dependencies-in-billing-of-instance-vms-on-brand-name "Permalink to this headline") +Status Power State and dependencies in billing of instance VMs on connectVM Cloud[🔗](#status-power-state-and-dependencies-in-billing-of-instance-vms-on-brand-name "Permalink to this headline") ================================================================================================================================================================================================= -In 3Engines, instances have their own Status and Power State: +In connectVM, instances have their own Status and Power State: > * **Status** informs about the present condition of the VM, while > * **Power** states tell us only whether virtual machines are running or not. diff --git a/docs/cloud/VM-created-with-option-Create-New-Volume-No-on-3Engines-Cloud.html.md b/docs/cloud/VM-created-with-option-Create-New-Volume-No-on-connectVM-Cloud.html.md similarity index 77% rename from docs/cloud/VM-created-with-option-Create-New-Volume-No-on-3Engines-Cloud.html.md rename to docs/cloud/VM-created-with-option-Create-New-Volume-No-on-connectVM-Cloud.html.md index bf81845..4ab8f92 100644 --- a/docs/cloud/VM-created-with-option-Create-New-Volume-No-on-3Engines-Cloud.html.md +++ b/docs/cloud/VM-created-with-option-Create-New-Volume-No-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -VM created with option Create New Volume No on 3Engines Cloud[🔗](#vm-created-with-option-create-new-volume-no-on-brand-name "Permalink to this headline") +VM created with option Create New Volume No on connectVM Cloud[🔗](#vm-created-with-option-create-new-volume-no-on-brand-name "Permalink to this headline") =========================================================================================================================================================== During creation of a VM you can select a source. If you choose “Image”, you can then choose **Yes** or **No** for the option “**Create New Volume**”. @@ -13,7 +13,7 @@ The new Virtual Machine will be created with the System Volume (Root Disk) size ![volno3.png](../_images/volno3.png) -If you want to select a different size for the System Volume (Root Disk) please read article [VM created with option Create New Volume Yes on 3Engines Cloud](VM-created-with-option-Create-New-Volume-Yes-on-3Engines-Cloud.html.md). +If you want to select a different size for the System Volume (Root Disk) please read article [VM created with option Create New Volume Yes on connectVM Cloud](VM-created-with-option-Create-New-Volume-Yes-on-connectVM-Cloud.html.md). ![volno4.png](../_images/volno4.png) diff --git a/docs/cloud/VM-created-with-option-Create-New-Volume-Yes-on-3Engines-Cloud.html.md b/docs/cloud/VM-created-with-option-Create-New-Volume-Yes-on-connectVM-Cloud.html.md similarity index 93% rename from docs/cloud/VM-created-with-option-Create-New-Volume-Yes-on-3Engines-Cloud.html.md rename to docs/cloud/VM-created-with-option-Create-New-Volume-Yes-on-connectVM-Cloud.html.md index be92967..fc71321 100644 --- a/docs/cloud/VM-created-with-option-Create-New-Volume-Yes-on-3Engines-Cloud.html.md +++ b/docs/cloud/VM-created-with-option-Create-New-Volume-Yes-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -VM created with option Create New Volume Yes on 3Engines Cloud[🔗](#vm-created-with-option-create-new-volume-yes-on-brand-name "Permalink to this headline") +VM created with option Create New Volume Yes on connectVM Cloud[🔗](#vm-created-with-option-create-new-volume-yes-on-brand-name "Permalink to this headline") ============================================================================================================================================================= Note diff --git a/docs/cloud/What-Image-Formats-are-available-in-3Engines-3Engines-Cloud-Cloud.html.md b/docs/cloud/What-Image-Formats-are-available-in-connectVM-connectVM-Cloud-Cloud.html.md similarity index 82% rename from docs/cloud/What-Image-Formats-are-available-in-3Engines-3Engines-Cloud-Cloud.html.md rename to docs/cloud/What-Image-Formats-are-available-in-connectVM-connectVM-Cloud-Cloud.html.md index c07c925..1d1f9b0 100644 --- a/docs/cloud/What-Image-Formats-are-available-in-3Engines-3Engines-Cloud-Cloud.html.md +++ b/docs/cloud/What-Image-Formats-are-available-in-connectVM-connectVM-Cloud-Cloud.html.md @@ -1,15 +1,15 @@ -What Image Formats are Available in 3Engines 3Engines Cloud cloud[🔗](#what-image-formats-are-available-in-3Engines-brand-name-cloud "Permalink to this headline") +What Image Formats are Available in connectVM connectVM Cloud cloud[🔗](#what-image-formats-are-available-in-connectVM-brand-name-cloud "Permalink to this headline") ===================================================================================================================================================================== -In 3Engines Cloud 3Engines ten image format extensions are available: +In connectVM Cloud connectVM ten image format extensions are available: -**QCOW2** - Formatted Virtual Machine Storage is a storage format for virtual machine disk images. QCOW stands for “QEMU copy on write”. It is used with the KVM hypervisor. The images are typically smaller than RAW images, so it is often faster to convert a raw image to qcow2 for uploading instead of uploading the raw file directly. Because raw images do not support snapshots, 3Engines Compute will automatically convert raw image files to qcow2 as needed. +**QCOW2** - Formatted Virtual Machine Storage is a storage format for virtual machine disk images. QCOW stands for “QEMU copy on write”. It is used with the KVM hypervisor. The images are typically smaller than RAW images, so it is often faster to convert a raw image to qcow2 for uploading instead of uploading the raw file directly. Because raw images do not support snapshots, connectVM Compute will automatically convert raw image files to qcow2 as needed. **RAW** - The RAW storage is the simplest one, and is natively supported by both KVM and Xen hypervisors. RAW image could be considered as the bit-equivalent of a block device file. It has a performance advantage over QCOW2 in that no formatting is applied to virtual machine disk images stored in the RAW format. No additional work from hosts is required in Virtual machine data operations on disk images stored in this format. **ISO** - The ISO format is a disk image formatted with the read-only ISO 9660 filesystem which is used for CDs and DVDs. While ISO is not frequently considered as a virtual machine image format, because of ISOs contain bootable filesystems with an installed operating system, it can be treated like other virtual machine image files. -**VDI** - Virtual Disk Image format used by VirtualBox for image files. None of the 3Engines Compute hypervisors supports VDI directly, so it will be needed to convert these files to a different format to use them. +**VDI** - Virtual Disk Image format used by VirtualBox for image files. None of the connectVM Compute hypervisors supports VDI directly, so it will be needed to convert these files to a different format to use them. **VHD** - Virtual Hard Disk format for images, widely used by Microsoft (e.g. Hyper-V, Microsoft Virtual PC). diff --git a/docs/cloud/What-is-an-3Engines-project-on-3Engines-Cloud.html.md b/docs/cloud/What-is-an-3Engines-project-on-3Engines-Cloud.html.md deleted file mode 100644 index fa24d52..0000000 --- a/docs/cloud/What-is-an-3Engines-project-on-3Engines-Cloud.html.md +++ /dev/null @@ -1,23 +0,0 @@ -What is an 3Engines project on 3Engines Cloud[🔗](#what-is-an-3Engines-project-on-brand-name "Permalink to this headline") -============================================================================================================================= - -A **project** is a isolated group of zero or more users who share common access with specific privileges to the software instance in 3Engines. A project is created for each set of instances and networks that are configured as a discrete entity for the project. In Compute, a project owns virtual machines (in Compute) or containers (in Object Storage). - -You can imagine that the whole 3Engines cloud is a big cake of resources (vCPU, disks, instances, etc…) and projects are the pieces of this cake served to the customers. - -Current project name is **visible** in the Horizon panel. - -![project1.png](../_images/project1.png) - -Projects are created, managed, and edited at the 3Engines **Projects** screen. - -![project2.png](../_images/project2.png) - -Users can be associated with more than one project, but once signed, they can only see and access the resources available in that project. -Each project and user pairing can have a role associated with it. - -3Engines users can create projects, and create new accounts using the 3Engines Dashboard. They can also associate other users with roles, projects, or both. - -To remove project its mandatory to manually remove all of its resources first. - -Users can create private networks for connectivity within projects [How to create a network with router in Horizon Dashboard on 3Engines Cloud](../networking/How-to-create-a-network-with-router-in-Horizon-Dashboard-on-3Engines-Cloud.html.md). By default, they are fully isolated and are not shared with other projects. \ No newline at end of file diff --git a/docs/cloud/What-is-an-3Engines-domain-on-3Engines-Cloud.html.md b/docs/cloud/What-is-an-connectVM-domain-on-connectVM-Cloud.html.md similarity index 56% rename from docs/cloud/What-is-an-3Engines-domain-on-3Engines-Cloud.html.md rename to docs/cloud/What-is-an-connectVM-domain-on-connectVM-Cloud.html.md index 71d3f1e..c444ef3 100644 --- a/docs/cloud/What-is-an-3Engines-domain-on-3Engines-Cloud.html.md +++ b/docs/cloud/What-is-an-connectVM-domain-on-connectVM-Cloud.html.md @@ -1,15 +1,15 @@ -What is an 3Engines domain on 3Engines Cloud[🔗](#what-is-an-3Engines-domain-on-brand-name "Permalink to this headline") +What is an connectVM domain on connectVM Cloud[🔗](#what-is-an-connectVM-domain-on-brand-name "Permalink to this headline") =========================================================================================================================== **Domain** -Intention of providing a domain in cloud environment is to define boundaries for management. 3Engines domain is a type of a container for projects, users and groups. +Intention of providing a domain in cloud environment is to define boundaries for management. connectVM domain is a type of a container for projects, users and groups. One crucial benefit is separating overlapping resource names for different domains. Furthermore, permissions in the project and domain are two not related things, hereby customization for administrator is made up much easier. Current domain name is **visible** beside the project that is currently selected in the Horizon panel. -![cloud/domain_3Enginescloud.png](_images/domain_3Enginescloud.png) +![cloud/domain_connectVMcloud.png](_images/domain_connectVMcloud.png) The name of the domain is grayed out, denoting that you can use only the domain that has been allocated to you by the system. @@ -17,10 +17,10 @@ You cannot create a new domain. **Service relation** -3Engines Cloud account is linked to your main account in particular domain, hence it allows you to login to the 3Engines dashboard without any need to deliver keystone credentials. +connectVM Cloud account is linked to your main account in particular domain, hence it allows you to login to the connectVM dashboard without any need to deliver keystone credentials. This type of facility is due to a proper implementation of KeyCloak and KeyStone relation. **Docs** -Click here if you want to see official [3Engines documentation for domains](https://docs.3Engines.org/security-guide/identity/domains.html.md). \ No newline at end of file +Click here if you want to see official [connectVM documentation for domains](https://docs.connectVM.org/security-guide/identity/domains.html.md). \ No newline at end of file diff --git a/docs/cloud/What-is-an-connectVM-project-on-connectVM-Cloud.html.md b/docs/cloud/What-is-an-connectVM-project-on-connectVM-Cloud.html.md new file mode 100644 index 0000000..4208fa4 --- /dev/null +++ b/docs/cloud/What-is-an-connectVM-project-on-connectVM-Cloud.html.md @@ -0,0 +1,23 @@ +What is an connectVM project on connectVM Cloud[🔗](#what-is-an-connectVM-project-on-brand-name "Permalink to this headline") +============================================================================================================================= + +A **project** is a isolated group of zero or more users who share common access with specific privileges to the software instance in connectVM. A project is created for each set of instances and networks that are configured as a discrete entity for the project. In Compute, a project owns virtual machines (in Compute) or containers (in Object Storage). + +You can imagine that the whole connectVM cloud is a big cake of resources (vCPU, disks, instances, etc…) and projects are the pieces of this cake served to the customers. + +Current project name is **visible** in the Horizon panel. + +![project1.png](../_images/project1.png) + +Projects are created, managed, and edited at the connectVM **Projects** screen. + +![project2.png](../_images/project2.png) + +Users can be associated with more than one project, but once signed, they can only see and access the resources available in that project. +Each project and user pairing can have a role associated with it. + +connectVM users can create projects, and create new accounts using the connectVM Dashboard. They can also associate other users with roles, projects, or both. + +To remove project its mandatory to manually remove all of its resources first. + +Users can create private networks for connectivity within projects [How to create a network with router in Horizon Dashboard on connectVM Cloud](../networking/How-to-create-a-network-with-router-in-Horizon-Dashboard-on-connectVM-Cloud.html.md). By default, they are fully isolated and are not shared with other projects. \ No newline at end of file diff --git a/docs/cloud/cloud.html.md b/docs/cloud/cloud.html.md index c96089e..6bdad14 100644 --- a/docs/cloud/cloud.html.md +++ b/docs/cloud/cloud.html.md @@ -2,37 +2,37 @@ ## Available Documentation -* [Dashboard Overview – Project Quotas And Flavors Limits on 3Engines Cloud](Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-3Engines-Cloud.html.md) -* [How to access the VM from 3Engines console on 3Engines Cloud](How-to-access-the-VM-from-3Engines-console-on-3Engines-Cloud.html.md) -* [How to clone existing and configured VMs on 3Engines Cloud](How-to-clone-existing-and-configured-VMs-on-3Engines-Cloud.html.md) -* [How to fix unresponsive console issue on 3Engines Cloud](How-to-fix-unresponsive-console-issue-on-3Engines-Cloud.html.md) -* [How to generate and manage EC2 credentials on 3Engines Cloud](How-to-generate-ec2-credentials-on-3Engines-Cloud.html.md) -* [How to generate or use Application Credentials via CLI on 3Engines Cloud](How-to-generate-or-use-Application-Credentials-via-CLI-on-3Engines-Cloud.html.md) -* [How to Use GUI in Linux VM on 3Engines Cloud and access it From Local Linux Computer](How-to-use-GUI-in-Linux-VM-on-3Engines-Cloud-and-access-it-from-local-Linux-computer.html.md) -* [How To Create a New Linux VM With NVIDIA Virtual GPU in the 3Engines Dashboard Horizon on 3Engines Cloud](How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md) -* [How to install and use Docker on Ubuntu 24.04](How-to-use-Docker-on-3Engines-Cloud.html.md) -* [How to use Security Groups in Horizon on 3Engines Cloud](How-to-use-Security-Groups-in-Horizon-on-3Engines-Cloud.html.md) -* [How to create key pair in 3Engines Dashboard on 3Engines Cloud](How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md) -* [How to create new Linux VM in 3Engines Dashboard Horizon on 3Engines Cloud](How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md) -* [How to install Python virtualenv or virtualenvwrapper on 3Engines Cloud](How-to-install-Python-virtualenv-or-virtualenvwrapper-on-3Engines-Cloud.html.md) -* [How to start a VM from a snapshot on 3Engines Cloud](How-to-start-a-VM-from-a-snapshot-on-3Engines-Cloud.html.md) -* [Status Power State and dependencies in billing of instance VMs on 3Engines Cloud](Status-Power-State-and-dependences-in-billing-of-instances-VMs-on-3Engines-Cloud.html.md) -* [How to upload your custom image using 3Engines CLI on 3Engines Cloud](How-to-upload-your-custom-image-using-3Engines-CLI-on-3Engines-Cloud.html.md) -* [VM created with option Create New Volume No on 3Engines Cloud](VM-created-with-option-Create-New-Volume-No-on-3Engines-Cloud.html.md) -* [VM created with option Create New Volume Yes on 3Engines Cloud](VM-created-with-option-Create-New-Volume-Yes-on-3Engines-Cloud.html.md) -* [What is an 3Engines domain on 3Engines Cloud](What-is-an-3Engines-domain-on-3Engines-Cloud.html.md) -* [What is an 3Engines project on 3Engines Cloud](What-is-an-3Engines-project-on-3Engines-Cloud.html.md) -* [How to create a Linux VM and access it from Windows desktop on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md) -* [How to create a Linux VM and access it from Linux command line on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md) -* [DNS as a Service on 3Engines Cloud Hosting](DNS-as-a-Service-on-3Engines-Cloud-Hosting.html.md) -* [What Image Formats are Available in 3Engines 3Engines Cloud cloud](What-Image-Formats-are-available-in-3Engines-3Engines-Cloud-Cloud.html.md) -* [How to upload custom image to 3Engines Cloud cloud using 3Engines Horizon dashboard](How-to-upload-custom-image-to-3Engines-Cloud-cloud-using-3Engines-Horizon-dashboard.html.md) -* [How to create Windows VM on 3Engines Horizon and access it via web console on 3Engines Cloud](How-to-create-Windows-VM-on-3Engines-Horizon-and-access-it-via-web-console-on-3Engines-Cloud.html.md) -* [How to transfer volumes between domains and projects using Horizon dashboard on 3Engines Cloud](How-to-transfer-volumes-between-domains-and-projects-using-Horizon-dashboard-on-3Engines-Cloud.html.md) -* [Spot instances on 3Engines Cloud](Spot-instances-on-3Engines-Cloud.html.md) -* [How to create instance snapshot using Horizon on 3Engines Cloud](How-to-create-instance-snapshot-using-Horizon-on-3Engines-Cloud.html.md) -* [How to start a VM from instance snapshot using Horizon dashboard on 3Engines Cloud](How-to-start-a-VM-from-instance-snapshot-using-Horizon-dashboard-on-3Engines-Cloud.html.md) -* [How to create a VM using the 3Engines CLI client on 3Engines Cloud cloud](How-to-create-a-VM-using-the-3Engines-CLI-client-on-3Engines-Cloud-cloud.html.md) -* [3Engines User Roles on 3Engines Cloud](3Engines-user-roles-on-3Engines-Cloud.html.md) -* [Resizing a virtual machine using 3Engines Horizon on 3Engines Cloud](Resizing-a-virtual-machine-using-3Engines-Horizon-on-3Engines-Cloud.html.md) -* [Block storage and object storage performance limits on 3Engines Cloud](Block-storage-and-object-storage-performance-limits-on-3Engines-Cloud.html.md) +* [Dashboard Overview – Project Quotas And Flavors Limits on connectVM Cloud](Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-connectVM-Cloud.html.md) +* [How to access the VM from connectVM console on connectVM Cloud](How-to-access-the-VM-from-connectVM-console-on-connectVM-Cloud.html.md) +* [How to clone existing and configured VMs on connectVM Cloud](How-to-clone-existing-and-configured-VMs-on-connectVM-Cloud.html.md) +* [How to fix unresponsive console issue on connectVM Cloud](How-to-fix-unresponsive-console-issue-on-connectVM-Cloud.html.md) +* [How to generate and manage EC2 credentials on connectVM Cloud](How-to-generate-ec2-credentials-on-connectVM-Cloud.html.md) +* [How to generate or use Application Credentials via CLI on connectVM Cloud](How-to-generate-or-use-Application-Credentials-via-CLI-on-connectVM-Cloud.html.md) +* [How to Use GUI in Linux VM on connectVM Cloud and access it From Local Linux Computer](How-to-use-GUI-in-Linux-VM-on-connectVM-Cloud-and-access-it-from-local-Linux-computer.html.md) +* [How To Create a New Linux VM With NVIDIA Virtual GPU in the connectVM Dashboard Horizon on connectVM Cloud](How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md) +* [How to install and use Docker on Ubuntu 24.04](How-to-use-Docker-on-connectVM-Cloud.html.md) +* [How to use Security Groups in Horizon on connectVM Cloud](How-to-use-Security-Groups-in-Horizon-on-connectVM-Cloud.html.md) +* [How to create key pair in connectVM Dashboard on connectVM Cloud](How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md) +* [How to create new Linux VM in connectVM Dashboard Horizon on connectVM Cloud](How-to-create-new-Linux-VM-in-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md) +* [How to install Python virtualenv or virtualenvwrapper on connectVM Cloud](How-to-install-Python-virtualenv-or-virtualenvwrapper-on-connectVM-Cloud.html.md) +* [How to start a VM from a snapshot on connectVM Cloud](How-to-start-a-VM-from-a-snapshot-on-connectVM-Cloud.html.md) +* [Status Power State and dependencies in billing of instance VMs on connectVM Cloud](Status-Power-State-and-dependences-in-billing-of-instances-VMs-on-connectVM-Cloud.html.md) +* [How to upload your custom image using connectVM CLI on connectVM Cloud](How-to-upload-your-custom-image-using-connectVM-CLI-on-connectVM-Cloud.html.md) +* [VM created with option Create New Volume No on connectVM Cloud](VM-created-with-option-Create-New-Volume-No-on-connectVM-Cloud.html.md) +* [VM created with option Create New Volume Yes on connectVM Cloud](VM-created-with-option-Create-New-Volume-Yes-on-connectVM-Cloud.html.md) +* [What is an connectVM domain on connectVM Cloud](What-is-an-connectVM-domain-on-connectVM-Cloud.html.md) +* [What is an connectVM project on connectVM Cloud](What-is-an-connectVM-project-on-connectVM-Cloud.html.md) +* [How to create a Linux VM and access it from Windows desktop on connectVM Cloud](How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-connectVM-Cloud.html.md) +* [How to create a Linux VM and access it from Linux command line on connectVM Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md) +* [DNS as a Service on connectVM Cloud Hosting](DNS-as-a-Service-on-connectVM-Cloud-Hosting.html.md) +* [What Image Formats are Available in connectVM connectVM Cloud cloud](What-Image-Formats-are-available-in-connectVM-connectVM-Cloud-Cloud.html.md) +* [How to upload custom image to connectVM Cloud cloud using connectVM Horizon dashboard](How-to-upload-custom-image-to-connectVM-Cloud-cloud-using-connectVM-Horizon-dashboard.html.md) +* [How to create Windows VM on connectVM Horizon and access it via web console on connectVM Cloud](How-to-create-Windows-VM-on-connectVM-Horizon-and-access-it-via-web-console-on-connectVM-Cloud.html.md) +* [How to transfer volumes between domains and projects using Horizon dashboard on connectVM Cloud](How-to-transfer-volumes-between-domains-and-projects-using-Horizon-dashboard-on-connectVM-Cloud.html.md) +* [Spot instances on connectVM Cloud](Spot-instances-on-connectVM-Cloud.html.md) +* [How to create instance snapshot using Horizon on connectVM Cloud](How-to-create-instance-snapshot-using-Horizon-on-connectVM-Cloud.html.md) +* [How to start a VM from instance snapshot using Horizon dashboard on connectVM Cloud](How-to-start-a-VM-from-instance-snapshot-using-Horizon-dashboard-on-connectVM-Cloud.html.md) +* [How to create a VM using the connectVM CLI client on connectVM Cloud cloud](How-to-create-a-VM-using-the-connectVM-CLI-client-on-connectVM-Cloud-cloud.html.md) +* [connectVM User Roles on connectVM Cloud](connectVM-user-roles-on-connectVM-Cloud.html.md) +* [Resizing a virtual machine using connectVM Horizon on connectVM Cloud](Resizing-a-virtual-machine-using-connectVM-Horizon-on-connectVM-Cloud.html.md) +* [Block storage and object storage performance limits on connectVM Cloud](Block-storage-and-object-storage-performance-limits-on-connectVM-Cloud.html.md) diff --git a/docs/cloud/3Engines-user-roles-on-3Engines-Cloud.html.md b/docs/cloud/connectVM-user-roles-on-connectVM-Cloud.html.md similarity index 73% rename from docs/cloud/3Engines-user-roles-on-3Engines-Cloud.html.md rename to docs/cloud/connectVM-user-roles-on-connectVM-Cloud.html.md index 8cd38be..6f8751b 100644 --- a/docs/cloud/3Engines-user-roles-on-3Engines-Cloud.html.md +++ b/docs/cloud/connectVM-user-roles-on-connectVM-Cloud.html.md @@ -1,9 +1,9 @@ -3Engines User Roles on 3Engines Cloud[🔗](#3Engines-user-roles-on-brand-name "Permalink to this headline") +connectVM User Roles on connectVM Cloud[🔗](#connectVM-user-roles-on-brand-name "Permalink to this headline") ============================================================================================================= -A **user role** in 3Engines cloud is a set of permissions that govern how members of specific groups interact with system resources, their access scope, and capabilities. +A **user role** in connectVM cloud is a set of permissions that govern how members of specific groups interact with system resources, their access scope, and capabilities. -This guide simplifies 3Engines roles for casual users of 3Engines Cloud VMs. It focuses on practical use cases and commonly required roles. +This guide simplifies connectVM roles for casual users of connectVM Cloud VMs. It focuses on practical use cases and commonly required roles. What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -28,28 +28,28 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") **1. Account** -You need a 3Engines Cloud hosting account with Horizon access: . +You need a connectVM Cloud hosting account with Horizon access: . Also see: -[What is an 3Engines project on 3Engines Cloud](What-is-an-3Engines-project-on-3Engines-Cloud.html.md) +[What is an connectVM project on connectVM Cloud](What-is-an-connectVM-project-on-connectVM-Cloud.html.md) -[What is an 3Engines domain on 3Engines Cloud](What-is-an-3Engines-domain-on-3Engines-Cloud.html.md) +[What is an connectVM domain on connectVM Cloud](What-is-an-connectVM-domain-on-connectVM-Cloud.html.md) -[How to generate or use Application Credentials via CLI on 3Engines Cloud](How-to-generate-or-use-Application-Credentials-via-CLI-on-3Engines-Cloud.html.md) +[How to generate or use Application Credentials via CLI on connectVM Cloud](How-to-generate-or-use-Application-Credentials-via-CLI-on-connectVM-Cloud.html.md) -**2. Familiarity with 3Engines Commands** +**2. Familiarity with connectVM Commands** -Ensure you know the following 3Engines commands: +Ensure you know the following connectVM commands: -**3Engines** -: The primary CLI for interacting with 3Engines services. - [How to install 3EnginesClient for Linux on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md) +**connectVM** +: The primary CLI for interacting with connectVM services. + [How to install connectVMClient for Linux on connectVM Cloud](../connectVMcli/How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md) **kubectl** : CLI for Kubernetes clusters. Example article: - [How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](../kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md) + [How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](../kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md) Frequently used user roles[🔗](#frequently-used-user-roles "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -61,22 +61,22 @@ Frequently used user roles[🔗](#frequently-used-user-roles "Permalink to this Note - Older 3Engines versions may use **\_member\_**. If both **member** and **\_member\_** exist, choose **member**. + Older connectVM versions may use **\_member\_**. If both **member** and **\_member\_** exist, choose **member**. * Horizon: **Project** -> **Overview** - * CLI: **3Engines server list**, **3Engines project list** + * CLI: **connectVM server list**, **connectVM project list** **observer** : Read-only access for monitoring and auditing resources. Suitable for third-party tools like Prometheus or Grafana. * Horizon: **Project** -> **Overview** - * CLI: **3Engines server show**, **3Engines project show** + * CLI: **connectVM server show**, **connectVM project show** **reader** : Read-only access with slightly broader permissions than **observer**. Ideal for monitoring and analytics tools requiring detailed resource data. * Horizon: **Project** -> **Overview** - * CLI: **3Engines server list**, **3Engines project list** + * CLI: **connectVM server list**, **connectVM project list** ### Roles for Kubernetes users[🔗](#roles-for-kubernetes-users "Permalink to this headline") @@ -104,13 +104,13 @@ Frequently used user roles[🔗](#frequently-used-user-roles "Permalink to this : Grants access to deploy applications behind load balancers. * Horizon: **Network** -> **Load Balancers** - * CLI: **3Engines loadbalancer member create**, **3Engines loadbalancer member list** + * CLI: **connectVM loadbalancer member create**, **connectVM loadbalancer member list** **load-balancer\_observer** : Read-only access to monitor load balancer configurations. * Horizon: **Network** -> **Load Balancers** - * CLI: **3Engines loadbalancer show**, **3Engines loadbalancer stats show** + * CLI: **connectVM loadbalancer show**, **connectVM loadbalancer stats show** How to View Roles in Horizon[🔗](#how-to-view-roles-in-horizon "Permalink to this headline") ------------------------------------------------------------------------------------------- @@ -123,7 +123,7 @@ You can view roles in Horizon by navigating to **Identity** -> **Roles**. Assigning multiple roles is best done during project creation rather than user creation. -![3Engines-user-roles-create-4.png](../_images/3Engines-user-roles-create-4.png) +![connectVM-user-roles-create-4.png](../_images/connectVM-user-roles-create-4.png) Examples of using user roles[🔗](#examples-of-using-user-roles "Permalink to this headline") ------------------------------------------------------------------------------------------- @@ -132,7 +132,7 @@ The following articles, as one of many steps, describe how to assign a role to t ### Using user roles while creating application credential in Horizon[🔗](#using-user-roles-while-creating-application-credential-in-horizon "Permalink to this headline") -Normally, you access the cloud via user credentials, which may be one- or two-factor credentials. 3Engines provides a more direct procedure of gaining access to cloud with application credential and you can create a credential with several user roles. +Normally, you access the cloud via user credentials, which may be one- or two-factor credentials. connectVM provides a more direct procedure of gaining access to cloud with application credential and you can create a credential with several user roles. That S3 article selects user roles when creating an application credential, through Horizon: @@ -144,7 +144,7 @@ That S3 article selects user roles when creating an application credential, thro This is the main article about application credentials; it is mostly using CLI: -[How to generate or use Application Credentials via CLI on 3Engines Cloud](How-to-generate-or-use-Application-Credentials-via-CLI-on-3Engines-Cloud.html.md) +[How to generate or use Application Credentials via CLI on connectVM Cloud](How-to-generate-or-use-Application-Credentials-via-CLI-on-connectVM-Cloud.html.md) Here is how to specify user roles through CLI parameters: @@ -152,14 +152,14 @@ Here is how to specify user roles through CLI parameters: ### Using user roles while creating a new project[🔗](#using-user-roles-while-creating-a-new-project "Permalink to this headline") -In article [How to Create and Configure New 3Engines Project Through Horizon on 3Engines Cloud Cloud](../3Enginescli/How-To-Create-and-Configure-New-Project-on-3Engines-Cloud-Cloud.html.md) we use command **Project Members** to define which users to include into the project: +In article [How to Create and Configure New connectVM Project Through Horizon on connectVM Cloud Cloud](../connectVMcli/How-To-Create-and-Configure-New-Project-on-connectVM-Cloud-Cloud.html.md) we use command **Project Members** to define which users to include into the project: ![user-roles-list-create-4.png](../_images/user-roles-list-create-4.png) You would then continue by defining the roles for each user in the project: ![user-roles-list-create-5.png](../_images/user-roles-list-create-5.png) -> See this Rancher article, [How to install Rancher RKE2 Kubernetes on 3Engines Cloud](../kubernetes/How-to-install-Rancher-RKE2-Kubernetes-on-3Engines-Cloud-cloud.html.md). Then, in Preparation step 1, a new project is created, with the following user roles: +> See this Rancher article, [How to install Rancher RKE2 Kubernetes on connectVM Cloud](../kubernetes/How-to-install-Rancher-RKE2-Kubernetes-on-connectVM-Cloud-cloud.html.md). Then, in Preparation step 1, a new project is created, with the following user roles: * **load-balancer\_member**, * **member** and @@ -169,9 +169,9 @@ You would then continue by defining the roles for each user in the project: ### Using member role only while creating a new user[🔗](#using-member-role-only-while-creating-a-new-user "Permalink to this headline") -In SLURM article, we first create a new 3Engines Keystone user, with the role of **member**. +In SLURM article, we first create a new connectVM Keystone user, with the role of **member**. -/cuttingedge/Sample-SLURM-Cluster-on-3Engines-Cloud-Cloud-with-ElastiCluster +/cuttingedge/Sample-SLURM-Cluster-on-connectVM-Cloud-Cloud-with-ElastiCluster ![user-roles-list-create-3.png](../_images/user-roles-list-create-3.png) diff --git a/docs/datavolume/Bootable-versus-non-bootable-volumes-on-3Engines-Cloud.html.md b/docs/datavolume/Bootable-versus-non-bootable-volumes-on-connectVM-Cloud.html.md similarity index 82% rename from docs/datavolume/Bootable-versus-non-bootable-volumes-on-3Engines-Cloud.html.md rename to docs/datavolume/Bootable-versus-non-bootable-volumes-on-connectVM-Cloud.html.md index 108751c..17eb18a 100644 --- a/docs/datavolume/Bootable-versus-non-bootable-volumes-on-3Engines-Cloud.html.md +++ b/docs/datavolume/Bootable-versus-non-bootable-volumes-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -Bootable versus non-bootable volumes on 3Engines Cloud[🔗](#bootable-versus-non-bootable-volumes-on-brand-name "Permalink to this headline") +Bootable versus non-bootable volumes on connectVM Cloud[🔗](#bootable-versus-non-bootable-volumes-on-brand-name "Permalink to this headline") ============================================================================================================================================= Each volume has an indicator called **bootable** which shows whether an operating system can be booted from it or not. That indicator can be set up manually at any time. If you set it up on a volume that does not contain a bootable operating system and later try to boot a VM from it, you will see an error as a response. @@ -6,7 +6,7 @@ Each volume has an indicator called **bootable** which shows whether an operatin In this article we will > * explain practical differences between **bootable** and **non-bootable** volumes and -> * provide procedures in Horizon and 3Engines CLI to check whether the volume **bootable** or not. +> * provide procedures in Horizon and connectVM CLI to check whether the volume **bootable** or not. Bootable vs. non-bootable volumes[🔗](#bootable-vs-non-bootable-volumes "Permalink to this headline") ---------------------------------------------------------------------------------------------------- @@ -30,7 +30,7 @@ What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this --------------------------------------------------------------------------------------- > * Which volumes appear when creating a virtual machine using Horizon dashboard? -> * Attempting to create a virtual machine from non-bootable volume using 3Engines CLI +> * Attempting to create a virtual machine from non-bootable volume using connectVM CLI > * Checking whether a volume is bootable > * Checking whether a volume snapshot was created from a bootable volume > * Modifying bootable status of a volume @@ -41,8 +41,8 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . -No. 2 **3Engines CLI client operational** +No. 2 **connectVM CLI client operational** -We assume you are familiar with 3Engines CLI client. If not, here are some articles to get you started: \ No newline at end of file +We assume you are familiar with connectVM CLI client. If not, here are some articles to get you started: \ No newline at end of file diff --git a/docs/datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-3Engines-Cloud.html.md b/docs/datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-3Engines-Cloud.html.md deleted file mode 100644 index 0d7a481..0000000 --- a/docs/datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-3Engines-Cloud.html.md +++ /dev/null @@ -1,10 +0,0 @@ -Ephemeral vs Persistent storage option Create New Volume on 3Engines Cloud[🔗](#ephemeral-vs-persistent-storage-option-create-new-volume-on-brand-name "Permalink to this headline") -===================================================================================================================================================================================== - -Volumes created in the **Volumes > Volumes** section are *persistent* storage. They can be attached to a virtual machine and then reattached to a different one. They survive the removal of the virtual machine to which they are connected. You can also clone them, which is a simple way of creating a backup. However, if you copy them, you might also be interested in [Volume snapshot inheritance and its consequences on 3Engines Cloud](Volume-snapshot-inheritance-and-its-consequences-on-3Engines-Cloud.html.md). - -If you follow the instructions in this article: [VM created with option Create New Volume Yes on 3Engines Cloud](../cloud/VM-created-with-option-Create-New-Volume-Yes-on-3Engines-Cloud.html.md) and set **Delete Volume on Instance Delete** to **No**, the boot drive of such virtual machine will also be persistent storage. You can, for example, use this feature to perform various tests and experiments. - -If you do not need persistent storage, use *ephemeral* storage. It cannot be reattached to a different machine and will be removed if the machine is removed. See the article [VM created with option Create New Volume No on 3Engines Cloud](../cloud/VM-created-with-option-Create-New-Volume-No-on-3Engines-Cloud.html.md) on how to create a virtual machine with this type of storage. - -You may find more information regarding this topic in [the official 3Engines documentation on design storage concepts](https://docs.3Engines.org/arch-design/design-storage/design-storage-concepts.html.md). \ No newline at end of file diff --git a/docs/datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-connectVM-Cloud.html.md b/docs/datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-connectVM-Cloud.html.md new file mode 100644 index 0000000..290e1d2 --- /dev/null +++ b/docs/datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-connectVM-Cloud.html.md @@ -0,0 +1,10 @@ +Ephemeral vs Persistent storage option Create New Volume on connectVM Cloud[🔗](#ephemeral-vs-persistent-storage-option-create-new-volume-on-brand-name "Permalink to this headline") +===================================================================================================================================================================================== + +Volumes created in the **Volumes > Volumes** section are *persistent* storage. They can be attached to a virtual machine and then reattached to a different one. They survive the removal of the virtual machine to which they are connected. You can also clone them, which is a simple way of creating a backup. However, if you copy them, you might also be interested in [Volume snapshot inheritance and its consequences on connectVM Cloud](Volume-snapshot-inheritance-and-its-consequences-on-connectVM-Cloud.html.md). + +If you follow the instructions in this article: [VM created with option Create New Volume Yes on connectVM Cloud](../cloud/VM-created-with-option-Create-New-Volume-Yes-on-connectVM-Cloud.html.md) and set **Delete Volume on Instance Delete** to **No**, the boot drive of such virtual machine will also be persistent storage. You can, for example, use this feature to perform various tests and experiments. + +If you do not need persistent storage, use *ephemeral* storage. It cannot be reattached to a different machine and will be removed if the machine is removed. See the article [VM created with option Create New Volume No on connectVM Cloud](../cloud/VM-created-with-option-Create-New-Volume-No-on-connectVM-Cloud.html.md) on how to create a virtual machine with this type of storage. + +You may find more information regarding this topic in [the official connectVM documentation on design storage concepts](https://docs.connectVM.org/arch-design/design-storage/design-storage-concepts.html.md). \ No newline at end of file diff --git a/docs/datavolume/How-To-Attach-Volume-To-Windows-VM-On-3Engines-Cloud.html.md b/docs/datavolume/How-To-Attach-Volume-To-Windows-VM-On-connectVM-Cloud.html.md similarity index 87% rename from docs/datavolume/How-To-Attach-Volume-To-Windows-VM-On-3Engines-Cloud.html.md rename to docs/datavolume/How-To-Attach-Volume-To-Windows-VM-On-connectVM-Cloud.html.md index 6fc13e7..5109fb4 100644 --- a/docs/datavolume/How-To-Attach-Volume-To-Windows-VM-On-3Engines-Cloud.html.md +++ b/docs/datavolume/How-To-Attach-Volume-To-Windows-VM-On-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How To Attach Volume To Windows VM On 3Engines Cloud[🔗](#how-to-attach-volume-to-windows-vm-on-brand-name "Permalink to this headline") +How To Attach Volume To Windows VM On connectVM Cloud[🔗](#how-to-attach-volume-to-windows-vm-on-brand-name "Permalink to this headline") ========================================================================================================================================= In this tutorial, you will attach a volume to your Windows virtual machine. It increases the storage available for your files. @@ -15,16 +15,16 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . No. 2 **Windows VM** -You must operate a Microsoft Windows virtual machine running on 3Engines Cloud cloud. You can access it using the webconsole ([How to access the VM from 3Engines console on 3Engines Cloud](../cloud/How-to-access-the-VM-from-3Engines-console-on-3Engines-Cloud.html.md)) or through RDP. If you are using RDP, we strongly recommend using a bastion host for your security: [Connecting to a Windows VM via RDP through a Linux bastion host port forwarding on 3Engines Cloud](../windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-3Engines-Cloud.html.md). +You must operate a Microsoft Windows virtual machine running on connectVM Cloud cloud. You can access it using the webconsole ([How to access the VM from connectVM console on connectVM Cloud](../cloud/How-to-access-the-VM-from-connectVM-console-on-connectVM-Cloud.html.md)) or through RDP. If you are using RDP, we strongly recommend using a bastion host for your security: [Connecting to a Windows VM via RDP through a Linux bastion host port forwarding on connectVM Cloud](../windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-connectVM-Cloud.html.md). Step 1: Create a New Volume[🔗](#step-1-create-a-new-volume "Permalink to this headline") ---------------------------------------------------------------------------------------- -Login to the Horizon panel available at . +Login to the Horizon panel available at . Go to the section **Volumes -> Volumes**: @@ -143,4 +143,4 @@ What To Do Next[🔗](#what-to-do-next "Permalink to this headline") Once you have gathered some data on your volume, you can create its backup, as explained in this article: -[How to Create Backup of Your Volume From Windows Machine on 3Engines Cloud](How-To-Create-Backup-Of-Your-Volume-From-Windows-Machine-on-3Engines-Cloud.html.md) \ No newline at end of file +[How to Create Backup of Your Volume From Windows Machine on connectVM Cloud](How-To-Create-Backup-Of-Your-Volume-From-Windows-Machine-on-connectVM-Cloud.html.md) \ No newline at end of file diff --git a/docs/datavolume/How-To-Create-Backup-Of-Your-Volume-From-Windows-Machine-on-3Engines-Cloud.html.md b/docs/datavolume/How-To-Create-Backup-Of-Your-Volume-From-Windows-Machine-on-connectVM-Cloud.html.md similarity index 87% rename from docs/datavolume/How-To-Create-Backup-Of-Your-Volume-From-Windows-Machine-on-3Engines-Cloud.html.md rename to docs/datavolume/How-To-Create-Backup-Of-Your-Volume-From-Windows-Machine-on-connectVM-Cloud.html.md index 89650ee..a34145d 100644 --- a/docs/datavolume/How-To-Create-Backup-Of-Your-Volume-From-Windows-Machine-on-3Engines-Cloud.html.md +++ b/docs/datavolume/How-To-Create-Backup-Of-Your-Volume-From-Windows-Machine-on-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -How to Create Backup of Your Volume From Windows Machine on 3Engines Cloud[🔗](#how-to-create-backup-of-your-volume-from-windows-machine-on-brand-name "Permalink to this headline") +How to Create Backup of Your Volume From Windows Machine on connectVM Cloud[🔗](#how-to-create-backup-of-your-volume-from-windows-machine-on-brand-name "Permalink to this headline") ===================================================================================================================================================================================== -In this tutorial you will learn how create a backup of your volume on 3Engines Cloud cloud. It allows you to save its state at a certain point in time and, for example, perform some experiments on it. You can then restore the volume to its previous state if you are unhappy with the results. +In this tutorial you will learn how create a backup of your volume on connectVM Cloud cloud. It allows you to save its state at a certain point in time and, for example, perform some experiments on it. You can then restore the volume to its previous state if you are unhappy with the results. Those backups are stored using object storage. Restoring a backup will delete all data added to a volume after backup was created. @@ -18,11 +18,11 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Windows VM** -You must operate a Microsoft Windows virtual machine running on 3Engines Cloud cloud. You can access it using the webconsole ([How to access the VM from 3Engines console on 3Engines Cloud](../cloud/How-to-access-the-VM-from-3Engines-console-on-3Engines-Cloud.html.md)) or through RDP. If you are using RDP, we strongly recommend using a bastion host for your security: [Connecting to a Windows VM via RDP through a Linux bastion host port forwarding on 3Engines Cloud](../windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-3Engines-Cloud.html.md). +You must operate a Microsoft Windows virtual machine running on connectVM Cloud cloud. You can access it using the webconsole ([How to access the VM from connectVM console on connectVM Cloud](../cloud/How-to-access-the-VM-from-connectVM-console-on-connectVM-Cloud.html.md)) or through RDP. If you are using RDP, we strongly recommend using a bastion host for your security: [Connecting to a Windows VM via RDP through a Linux bastion host port forwarding on connectVM Cloud](../windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-connectVM-Cloud.html.md). No. 3 **Volume** @@ -55,7 +55,7 @@ If you receive the following warning: make sure that the removal does not break your workflow and click **Yes**. -Shut down the virtual machine and return to the Horizon dashboard: +Shut down the virtual machine and return to the Horizon dashboard: Go to **Volumes** > **Volumes**. You should see your volume there: diff --git a/docs/datavolume/How-many-objects-can-I-put-into-Object-Storage-container-bucket-on-3Engines-Cloud.html.md b/docs/datavolume/How-many-objects-can-I-put-into-Object-Storage-container-bucket-on-connectVM-Cloud.html.md similarity index 80% rename from docs/datavolume/How-many-objects-can-I-put-into-Object-Storage-container-bucket-on-3Engines-Cloud.html.md rename to docs/datavolume/How-many-objects-can-I-put-into-Object-Storage-container-bucket-on-connectVM-Cloud.html.md index 124affa..7340c01 100644 --- a/docs/datavolume/How-many-objects-can-I-put-into-Object-Storage-container-bucket-on-3Engines-Cloud.html.md +++ b/docs/datavolume/How-many-objects-can-I-put-into-Object-Storage-container-bucket-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How many objects can I put into Object Storage container bucket on 3Engines Cloud[🔗](#how-many-objects-can-i-put-into-object-storage-container-bucket-on-brand-name "Permalink to this headline") +How many objects can I put into Object Storage container bucket on connectVM Cloud[🔗](#how-many-objects-can-i-put-into-object-storage-container-bucket-on-brand-name "Permalink to this headline") =================================================================================================================================================================================================== It is highly advisable to put no more than 1 million (1 000 000) objects into one bucket (container). Having more objects makes listing of them very inefficient. We suggest to create many buckets with a small amount of objects instead of a small amount of buckets with many objects. \ No newline at end of file diff --git a/docs/datavolume/How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-3Engines-Cloud.html.md b/docs/datavolume/How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-connectVM-Cloud.html.md similarity index 90% rename from docs/datavolume/How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-3Engines-Cloud.html.md rename to docs/datavolume/How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-connectVM-Cloud.html.md index 40f4663..441d4e7 100644 --- a/docs/datavolume/How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-3Engines-Cloud.html.md +++ b/docs/datavolume/How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-connectVM-Cloud.html.md @@ -1,11 +1,11 @@ -How to attach a volume to VM less than 2TB on Linux on 3Engines Cloud[🔗](#how-to-attach-a-volume-to-vm-less-than-2tb-on-linux-on-brand-name "Permalink to this headline") +How to attach a volume to VM less than 2TB on Linux on connectVM Cloud[🔗](#how-to-attach-a-volume-to-vm-less-than-2tb-on-linux-on-brand-name "Permalink to this headline") =========================================================================================================================================================================== In this tutorial, you will create a volume which is smaller than 2 TB. Then, you will attach it to a VM and format it in the appropriate way. Note -If you want to create and attach a volume that has more than 2 TB of storage, you will need to use different software for its formatting. If this is the case, please visit the following article instead: [How to attach a volume to VM more than 2TB on Linux on 3Engines Cloud](How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-3Engines-Cloud.html.md). +If you want to create and attach a volume that has more than 2 TB of storage, you will need to use different software for its formatting. If this is the case, please visit the following article instead: [How to attach a volume to VM more than 2TB on Linux on connectVM Cloud](How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-connectVM-Cloud.html.md). What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -19,17 +19,17 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . -No. 2 Linux VM running on the 3Engines Cloud cloud +No. 2 Linux VM running on the connectVM Cloud cloud Instructions for creating and accessing a Linux VM using default images can be found here: -[How to create a Linux VM and access it from Linux command line on 3Engines Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md) +[How to create a Linux VM and access it from Linux command line on connectVM Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md) or here: -[How to create a Linux VM and access it from Windows desktop on 3Engines Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md). +[How to create a Linux VM and access it from Windows desktop on connectVM Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-connectVM-Cloud.html.md). The instructions included in this article are designed for Ubuntu 22.04 LTS. @@ -39,12 +39,12 @@ You will need basic knowledge of the Linux command line. No. 4 **SSH access to the VM** -[How to connect to your virtual machine via SSH in Linux on 3Engines Cloud](../networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-3Engines-Cloud.html.md). +[How to connect to your virtual machine via SSH in Linux on connectVM Cloud](../networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-connectVM-Cloud.html.md). Step 1: Create a Volume[🔗](#step-1-create-a-volume "Permalink to this headline") -------------------------------------------------------------------------------- -Login to the Horizon panel available at . +Login to the Horizon panel available at . Go to the section **Volumes -> Volumes**: diff --git a/docs/datavolume/How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-3Engines-Cloud.html.md b/docs/datavolume/How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-connectVM-Cloud.html.md similarity index 91% rename from docs/datavolume/How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-3Engines-Cloud.html.md rename to docs/datavolume/How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-connectVM-Cloud.html.md index a6153ee..b0fdd57 100644 --- a/docs/datavolume/How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-3Engines-Cloud.html.md +++ b/docs/datavolume/How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-connectVM-Cloud.html.md @@ -1,11 +1,11 @@ -How to attach a volume to VM more than 2TB on Linux on 3Engines Cloud[🔗](#how-to-attach-a-volume-to-vm-more-than-2tb-on-linux-on-brand-name "Permalink to this headline") +How to attach a volume to VM more than 2TB on Linux on connectVM Cloud[🔗](#how-to-attach-a-volume-to-vm-more-than-2tb-on-linux-on-brand-name "Permalink to this headline") =========================================================================================================================================================================== In this tutorial, you will create a volume which is larger than 2 TB. Then, you will attach it to a VM and format it in the appropriate way. Note -If you want to create and attach a volume that has less than 2 TB of storage, you will need to use different software for its formatting. If this is the case, please visit the following article instead: [How to attach a volume to VM less than 2TB on Linux on 3Engines Cloud](How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-3Engines-Cloud.html.md). +If you want to create and attach a volume that has less than 2 TB of storage, you will need to use different software for its formatting. If this is the case, please visit the following article instead: [How to attach a volume to VM less than 2TB on Linux on connectVM Cloud](How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-connectVM-Cloud.html.md). What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -19,15 +19,15 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . -No. 2 Linux VM running on 3Engines Cloud cloud +No. 2 Linux VM running on connectVM Cloud cloud Instructions for creating and accessing a Linux VM using default images can be found here: -[How to create a Linux VM and access it from Linux command line on 3Engines Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md) or here: +[How to create a Linux VM and access it from Linux command line on connectVM Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md) or here: -[How to create a Linux VM and access it from Windows desktop on 3Engines Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md). +[How to create a Linux VM and access it from Windows desktop on connectVM Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-connectVM-Cloud.html.md). The instructions included in this article are designed for Ubuntu 20.04 LTS. @@ -37,12 +37,12 @@ You will need basic knowledge of the Linux command line. No. 4 **SSH access to the VM** -[How to connect to your virtual machine via SSH in Linux on 3Engines Cloud](../networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-3Engines-Cloud.html.md). +[How to connect to your virtual machine via SSH in Linux on connectVM Cloud](../networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-connectVM-Cloud.html.md). Step 1: Create a Volume[🔗](#step-1-create-a-volume "Permalink to this headline") -------------------------------------------------------------------------------- -Login to the Horizon panel available at . +Login to the Horizon panel available at . Go to the section **Volumes -> Volumes**: diff --git a/docs/datavolume/How-to-create-or-delete-volume-snapshot-on-3Engines-Cloud.html.md b/docs/datavolume/How-to-create-or-delete-volume-snapshot-on-connectVM-Cloud.html.md similarity index 69% rename from docs/datavolume/How-to-create-or-delete-volume-snapshot-on-3Engines-Cloud.html.md rename to docs/datavolume/How-to-create-or-delete-volume-snapshot-on-connectVM-Cloud.html.md index 4515988..99ea25a 100644 --- a/docs/datavolume/How-to-create-or-delete-volume-snapshot-on-3Engines-Cloud.html.md +++ b/docs/datavolume/How-to-create-or-delete-volume-snapshot-on-connectVM-Cloud.html.md @@ -1,14 +1,14 @@ -How to create or delete volume snapshot on 3Engines Cloud[🔗](#how-to-create-or-delete-volume-snapshot-on-brand-name "Permalink to this headline") +How to create or delete volume snapshot on connectVM Cloud[🔗](#how-to-create-or-delete-volume-snapshot-on-brand-name "Permalink to this headline") =================================================================================================================================================== -Volume snapshot allows you to save the state of volume at a specific point in time. Here is how to create or delete volume snapshot using Horizon dashboard or 3Engines CLI client. +Volume snapshot allows you to save the state of volume at a specific point in time. Here is how to create or delete volume snapshot using Horizon dashboard or connectVM CLI client. Prerequisites[🔗](#prerequisites "Permalink to this headline") ------------------------------------------------------------- No. 1 **Hosting** -You need a 3Engines Cloud hosting account with access to Horizon interface: +You need a connectVM Cloud hosting account with access to Horizon interface: No. 2 **A volume** diff --git a/docs/datavolume/How-to-create-volume-Snapshot-and-attach-as-Volume-on-Linux-or-Windows-on-3Engines-Cloud.html.md b/docs/datavolume/How-to-create-volume-Snapshot-and-attach-as-Volume-on-Linux-or-Windows-on-connectVM-Cloud.html.md similarity index 87% rename from docs/datavolume/How-to-create-volume-Snapshot-and-attach-as-Volume-on-Linux-or-Windows-on-3Engines-Cloud.html.md rename to docs/datavolume/How-to-create-volume-Snapshot-and-attach-as-Volume-on-Linux-or-Windows-on-connectVM-Cloud.html.md index d630729..017900e 100644 --- a/docs/datavolume/How-to-create-volume-Snapshot-and-attach-as-Volume-on-Linux-or-Windows-on-3Engines-Cloud.html.md +++ b/docs/datavolume/How-to-create-volume-Snapshot-and-attach-as-Volume-on-Linux-or-Windows-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How to create volume Snapshot and attach as Volume on Linux or Windows on 3Engines Cloud[🔗](#how-to-create-volume-snapshot-and-attach-as-volume-on-linux-or-windows-on-brand-name "Permalink to this headline") +How to create volume Snapshot and attach as Volume on Linux or Windows on connectVM Cloud[🔗](#how-to-create-volume-snapshot-and-attach-as-volume-on-linux-or-windows-on-brand-name "Permalink to this headline") ================================================================================================================================================================================================================= To create a snapshot of a Volume: diff --git a/docs/datavolume/How-to-export-a-volume-over-NFS-on-3Engines-Cloud.html.md b/docs/datavolume/How-to-export-a-volume-over-NFS-on-connectVM-Cloud.html.md similarity index 90% rename from docs/datavolume/How-to-export-a-volume-over-NFS-on-3Engines-Cloud.html.md rename to docs/datavolume/How-to-export-a-volume-over-NFS-on-connectVM-Cloud.html.md index 8b84e1c..a9fb49b 100644 --- a/docs/datavolume/How-to-export-a-volume-over-NFS-on-3Engines-Cloud.html.md +++ b/docs/datavolume/How-to-export-a-volume-over-NFS-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How to export a volume over NFS on 3Engines Cloud[🔗](#how-to-export-a-volume-over-nfs-on-brand-name "Permalink to this headline") +How to export a volume over NFS on connectVM Cloud[🔗](#how-to-export-a-volume-over-nfs-on-brand-name "Permalink to this headline") =================================================================================================================================== **Server configuration** @@ -104,7 +104,7 @@ sudo systemctl restart nfs-kernel-server **IT IS NECESSARY TO OPEN THE PORT 2049 IN A SECURITY GROUP!** -(The FAQ about opening ports in a security group is available at [How can I open new ports for http for my service or instance on 3Engines Cloud](../networking/How-can-I-open-new-ports-port-80-for-http-for-my-service-or-instance-on-3Engines-Cloud.html.md)) +(The FAQ about opening ports in a security group is available at [How can I open new ports for http for my service or instance on connectVM Cloud](../networking/How-can-I-open-new-ports-port-80-for-http-for-my-service-or-instance-on-connectVM-Cloud.html.md)) **Client Configuration** diff --git a/docs/datavolume/How-to-export-a-volume-over-NFS-outside-of-a-project-on-3Engines-Cloud.html.md b/docs/datavolume/How-to-export-a-volume-over-NFS-outside-of-a-project-on-connectVM-Cloud.html.md similarity index 85% rename from docs/datavolume/How-to-export-a-volume-over-NFS-outside-of-a-project-on-3Engines-Cloud.html.md rename to docs/datavolume/How-to-export-a-volume-over-NFS-outside-of-a-project-on-connectVM-Cloud.html.md index 2040494..f29d82d 100644 --- a/docs/datavolume/How-to-export-a-volume-over-NFS-outside-of-a-project-on-3Engines-Cloud.html.md +++ b/docs/datavolume/How-to-export-a-volume-over-NFS-outside-of-a-project-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How to export a volume over NFS outside of a project on 3Engines Cloud[🔗](#how-to-export-a-volume-over-nfs-outside-of-a-project-on-brand-name "Permalink to this headline") +How to export a volume over NFS outside of a project on connectVM Cloud[🔗](#how-to-export-a-volume-over-nfs-outside-of-a-project-on-brand-name "Permalink to this headline") ============================================================================================================================================================================= **Prerequisites** @@ -47,7 +47,7 @@ eouser@host:~$ sudo service nfs-kernel-server start ``` -Now go to +Now go to Create new security group. @@ -73,7 +73,7 @@ CIDR: 64.225.128.2 Click “Add” -Go to +Go to From the drop-down menu on the right of the “Host” instance, choose “Edit Security Groups”. diff --git a/docs/datavolume/How-to-extend-the-volume-in-Linux-on-3Engines-Cloud.html.md b/docs/datavolume/How-to-extend-the-volume-in-Linux-on-connectVM-Cloud.html.md similarity index 87% rename from docs/datavolume/How-to-extend-the-volume-in-Linux-on-3Engines-Cloud.html.md rename to docs/datavolume/How-to-extend-the-volume-in-Linux-on-connectVM-Cloud.html.md index 2e4660e..18d5ef1 100644 --- a/docs/datavolume/How-to-extend-the-volume-in-Linux-on-3Engines-Cloud.html.md +++ b/docs/datavolume/How-to-extend-the-volume-in-Linux-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How to extend the volume in Linux on 3Engines Cloud[🔗](#how-to-extend-the-volume-in-linux-on-brand-name "Permalink to this headline") +How to extend the volume in Linux on connectVM Cloud[🔗](#how-to-extend-the-volume-in-linux-on-brand-name "Permalink to this headline") ======================================================================================================================================= It is possible to extend a Volume from the Horizon dashboard. @@ -11,9 +11,9 @@ Warning Warning -2. If you have a volume < 2TB and you want to extend it above 2TB, please do not follow below instructions. Instead please create a new volume, format it according to another article: [How to attach a volume to VM more than 2TB on Linux on 3Engines Cloud](How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-3Engines-Cloud.html.md), attach it to the VM, copy the data from the old volume to the new one, check if it is fully copied, detach and delete the old volume. +2. If you have a volume < 2TB and you want to extend it above 2TB, please do not follow below instructions. Instead please create a new volume, format it according to another article: [How to attach a volume to VM more than 2TB on Linux on connectVM Cloud](How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-connectVM-Cloud.html.md), attach it to the VM, copy the data from the old volume to the new one, check if it is fully copied, detach and delete the old volume. -You may use following guide to backup the volume: [How to create volume Snapshot and attach as Volume on Linux or Windows on 3Engines Cloud](How-to-create-volume-Snapshot-and-attach-as-Volume-on-Linux-or-Windows-on-3Engines-Cloud.html.md) +You may use following guide to backup the volume: [How to create volume Snapshot and attach as Volume on Linux or Windows on connectVM Cloud](How-to-create-volume-Snapshot-and-attach-as-Volume-on-Linux-or-Windows-on-connectVM-Cloud.html.md) **Resizing the volume:** diff --git a/docs/datavolume/How-to-mount-object-storage-in-Linux-on-3Engines-Cloud.html.md b/docs/datavolume/How-to-mount-object-storage-in-Linux-on-connectVM-Cloud.html.md similarity index 74% rename from docs/datavolume/How-to-mount-object-storage-in-Linux-on-3Engines-Cloud.html.md rename to docs/datavolume/How-to-mount-object-storage-in-Linux-on-connectVM-Cloud.html.md index 6f18377..723b1fb 100644 --- a/docs/datavolume/How-to-mount-object-storage-in-Linux-on-3Engines-Cloud.html.md +++ b/docs/datavolume/How-to-mount-object-storage-in-Linux-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How to mount object storage in Linux on 3Engines Cloud[🔗](#how-to-mount-object-storage-in-linux-on-brand-name "Permalink to this headline") +How to mount object storage in Linux on connectVM Cloud[🔗](#how-to-mount-object-storage-in-linux-on-brand-name "Permalink to this headline") ============================================================================================================================================= S3 is a protocol for storing and retrieving data on and from remote servers. The user has their own S3 account and is identified by a pair of identifiers, which are called Access Key and Secret Key. These keys act as a username and password for your S3 account. @@ -10,15 +10,15 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") Prerequisite No. 1 **Hosting** -To use s3 protocol, you need a 3Engines Cloud hosting account. It comes with graphical user interface called Horizon: but you can also use s3 commands from terminal in various operating systems. +To use s3 protocol, you need a connectVM Cloud hosting account. It comes with graphical user interface called Horizon: but you can also use s3 commands from terminal in various operating systems. Prerequisite No. 2 **Valid EC2 credentials** The Access Key and Secret Key for access to an s3 account are also called the “EC2 credentials”. See article -[How to generate and manage EC2 credentials on 3Engines Cloud](../cloud/How-to-generate-ec2-credentials-on-3Engines-Cloud.html.md) +[How to generate and manage EC2 credentials on connectVM Cloud](../cloud/How-to-generate-ec2-credentials-on-connectVM-Cloud.html.md) -At this point, you should have access to the cloud environment, using the 3Engines CLI client. It means that the command **3Engines** is operational. +At this point, you should have access to the cloud environment, using the connectVM CLI client. It means that the command **connectVM** is operational. Check your credentials and save them in a file[🔗](#check-your-credentials-and-save-them-in-a-file "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------------------- @@ -26,7 +26,7 @@ Check your credentials and save them in a file[🔗](#check-your-credentials-and Check your credentials with the following command: ``` -3Engines ec2 credentials list +connectVM ec2 credentials list ``` @@ -63,7 +63,7 @@ sudo nano /etc/fuse.conf Now you are ready to mount your object storage to your Linux system. The command looks like: ``` -s3fs w-container-1 /local/mount/point - passwd_file=~/.passwd-s3fs -o url=https://s3.waw3-1.3Engines.com -o use_path_request_style -o umask=0002 -o allow_other +s3fs w-container-1 /local/mount/point - passwd_file=~/.passwd-s3fs -o url=https://s3.waw3-1.connectVM.com -o use_path_request_style -o umask=0002 -o allow_other ``` @@ -72,4 +72,4 @@ What To Do Next[🔗](#what-to-do-next "Permalink to this headline") If you want to access s3 files without mounting to the local computer, use command **s3cmd**. -[How to access private object storage using S3cmd or boto3 on 3Engines Cloud](../s3/How-to-access-private-object-storage-using-S3cmd-or-boto3-on-3Engines-Cloud.html.md) \ No newline at end of file +[How to access private object storage using S3cmd or boto3 on connectVM Cloud](../s3/How-to-access-private-object-storage-using-S3cmd-or-boto3-on-connectVM-Cloud.html.md) \ No newline at end of file diff --git a/docs/datavolume/How-to-move-data-volume-between-two-VMs-using-3Engines-Horizon-on-3Engines-Cloud.html.md b/docs/datavolume/How-to-move-data-volume-between-two-VMs-using-connectVM-Horizon-on-connectVM-Cloud.html.md similarity index 89% rename from docs/datavolume/How-to-move-data-volume-between-two-VMs-using-3Engines-Horizon-on-3Engines-Cloud.html.md rename to docs/datavolume/How-to-move-data-volume-between-two-VMs-using-connectVM-Horizon-on-connectVM-Cloud.html.md index 9bad034..2f8dc03 100644 --- a/docs/datavolume/How-to-move-data-volume-between-two-VMs-using-3Engines-Horizon-on-3Engines-Cloud.html.md +++ b/docs/datavolume/How-to-move-data-volume-between-two-VMs-using-connectVM-Horizon-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How to move data volume between two VMs using 3Engines Horizon on 3Engines Cloud[🔗](#how-to-move-data-volume-between-two-vms-using-3Engines-horizon-on-brand-name "Permalink to this headline") +How to move data volume between two VMs using connectVM Horizon on connectVM Cloud[🔗](#how-to-move-data-volume-between-two-vms-using-connectVM-horizon-on-brand-name "Permalink to this headline") =================================================================================================================================================================================================== Volumes are used to store data and those data can be accessed from a virtual machine to which the volume is attached. To access data stored on a volume from another virtual machine, you need to disconnect that volume from virtual machine to which it is currently connected, and connect it to another instance. @@ -10,7 +10,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . No. 2 **Source virtual machine and volume** diff --git a/docs/datavolume/How-to-restore-volume-from-snapshot-on-3Engines-Cloud.html.md b/docs/datavolume/How-to-restore-volume-from-snapshot-on-connectVM-Cloud.html.md similarity index 55% rename from docs/datavolume/How-to-restore-volume-from-snapshot-on-3Engines-Cloud.html.md rename to docs/datavolume/How-to-restore-volume-from-snapshot-on-connectVM-Cloud.html.md index 99197ce..e5aae02 100644 --- a/docs/datavolume/How-to-restore-volume-from-snapshot-on-3Engines-Cloud.html.md +++ b/docs/datavolume/How-to-restore-volume-from-snapshot-on-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -How to restore volume from snapshot on 3Engines Cloud[🔗](#how-to-restore-volume-from-snapshot-on-brand-name "Permalink to this headline") +How to restore volume from snapshot on connectVM Cloud[🔗](#how-to-restore-volume-from-snapshot-on-brand-name "Permalink to this headline") =========================================================================================================================================== -In this article, you will learn how to restore volume from volume snapshot using Horizon dashboard or 3Engines CLI client. +In this article, you will learn how to restore volume from volume snapshot using Horizon dashboard or connectVM CLI client. This can be achieved by creating a new volume from existing snapshot. You can then delete the previous snapshot and, optionally, previous volume. @@ -10,12 +10,12 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with access to Horizon interface: +You need a connectVM Cloud hosting account with access to Horizon interface: No. 2 **A volume snapshot** You need to have a volume snapshot which you want to restore. -No. 3 **3Engines CLI client** +No. 3 **connectVM CLI client** -If you want to interact with 3Engines Cloud cloud using the 3Engines CLI client, you need to have it installed. Check one of these articles: \ No newline at end of file +If you want to interact with connectVM Cloud cloud using the connectVM CLI client, you need to have it installed. Check one of these articles: \ No newline at end of file diff --git a/docs/datavolume/Volume-snapshot-inheritance-and-its-consequences-on-3Engines-Cloud.html.md b/docs/datavolume/Volume-snapshot-inheritance-and-its-consequences-on-connectVM-Cloud.html.md similarity index 79% rename from docs/datavolume/Volume-snapshot-inheritance-and-its-consequences-on-3Engines-Cloud.html.md rename to docs/datavolume/Volume-snapshot-inheritance-and-its-consequences-on-connectVM-Cloud.html.md index 6e67116..183724f 100644 --- a/docs/datavolume/Volume-snapshot-inheritance-and-its-consequences-on-3Engines-Cloud.html.md +++ b/docs/datavolume/Volume-snapshot-inheritance-and-its-consequences-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -Volume snapshot inheritance and its consequences on 3Engines Cloud[🔗](#volume-snapshot-inheritance-and-its-consequences-on-brand-name "Permalink to this headline") +Volume snapshot inheritance and its consequences on connectVM Cloud[🔗](#volume-snapshot-inheritance-and-its-consequences-on-brand-name "Permalink to this headline") ===================================================================================================================================================================== Performing a volume snapshot is a common form of securing your data against loss. @@ -13,7 +13,7 @@ Next we create an “SA” snapshot from the “VA” volume. ![volsnap2.png](../_images/volsnap2.png) -From the 3Engines dashboard we can create new volumes “Volume B” and “Volume C” based on the previously created snapshot “Snapshot A”. +From the connectVM dashboard we can create new volumes “Volume B” and “Volume C” based on the previously created snapshot “Snapshot A”. ![volsnap3.png](../_images/volsnap3.png) @@ -33,4 +33,4 @@ To delete a volume from which snapshots volumes were created, we must also delet In conclusion, when creating new volumes from a snapshot, remember about inheritance. Snapshot “Snapshot A” is a parent for the volumes (children) “Volume B” and “Volume C” and if we want to delete the volume “Volume A”, we have to do it from the youngest generation (Volume B and Volume C). -Backups are another solution and they do not create such bonds as snapshots and may exist even after the volume from which the backup was created has been deleted. Please see [How to Backup an Instance and Download it to the Desktop on 3Engines Cloud 3Engines Hosting](../3Enginescli/How-to-backup-an-instance-and-download-it-to-the-desktop-on-3Engines-Cloud.html.md). \ No newline at end of file +Backups are another solution and they do not create such bonds as snapshots and may exist even after the volume from which the backup was created has been deleted. Please see [How to Backup an Instance and Download it to the Desktop on connectVM Cloud connectVM Hosting](../connectVMcli/How-to-backup-an-instance-and-download-it-to-the-desktop-on-connectVM-Cloud.html.md). \ No newline at end of file diff --git a/docs/datavolume/datavolume.html.md b/docs/datavolume/datavolume.html.md index 71ce2be..2e17ee9 100644 --- a/docs/datavolume/datavolume.html.md +++ b/docs/datavolume/datavolume.html.md @@ -2,19 +2,19 @@ ## Available Documentation -* [How to attach a volume to VM less than 2TB on Linux on 3Engines Cloud](How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-3Engines-Cloud.html.md) -* [How to attach a volume to VM more than 2TB on Linux on 3Engines Cloud](How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-3Engines-Cloud.html.md) -* [Ephemeral vs Persistent storage option Create New Volume on 3Engines Cloud](Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-3Engines-Cloud.html.md) -* [How to export a volume over NFS on 3Engines Cloud](How-to-export-a-volume-over-NFS-on-3Engines-Cloud.html.md) -* [How to export a volume over NFS outside of a project on 3Engines Cloud](How-to-export-a-volume-over-NFS-outside-of-a-project-on-3Engines-Cloud.html.md) -* [How to extend the volume in Linux on 3Engines Cloud](How-to-extend-the-volume-in-Linux-on-3Engines-Cloud.html.md) -* [How to mount object storage in Linux on 3Engines Cloud](How-to-mount-object-storage-in-Linux-on-3Engines-Cloud.html.md) -* [How to move data volume between two VMs using 3Engines Horizon on 3Engines Cloud](How-to-move-data-volume-between-two-VMs-using-3Engines-Horizon-on-3Engines-Cloud.html.md) -* [How many objects can I put into Object Storage container bucket on 3Engines Cloud](How-many-objects-can-I-put-into-Object-Storage-container-bucket-on-3Engines-Cloud.html.md) -* [How to create volume Snapshot and attach as Volume on Linux or Windows on 3Engines Cloud](How-to-create-volume-Snapshot-and-attach-as-Volume-on-Linux-or-Windows-on-3Engines-Cloud.html.md) -* [Volume snapshot inheritance and its consequences on 3Engines Cloud](Volume-snapshot-inheritance-and-its-consequences-on-3Engines-Cloud.html.md) -* [How to Create Backup of Your Volume From Windows Machine on 3Engines Cloud](How-To-Create-Backup-Of-Your-Volume-From-Windows-Machine-on-3Engines-Cloud.html.md) -* [How To Attach Volume To Windows VM On 3Engines Cloud](How-To-Attach-Volume-To-Windows-VM-On-3Engines-Cloud.html.md) -* [How to create or delete volume snapshot on 3Engines Cloud](How-to-create-or-delete-volume-snapshot-on-3Engines-Cloud.html.md) -* [How to restore volume from snapshot on 3Engines Cloud](How-to-restore-volume-from-snapshot-on-3Engines-Cloud.html.md) -* [Bootable versus non-bootable volumes on 3Engines Cloud](Bootable-versus-non-bootable-volumes-on-3Engines-Cloud.html.md) +* [How to attach a volume to VM less than 2TB on Linux on connectVM Cloud](How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-connectVM-Cloud.html.md) +* [How to attach a volume to VM more than 2TB on Linux on connectVM Cloud](How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-connectVM-Cloud.html.md) +* [Ephemeral vs Persistent storage option Create New Volume on connectVM Cloud](Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-connectVM-Cloud.html.md) +* [How to export a volume over NFS on connectVM Cloud](How-to-export-a-volume-over-NFS-on-connectVM-Cloud.html.md) +* [How to export a volume over NFS outside of a project on connectVM Cloud](How-to-export-a-volume-over-NFS-outside-of-a-project-on-connectVM-Cloud.html.md) +* [How to extend the volume in Linux on connectVM Cloud](How-to-extend-the-volume-in-Linux-on-connectVM-Cloud.html.md) +* [How to mount object storage in Linux on connectVM Cloud](How-to-mount-object-storage-in-Linux-on-connectVM-Cloud.html.md) +* [How to move data volume between two VMs using connectVM Horizon on connectVM Cloud](How-to-move-data-volume-between-two-VMs-using-connectVM-Horizon-on-connectVM-Cloud.html.md) +* [How many objects can I put into Object Storage container bucket on connectVM Cloud](How-many-objects-can-I-put-into-Object-Storage-container-bucket-on-connectVM-Cloud.html.md) +* [How to create volume Snapshot and attach as Volume on Linux or Windows on connectVM Cloud](How-to-create-volume-Snapshot-and-attach-as-Volume-on-Linux-or-Windows-on-connectVM-Cloud.html.md) +* [Volume snapshot inheritance and its consequences on connectVM Cloud](Volume-snapshot-inheritance-and-its-consequences-on-connectVM-Cloud.html.md) +* [How to Create Backup of Your Volume From Windows Machine on connectVM Cloud](How-To-Create-Backup-Of-Your-Volume-From-Windows-Machine-on-connectVM-Cloud.html.md) +* [How To Attach Volume To Windows VM On connectVM Cloud](How-To-Attach-Volume-To-Windows-VM-On-connectVM-Cloud.html.md) +* [How to create or delete volume snapshot on connectVM Cloud](How-to-create-or-delete-volume-snapshot-on-connectVM-Cloud.html.md) +* [How to restore volume from snapshot on connectVM Cloud](How-to-restore-volume-from-snapshot-on-connectVM-Cloud.html.md) +* [Bootable versus non-bootable volumes on connectVM Cloud](Bootable-versus-non-bootable-volumes-on-connectVM-Cloud.html.md) diff --git a/docs/index.md b/docs/index.md index 5e65292..5d70735 100644 --- a/docs/index.md +++ b/docs/index.md @@ -1,6 +1,6 @@ -# Welcome to 3Engines Cloud Documentation 🌐 +# Welcome to connectVM Cloud Documentation 🌐 -> **3Engines Cloud** delivers **robust**, **scalable**, and **secure** cloud solutions for modern enterprises. Dive into our comprehensive documentation to kickstart your journey, manage resources efficiently, and optimize your cloud experience! 🚀 +> **connectVM Cloud** delivers **robust**, **scalable**, and **secure** cloud solutions for modern enterprises. Dive into our comprehensive documentation to kickstart your journey, manage resources efficiently, and optimize your cloud experience! 🚀 --- @@ -19,34 +19,34 @@ Get up and running with these essential guides: Essential steps to get your virtual machine up and running with proper configuration: ### 1. Key Pair Management 🔑 -- **Create SSH Key Pair**: [How to create key pair in 3Engines Dashboard](cloud/How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md) -- **Import SSH Key**: [How to import SSH public key to 3Engines Horizon](networking/How-to-Import-SSH-Public-Key-to-3Engines-Horizon-on-3Engines-Cloud.html.md) -- **Generate SSH Key in Linux**: [Generating an SSH keypair in Linux](networking/Generating-a-SSH-keypair-in-Linux-on-3Engines-Cloud.html.md) +- **Create SSH Key Pair**: [How to create key pair in connectVM Dashboard](cloud/How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md) +- **Import SSH Key**: [How to import SSH public key to connectVM Horizon](networking/How-to-Import-SSH-Public-Key-to-connectVM-Horizon-on-connectVM-Cloud.html.md) +- **Generate SSH Key in Linux**: [Generating an SSH keypair in Linux](networking/Generating-a-SSH-keypair-in-Linux-on-connectVM-Cloud.html.md) ### 2. Private Networks & Router Setup 🌐 -- **Create Network with Router**: [How to create a network with router in Horizon Dashboard](networking/How-to-create-a-network-with-router-in-Horizon-Dashboard-on-3Engines-Cloud.html.md) -- **Understanding Projects**: [What is an 3Engines project](cloud/What-is-an-3Engines-project-on-3Engines-Cloud.html.md) -- **Understanding Domains**: [What is an 3Engines domain](cloud/What-is-an-3Engines-domain-on-3Engines-Cloud.html.md) +- **Create Network with Router**: [How to create a network with router in Horizon Dashboard](networking/How-to-create-a-network-with-router-in-Horizon-Dashboard-on-connectVM-Cloud.html.md) +- **Understanding Projects**: [What is an connectVM project](cloud/What-is-an-connectVM-project-on-connectVM-Cloud.html.md) +- **Understanding Domains**: [What is an connectVM domain](cloud/What-is-an-connectVM-domain-on-connectVM-Cloud.html.md) ### 3. Security Groups Configuration 🛡️ -- **Setup Security Groups**: [How to use Security Groups in Horizon](cloud/How-to-use-Security-Groups-in-Horizon-on-3Engines-Cloud.html.md) -- **Open HTTP Ports**: [How to open new ports for http](networking/How-can-I-open-new-ports-port-80-for-http-for-my-service-or-instance-on-3Engines-Cloud.html.md) -- **SSH Access Troubleshooting**: [Cannot access VM with SSH or PING](networking/Cannot-access-VM-with-SSH-or-PING-on-3Engines-Cloud.html.md) +- **Setup Security Groups**: [How to use Security Groups in Horizon](cloud/How-to-use-Security-Groups-in-Horizon-on-connectVM-Cloud.html.md) +- **Open HTTP Ports**: [How to open new ports for http](networking/How-can-I-open-new-ports-port-80-for-http-for-my-service-or-instance-on-connectVM-Cloud.html.md) +- **SSH Access Troubleshooting**: [Cannot access VM with SSH or PING](networking/Cannot-access-VM-with-SSH-or-PING-on-connectVM-Cloud.html.md) ### 4. VM Instance Creation 💻 -- **Create Linux VM**: [How to create new Linux VM in 3Engines Dashboard Horizon](cloud/How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md) -- **Access VM Console**: [How to access the VM from 3Engines console](cloud/How-to-access-the-VM-from-3Engines-console-on-3Engines-Cloud.html.md) -- **Storage Options**: [VM created with option Create New Volume](cloud/VM-created-with-option-Create-New-Volume-Yes-on-3Engines-Cloud.html.md) +- **Create Linux VM**: [How to create new Linux VM in connectVM Dashboard Horizon](cloud/How-to-create-new-Linux-VM-in-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md) +- **Access VM Console**: [How to access the VM from connectVM console](cloud/How-to-access-the-VM-from-connectVM-console-on-connectVM-Cloud.html.md) +- **Storage Options**: [VM created with option Create New Volume](cloud/VM-created-with-option-Create-New-Volume-Yes-on-connectVM-Cloud.html.md) ### 5. Floating IP Assignment 🌍 -- **Add/Remove Floating IPs**: [How to Add or Remove Floating IP's to your VM](networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md) -- **SSH Connection**: [How to connect to your virtual machine via SSH in Linux](networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-3Engines-Cloud.html.md) -- **Linux Command Line Access**: [How to create a Linux VM and access it from Linux command line](cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md) +- **Add/Remove Floating IPs**: [How to Add or Remove Floating IP's to your VM](networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md) +- **SSH Connection**: [How to connect to your virtual machine via SSH in Linux](networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-connectVM-Cloud.html.md) +- **Linux Command Line Access**: [How to create a Linux VM and access it from Linux command line](cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md) ### 6. Quick Reference URLs 📖 -- **Dashboard Overview**: [Project Quotas And Flavors Limits](cloud/Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-3Engines-Cloud.html.md) -- **User Roles**: [3Engines User Roles](cloud/3Engines-user-roles-on-3Engines-Cloud.html.md) -- **VM Management**: [How to clone existing and configured VMs](cloud/How-to-clone-existing-and-configured-VMs-on-3Engines-Cloud.html.md) +- **Dashboard Overview**: [Project Quotas And Flavors Limits](cloud/Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-connectVM-Cloud.html.md) +- **User Roles**: [connectVM User Roles](cloud/connectVM-user-roles-on-connectVM-Cloud.html.md) +- **VM Management**: [How to clone existing and configured VMs](cloud/How-to-clone-existing-and-configured-VMs-on-connectVM-Cloud.html.md) > **💡 Pro Tip**: Follow the sequence above for a smooth VM setup experience. Start with key pairs, configure networking, set up security groups, create your VM, and finally assign floating IPs for external access. @@ -78,7 +78,7 @@ Stay updated with the latest changes and features in [Release Notes](releasenote Need assistance? Our dedicated support team is here to help! - **General Support**: [support@rootxwire.com](mailto:support@rootxwire.com) - **Admin Inquiries**: [admin@rootxwire.com](mailto:admin@rootxwire.com) -We’re committed to ensuring your success on 3Engines Cloud! 🌟 +We’re committed to ensuring your success on connectVM Cloud! 🌟 --- @@ -92,153 +92,153 @@ We’re committed to ensuring your success on 3Engines Cloud! 🌟 ## CLOUD ☁️ -- [Dashboard Overview – Project Quotas And Flavors Limits on 3Engines Cloud](cloud/Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-3Engines-Cloud.html.md) -- [How to access the VM from 3Engines console on 3Engines Cloud](cloud/How-to-access-the-VM-from-3Engines-console-on-3Engines-Cloud.html.md) -- [How to clone existing and configured VMs on 3Engines Cloud](cloud/How-to-clone-existing-and-configured-VMs-on-3Engines-Cloud.html.md) -- [How to fix unresponsive console issue on 3Engines Cloud](cloud/How-to-fix-unresponsive-console-issue-on-3Engines-Cloud.html.md) -- [How to generate and manage EC2 credentials on 3Engines Cloud](cloud/How-to-generate-ec2-credentials-on-3Engines-Cloud.html.md) -- [How to generate or use Application Credentials via CLI on 3Engines Cloud](cloud/How-to-generate-or-use-Application-Credentials-via-CLI-on-3Engines-Cloud.html.md) -- [How to Use GUI in Linux VM on 3Engines Cloud and access it From Local Linux Computer](cloud/How-to-use-GUI-in-Linux-VM-on-3Engines-Cloud-and-access-it-from-local-Linux-computer.html.md) -- [How To Create a New Linux VM With NVIDIA Virtual GPU in the 3Engines Dashboard Horizon on 3Engines Cloud](cloud/How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md) -- [How to install and use Docker on Ubuntu 24.04](cloud/How-to-use-Docker-on-3Engines-Cloud.html.md) -- [How to use Security Groups in Horizon on 3Engines Cloud](cloud/How-to-use-Security-Groups-in-Horizon-on-3Engines-Cloud.html.md) -- [How to create key pair in 3Engines Dashboard on 3Engines Cloud](cloud/How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md) -- [How to create new Linux VM in 3Engines Dashboard Horizon on 3Engines Cloud](cloud/How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md) -- [How to install Python virtualenv or virtualenvwrapper on 3Engines Cloud](cloud/How-to-install-Python-virtualenv-or-virtualenvwrapper-on-3Engines-Cloud.html.md) -- [How to start a VM from a snapshot on 3Engines Cloud](cloud/How-to-start-a-VM-from-a-snapshot-on-3Engines-Cloud.html.md) -- [Status Power State and dependencies in billing of instance VMs on 3Engines Cloud](cloud/Status-Power-State-and-dependences-in-billing-of-instances-VMs-on-3Engines-Cloud.html.md) -- [How to upload your custom image using 3Engines CLI on 3Engines Cloud](cloud/How-to-upload-your-custom-image-using-3Engines-CLI-on-3Engines-Cloud.html.md) -- [VM created with option Create New Volume No on 3Engines Cloud](cloud/VM-created-with-option-Create-New-Volume-No-on-3Engines-Cloud.html.md) -- [VM created with option Create New Volume Yes on 3Engines Cloud](cloud/VM-created-with-option-Create-New-Volume-Yes-on-3Engines-Cloud.html.md) -- [What is an 3Engines domain on 3Engines Cloud](cloud/What-is-an-3Engines-domain-on-3Engines-Cloud.html.md) -- [What is an 3Engines project on 3Engines Cloud](cloud/What-is-an-3Engines-project-on-3Engines-Cloud.html.md) -- [How to create a Linux VM and access it from Windows desktop on 3Engines Cloud](cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md) -- [How to create a Linux VM and access it from Linux command line on 3Engines Cloud](cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md) -- [DNS as a Service on 3Engines Cloud Hosting](cloud/DNS-as-a-Service-on-3Engines-Cloud-Hosting.html.md) -- [What Image Formats are Available in 3Engines 3Engines Cloud cloud](cloud/What-Image-Formats-are-available-in-3Engines-3Engines-Cloud-Cloud.html.md) -- [How to upload custom image to 3Engines Cloud cloud using 3Engines Horizon dashboard](cloud/How-to-upload-custom-image-to-3Engines-Cloud-cloud-using-3Engines-Horizon-dashboard.html.md) -- [How to create Windows VM on 3Engines Horizon and access it via web console on 3Engines Cloud](cloud/How-to-create-Windows-VM-on-3Engines-Horizon-and-access-it-via-web-console-on-3Engines-Cloud.html.md) -- [How to transfer volumes between domains and projects using Horizon dashboard on 3Engines Cloud](cloud/How-to-transfer-volumes-between-domains-and-projects-using-Horizon-dashboard-on-3Engines-Cloud.html.md) -- [Spot instances on 3Engines Cloud](cloud/Spot-instances-on-3Engines-Cloud.html.md) -- [How to create instance snapshot using Horizon on 3Engines Cloud](cloud/How-to-create-instance-snapshot-using-Horizon-on-3Engines-Cloud.html.md) -- [How to start a VM from instance snapshot using Horizon dashboard on 3Engines Cloud](cloud/How-to-start-a-VM-from-instance-snapshot-using-Horizon-dashboard-on-3Engines-Cloud.html.md) -- [How to create a VM using the 3Engines CLI client on 3Engines Cloud cloud](cloud/How-to-create-a-VM-using-the-3Engines-CLI-client-on-3Engines-Cloud-cloud.html.md) -- [3Engines User Roles on 3Engines Cloud](cloud/3Engines-user-roles-on-3Engines-Cloud.html.md) -- [Resizing a virtual machine using 3Engines Horizon on 3Engines Cloud](cloud/Resizing-a-virtual-machine-using-3Engines-Horizon-on-3Engines-Cloud.html.md) -- [Block storage and object storage performance limits on 3Engines Cloud](cloud/Block-storage-and-object-storage-performance-limits-on-3Engines-Cloud.html.md) +- [Dashboard Overview – Project Quotas And Flavors Limits on connectVM Cloud](cloud/Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-connectVM-Cloud.html.md) +- [How to access the VM from connectVM console on connectVM Cloud](cloud/How-to-access-the-VM-from-connectVM-console-on-connectVM-Cloud.html.md) +- [How to clone existing and configured VMs on connectVM Cloud](cloud/How-to-clone-existing-and-configured-VMs-on-connectVM-Cloud.html.md) +- [How to fix unresponsive console issue on connectVM Cloud](cloud/How-to-fix-unresponsive-console-issue-on-connectVM-Cloud.html.md) +- [How to generate and manage EC2 credentials on connectVM Cloud](cloud/How-to-generate-ec2-credentials-on-connectVM-Cloud.html.md) +- [How to generate or use Application Credentials via CLI on connectVM Cloud](cloud/How-to-generate-or-use-Application-Credentials-via-CLI-on-connectVM-Cloud.html.md) +- [How to Use GUI in Linux VM on connectVM Cloud and access it From Local Linux Computer](cloud/How-to-use-GUI-in-Linux-VM-on-connectVM-Cloud-and-access-it-from-local-Linux-computer.html.md) +- [How To Create a New Linux VM With NVIDIA Virtual GPU in the connectVM Dashboard Horizon on connectVM Cloud](cloud/How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md) +- [How to install and use Docker on Ubuntu 24.04](cloud/How-to-use-Docker-on-connectVM-Cloud.html.md) +- [How to use Security Groups in Horizon on connectVM Cloud](cloud/How-to-use-Security-Groups-in-Horizon-on-connectVM-Cloud.html.md) +- [How to create key pair in connectVM Dashboard on connectVM Cloud](cloud/How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md) +- [How to create new Linux VM in connectVM Dashboard Horizon on connectVM Cloud](cloud/How-to-create-new-Linux-VM-in-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md) +- [How to install Python virtualenv or virtualenvwrapper on connectVM Cloud](cloud/How-to-install-Python-virtualenv-or-virtualenvwrapper-on-connectVM-Cloud.html.md) +- [How to start a VM from a snapshot on connectVM Cloud](cloud/How-to-start-a-VM-from-a-snapshot-on-connectVM-Cloud.html.md) +- [Status Power State and dependencies in billing of instance VMs on connectVM Cloud](cloud/Status-Power-State-and-dependences-in-billing-of-instances-VMs-on-connectVM-Cloud.html.md) +- [How to upload your custom image using connectVM CLI on connectVM Cloud](cloud/How-to-upload-your-custom-image-using-connectVM-CLI-on-connectVM-Cloud.html.md) +- [VM created with option Create New Volume No on connectVM Cloud](cloud/VM-created-with-option-Create-New-Volume-No-on-connectVM-Cloud.html.md) +- [VM created with option Create New Volume Yes on connectVM Cloud](cloud/VM-created-with-option-Create-New-Volume-Yes-on-connectVM-Cloud.html.md) +- [What is an connectVM domain on connectVM Cloud](cloud/What-is-an-connectVM-domain-on-connectVM-Cloud.html.md) +- [What is an connectVM project on connectVM Cloud](cloud/What-is-an-connectVM-project-on-connectVM-Cloud.html.md) +- [How to create a Linux VM and access it from Windows desktop on connectVM Cloud](cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-connectVM-Cloud.html.md) +- [How to create a Linux VM and access it from Linux command line on connectVM Cloud](cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md) +- [DNS as a Service on connectVM Cloud Hosting](cloud/DNS-as-a-Service-on-connectVM-Cloud-Hosting.html.md) +- [What Image Formats are Available in connectVM connectVM Cloud cloud](cloud/What-Image-Formats-are-available-in-connectVM-connectVM-Cloud-Cloud.html.md) +- [How to upload custom image to connectVM Cloud cloud using connectVM Horizon dashboard](cloud/How-to-upload-custom-image-to-connectVM-Cloud-cloud-using-connectVM-Horizon-dashboard.html.md) +- [How to create Windows VM on connectVM Horizon and access it via web console on connectVM Cloud](cloud/How-to-create-Windows-VM-on-connectVM-Horizon-and-access-it-via-web-console-on-connectVM-Cloud.html.md) +- [How to transfer volumes between domains and projects using Horizon dashboard on connectVM Cloud](cloud/How-to-transfer-volumes-between-domains-and-projects-using-Horizon-dashboard-on-connectVM-Cloud.html.md) +- [Spot instances on connectVM Cloud](cloud/Spot-instances-on-connectVM-Cloud.html.md) +- [How to create instance snapshot using Horizon on connectVM Cloud](cloud/How-to-create-instance-snapshot-using-Horizon-on-connectVM-Cloud.html.md) +- [How to start a VM from instance snapshot using Horizon dashboard on connectVM Cloud](cloud/How-to-start-a-VM-from-instance-snapshot-using-Horizon-dashboard-on-connectVM-Cloud.html.md) +- [How to create a VM using the connectVM CLI client on connectVM Cloud cloud](cloud/How-to-create-a-VM-using-the-connectVM-CLI-client-on-connectVM-Cloud-cloud.html.md) +- [connectVM User Roles on connectVM Cloud](cloud/connectVM-user-roles-on-connectVM-Cloud.html.md) +- [Resizing a virtual machine using connectVM Horizon on connectVM Cloud](cloud/Resizing-a-virtual-machine-using-connectVM-Horizon-on-connectVM-Cloud.html.md) +- [Block storage and object storage performance limits on connectVM Cloud](cloud/Block-storage-and-object-storage-performance-limits-on-connectVM-Cloud.html.md) ## DATA VOLUME 💾 -- [How to attach a volume to VM less than 2TB on Linux on 3Engines Cloud](datavolume/How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-3Engines-Cloud.html.md) -- [How to attach a volume to VM more than 2TB on Linux on 3Engines Cloud](datavolume/How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-3Engines-Cloud.html.md) -- [Ephemeral vs Persistent storage option Create New Volume on 3Engines Cloud](datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-3Engines-Cloud.html.md) -- [How to export a volume over NFS on 3Engines Cloud](datavolume/How-to-export-a-volume-over-NFS-on-3Engines-Cloud.html.md) -- [How to export a volume over NFS outside of a project on 3Engines Cloud](datavolume/How-to-export-a-volume-over-NFS-outside-of-a-project-on-3Engines-Cloud.html.md) -- [How to extend the volume in Linux on 3Engines Cloud](datavolume/How-to-extend-the-volume-in-Linux-on-3Engines-Cloud.html.md) -- [How to mount object storage in Linux on 3Engines Cloud](datavolume/How-to-mount-object-storage-in-Linux-on-3Engines-Cloud.html.md) -- [How to move data volume between two VMs using 3Engines Horizon on 3Engines Cloud](datavolume/How-to-move-data-volume-between-two-VMs-using-3Engines-Horizon-on-3Engines-Cloud.html.md) -- [How many objects can I put into Object Storage container bucket on 3Engines Cloud](datavolume/How-many-objects-can-I-put-into-Object-Storage-container-bucket-on-3Engines-Cloud.html.md) -- [How to create volume Snapshot and attach as Volume on Linux or Windows on 3Engines Cloud](datavolume/How-to-create-volume-Snapshot-and-attach-as-Volume-on-Linux-or-Windows-on-3Engines-Cloud.html.md) -- [Volume snapshot inheritance and its consequences on 3Engines Cloud](datavolume/Volume-snapshot-inheritance-and-its-consequences-on-3Engines-Cloud.html.md) -- [How to Create Backup of Your Volume From Windows Machine on 3Engines Cloud](datavolume/How-To-Create-Backup-Of-Your-Volume-From-Windows-Machine-on-3Engines-Cloud.html.md) -- [How To Attach Volume To Windows VM On 3Engines Cloud](datavolume/How-To-Attach-Volume-To-Windows-VM-On-3Engines-Cloud.html.md) -- [How to create or delete volume snapshot on 3Engines Cloud](datavolume/How-to-create-or-delete-volume-snapshot-on-3Engines-Cloud.html.md) -- [How to restore volume from snapshot on 3Engines Cloud](datavolume/How-to-restore-volume-from-snapshot-on-3Engines-Cloud.html.md) -- [Bootable versus non-bootable volumes on 3Engines Cloud](datavolume/Bootable-versus-non-bootable-volumes-on-3Engines-Cloud.html.md) +- [How to attach a volume to VM less than 2TB on Linux on connectVM Cloud](datavolume/How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-connectVM-Cloud.html.md) +- [How to attach a volume to VM more than 2TB on Linux on connectVM Cloud](datavolume/How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-connectVM-Cloud.html.md) +- [Ephemeral vs Persistent storage option Create New Volume on connectVM Cloud](datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-connectVM-Cloud.html.md) +- [How to export a volume over NFS on connectVM Cloud](datavolume/How-to-export-a-volume-over-NFS-on-connectVM-Cloud.html.md) +- [How to export a volume over NFS outside of a project on connectVM Cloud](datavolume/How-to-export-a-volume-over-NFS-outside-of-a-project-on-connectVM-Cloud.html.md) +- [How to extend the volume in Linux on connectVM Cloud](datavolume/How-to-extend-the-volume-in-Linux-on-connectVM-Cloud.html.md) +- [How to mount object storage in Linux on connectVM Cloud](datavolume/How-to-mount-object-storage-in-Linux-on-connectVM-Cloud.html.md) +- [How to move data volume between two VMs using connectVM Horizon on connectVM Cloud](datavolume/How-to-move-data-volume-between-two-VMs-using-connectVM-Horizon-on-connectVM-Cloud.html.md) +- [How many objects can I put into Object Storage container bucket on connectVM Cloud](datavolume/How-many-objects-can-I-put-into-Object-Storage-container-bucket-on-connectVM-Cloud.html.md) +- [How to create volume Snapshot and attach as Volume on Linux or Windows on connectVM Cloud](datavolume/How-to-create-volume-Snapshot-and-attach-as-Volume-on-Linux-or-Windows-on-connectVM-Cloud.html.md) +- [Volume snapshot inheritance and its consequences on connectVM Cloud](datavolume/Volume-snapshot-inheritance-and-its-consequences-on-connectVM-Cloud.html.md) +- [How to Create Backup of Your Volume From Windows Machine on connectVM Cloud](datavolume/How-To-Create-Backup-Of-Your-Volume-From-Windows-Machine-on-connectVM-Cloud.html.md) +- [How To Attach Volume To Windows VM On connectVM Cloud](datavolume/How-To-Attach-Volume-To-Windows-VM-On-connectVM-Cloud.html.md) +- [How to create or delete volume snapshot on connectVM Cloud](datavolume/How-to-create-or-delete-volume-snapshot-on-connectVM-Cloud.html.md) +- [How to restore volume from snapshot on connectVM Cloud](datavolume/How-to-restore-volume-from-snapshot-on-connectVM-Cloud.html.md) +- [Bootable versus non-bootable volumes on connectVM Cloud](datavolume/Bootable-versus-non-bootable-volumes-on-connectVM-Cloud.html.md) ## NETWORKING 🌍 -- [How can I access my VMs using names instead of IP addresses on 3Engines Cloud](networking/How-can-I-access-my-VMs-using-names-instead-of-IP-addresses-on-3Engines-Cloud.html.md) -- [How to Add or Remove Floating IP’s to your VM on 3Engines Cloud](networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md) -- [Cannot access VM with SSH or PING on 3Engines Cloud](networking/Cannot-access-VM-with-SSH-or-PING-on-3Engines-Cloud.html.md) -- [Cannot ping VM on 3Engines Cloud](networking/Cannot-ping-VM-on-3Engines-Cloud.html.md) -- [How to connect to your virtual machine via SSH in Linux on 3Engines Cloud](networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-3Engines-Cloud.html.md) -- [How to create a network with router in Horizon Dashboard on 3Engines Cloud](networking/How-to-create-a-network-with-router-in-Horizon-Dashboard-on-3Engines-Cloud.html.md) -- [How can I open new ports for http for my service or instance on 3Engines Cloud](networking/How-can-I-open-new-ports-port-80-for-http-for-my-service-or-instance-on-3Engines-Cloud.html.md) -- [Generating an SSH keypair in Linux on 3Engines Cloud](networking/Generating-a-SSH-keypair-in-Linux-on-3Engines-Cloud.html.md) -- [How to add SSH key from Horizon web console on 3Engines Cloud](networking/How-to-add-SSH-key-from-Horizon-web-console-on-3Engines-Cloud.html.md) -- [How is my VM visible in the internet with no Floating IP attached on 3Engines Cloud](networking/How-is-my-VM-visible-in-the-internet-with-no-Floating-IP-attached-on-3Engines-Cloud.html.md) -- [How to run and configure Firewall as a service and VPN as a service on 3Engines Cloud](networking/How-to-run-and-configure-Firewall-as-a-service-and-VPN-as-a-service-on-3Engines-Cloud.html.md) -- [How to import SSH public key to 3Engines Horizon on 3Engines Cloud](networking/How-to-Import-SSH-Public-Key-to-3Engines-Horizon-on-3Engines-Cloud.html.md) +- [How can I access my VMs using names instead of IP addresses on connectVM Cloud](networking/How-can-I-access-my-VMs-using-names-instead-of-IP-addresses-on-connectVM-Cloud.html.md) +- [How to Add or Remove Floating IP’s to your VM on connectVM Cloud](networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md) +- [Cannot access VM with SSH or PING on connectVM Cloud](networking/Cannot-access-VM-with-SSH-or-PING-on-connectVM-Cloud.html.md) +- [Cannot ping VM on connectVM Cloud](networking/Cannot-ping-VM-on-connectVM-Cloud.html.md) +- [How to connect to your virtual machine via SSH in Linux on connectVM Cloud](networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-connectVM-Cloud.html.md) +- [How to create a network with router in Horizon Dashboard on connectVM Cloud](networking/How-to-create-a-network-with-router-in-Horizon-Dashboard-on-connectVM-Cloud.html.md) +- [How can I open new ports for http for my service or instance on connectVM Cloud](networking/How-can-I-open-new-ports-port-80-for-http-for-my-service-or-instance-on-connectVM-Cloud.html.md) +- [Generating an SSH keypair in Linux on connectVM Cloud](networking/Generating-a-SSH-keypair-in-Linux-on-connectVM-Cloud.html.md) +- [How to add SSH key from Horizon web console on connectVM Cloud](networking/How-to-add-SSH-key-from-Horizon-web-console-on-connectVM-Cloud.html.md) +- [How is my VM visible in the internet with no Floating IP attached on connectVM Cloud](networking/How-is-my-VM-visible-in-the-internet-with-no-Floating-IP-attached-on-connectVM-Cloud.html.md) +- [How to run and configure Firewall as a service and VPN as a service on connectVM Cloud](networking/How-to-run-and-configure-Firewall-as-a-service-and-VPN-as-a-service-on-connectVM-Cloud.html.md) +- [How to import SSH public key to connectVM Horizon on connectVM Cloud](networking/How-to-Import-SSH-Public-Key-to-connectVM-Horizon-on-connectVM-Cloud.html.md) - + - + \ No newline at end of file diff --git a/docs/kubernetes/Automatic-Kubernetes-cluster-upgrade-on-3Engines-Cloud-3Engines-Magnum.html.md b/docs/kubernetes/Automatic-Kubernetes-cluster-upgrade-on-3Engines-Cloud-3Engines-Magnum.html.md deleted file mode 100644 index 3c2109b..0000000 --- a/docs/kubernetes/Automatic-Kubernetes-cluster-upgrade-on-3Engines-Cloud-3Engines-Magnum.html.md +++ /dev/null @@ -1,12 +0,0 @@ -Automatic Kubernetes cluster upgrade on 3Engines Cloud 3Engines Magnum[🔗](#automatic-kubernetes-cluster-upgrade-on-brand-name-3Engines-magnum "Permalink to this headline") -=============================================================================================================================================================================== - -Warning - -Upgradeable cluster templates are available on 3Engines Cloud WAW4-1 region only at the moment of this writing. - -3Engines Magnum clusters created in 3Engines Cloud can be **automatically** upgraded to the next minor Kubernetes version. This feature is available for clusters starting with version 1.29 of Kubernetes. - -In this article we demonstrate an upgrade of a Magnum Kubernetes cluster from version 1.29 to version 1.30. - -What are we going to cover \ No newline at end of file diff --git a/docs/kubernetes/Automatic-Kubernetes-cluster-upgrade-on-connectVM-Cloud-connectVM-Magnum.html.md b/docs/kubernetes/Automatic-Kubernetes-cluster-upgrade-on-connectVM-Cloud-connectVM-Magnum.html.md new file mode 100644 index 0000000..2d2f27c --- /dev/null +++ b/docs/kubernetes/Automatic-Kubernetes-cluster-upgrade-on-connectVM-Cloud-connectVM-Magnum.html.md @@ -0,0 +1,12 @@ +Automatic Kubernetes cluster upgrade on connectVM Cloud connectVM Magnum[🔗](#automatic-kubernetes-cluster-upgrade-on-brand-name-connectVM-magnum "Permalink to this headline") +=============================================================================================================================================================================== + +Warning + +Upgradeable cluster templates are available on connectVM Cloud WAW4-1 region only at the moment of this writing. + +connectVM Magnum clusters created in connectVM Cloud can be **automatically** upgraded to the next minor Kubernetes version. This feature is available for clusters starting with version 1.29 of Kubernetes. + +In this article we demonstrate an upgrade of a Magnum Kubernetes cluster from version 1.29 to version 1.30. + +What are we going to cover \ No newline at end of file diff --git a/docs/kubernetes/Autoscaling-Kubernetes-Cluster-Resources-on-3Engines-Cloud-3Engines-Magnum.html.md b/docs/kubernetes/Autoscaling-Kubernetes-Cluster-Resources-on-connectVM-Cloud-connectVM-Magnum.html.md similarity index 77% rename from docs/kubernetes/Autoscaling-Kubernetes-Cluster-Resources-on-3Engines-Cloud-3Engines-Magnum.html.md rename to docs/kubernetes/Autoscaling-Kubernetes-Cluster-Resources-on-connectVM-Cloud-connectVM-Magnum.html.md index 39560ce..3a59667 100644 --- a/docs/kubernetes/Autoscaling-Kubernetes-Cluster-Resources-on-3Engines-Cloud-3Engines-Magnum.html.md +++ b/docs/kubernetes/Autoscaling-Kubernetes-Cluster-Resources-on-connectVM-Cloud-connectVM-Magnum.html.md @@ -1,4 +1,4 @@ -Autoscaling Kubernetes Cluster Resources on 3Engines Cloud 3Engines Magnum[🔗](#autoscaling-kubernetes-cluster-resources-on-brand-name-3Engines-magnum "Permalink to this headline") +Autoscaling Kubernetes Cluster Resources on connectVM Cloud connectVM Magnum[🔗](#autoscaling-kubernetes-cluster-resources-on-brand-name-connectVM-magnum "Permalink to this headline") ======================================================================================================================================================================================= When **autoscaling of Kubernetes clusters** is turned on, the system can @@ -7,7 +7,7 @@ When **autoscaling of Kubernetes clusters** is turned on, the system can > * Remove unneeded resources when the demand is low and thus keep the costs down. > * The whole process can be automatic, helping the administrator concentrate on more important tasks at hand. -This article explains various commands to resize or scale the cluster and will lead to a command to automatically create an autoscalable Kubernetes cluster for 3Engines Magnum. +This article explains various commands to resize or scale the cluster and will lead to a command to automatically create an autoscalable Kubernetes cluster for connectVM Magnum. What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -23,23 +23,23 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . No. 2 **Creating clusters with CLI** -The article [How To Use Command Line Interface for Kubernetes Clusters On 3Engines Cloud 3Engines Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-3Engines-Cloud-3Engines-Magnum.html.md) will introduce you to creation of clusters using a command line interface. +The article [How To Use Command Line Interface for Kubernetes Clusters On connectVM Cloud connectVM Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-connectVM-Cloud-connectVM-Magnum.html.md) will introduce you to creation of clusters using a command line interface. -No. 3 **Connect 3Engines client to the cloud** +No. 3 **Connect connectVM client to the cloud** -Prepare **3Engines** and **magnum** clients by executing *Step 2 Connect 3Engines and Magnum Clients to Horizon Cloud* from article [How To Install 3Engines and Magnum Clients for Command Line Interface to 3Engines Cloud Horizon](How-To-Install-3Engines-and-Magnum-Clients-for-Command-Line-Interface-to-3Engines-Cloud-Horizon.html.md) +Prepare **connectVM** and **magnum** clients by executing *Step 2 Connect connectVM and Magnum Clients to Horizon Cloud* from article [How To Install connectVM and Magnum Clients for Command Line Interface to connectVM Cloud Horizon](How-To-Install-connectVM-and-Magnum-Clients-for-Command-Line-Interface-to-connectVM-Cloud-Horizon.html.md) No. 4. **Resizing Nodegroups** -Step 7 of article [Creating Additional Nodegroups in Kubernetes Cluster on 3Engines Cloud 3Engines Magnum](Creating-Additional-Nodegroups-in-Kubernetes-Cluster-on-3Engines-Cloud-3Engines-Magnum.html.md) shows example of resizing the nodegroups for autoscaling. +Step 7 of article [Creating Additional Nodegroups in Kubernetes Cluster on connectVM Cloud connectVM Magnum](Creating-Additional-Nodegroups-in-Kubernetes-Cluster-on-connectVM-Cloud-connectVM-Magnum.html.md) shows example of resizing the nodegroups for autoscaling. No. 5 **Creating Clusters** -Step 2 of article [How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md) shows how to define master and worker nodes for autoscaling. +Step 2 of article [How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md) shows how to define master and worker nodes for autoscaling. There are three different autoscaling features that a Kubernetes cloud can offer: @@ -85,7 +85,7 @@ Autoscaling Node Groups at Run Time[🔗](#autoscaling-node-groups-at-run-time " The autoscaler in Magnum uses Node Groups. Node groups can be used to create workers with different flavors. The default-worker node group is automatically created when cluster is provisioned. Node groups have lower and upper limits of node count. This is the command to print them out for a given cluster: ``` -3Engines coe nodegroup show NoLoadBalancer default-worker -f json -c max_node_count -c node_count -c min_node_count +connectVM coe nodegroup show NoLoadBalancer default-worker -f json -c max_node_count -c node_count -c min_node_count ``` @@ -103,7 +103,7 @@ The result would be: This works fine until you try to resize cluster beyond the limit set in node group. If you try to resize the above cluster to 12 nodes, like this: ``` -3Engines coe cluster resize NoLoadBalancer --nodegroup default-worker 12 +connectVM coe cluster resize NoLoadBalancer --nodegroup default-worker 12 ``` @@ -117,18 +117,18 @@ Resizing default-worker outside the allowed range: min_node_count = 1, max_node_ To resolve this error, change *node\_group max\_node\_count* manually: ``` -3Engines coe nodegroup update NoLoadBalancer default-worker replace max_node_count=15 +connectVM coe nodegroup update NoLoadBalancer default-worker replace max_node_count=15 ``` and then resize cluster to the desired value which was less that 15 in this example: -3Engines coe cluster resize NoLoadBalancer –nodegroup default-worker 12 +connectVM coe cluster resize NoLoadBalancer –nodegroup default-worker 12 If you repeat the first statement: ``` -3Engines coe nodegroup show NoLoadBalancer default-worker -f json -c max_node_count -c node_count -c min_node_count +connectVM coe nodegroup show NoLoadBalancer default-worker -f json -c max_node_count -c node_count -c min_node_count ``` @@ -149,7 +149,7 @@ How Autoscaling Detects Upper Limit[🔗](#how-autoscaling-detects-upper-limit " The first version of Autoscaling would take the current upper limit of autoscaling in variable *node\_count* and add 1 to it. If the command to create a cluster were ``` -3Engines coe cluster create mycluster --cluster-template mytemplate --node-count 8 --master-count 3 +connectVM coe cluster create mycluster --cluster-template mytemplate --node-count 8 --master-count 3 ``` @@ -158,7 +158,7 @@ that version of Autoscaler would take the value of **9** (counting as **8 + 1**) The current Autoscaler can support multiple node groups by detecting the role of the node group: ``` -3Engines coe nodegroup show NoLoadBalancer default-worker -f json -c role +connectVM coe nodegroup show NoLoadBalancer default-worker -f json -c role ``` @@ -177,7 +177,7 @@ Attention Any additional node group must include concrete *max\_node\_count* attribute. -See Prerequisites No. 4 for detailed examples of using the **3Engines coe nodegroup** family of commands. +See Prerequisites No. 4 for detailed examples of using the **connectVM coe nodegroup** family of commands. Autoscaling Labels for Clusters[🔗](#autoscaling-labels-for-clusters "Permalink to this headline") ------------------------------------------------------------------------------------------------- @@ -206,12 +206,12 @@ The command to create a cluster with CLI must encompass all of the usual paramet This is what one such command could look like: ``` -3Engines coe cluster create mycluster +connectVM coe cluster create mycluster --cluster-template k8s-stable-1.23.5 --keypair sshkey --master-count 1 --node-count 3 ---labels auto_scaling_enabled=true,autoscaler_tag=v1.22.0,calico_ipv4pool_ipip=Always,cinder_csi_plugin_tag=v1.21.0,cloud_provider_enabled=true,cloud_provider_tag=v1.21.0,container_infra_prefix=registry-public.3Engines.com/magnum/,eodata_access_enabled=false,etcd_volume_size=8,etcd_volume_type=ssd,hyperkube_prefix=registry-public.3Engines.com/magnum/,k8s_keystone_auth_tag=v1.21.0,kube_tag=v1.21.5-rancher1,master_lb_floating_ip_enabled=true +--labels auto_scaling_enabled=true,autoscaler_tag=v1.22.0,calico_ipv4pool_ipip=Always,cinder_csi_plugin_tag=v1.21.0,cloud_provider_enabled=true,cloud_provider_tag=v1.21.0,container_infra_prefix=registry-public.connectVM.com/magnum/,eodata_access_enabled=false,etcd_volume_size=8,etcd_volume_type=ssd,hyperkube_prefix=registry-public.connectVM.com/magnum/,k8s_keystone_auth_tag=v1.21.0,kube_tag=v1.21.5-rancher1,master_lb_floating_ip_enabled=true ``` @@ -223,7 +223,7 @@ The line containing labels will be only partially visible on the screen, but onc The command is: -> **3Engines coe cluster create mycluster –cluster-template k8s-stable-1.23.5 –keypair sshkey –master-count 1 –node-count 3 –labels auto\_scaling\_enabled=true,autoscaler\_tag=v1.22.0,calico\_ipv4pool\_ipip=Always,cinder\_csi\_plugin\_tag=v1.21.0/,cloud\_provider\_enabled=true,cloud\_provider\_tag=v1.21.0,container\_infra\_prefix=registry-public.3Engines.com/magnum/,eodata\_access\_enabled=false,etcd\_volume\_size=8,etcd\_volume\_type=ssd,hyperkube\_prefix=registry-public.3Engines.com/magnum/,k8s\_keystone\_auth\_tag=v1.21.0,kube\_tag=v1.21.5-rancher1,master\_lb\_floating\_ip\_enabled=true,min\_node\_count=2,max\_node\_count=4** +> **connectVM coe cluster create mycluster –cluster-template k8s-stable-1.23.5 –keypair sshkey –master-count 1 –node-count 3 –labels auto\_scaling\_enabled=true,autoscaler\_tag=v1.22.0,calico\_ipv4pool\_ipip=Always,cinder\_csi\_plugin\_tag=v1.21.0/,cloud\_provider\_enabled=true,cloud\_provider\_tag=v1.21.0,container\_infra\_prefix=registry-public.connectVM.com/magnum/,eodata\_access\_enabled=false,etcd\_volume\_size=8,etcd\_volume\_type=ssd,hyperkube\_prefix=registry-public.connectVM.com/magnum/,k8s\_keystone\_auth\_tag=v1.21.0,kube\_tag=v1.21.5-rancher1,master\_lb\_floating\_ip\_enabled=true,min\_node\_count=2,max\_node\_count=4** The name will be *mycluster*, one master node and three worker nodes in the beginning. @@ -248,7 +248,7 @@ The “worker” role is assigned by default if not specified. The maximum numbe First see which nodegroups are present for cluster *k8s-cluster*. The command is ``` -3Engines coe nodegroup list k8s-cluster -c name -c node_count -c status -c role +connectVM coe nodegroup list k8s-cluster -c name -c node_count -c status -c role ``` @@ -259,9 +259,9 @@ Switch **-c** denotes which column to show, disregarding all other columns that Now add and print a nodegroup without role: ``` -3Engines coe nodegroup create k8s-cluster nodegroup-without-role --node-count 1 --min-nodes 1 --max-nodes 5 +connectVM coe nodegroup create k8s-cluster nodegroup-without-role --node-count 1 --min-nodes 1 --max-nodes 5 -3Engines coe nodegroup list k8s-cluster -c name -c node_count -c status -c role +connectVM coe nodegroup list k8s-cluster -c name -c node_count -c status -c role ``` @@ -272,9 +272,9 @@ Since the role was not specified, a default value of “worker” was assigned t Now add a node group called *nodegroup-with-role* and the name of the role will be *custom*: ``` -3Engines coe nodegroup create k8s-cluster nodegroup-with-role --node-count 1 --min-nodes 1 --max-nodes 5 --role custom +connectVM coe nodegroup create k8s-cluster nodegroup-with-role --node-count 1 --min-nodes 1 --max-nodes 5 --role custom -3Engines coe nodegroup list k8s-cluster -c name -c node_count -c status -c role +connectVM coe nodegroup list k8s-cluster -c name -c node_count -c status -c role ``` @@ -285,9 +285,9 @@ That will add a nodegroup but will not autoscale it on its own, as there is no * Finally, add a nodegroup called *nodegroup-with-role-2* which will have two roles defined in one statement, that is, both *custom* and *worker*. Since at least one of the roles is *worker*, it will autoscale automatically. ``` -3Engines coe nodegroup create k8s-cluster nodegroup-with-role-2 --node-count 1 --min-nodes 1 --max-nodes 5 --role custom,worker +connectVM coe nodegroup create k8s-cluster nodegroup-with-role-2 --node-count 1 --min-nodes 1 --max-nodes 5 --role custom,worker -3Engines coe nodegroup list k8s-cluster -c name -c node_count -c status -c role +connectVM coe nodegroup list k8s-cluster -c name -c node_count -c status -c role ``` @@ -300,18 +300,18 @@ Cluster **k8s-cluster** now has **8** nodes: You can delete these three clusters with the following set of commands: ``` -3Engines coe nodegroup delete k8s-cluster nodegroup-with-role +connectVM coe nodegroup delete k8s-cluster nodegroup-with-role -3Engines coe nodegroup delete k8s-cluster nodegroup-with-role-2 +connectVM coe nodegroup delete k8s-cluster nodegroup-with-role-2 -3Engines coe nodegroup delete k8s-cluster nodegroup-without-role +connectVM coe nodegroup delete k8s-cluster nodegroup-without-role ``` Once again, see the result: ``` -3Engines coe nodegroup list k8s-cluster -c name -c node_count -c status -c role +connectVM coe nodegroup list k8s-cluster -c name -c node_count -c status -c role ``` @@ -332,7 +332,7 @@ How To Obtain All Labels From the CLI[🔗](#how-to-obtain-all-labels-from-the-c There is a special command which will produce labels from a cluster: ``` -3Engines coe cluster template show k8s-stable-1.23.5 -c labels -f yaml +connectVM coe cluster template show k8s-stable-1.23.5 -c labels -f yaml ``` diff --git a/docs/kubernetes/Backup-of-Kubernetes-Cluster-using-Velero.html.md b/docs/kubernetes/Backup-of-Kubernetes-Cluster-using-Velero.html.md index cd15ed1..c43f0f8 100644 --- a/docs/kubernetes/Backup-of-Kubernetes-Cluster-using-Velero.html.md +++ b/docs/kubernetes/Backup-of-Kubernetes-Cluster-using-Velero.html.md @@ -6,7 +6,7 @@ What is Velero[🔗](#what-is-velero "Permalink to this headline") [Velero](https://velero.io) is the official open source project from VMware. It can back up all Kubernetes API objects and persistent volumes from the cluster on which it is installed. Backed up objects can be restored on the same cluster, or on a new one. Using a package like Velero is essential for any serious development in the Kubernetes cluster. -In essence, you create object store under 3Engines, either using Horizon or Swift module of **3Engines** command and then save cluster state into it. Restoring is the same in reverse – read from that object store and save it to a Kubernetes cluster. +In essence, you create object store under connectVM, either using Horizon or Swift module of **connectVM** command and then save cluster state into it. Restoring is the same in reverse – read from that object store and save it to a Kubernetes cluster. Velero has its own CLI command system so it is possible to automate creation of backups using cron jobs. @@ -26,15 +26,15 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . -The resources that you require and use will reflect on the state of your account wallet. Check your account statistics at . +The resources that you require and use will reflect on the state of your account wallet. Check your account statistics at . No. 2 **How to Access Kubernetes cluster post-deployment** We shall also assume that you have one or more Kubernetes clusters ready and accessible via a **kubectl** command: -[How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md) +[How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md) The result of that article will be setting up of system variable **KUBECONFIG**, which points to the configuration file for access to the Kubernetes cloud. A typical command will be: @@ -54,24 +54,24 @@ No. 3 **Handling Helm** To install Velero, we shall use Helm: -[Deploying Helm Charts on Magnum Kubernetes Clusters on 3Engines Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md). +[Deploying Helm Charts on Magnum Kubernetes Clusters on connectVM Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md). No. 4 **An object storage S3 bucket available** To create one, you can access object storage with Horizon interface or CLI. Horizon commands -: [How to use Object Storage on 3Engines Cloud](../s3/How-to-use-Object-Storage-on-3Engines-Cloud.html.md). +: [How to use Object Storage on connectVM Cloud](../s3/How-to-use-Object-Storage-on-connectVM-Cloud.html.md). CLI : You can also use command such as ``` -3Engines container +connectVM container ``` -to work with object storage. For more information see [How to access object storage using 3Engines CLI on 3Engines Cloud](../3Enginescli/How-to-access-object-storage-using-3Engines-CLI-on-3Engines-Cloud.html.md) +to work with object storage. For more information see [How to access object storage using connectVM CLI on connectVM Cloud](../connectVMcli/How-to-access-object-storage-using-connectVM-CLI-on-connectVM-Cloud.html.md) Either way, we shall assume that there is a container called “bucketnew”: @@ -95,11 +95,11 @@ It will be necessary to have access to a Kubernetes cluster, v1.16 or later, wit ### Installation step 1 Getting EC2 client credentials[🔗](#installation-step-1-getting-ec2-client-credentials "Permalink to this headline") -First fetch EC2 credentials from 3Engines. They are necessary to access private bucket (container). Generate them on your own by executing the following commands: +First fetch EC2 credentials from connectVM. They are necessary to access private bucket (container). Generate them on your own by executing the following commands: ``` -3Engines ec2 credentials create -3Engines ec2 credentials list +connectVM ec2 credentials create +connectVM ec2 credentials list ``` @@ -134,12 +134,12 @@ WAW4-1WAW3-1WAW3-2FRA1-2 > backupStorageLocation: > provider: aws > name: ## enter name of backup storage location (could be anything) -> bucket: ## enter name of bucket created in 3Engines +> bucket: ## enter name of bucket created in connectVM > default: true > config: > region: default > s3ForcePathStyle: true -> s3Url: ## enter URL of object storage (for example "https://s3.waw4-1.3Engines.com") +> s3Url: ## enter URL of object storage (for example "https://s3.waw4-1.connectVM.com") > credentials: > secretContents: ## enter access and secret key to ec2 bucket. This configuration will create kubernetes secret. > cloud: | @@ -176,12 +176,12 @@ configuration: backupStorageLocation: provider: aws name: ## enter name of backup storage location (could be anything) - bucket: ## enter name of bucket created in 3Engines + bucket: ## enter name of bucket created in connectVM default: true config: region: waw3-1 s3ForcePathStyle: true - s3Url: ## enter URL of object storage (for example "https://s3.waw3-1.3Engines.com") + s3Url: ## enter URL of object storage (for example "https://s3.waw3-1.connectVM.com") credentials: secretContents: ## enter access and secret key to ec2 bucket. This configuration will create kubernetes secret. cloud: | @@ -218,12 +218,12 @@ configuration: backupStorageLocation: provider: aws name: ## enter name of backup storage location (could be anything) - bucket: ## enter name of bucket created in 3Engines + bucket: ## enter name of bucket created in connectVM default: true config: region: default s3ForcePathStyle: true - s3Url: ## enter URL of object storage (for example "https://s3.waw3-2.3Engines.com") + s3Url: ## enter URL of object storage (for example "https://s3.waw3-2.connectVM.com") credentials: secretContents: ## enter access and secret key to ec2 bucket. This configuration will create kubernetes secret. cloud: | @@ -260,12 +260,12 @@ configuration: backupStorageLocation: provider: aws name: ## enter name of backup storage location (could be anything) - bucket: ## enter name of bucket created in 3Engines + bucket: ## enter name of bucket created in connectVM default: true config: region: default s3ForcePathStyle: true - s3Url: ## enter URL of object storage (for example "https://s3.fra1-2.3Engines.com") + s3Url: ## enter URL of object storage (for example "https://s3.fra1-2.connectVM.com") credentials: secretContents: ## enter access and secret key to ec2 bucket. This configuration will create kubernetes secret. cloud: | @@ -313,7 +313,7 @@ configuration: config: region: default s3ForcePathStyle: true - s3Url: https://s3.waw4-1.3Engines.com + s3Url: https://s3.waw4-1.connectVM.com credentials: secretContents: ## enter access and secret key to ec2 bucket. This configuration will create kubernetes secret. cloud: | @@ -355,7 +355,7 @@ configuration: config: region: waw3-1 s3ForcePathStyle: true - s3Url: https://s3.waw3-1.3Engines.com + s3Url: https://s3.waw3-1.connectVM.com credentials: secretContents: ## enter access and secret key to ec2 bucket. This configuration will create kubernetes secret. cloud: | @@ -397,7 +397,7 @@ configuration: config: region: default s3ForcePathStyle: true - s3Url: https://s3.waw3-2.3Engines.com + s3Url: https://s3.waw3-2.connectVM.com credentials: secretContents: ## enter access and secret key to ec2 bucket. This configuration will create kubernetes secret. cloud: | @@ -439,7 +439,7 @@ configuration: config: region: default s3ForcePathStyle: true - s3Url: https://s3.fra1-2.3Engines.com + s3Url: https://s3.fra1-2.connectVM.com credentials: secretContents: ## enter access and secret key to ec2 bucket. This configuration will create kubernetes secret. cloud: | diff --git a/docs/kubernetes/CICD-pipelines-with-GitLab-on-3Engines-Cloud-Kubernetes-building-a-Docker-image.html.md b/docs/kubernetes/CICD-pipelines-with-GitLab-on-connectVM-Cloud-Kubernetes-building-a-Docker-image.html.md similarity index 90% rename from docs/kubernetes/CICD-pipelines-with-GitLab-on-3Engines-Cloud-Kubernetes-building-a-Docker-image.html.md rename to docs/kubernetes/CICD-pipelines-with-GitLab-on-connectVM-Cloud-Kubernetes-building-a-Docker-image.html.md index 5bf10b7..0c3ef1b 100644 --- a/docs/kubernetes/CICD-pipelines-with-GitLab-on-3Engines-Cloud-Kubernetes-building-a-Docker-image.html.md +++ b/docs/kubernetes/CICD-pipelines-with-GitLab-on-connectVM-Cloud-Kubernetes-building-a-Docker-image.html.md @@ -1,4 +1,4 @@ -CI/CD pipelines with GitLab on 3Engines Cloud Kubernetes - building a Docker image[🔗](#ci-cd-pipelines-with-gitlab-on-brand-name-kubernetes-building-a-docker-image "Permalink to this headline") +CI/CD pipelines with GitLab on connectVM Cloud Kubernetes - building a Docker image[🔗](#ci-cd-pipelines-with-gitlab-on-brand-name-kubernetes-building-a-docker-image "Permalink to this headline") =================================================================================================================================================================================================== GitLab provides an isolated, private code registry and space for collaboration on code by teams. It also offers a broad range of code deployment automation capabilities. In this article, we will explain how to automate building a Docker image of your app. @@ -17,17 +17,17 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Kubernetes cluster** -[How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md) +[How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md) No. 3 **Local version of GitLab available** Your local instance of GitLab is available and properly accessible by your GitLab user. -In this article we assume the setup according to this article [Install GitLab on 3Engines Cloud Kubernetes](Install-GitLab-on-3Engines-Cloud-Kubernetes.html.md). If you use a different instance of GitLab, there can be some differences e.g. where certain functionalities are located in the GUI. +In this article we assume the setup according to this article [Install GitLab on connectVM Cloud Kubernetes](Install-GitLab-on-connectVM-Cloud-Kubernetes.html.md). If you use a different instance of GitLab, there can be some differences e.g. where certain functionalities are located in the GUI. In this article, we shall be using **gitlab.mysampledomain.info** as the gitlab instance. Be sure to replace it with your own domain. @@ -46,9 +46,9 @@ is a tool to build container images based on a provided Dockerfile. For more ela No. 7 **Private and public keys available** -To connect to our GitLab instance we need a combination of a private and a public key. You can use any key pair, one option is to use 3Engines Horizon to create one. For reference see: +To connect to our GitLab instance we need a combination of a private and a public key. You can use any key pair, one option is to use connectVM Horizon to create one. For reference see: -See [How to create key pair in 3Engines Dashboard on 3Engines Cloud](../cloud/How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md) +See [How to create key pair in connectVM Dashboard on connectVM Cloud](../cloud/How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md) Here, we use the key pair to connect to GitLab instance that we previously installed in Prerequisite No. 3. @@ -81,7 +81,7 @@ You should see an output similar to the following: Step 2 Create project in GitLab and add sample application code[🔗](#step-2-create-project-in-gitlab-and-add-sample-application-code "Permalink to this headline") ----------------------------------------------------------------------------------------------------------------------------------------------------------------- -We will first add a sample application in GitLab. This is a minimal Python-Flask application, its code can be downloaded from this 3Engines Cloud [GitHub repository accompanying this Knowledge Base](https://github.com/3Engines/K8s-samples/tree/main/HelloWorld-Docker-image-Flask). +We will first add a sample application in GitLab. This is a minimal Python-Flask application, its code can be downloaded from this connectVM Cloud [GitHub repository accompanying this Knowledge Base](https://github.com/connectVM/K8s-samples/tree/main/HelloWorld-Docker-image-Flask). As a first step in this section, we will initiate the GitLab remote origin. Login to GitLab GUI and enter the default screen, click on button “New Project”, then “Create blank project”. It will transfer you to the view below. @@ -95,7 +95,7 @@ If there already are some users defined in GitLab, their names will appear in a Enter your preferred project name and slug, in our case “GitLabCI Sample” and “GitLabCI-sample”, respectively. Choose the visibility level to your preference. Uncheck box “Initialize repository with a README”, because we will initiate the repository from the existing code. (We are not initializing the repo, we are only establishing the project in the origin.) -After submitting the “Create project” form, you will receive a list of commands to work with your repo. Review them and switch to the CLI. Clone the entire 3Engines K8s samples repo, then extract the sub-folder called *HelloWorld-Docker-image-Flask*. For clarity, we rename its contents to a new folder, **GitLabCI-sample**. Use +After submitting the “Create project” form, you will receive a list of commands to work with your repo. Review them and switch to the CLI. Clone the entire connectVM K8s samples repo, then extract the sub-folder called *HelloWorld-Docker-image-Flask*. For clarity, we rename its contents to a new folder, **GitLabCI-sample**. Use ``` mkdir ~/GitLabCI-sample @@ -105,7 +105,7 @@ mkdir ~/GitLabCI-sample if this is the first time you are working through this article, so the folder would be ready for the following set of commands: ``` -git clone https://github.com/3Engines/K8s-samples +git clone https://github.com/connectVM/K8s-samples mv ~/K8s-samples/HelloWorld-Docker-image-Flask/* ~/GitLabCI-sample rm K8s-samples/ -rf diff --git a/docs/kubernetes/Configuring-IP-Whitelisting-for-3Engines-Load-Balancer-using-Horizon-and-CLI-on-3Engines-Cloud.html.md b/docs/kubernetes/Configuring-IP-Whitelisting-for-connectVM-Load-Balancer-using-Horizon-and-CLI-on-connectVM-Cloud.html.md similarity index 87% rename from docs/kubernetes/Configuring-IP-Whitelisting-for-3Engines-Load-Balancer-using-Horizon-and-CLI-on-3Engines-Cloud.html.md rename to docs/kubernetes/Configuring-IP-Whitelisting-for-connectVM-Load-Balancer-using-Horizon-and-CLI-on-connectVM-Cloud.html.md index 6909016..b76c221 100644 --- a/docs/kubernetes/Configuring-IP-Whitelisting-for-3Engines-Load-Balancer-using-Horizon-and-CLI-on-3Engines-Cloud.html.md +++ b/docs/kubernetes/Configuring-IP-Whitelisting-for-connectVM-Load-Balancer-using-Horizon-and-CLI-on-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -Configuring IP Whitelisting for 3Engines Load Balancer using Horizon and CLI on 3Engines Cloud[🔗](#configuring-ip-whitelisting-for-3Engines-load-balancer-using-horizon-and-cli-on-brand-name "Permalink to this headline") +Configuring IP Whitelisting for connectVM Load Balancer using Horizon and CLI on connectVM Cloud[🔗](#configuring-ip-whitelisting-for-connectVM-load-balancer-using-horizon-and-cli-on-brand-name "Permalink to this headline") =============================================================================================================================================================================================================================== -This guide explains how to configure IP whitelisting (**allowed\_cidrs**) on an existing 3Engines Load Balancer using Horizon and CLI commands. The configuration will limit access to your cluster through load balancer. +This guide explains how to configure IP whitelisting (**allowed\_cidrs**) on an existing connectVM Load Balancer using Horizon and CLI commands. The configuration will limit access to your cluster through load balancer. What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -14,7 +14,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **List of IP addresses/ranges to whitelist** @@ -27,7 +27,7 @@ In this article, we will use the following two addresses to whitelist: No. 3 **Python Octavia Client** -To operate Load Balancers with CLI, the Python Octavia Client (python-octaviaclient) is required. It is a command-line client for the 3Engines Load Balancing service. Install the load-balancer (Octavia) plugin with the following command from the Terminal window, on Ubuntu 22.04: +To operate Load Balancers with CLI, the Python Octavia Client (python-octaviaclient) is required. It is a command-line client for the connectVM Load Balancing service. Install the load-balancer (Octavia) plugin with the following command from the Terminal window, on Ubuntu 22.04: ``` pip install python-octaviaclient @@ -74,7 +74,7 @@ At the bottom of the window, find the Stack ID: Now execute the commands: ``` -3Engines coe cluster show \ +connectVM coe cluster show \ -f value -c stack_id \ @@ -83,7 +83,7 @@ Now execute the commands: To find **LB\_ID** ``` -3Engines stack resource list \ +connectVM stack resource list \ -n 5 -c resource_name -c physical_resource_id \ | grep loadbalancer_with_flavor \ | loadbalancer_with_flavor \ @@ -94,7 +94,7 @@ To find **LB\_ID** With that information, now we can check our **listener\_id**; it is to this component that we will attach the whitelist: ``` -3Engines loadbalancer \ +connectVM loadbalancer \ show 2d6b335f-fb05-4496-8593-887f7e2c49cf \ -c listeners \ -f value \ @@ -107,7 +107,7 @@ show 2d6b335f-fb05-4496-8593-887f7e2c49cf \ We now have the listener and the IP addresses which will be whitelisted. This is the command that will set up the whitelisting: ``` -3Engines loadbalancer listener set \ +connectVM loadbalancer listener set \ --allowed-cidr 10.0.0.0/8 \ --allowed-cidr 10.95.255.0/24 \ @@ -230,6 +230,6 @@ curl http:// What To Do Next[🔗](#what-to-do-next "Permalink to this headline") ----------------------------------------------------------------- -You can wrap up this procedure with Terraform and apply to a larger number of load balancers. See [Configuring IP Whitelisting for 3Engines Load Balancer using Terraform on 3Engines Cloud](Configuring-IP-Whitelisting-for-3Engines-Load-Balancer-using-Terraform-on-3Engines-Cloud.html.md) +You can wrap up this procedure with Terraform and apply to a larger number of load balancers. See [Configuring IP Whitelisting for connectVM Load Balancer using Terraform on connectVM Cloud](Configuring-IP-Whitelisting-for-connectVM-Load-Balancer-using-Terraform-on-connectVM-Cloud.html.md) -Also, compare with [Implementing IP Whitelisting for Load Balancers with Security Groups on 3Engines Cloud](Implementing-IP-Whitelisting-for-Load-Balancers-with-Security-Groups-on-3Engines-Cloud.html.md) \ No newline at end of file +Also, compare with [Implementing IP Whitelisting for Load Balancers with Security Groups on connectVM Cloud](Implementing-IP-Whitelisting-for-Load-Balancers-with-Security-Groups-on-connectVM-Cloud.html.md) \ No newline at end of file diff --git a/docs/kubernetes/Configuring-IP-Whitelisting-for-3Engines-Load-Balancer-using-Terraform-on-3Engines-Cloud.html.md b/docs/kubernetes/Configuring-IP-Whitelisting-for-connectVM-Load-Balancer-using-Terraform-on-connectVM-Cloud.html.md similarity index 75% rename from docs/kubernetes/Configuring-IP-Whitelisting-for-3Engines-Load-Balancer-using-Terraform-on-3Engines-Cloud.html.md rename to docs/kubernetes/Configuring-IP-Whitelisting-for-connectVM-Load-Balancer-using-Terraform-on-connectVM-Cloud.html.md index 66744b7..86fce00 100644 --- a/docs/kubernetes/Configuring-IP-Whitelisting-for-3Engines-Load-Balancer-using-Terraform-on-3Engines-Cloud.html.md +++ b/docs/kubernetes/Configuring-IP-Whitelisting-for-connectVM-Load-Balancer-using-Terraform-on-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -Configuring IP Whitelisting for 3Engines Load Balancer using Terraform on 3Engines Cloud[🔗](#configuring-ip-whitelisting-for-3Engines-load-balancer-using-terraform-on-brand-name "Permalink to this headline") +Configuring IP Whitelisting for connectVM Load Balancer using Terraform on connectVM Cloud[🔗](#configuring-ip-whitelisting-for-connectVM-load-balancer-using-terraform-on-brand-name "Permalink to this headline") =================================================================================================================================================================================================================== -This guide explains how to configure IP whitelisting (**allowed\_cidrs**) on an existing 3Engines Load Balancer using Terraform. The configuration will limit access to your cluster through load balancer. +This guide explains how to configure IP whitelisting (**allowed\_cidrs**) on an existing connectVM Load Balancer using Terraform. The configuration will limit access to your cluster through load balancer. What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -17,26 +17,26 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Basic parameters already defined for whitelisting** -See article [Configuring IP Whitelisting for 3Engines Load Balancer using Horizon and CLI on 3Engines Cloud](Configuring-IP-Whitelisting-for-3Engines-Load-Balancer-using-Horizon-and-CLI-on-3Engines-Cloud.html.md) for definition of basic notions and parameters. +See article [Configuring IP Whitelisting for connectVM Load Balancer using Horizon and CLI on connectVM Cloud](Configuring-IP-Whitelisting-for-connectVM-Load-Balancer-using-Horizon-and-CLI-on-connectVM-Cloud.html.md) for definition of basic notions and parameters. No. 3 **Terraform installed** You will need version 1.50 or higher to be operational. -For complete introduction and installation of Terrafom on 3Engines see article [Generating and authorizing Terraform using Keycloak user on 3Engines Cloud](../3Enginesdev/Generating-and-authorizing-Terraform-using-Keycloak-user-on-3Engines-Cloud.html.md) +For complete introduction and installation of Terrafom on connectVM see article [Generating and authorizing Terraform using Keycloak user on connectVM Cloud](../connectVMdev/Generating-and-authorizing-Terraform-using-Keycloak-user-on-connectVM-Cloud.html.md) No. 4 **Unrestricted application credentials** -You need to have 3Engines application credentials with unrestricted checkbox. Check article [How to generate or use Application Credentials via CLI on 3Engines Cloud](../cloud/How-to-generate-or-use-Application-Credentials-via-CLI-on-3Engines-Cloud.html.md) +You need to have connectVM application credentials with unrestricted checkbox. Check article [How to generate or use Application Credentials via CLI on connectVM Cloud](../cloud/How-to-generate-or-use-Application-Credentials-via-CLI-on-connectVM-Cloud.html.md) -The first part of that article describes how to have installed 3Engines client and connect it to the cloud. With that provision, the quickest way to create an unrestricted application credential is to apply the command like this: +The first part of that article describes how to have installed connectVM client and connect it to the cloud. With that provision, the quickest way to create an unrestricted application credential is to apply the command like this: ``` -3Engines application credential create cred_unrestricted --unrestricted +connectVM application credential create cred_unrestricted --unrestricted ``` @@ -60,10 +60,10 @@ Configure Terraform for whitelisting[🔗](#configure-terraform-for-whitelisting Instead of performing the whitelisting procedure manually, we can use Terraform and store the procedure in the remote repo. -Create file **3Engines\_auth.sh** +Create file **connectVM\_auth.sh** ``` -export OS_AUTH_URL="https://your-3Engines-url:5000/v3" +export OS_AUTH_URL="https://your-connectVM-url:5000/v3" export OS_PROJECT_NAME="your-project" export OS_USERNAME="your-username" export OS_PASSWORD="your-password" @@ -84,14 +84,14 @@ Create Terraform file: ``` terraform { required_providers { - 3Engines = { - source = "terraform-provider-3Engines/3Engines" + connectVM = { + source = "terraform-provider-connectVM/connectVM" version = "1.47.0" } } } -provider "3Engines" { +provider "connectVM" { use_octavia = true # Required for Load Balancer v2 API } @@ -102,7 +102,7 @@ provider "3Engines" { ``` variable "ID_OF_LOADBALANCER" { type = string - description = "ID of the existing 3Engines Load Balancer" + description = "ID of the existing connectVM Load Balancer" } variable "allowed_cidrs" { @@ -127,7 +127,7 @@ allowed_cidrs = [ **lb.tf** ``` -resource "3Engines_lb_listener_v2" "k8s_api_listener" { +resource "connectVM_lb_listener_v2" "k8s_api_listener" { loadbalancer_id = var.ID_OF_LOADBALANCER allowed_cidrs = var.allowed_cidrs protocol_port = "6443" @@ -145,7 +145,7 @@ Since Terraform 1.5 can import your resource in declarative way. ``` import { - to = 3Engines_lb_listener_v2.k8s_api_listener + to = connectVM_lb_listener_v2.k8s_api_listener id = "your-listener-id" } @@ -154,7 +154,7 @@ import { Or you can do it in an imperative way: ``` -terraform import 3Engines_lb_listener_v2.k8s_api_listener "" +terraform import connectVM_lb_listener_v2.k8s_api_listener "" ``` @@ -176,8 +176,8 @@ terraform apply generated_listener.tf ``` Terraform apply generated_listener.tf -3Engines_lb_listener_v2.k8s_api_listener: Preparing import... [id=bbf39f1c-6936-4344-9957-7517d4a979b6] -3Engines_lb_listener_v2.k8s_api_listener: Refreshing state... [id=bbf39f1c-6936-4344-9957-7517d4a979b6] +connectVM_lb_listener_v2.k8s_api_listener: Preparing import... [id=bbf39f1c-6936-4344-9957-7517d4a979b6] +connectVM_lb_listener_v2.k8s_api_listener: Refreshing state... [id=bbf39f1c-6936-4344-9957-7517d4a979b6] Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: @@ -185,9 +185,9 @@ plan. Resource actions are indicated with the following symbols: Terraform will perform the following actions: - # 3Engines_lb_listener_v2.k8s_api_listener will be updated in-place + # connectVM_lb_listener_v2.k8s_api_listener will be updated in-place # (imported from "bbf39f1c-6936-4344-9957-7517d4a979b6") - ~ resource "3Engines_lb_listener_v2" "k8s_api_listener" { + ~ resource "connectVM_lb_listener_v2" "k8s_api_listener" { admin_state_up = true ~ allowed_cidrs = [ + "10.0.0.1/32", @@ -271,4 +271,4 @@ curl: (28) Connection timed out after 5000 milliseconds What To Do Next[🔗](#what-to-do-next "Permalink to this headline") ----------------------------------------------------------------- -Compare with [Implementing IP Whitelisting for Load Balancers with Security Groups on 3Engines Cloud](Implementing-IP-Whitelisting-for-Load-Balancers-with-Security-Groups-on-3Engines-Cloud.html.md) \ No newline at end of file +Compare with [Implementing IP Whitelisting for Load Balancers with Security Groups on connectVM Cloud](Implementing-IP-Whitelisting-for-Load-Balancers-with-Security-Groups-on-connectVM-Cloud.html.md) \ No newline at end of file diff --git a/docs/kubernetes/Create-and-access-NFS-server-from-Kubernetes-on-3Engines-Cloud.html.md b/docs/kubernetes/Create-and-access-NFS-server-from-Kubernetes-on-connectVM-Cloud.html.md similarity index 83% rename from docs/kubernetes/Create-and-access-NFS-server-from-Kubernetes-on-3Engines-Cloud.html.md rename to docs/kubernetes/Create-and-access-NFS-server-from-Kubernetes-on-connectVM-Cloud.html.md index 20006ef..3293640 100644 --- a/docs/kubernetes/Create-and-access-NFS-server-from-Kubernetes-on-3Engines-Cloud.html.md +++ b/docs/kubernetes/Create-and-access-NFS-server-from-Kubernetes-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -Create and access NFS server from Kubernetes on 3Engines Cloud[🔗](#create-and-access-nfs-server-from-kubernetes-on-brand-name "Permalink to this headline") +Create and access NFS server from Kubernetes on connectVM Cloud[🔗](#create-and-access-nfs-server-from-kubernetes-on-brand-name "Permalink to this headline") ============================================================================================================================================================= In order to enable simultaneous read-write storage to multiple pods running on a Kubernetes cluster, we can use an NFS server. @@ -18,28 +18,28 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . -The resources that you require and use will reflect on the state of your account wallet. Check your account statistics at . +The resources that you require and use will reflect on the state of your account wallet. Check your account statistics at . No. 2 **Familiarity with Linux and cloud management** -We assume you know the basics of Linux and 3Engines Cloud cloud management: +We assume you know the basics of Linux and connectVM Cloud cloud management: * Creating, accessing and using virtual machines - [How to create new Linux VM in 3Engines Dashboard Horizon on 3Engines Cloud](../cloud/How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md) + [How to create new Linux VM in connectVM Dashboard Horizon on connectVM Cloud](../cloud/How-to-create-new-Linux-VM-in-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md) -* Creating security groups [How to use Security Groups in Horizon on 3Engines Cloud](../cloud/How-to-use-Security-Groups-in-Horizon-on-3Engines-Cloud.html.md) +* Creating security groups [How to use Security Groups in Horizon on connectVM Cloud](../cloud/How-to-use-Security-Groups-in-Horizon-on-connectVM-Cloud.html.md) -* Attaching floating IPs [How to Add or Remove Floating IP’s to your VM on 3Engines Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md) +* Attaching floating IPs [How to Add or Remove Floating IP’s to your VM on connectVM Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md) No. 3 **A running Kubernetes cluster** -You will also need a Kubernetes cluster to try out the commands. To create one from scratch, see [How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md) +You will also need a Kubernetes cluster to try out the commands. To create one from scratch, see [How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md) No. 4 **kubectl access to the Kubernetes cloud** -As usual when working with Kubernetes clusters, you will need to use the **kubectl** command: [How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md) +As usual when working with Kubernetes clusters, you will need to use the **kubectl** command: [How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md) 1. Set up NFS server on a VM[🔗](#set-up-nfs-server-on-a-vm "Permalink to this headline") ---------------------------------------------------------------------------------------- diff --git a/docs/kubernetes/Creating-Additional-Nodegroups-in-Kubernetes-Cluster-on-3Engines-Cloud-3Engines-Magnum.html.md b/docs/kubernetes/Creating-Additional-Nodegroups-in-Kubernetes-Cluster-on-connectVM-Cloud-connectVM-Magnum.html.md similarity index 80% rename from docs/kubernetes/Creating-Additional-Nodegroups-in-Kubernetes-Cluster-on-3Engines-Cloud-3Engines-Magnum.html.md rename to docs/kubernetes/Creating-Additional-Nodegroups-in-Kubernetes-Cluster-on-connectVM-Cloud-connectVM-Magnum.html.md index afd86fc..c8b2640 100644 --- a/docs/kubernetes/Creating-Additional-Nodegroups-in-Kubernetes-Cluster-on-3Engines-Cloud-3Engines-Magnum.html.md +++ b/docs/kubernetes/Creating-Additional-Nodegroups-in-Kubernetes-Cluster-on-connectVM-Cloud-connectVM-Magnum.html.md @@ -1,4 +1,4 @@ -Creating Additional Nodegroups in Kubernetes Cluster on 3Engines Cloud 3Engines Magnum[🔗](#creating-additional-nodegroups-in-kubernetes-cluster-on-brand-name-3Engines-magnum "Permalink to this headline") +Creating Additional Nodegroups in Kubernetes Cluster on connectVM Cloud connectVM Magnum[🔗](#creating-additional-nodegroups-in-kubernetes-cluster-on-brand-name-connectVM-magnum "Permalink to this headline") =============================================================================================================================================================================================================== The Benefits of Using Nodegroups[🔗](#the-benefits-of-using-nodegroups "Permalink to this headline") @@ -21,7 +21,7 @@ Other uses of nodegroup roles also include: What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- -> * The structure of command **3Engines coe nodelist** +> * The structure of command **connectVM coe nodelist** > * How to produce manageable output from **nodelist** set of commands > * How to **list** what nodegroups are available in a cluster > * How to **show** the contents of one particular *nodegroup* in a cluster @@ -36,35 +36,35 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . No. 2 **Creating clusters with CLI** -The article [How To Use Command Line Interface for Kubernetes Clusters On 3Engines Cloud 3Engines Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-3Engines-Cloud-3Engines-Magnum.html.md) will introduce you to creation of clusters using a command line interface. +The article [How To Use Command Line Interface for Kubernetes Clusters On connectVM Cloud connectVM Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-connectVM-Cloud-connectVM-Magnum.html.md) will introduce you to creation of clusters using a command line interface. -No. 3 **Connect 3Engines client to the cloud** +No. 3 **Connect connectVM client to the cloud** -Prepare **3Engines** and **magnum** clients by executing *Step 2 Connect 3Engines and Magnum Clients to Horizon Cloud* from article [How To Install 3Engines and Magnum Clients for Command Line Interface to 3Engines Cloud Horizon](How-To-Install-3Engines-and-Magnum-Clients-for-Command-Line-Interface-to-3Engines-Cloud-Horizon.html.md) +Prepare **connectVM** and **magnum** clients by executing *Step 2 Connect connectVM and Magnum Clients to Horizon Cloud* from article [How To Install connectVM and Magnum Clients for Command Line Interface to connectVM Cloud Horizon](How-To-Install-connectVM-and-Magnum-Clients-for-Command-Line-Interface-to-connectVM-Cloud-Horizon.html.md) No. 4 **Check available quotas** -Before creating additional node groups check the state of the resources with Horizon commands **Computer** => **Overview**. See [Dashboard Overview – Project Quotas And Flavors Limits on 3Engines Cloud](../cloud/Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-3Engines-Cloud.html.md). +Before creating additional node groups check the state of the resources with Horizon commands **Computer** => **Overview**. See [Dashboard Overview – Project Quotas And Flavors Limits on connectVM Cloud](../cloud/Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-connectVM-Cloud.html.md). Nodegroup Subcommands[🔗](#nodegroup-subcommands "Permalink to this headline") ----------------------------------------------------------------------------- -Once you create a Kubernetes cluster on 3Engines Magnum, there are five *nodegroup* commands at your disposal: +Once you create a Kubernetes cluster on connectVM Magnum, there are five *nodegroup* commands at your disposal: ``` -3Engines coe nodegroup create +connectVM coe nodegroup create -3Engines coe nodegroup delete +connectVM coe nodegroup delete -3Engines coe nodegroup list +connectVM coe nodegroup list -3Engines coe nodegroup show +connectVM coe nodegroup show -3Engines coe nodegroup update +connectVM coe nodegroup update ``` @@ -76,18 +76,18 @@ Step 1 Access the Current State of Clusters and Their Nodegroups[🔗](#step-1-a Here is which clusters are available in the system: ``` -3Engines coe cluster list --max-width 120 +connectVM coe cluster list --max-width 120 ``` ![present_clusters.png](../_images/present_clusters.png) -The default process of creating Kubernetes clusters on 3Engines Magnum produces two nodegroups, **default-master** and **default-worker**. Use commands +The default process of creating Kubernetes clusters on connectVM Magnum produces two nodegroups, **default-master** and **default-worker**. Use commands ``` -3Engines coe nodegroup list kubelbtrue +connectVM coe nodegroup list kubelbtrue -3Engines coe nodegroup list k8s-cluster +connectVM coe nodegroup list k8s-cluster ``` @@ -103,7 +103,7 @@ Step 2 How to Create a New Nodegroup[🔗](#step-2-how-to-create-a-new-nodegroup In this step you learn about the parameters available for the **nodegroup create** command. This is the general structure: ``` -3Engines coe nodegroup create [-h] +connectVM coe nodegroup create [-h] [--docker-volume-size ] [--labels ] [--node-count ] @@ -120,7 +120,7 @@ In this step you learn about the parameters available for the **nodegroup create You will now create a nodegroup of two members, it will be called *testing*, the role will be called *test*, and add it to the cluster *k8s-cluster*: ``` -3Engines coe nodegroup create \ +connectVM coe nodegroup create \ --node-count 2 \ --role test \ k8s-cluster testing @@ -130,7 +130,7 @@ k8s-cluster testing Then use the command ``` -3Engines coe nodegroup list k8s-cluster +connectVM coe nodegroup list k8s-cluster ``` @@ -152,7 +152,7 @@ Step 3 Using **role** to Filter Nodegroups in the Cluster[🔗](#step-3-using-ro It is possible to filter node groups according to the role. Here is the command to show only the *test* nodegroup: ``` -3Engines coe nodegroup list k8s-cluster --role test +connectVM coe nodegroup list k8s-cluster --role test ``` @@ -168,7 +168,7 @@ Step 4 Show Details of the Nodegroup Created[🔗](#step-4-show-details-of-the-n Command **show** presents the details of a nodegroup in various formats – *json*, *table*, *shell*, *value* or *yaml*. The default is *table* but use parameter **–max-width** to limit the number of columns in it: ``` -3Engines coe nodegroup show --max-width 80 k8s-cluster testing +connectVM coe nodegroup show --max-width 80 k8s-cluster testing ``` @@ -180,7 +180,7 @@ Step 5 Delete the Existing Nodegroup[🔗](#step-5-delete-the-existing-nodegroup In this step you shall try to create a nodegroup with small footprint: ``` -3Engines coe nodegroup create \ +connectVM coe nodegroup create \ --node-count 2 \ --role test \ --image cirros-0.4.0-x86_64-2 \ @@ -194,7 +194,7 @@ After one hour, the command was cancelled and the creation has failed. The resou One way is to use the CLI **delete** subcommand, like this: ``` -3Engines coe nodegroup delete k8s-cluster cirros +connectVM coe nodegroup delete k8s-cluster cirros ``` @@ -218,7 +218,7 @@ Step 6 Update the Existing Nodegroup[🔗](#step-6-update-the-existing-nodegroup In this step you will directly update the existing nodegroup, rather than adding and deleting them in a row. The example command is: ``` -3Engines coe nodegroup update k8s-cluster testing replace min_node_count=1 +connectVM coe nodegroup update k8s-cluster testing replace min_node_count=1 ``` @@ -232,14 +232,14 @@ Step 7 Resize the Nodegroup[🔗](#step-7-resize-the-nodegroup "Permalink to thi Resizing the *nodegroup* is similar to resizing the cluster, with the addition of parameter **–nodegroup**. Currently, the number of nodes in group *testing* is 2. Make it **1**: ``` -3Engines coe cluster resize k8s-cluster --nodegroup testing 1 +connectVM coe cluster resize k8s-cluster --nodegroup testing 1 ``` To see the result, apply the command ``` -3Engines coe nodegroup list --max-width 120 k8s-cluster +connectVM coe nodegroup list --max-width 120 k8s-cluster ``` diff --git a/docs/kubernetes/Default-Kubernetes-cluster-templates-in-3Engines-Cloud-Cloud.html.md b/docs/kubernetes/Default-Kubernetes-cluster-templates-in-connectVM-Cloud-Cloud.html.md similarity index 85% rename from docs/kubernetes/Default-Kubernetes-cluster-templates-in-3Engines-Cloud-Cloud.html.md rename to docs/kubernetes/Default-Kubernetes-cluster-templates-in-connectVM-Cloud-Cloud.html.md index bf5f644..ebf7923 100644 --- a/docs/kubernetes/Default-Kubernetes-cluster-templates-in-3Engines-Cloud-Cloud.html.md +++ b/docs/kubernetes/Default-Kubernetes-cluster-templates-in-connectVM-Cloud-Cloud.html.md @@ -1,7 +1,7 @@ -Default Kubernetes cluster templates in 3Engines Cloud Cloud[🔗](#default-kubernetes-cluster-templates-in-brand-name-cloud "Permalink to this headline") +Default Kubernetes cluster templates in connectVM Cloud Cloud[🔗](#default-kubernetes-cluster-templates-in-brand-name-cloud "Permalink to this headline") ========================================================================================================================================================= -In this article we shall list Kubernetes cluster templates available on 3Engines Cloud and explain the differences among them. +In this article we shall list Kubernetes cluster templates available on connectVM Cloud and explain the differences among them. What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -17,11 +17,11 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Private and public keys** -To create a cluster, you will need an available SSH key pair. If you do not have one already, follow this article to create it in the 3Engines dashboard: [How to create key pair in 3Engines Dashboard on 3Engines Cloud](../cloud/How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md). +To create a cluster, you will need an available SSH key pair. If you do not have one already, follow this article to create it in the connectVM dashboard: [How to create key pair in connectVM Dashboard on connectVM Cloud](../cloud/How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md). No. 3 **Documentation for standard templates** @@ -37,13 +37,13 @@ Documentation for *localstorage* templates: No. 4 **How to create Kubernetes clusters** -The general procedure is explained in [How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md). +The general procedure is explained in [How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md). No. 5 **Using vGPU in Kubernetes clusters** If template name contains “vgpu”, this template can be used to create so-called “vGPU-first” clusters. -To learn how to set up vGPU in Kubernetes clusters on 3Engines Cloud cloud, see [Deploying vGPU workloads on 3Engines Cloud Kubernetes](Deploying-vGPU-workloads-on-3Engines-Cloud-Kubernetes.html.md). +To learn how to set up vGPU in Kubernetes clusters on connectVM Cloud cloud, see [Deploying vGPU workloads on connectVM Cloud Kubernetes](Deploying-vGPU-workloads-on-connectVM-Cloud-Kubernetes.html.md). Templates available on your cloud[🔗](#templates-available-on-your-cloud "Permalink to this headline") ----------------------------------------------------------------------------------------------------- @@ -77,7 +77,7 @@ How to choose a proper template[🔗](#how-to-choose-a-proper-template "Permalin **Standard templates** -Standard templates are general in nature and you can use them for any type of Kubernetes cluster. Each will produce a working Kubernetes cluster on 3Engines Cloud 3Engines Magnum hosting. The default network driver is *calico*. Template that does not specify calico, k8s-1.23.16-v1.0.3, and is identical to the template that does specify *calico* in its name. Both are placed in the left column in the following table: +Standard templates are general in nature and you can use them for any type of Kubernetes cluster. Each will produce a working Kubernetes cluster on connectVM Cloud connectVM Magnum hosting. The default network driver is *calico*. Template that does not specify calico, k8s-1.23.16-v1.0.3, and is identical to the template that does specify *calico* in its name. Both are placed in the left column in the following table: | calico | cilium | | --- | --- | @@ -105,7 +105,7 @@ You can also dig deeper and choose the template according to the the network plu ### Network plugins for Kubernetes clusters[🔗](#network-plugins-for-kubernetes-clusters "Permalink to this headline") -Kubernetes cluster templates at 3Engines Cloud cloud use *calico* or *cilium* plugins for controlling network traffic. Both are [CNI](https://www.cncf.io/projects/kubernetes/) compliant. *Calico* is the default plugin, meaning that if the template name does not specify the plugin, the *calico* driver is used. If the template name specifies *cilium* then, of course, the *cilium* driver is used. +Kubernetes cluster templates at connectVM Cloud cloud use *calico* or *cilium* plugins for controlling network traffic. Both are [CNI](https://www.cncf.io/projects/kubernetes/) compliant. *Calico* is the default plugin, meaning that if the template name does not specify the plugin, the *calico* driver is used. If the template name specifies *cilium* then, of course, the *cilium* driver is used. ### Calico (the default)[🔗](#calico-the-default "Permalink to this headline") @@ -139,7 +139,7 @@ Applications such as day trading, personal finances, AI and the similar, may hav In WAW3-1 cloud, virtual machine flavors with NVMe have the prefix of HMD and they are resource-intensive: ``` -3Engines flavor list +connectVM flavor list +--------------+--------+------+-----------+-------+ | Name | RAM | Disk | Ephemeral | VCPUs | +--------------+--------+------+-----------+-------+ diff --git a/docs/kubernetes/Deploy-Keycloak-on-Kubernetes-with-a-sample-app-on-3Engines-Cloud.html.md b/docs/kubernetes/Deploy-Keycloak-on-Kubernetes-with-a-sample-app-on-connectVM-Cloud.html.md similarity index 95% rename from docs/kubernetes/Deploy-Keycloak-on-Kubernetes-with-a-sample-app-on-3Engines-Cloud.html.md rename to docs/kubernetes/Deploy-Keycloak-on-Kubernetes-with-a-sample-app-on-connectVM-Cloud.html.md index d3d65b1..2de0889 100644 --- a/docs/kubernetes/Deploy-Keycloak-on-Kubernetes-with-a-sample-app-on-3Engines-Cloud.html.md +++ b/docs/kubernetes/Deploy-Keycloak-on-Kubernetes-with-a-sample-app-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -Deploy Keycloak on Kubernetes with a sample app on 3Engines Cloud[🔗](#deploy-keycloak-on-kubernetes-with-a-sample-app-on-brand-name "Permalink to this headline") +Deploy Keycloak on Kubernetes with a sample app on connectVM Cloud[🔗](#deploy-keycloak-on-kubernetes-with-a-sample-app-on-brand-name "Permalink to this headline") =================================================================================================================================================================== [Keycloak](https://www.keycloak.org/) is a large Open-Source Identity Management suite capable of handling a wide range of identity-related use cases. @@ -17,11 +17,11 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . No. 2 **A running Kubernetes cluster and kubectl activated** -A Kubernetes cluster, to create one refer to: [How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md). To activate **kubectl**, see [How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md). +A Kubernetes cluster, to create one refer to: [How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md). To activate **kubectl**, see [How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md). No. 3 **Basic knowledge of Python and pip package management** diff --git a/docs/kubernetes/Deploying-HTTPS-Services-on-Magnum-Kubernetes-in-3Engines-Cloud-Cloud.html.md b/docs/kubernetes/Deploying-HTTPS-Services-on-Magnum-Kubernetes-in-connectVM-Cloud-Cloud.html.md similarity index 88% rename from docs/kubernetes/Deploying-HTTPS-Services-on-Magnum-Kubernetes-in-3Engines-Cloud-Cloud.html.md rename to docs/kubernetes/Deploying-HTTPS-Services-on-Magnum-Kubernetes-in-connectVM-Cloud-Cloud.html.md index 5a2a6b8..66f4114 100644 --- a/docs/kubernetes/Deploying-HTTPS-Services-on-Magnum-Kubernetes-in-3Engines-Cloud-Cloud.html.md +++ b/docs/kubernetes/Deploying-HTTPS-Services-on-Magnum-Kubernetes-in-connectVM-Cloud-Cloud.html.md @@ -1,9 +1,9 @@ -Deploying HTTPS Services on Magnum Kubernetes in 3Engines Cloud Cloud[🔗](#deploying-https-services-on-magnum-kubernetes-in-brand-name-cloud-name-cloud "Permalink to this headline") +Deploying HTTPS Services on Magnum Kubernetes in connectVM Cloud Cloud[🔗](#deploying-https-services-on-magnum-kubernetes-in-brand-name-cloud-name-cloud "Permalink to this headline") ====================================================================================================================================================================================== Kubernetes makes it very quick to deploy and publicly expose an application, for example using the LoadBalancer service type. Sample deployments, which demonstrate such capability, are usually served with HTTP. Deploying a production-ready service, secured with HTTPS, can also be done smoothly, by using additional tools. -In this article, we show how to deploy a sample HTTPS-protected service on 3Engines Cloud cloud. +In this article, we show how to deploy a sample HTTPS-protected service on connectVM Cloud cloud. What We are Going to Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -20,25 +20,25 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Kubernetes cluster deployed on** **cloud, with NGINX Ingress enabled** -See this article [How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md) +See this article [How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md) No. 3 **Familiarity with kubectl** -For further instructions refer to [How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md) +For further instructions refer to [How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md) No. 4 **Familiarity with Kubernetes Ingress feature** -It is explained in article [Using Kubernetes Ingress on 3Engines Cloud 3Engines Magnum](Using-Kubernetes-Ingress-on-3Engines-Cloud-3Engines-Magnum.html.md) +It is explained in article [Using Kubernetes Ingress on connectVM Cloud connectVM Magnum](Using-Kubernetes-Ingress-on-connectVM-Cloud-connectVM-Magnum.html.md) No. 5 **Familiarity with deploying Helm charts** See this article: -[Deploying Helm Charts on Magnum Kubernetes Clusters on 3Engines Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md) +[Deploying Helm Charts on Magnum Kubernetes Clusters on connectVM Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md) No. 6 **Must have domain purchased from a registrar** @@ -48,7 +48,7 @@ No. 7 **Use DNS command Horizon to connect to the domain name** This is optional. Here is the article with detailed information: -[DNS as a Service on 3Engines Cloud Hosting](../cloud/DNS-as-a-Service-on-3Engines-Cloud-Hosting.html.md) +[DNS as a Service on connectVM Cloud Hosting](../cloud/DNS-as-a-Service-on-connectVM-Cloud-Hosting.html.md) Step 1 Install Cert Manager’s Custom Resource Definitions (CRDs)[🔗](#step-1-install-cert-manager-s-custom-resource-definitions-crds "Permalink to this headline") ----------------------------------------------------------------------------------------------------------------------------------------------------------------- @@ -90,7 +90,7 @@ orders.acme.cert-manager.io 2022-12-18T11:15:08Z Warning -Magnum introduces a few pod security policies (PSP) which provide some extra safety precautions for the cluster, but will cause conflict with the CertManager Helm chart. PodSecurityPolicy is deprecated until Kubernetes v. 1.25, but still supported in version of Kubernetes 1.21 to 1.23 available on 3Engines Cloud cloud. The commands below may produce warnings about deprecation but the installation should continue nevertheless. +Magnum introduces a few pod security policies (PSP) which provide some extra safety precautions for the cluster, but will cause conflict with the CertManager Helm chart. PodSecurityPolicy is deprecated until Kubernetes v. 1.25, but still supported in version of Kubernetes 1.21 to 1.23 available on connectVM Cloud cloud. The commands below may produce warnings about deprecation but the installation should continue nevertheless. Step 2 Install CertManager Helm chart[🔗](#step-2-install-certmanager-helm-chart "Permalink to this headline") ------------------------------------------------------------------------------------------------------------- @@ -299,6 +299,6 @@ If all works well, the effort is complete and after a couple of minutes we shoul What To Do Next[🔗](#what-to-do-next "Permalink to this headline") ----------------------------------------------------------------- -The article [Using Kubernetes Ingress on 3Engines Cloud 3Engines Magnum](Using-Kubernetes-Ingress-on-3Engines-Cloud-3Engines-Magnum.html.md) shows how to create an HTTP based service or a site. +The article [Using Kubernetes Ingress on connectVM Cloud connectVM Magnum](Using-Kubernetes-Ingress-on-connectVM-Cloud-connectVM-Magnum.html.md) shows how to create an HTTP based service or a site. -If you need additional information on Helm charts: [Deploying Helm Charts on Magnum Kubernetes Clusters on 3Engines Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md). \ No newline at end of file +If you need additional information on Helm charts: [Deploying Helm Charts on Magnum Kubernetes Clusters on connectVM Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md). \ No newline at end of file diff --git a/docs/kubernetes/Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md b/docs/kubernetes/Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md similarity index 90% rename from docs/kubernetes/Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md rename to docs/kubernetes/Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md index 3b0e0c7..66e069f 100644 --- a/docs/kubernetes/Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md +++ b/docs/kubernetes/Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md @@ -1,4 +1,4 @@ -Deploying Helm Charts on Magnum Kubernetes Clusters on 3Engines Cloud Cloud[🔗](#deploying-helm-charts-on-magnum-kubernetes-clusters-on-brand-name-cloud-name-cloud "Permalink to this headline") +Deploying Helm Charts on Magnum Kubernetes Clusters on connectVM Cloud Cloud[🔗](#deploying-helm-charts-on-magnum-kubernetes-clusters-on-brand-name-cloud-name-cloud "Permalink to this headline") ================================================================================================================================================================================================== Kubernetes is a robust and battle-tested environment for running apps and services, yet it could be time consuming to manually provision all resources required to run a production-ready deployment. This article introduces [Helm](https://helm.sh/) as a package manager for Kubernetes. With it, you will be able to quickly deploy complex Kubernetes applications, consisting of code, databases, user interfaces and more. @@ -18,7 +18,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Basic understanding of Kubernetes** @@ -26,11 +26,11 @@ We assume you have basic understanding of Kubernetes, its notions and ways of wo No. 3 **A cluster created on** **cloud** -For trying out Helm installation and deployment in an actual environment, create a cluster on cloud using 3Engines Magnum [How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md). +For trying out Helm installation and deployment in an actual environment, create a cluster on cloud using connectVM Magnum [How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md). No. 4 **Active connection to the cloud** -For Kubernetes, that means a **kubectl** command line tool installed and **kubeconfig** pointing to a cluster. Instructions are provided in this article [How To Use Command Line Interface for Kubernetes Clusters On 3Engines Cloud 3Engines Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-3Engines-Cloud-3Engines-Magnum.html.md). +For Kubernetes, that means a **kubectl** command line tool installed and **kubeconfig** pointing to a cluster. Instructions are provided in this article [How To Use Command Line Interface for Kubernetes Clusters On connectVM Cloud connectVM Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-connectVM-Cloud-connectVM-Magnum.html.md). No. 5 **Access to Ubuntu to run code on** @@ -38,11 +38,11 @@ Code samples in this article assume you are running Ubuntu 20.04 LTS or similar > * Windows with Linux subsystem, > * genuine desktop Ubuntu operating system or you can also -> * create a virtual machine in the 3Engines Cloud cloud and run the examples from there. These articles will provide technical know-how if you need it: +> * create a virtual machine in the connectVM Cloud cloud and run the examples from there. These articles will provide technical know-how if you need it: -[How to create a Linux VM and access it from Windows desktop on 3Engines Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md) +[How to create a Linux VM and access it from Windows desktop on connectVM Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-connectVM-Cloud.html.md) -[How to create a Linux VM and access it from Linux command line on 3Engines Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md) +[How to create a Linux VM and access it from Linux command line on connectVM Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md) Background - How Helm works[🔗](#background-how-helm-works "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -238,4 +238,4 @@ Remember that a chart deployed with Helm is, in the end, just a set of Kubernete The following article will show how to use JetStack repo to install CertManager, with which you can deploy HTTPS services on Kubernetes cloud: -[Deploying HTTPS Services on Magnum Kubernetes in 3Engines Cloud Cloud](Deploying-HTTPS-Services-on-Magnum-Kubernetes-in-3Engines-Cloud-Cloud.html.md) \ No newline at end of file +[Deploying HTTPS Services on Magnum Kubernetes in connectVM Cloud Cloud](Deploying-HTTPS-Services-on-Magnum-Kubernetes-in-connectVM-Cloud-Cloud.html.md) \ No newline at end of file diff --git a/docs/kubernetes/Deploying-vGPU-workloads-on-3Engines-Cloud-Kubernetes.html.md b/docs/kubernetes/Deploying-vGPU-workloads-on-connectVM-Cloud-Kubernetes.html.md similarity index 89% rename from docs/kubernetes/Deploying-vGPU-workloads-on-3Engines-Cloud-Kubernetes.html.md rename to docs/kubernetes/Deploying-vGPU-workloads-on-connectVM-Cloud-Kubernetes.html.md index 750ef2e..3b5587c 100644 --- a/docs/kubernetes/Deploying-vGPU-workloads-on-3Engines-Cloud-Kubernetes.html.md +++ b/docs/kubernetes/Deploying-vGPU-workloads-on-connectVM-Cloud-Kubernetes.html.md @@ -1,4 +1,4 @@ -Deploying vGPU workloads on 3Engines Cloud Kubernetes[🔗](#deploying-vgpu-workloads-on-brand-name-kubernetes "Permalink to this headline") +Deploying vGPU workloads on connectVM Cloud Kubernetes[🔗](#deploying-vgpu-workloads-on-brand-name-kubernetes "Permalink to this headline") =========================================================================================================================================== Utilizing GPU (Graphical Processing Units) presents a highly efficient alternative for fast, highly parallel processing of demanding computational tasks such as image processing, machine learning and many others. @@ -22,13 +22,13 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . No. 2 **Knowledge of RC files and CLI commands for Magnum** -You should be familiar with utilizing 3Engines CLI and Magnum CLI. Your RC file should be sourced and pointing to your project in 3Engines. See article +You should be familiar with utilizing connectVM CLI and Magnum CLI. Your RC file should be sourced and pointing to your project in connectVM. See article -[How To Install 3Engines and Magnum Clients for Command Line Interface to 3Engines Cloud Horizon](How-To-Install-3Engines-and-Magnum-Clients-for-Command-Line-Interface-to-3Engines-Cloud-Horizon.html.md). +[How To Install connectVM and Magnum Clients for Command Line Interface to connectVM Cloud Horizon](How-To-Install-connectVM-and-Magnum-Clients-for-Command-Line-Interface-to-connectVM-Cloud-Horizon.html.md). Note @@ -38,11 +38,11 @@ If you are using CLI when creating vGPU nodegroups and are being authenticated w No. 3 **Cluster and kubectl should be operational** -To connect to the cluster via **kubectl** tool, see this article [How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md). +To connect to the cluster via **kubectl** tool, see this article [How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md). No. 4 **Familiarity with the notion of nodegroups** -[Creating Additional Nodegroups in Kubernetes Cluster on 3Engines Cloud 3Engines Magnum](Creating-Additional-Nodegroups-in-Kubernetes-Cluster-on-3Engines-Cloud-3Engines-Magnum.html.md). +[Creating Additional Nodegroups in Kubernetes Cluster on connectVM Cloud connectVM Magnum](Creating-Additional-Nodegroups-in-Kubernetes-Cluster-on-connectVM-Cloud-connectVM-Magnum.html.md). vGPU flavors per cloud[🔗](#vgpu-flavors-per-cloud "Permalink to this headline") ------------------------------------------------------------------------------- @@ -50,7 +50,7 @@ vGPU flavors per cloud[🔗](#vgpu-flavors-per-cloud "Permalink to this headline Below is the list of GPU flavors in each cloud, applicable for using with Magnum Kubernetes service. WAW3-1 -: WAW3-1 supports both four GPU flavors and the Kubernetes, through 3Engines Magnum. +: WAW3-1 supports both four GPU flavors and the Kubernetes, through connectVM Magnum. > | | | | | > | --- | --- | --- | --- | @@ -61,7 +61,7 @@ WAW3-1 > | **vm.a6000.4** | 114688 | 320 | 16 | WAW3-2 -: These are the vGPU flavors for WAW3-2 and Kubernetes, through 3Engines Magnum: +: These are the vGPU flavors for WAW3-2 and Kubernetes, through connectVM Magnum: > | | | | | | > | --- | --- | --- | --- | --- | @@ -72,7 +72,7 @@ WAW3-2 > | **gpu.l40sx8** | 254 | 953.75 GB | 1000 GB | Yes | FRA1-2 -: FRA1-2 Supports L40S and the Kubernetes, through 3Engines Magnum. +: FRA1-2 Supports L40S and the Kubernetes, through connectVM Magnum. > | | | | | | > | --- | --- | --- | --- | --- | @@ -109,7 +109,7 @@ Scenario 1 - Add vGPU nodes as a nodegroup on a non-GPU Kubernetes clusters crea In order to create a new nodegroup, called **gpu**, with one node vGPU flavor, say, **vm.a6000.2**, we can use the following Magnum CLI command: ``` -3Engines coe nodegroup create $CLUSTER_ID gpu \ +connectVM coe nodegroup create $CLUSTER_ID gpu \ --labels "worker_type=gpu" \ --merge-labels \ --role worker \ @@ -129,7 +129,7 @@ Your request will be accepted: Now list the available nodegroups: ``` -3Engines coe nodegroup list $CLUSTER_ID_RECENT \ +connectVM coe nodegroup list $CLUSTER_ID_RECENT \ --max-width 120 ``` @@ -156,7 +156,7 @@ where **$MASTER\_0\_SERVER\_ID** is the ID of the **master0** VM from your clust > * or using a CLI command to isolate the *uuid* for the master node: ``` -3Engines coe nodegroup list $CLUSTER_ID_OLDER \ +connectVM coe nodegroup list $CLUSTER_ID_OLDER \ -c uuid \ -c name \ -c status \ @@ -176,7 +176,7 @@ export MASTER_0_SERVER_ID="413c7486-caa9-4e12-be3b-3d9410f2d32f" and execute the following command to create an additional nodegroup in this scenario: ``` -3Engines coe nodegroup create $CLUSTER_ID_OLDER gpu \ +connectVM coe nodegroup create $CLUSTER_ID_OLDER gpu \ --labels "worker_type=gpu,existing_helm_handler_master_id=$MASTER_0_SERVER_ID" \ --merge-labels \ --role worker \ @@ -190,7 +190,7 @@ There may not be any space between the labels. The request will be accepted and after a while, a new nodegroup will be available and based on GPU flavor. List the nodegroups with the command: ``` -3Engines coe nodegroup list $CLUSTER_ID_OLDER --max-width 120 +connectVM coe nodegroup list $CLUSTER_ID_OLDER --max-width 120 ``` @@ -218,7 +218,7 @@ kubectl get namespaces The final command to create the required cluster is: ``` -3Engines coe cluster create k8s-gpu-with_template \ +connectVM coe cluster create k8s-gpu-with_template \ --cluster-template "k8s-1.23.16-vgpu-v1.0.0" \ --keypair=$KEYPAIR \ --master-count 1 \ @@ -271,7 +271,7 @@ and the result will look like this: Also, GPU workers are tainted by default with the taint: ``` -node.3Engines.com/type=gpu:NoSchedule +node.connectVM.com/type=gpu:NoSchedule ``` @@ -306,7 +306,7 @@ spec: operator: Exists effect: NoSchedule - effect: NoSchedule - key: node.3Engines.com/type + key: node.connectVM.com/type operator: Equal value: gpu @@ -353,7 +353,7 @@ In such clusters, to add an additional, non-GPU nodegroup, you will need to: In order to retrieve the image ID, you need to know with which template you want to use to create the new nodegroup. Out of the existing non-GPU templates, we select **k8s-1.23.16-v1.0.2** for this example. Run the following command to extract the template ID, as that will be needed for nodegroup creation: ``` -3Engines coe cluster \ +connectVM coe cluster \ template show k8s-1.23.16-v1.0.2 | grep image_id ``` @@ -367,7 +367,7 @@ We can then add the non-GPU nodegroup with the following command, in which you c ``` export CLUSTER_ID="k8s-gpu-with_template" export IMAGE_ID="42696e90-57af-4124-8e20-d017a44d6e24" -3Engines coe nodegroup create $CLUSTER_ID default \ +connectVM coe nodegroup create $CLUSTER_ID default \ --labels "worker_type=default" \ --merge-labels \ --role worker \ @@ -380,7 +380,7 @@ export IMAGE_ID="42696e90-57af-4124-8e20-d017a44d6e24" Then list the nodegroup contents to see whether the creation succeeded: ``` -3Engines coe nodegroup list $CLUSTER_ID \ +connectVM coe nodegroup list $CLUSTER_ID \ --max-width 120 ``` diff --git a/docs/kubernetes/Enable-Kubeapps-app-launcher-on-3Engines-Cloud-Magnum-Kubernetes-cluster.html.md b/docs/kubernetes/Enable-Kubeapps-app-launcher-on-connectVM-Cloud-Magnum-Kubernetes-cluster.html.md similarity index 84% rename from docs/kubernetes/Enable-Kubeapps-app-launcher-on-3Engines-Cloud-Magnum-Kubernetes-cluster.html.md rename to docs/kubernetes/Enable-Kubeapps-app-launcher-on-connectVM-Cloud-Magnum-Kubernetes-cluster.html.md index ea34174..c4d91a1 100644 --- a/docs/kubernetes/Enable-Kubeapps-app-launcher-on-3Engines-Cloud-Magnum-Kubernetes-cluster.html.md +++ b/docs/kubernetes/Enable-Kubeapps-app-launcher-on-connectVM-Cloud-Magnum-Kubernetes-cluster.html.md @@ -1,4 +1,4 @@ -Enable Kubeapps app launcher on 3Engines Cloud Magnum Kubernetes cluster[🔗](#enable-kubeapps-app-launcher-on-brand-name-magnum-kubernetes-cluster "Permalink to this headline") +Enable Kubeapps app launcher on connectVM Cloud Magnum Kubernetes cluster[🔗](#enable-kubeapps-app-launcher-on-brand-name-magnum-kubernetes-cluster "Permalink to this headline") ================================================================================================================================================================================= [Kubeapps](https://kubeapps.dev/) app-launcher enables quick deployments of applications on your Kubernetes cluster, with convenient graphical user interface. In this article we provide guidelines for creating Kubernetes cluster with Kubeapps feature enabled, and deploying sample applications. @@ -17,23 +17,23 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . -The resources that you require and use will reflect on the state of your account wallet. Check your account statistics at . +The resources that you require and use will reflect on the state of your account wallet. Check your account statistics at . No. 2 **Create Kubernetes cluster from Horizon GUI** -Know how to create a Kubernetes cluster from Horizon GUI, as described in article [How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md) +Know how to create a Kubernetes cluster from Horizon GUI, as described in article [How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md) No. 3 **How to Access Kubernetes cluster post-deployment** -Access to Linux command line and ability to access cluster, as described in article [How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md) +Access to Linux command line and ability to access cluster, as described in article [How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md) No. 4 **Handling Helm** -Some familiarity with Helm, to customize app deployments with Kubeapps. See [Deploying Helm Charts on Magnum Kubernetes Clusters on 3Engines Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md). +Some familiarity with Helm, to customize app deployments with Kubeapps. See [Deploying Helm Charts on Magnum Kubernetes Clusters on connectVM Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md). -No. 5 **Access to 3Engines clouds** +No. 5 **Access to connectVM clouds** Kubeapps is available on one of the clouds: WAW3-2, FRA1-2, WAW3-1. @@ -139,10 +139,10 @@ The results will be similar to this: Current limitations[🔗](#current-limitations "Permalink to this headline") ------------------------------------------------------------------------- -Both Kubeapps and Helm charts deployed by this launcher are open-source projects, which are continuously evolving. The versions installed on 3Engines Cloud cloud provide a snapshot of this development, as a convenience feature. +Both Kubeapps and Helm charts deployed by this launcher are open-source projects, which are continuously evolving. The versions installed on connectVM Cloud cloud provide a snapshot of this development, as a convenience feature. It is expected that not all applications can be installed with one-click and additional configuration will be needed in each particular case. -One known limitation is that certain charts will require RWM (ReadWriteMany) persistent volume claims to properly operate. Currently, RWM persistent volumes are not natively available on 3Engines Cloud cloud. A workaround could be installing NFS server and deploying a StorageClass with RWM-supportive provisioner e.g. using [nfs-subdir-external-provisioner](https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner) project from GitHub. +One known limitation is that certain charts will require RWM (ReadWriteMany) persistent volume claims to properly operate. Currently, RWM persistent volumes are not natively available on connectVM Cloud cloud. A workaround could be installing NFS server and deploying a StorageClass with RWM-supportive provisioner e.g. using [nfs-subdir-external-provisioner](https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner) project from GitHub. -For NFS on Kubernetes cluster, see [Create and access NFS server from Kubernetes on 3Engines Cloud](Create-and-access-NFS-server-from-Kubernetes-on-3Engines-Cloud.html.md). \ No newline at end of file +For NFS on Kubernetes cluster, see [Create and access NFS server from Kubernetes on connectVM Cloud](Create-and-access-NFS-server-from-Kubernetes-on-connectVM-Cloud.html.md). \ No newline at end of file diff --git a/docs/kubernetes/GitOps-with-Argo-CD-on-3Engines-Cloud-Kubernetes.html.md b/docs/kubernetes/GitOps-with-Argo-CD-on-connectVM-Cloud-Kubernetes.html.md similarity index 86% rename from docs/kubernetes/GitOps-with-Argo-CD-on-3Engines-Cloud-Kubernetes.html.md rename to docs/kubernetes/GitOps-with-Argo-CD-on-connectVM-Cloud-Kubernetes.html.md index 4fb2646..04adecb 100644 --- a/docs/kubernetes/GitOps-with-Argo-CD-on-3Engines-Cloud-Kubernetes.html.md +++ b/docs/kubernetes/GitOps-with-Argo-CD-on-connectVM-Cloud-Kubernetes.html.md @@ -1,4 +1,4 @@ -GitOps with Argo CD on 3Engines Cloud Kubernetes[🔗](#gitops-with-argo-cd-on-brand-name-kubernetes "Permalink to this headline") +GitOps with Argo CD on connectVM Cloud Kubernetes[🔗](#gitops-with-argo-cd-on-brand-name-kubernetes "Permalink to this headline") ================================================================================================================================= Argo CD is a continuous deployment tool for Kubernetes, designed with GitOps and Infrastructure as Code (IaC) principles in mind. It automatically ensures that the state of applications deployed on a Kubernetes cluster is always in sync with a dedicated Git repository where we define such desired state. @@ -19,25 +19,25 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Kubernetes cluster** -[How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md) +[How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md) No. 3 **Access to cluster with kubectl** -[How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md) +[How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md) No. 4 **Familiarity with Helm** Here is how to install and start using Helm charts: -[Deploying Helm Charts on Magnum Kubernetes Clusters on 3Engines Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md) +[Deploying Helm Charts on Magnum Kubernetes Clusters on connectVM Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md) No. 5 **Access to your own Git repository** -You can host the repository for this article on GitLab instance created in article [Install GitLab on 3Engines Cloud Kubernetes](Install-GitLab-on-3Engines-Cloud-Kubernetes.html.md). You may also use it with [GitHub](https://github.com/git-guides/install-git), [GitLab](https://docs.gitlab.com/ee/topics/git/how_to_install_git/) and other source control platforms based on **git**. +You can host the repository for this article on GitLab instance created in article [Install GitLab on connectVM Cloud Kubernetes](Install-GitLab-on-connectVM-Cloud-Kubernetes.html.md). You may also use it with [GitHub](https://github.com/git-guides/install-git), [GitLab](https://docs.gitlab.com/ee/topics/git/how_to_install_git/) and other source control platforms based on **git**. No. 6 **git CLI operational** @@ -45,7 +45,7 @@ No. 6 **git CLI operational** No. 7 **Access to exemplary Flask application** -You should have access to the [example Flask application](https://github.com/3Engines/K8s-samples/tree/main/Flask-K8s-deployment), to be downloaded from GitHub in the article. It will serve as an example of a minimal application and by changing it, we will demonstrate that Argo CD is capturing those changes in a continual manner. +You should have access to the [example Flask application](https://github.com/connectVM/K8s-samples/tree/main/Flask-K8s-deployment), to be downloaded from GitHub in the article. It will serve as an example of a minimal application and by changing it, we will demonstrate that Argo CD is capturing those changes in a continual manner. Step 1 Install Argo CD[🔗](#step-1-install-argo-cd "Permalink to this headline") ------------------------------------------------------------------------------- @@ -128,7 +128,7 @@ Step 4 Download Flask application[🔗](#step-4-download-flask-application "Perm The next goal is to download two yaml files to a folder called **ArgoCD-sample** and its subfolder **deployment**. -After submitting the “Create project” form, you will receive a list of commands to work with your repo. Review them and switch to the CLI from Prerequisite No. 6. Clone the entire 3Engines K8s samples repo, then extract the sub-folder called *Flask-K8s-deployment*. For clarity, we rename its contents to a new folder, **ArgoCD-sample**. Use +After submitting the “Create project” form, you will receive a list of commands to work with your repo. Review them and switch to the CLI from Prerequisite No. 6. Clone the entire connectVM K8s samples repo, then extract the sub-folder called *Flask-K8s-deployment*. For clarity, we rename its contents to a new folder, **ArgoCD-sample**. Use ``` mkdir ~/ArgoCD-sample @@ -138,13 +138,13 @@ mkdir ~/ArgoCD-sample if this is the first time you are working through this article. Then apply the following set of commands: ``` -git clone https://github.com/3Engines/K8s-samples +git clone https://github.com/connectVM/K8s-samples mv ~/K8s-samples/Flask-K8s-deployment ~/ArgoCD-sample/deployment rm K8s-samples/ -rf ``` -Files **deployment.yaml** and **service.yaml** deploy a sample Flask application on Kubernetes and expose it as a service. These are typical minimal examples for deployment and service and can be obtained from the 3Engines Kubernetes samples repository. +Files **deployment.yaml** and **service.yaml** deploy a sample Flask application on Kubernetes and expose it as a service. These are typical minimal examples for deployment and service and can be obtained from the connectVM Kubernetes samples repository. Step 5 Push your app deployment configurations[🔗](#step-5-push-your-app-deployment-configurations "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------------------- @@ -268,6 +268,6 @@ What To Do Next[🔗](#what-to-do-next "Permalink to this headline") * test applying changes to the deployment in the repository (e.g. commit a deployment with different image in the container spec), verify ArgoCD capturing the change and changing the cluster state * customize the deployment of Argo CD to enable HTTPS -* integrate Argo CD with your identity management tool; for details, see [Deploy Keycloak on Kubernetes with a sample app on 3Engines Cloud](Deploy-Keycloak-on-Kubernetes-with-a-sample-app-on-3Engines-Cloud.html.md) +* integrate Argo CD with your identity management tool; for details, see [Deploy Keycloak on Kubernetes with a sample app on connectVM Cloud](Deploy-Keycloak-on-Kubernetes-with-a-sample-app-on-connectVM-Cloud.html.md) -Also of interest would be the following article: [CI/CD pipelines with GitLab on 3Engines Cloud Kubernetes - building a Docker image](CICD-pipelines-with-GitLab-on-3Engines-Cloud-Kubernetes-building-a-Docker-image.html.md) \ No newline at end of file +Also of interest would be the following article: [CI/CD pipelines with GitLab on connectVM Cloud Kubernetes - building a Docker image](CICD-pipelines-with-GitLab-on-connectVM-Cloud-Kubernetes-building-a-Docker-image.html.md) \ No newline at end of file diff --git a/docs/kubernetes/HTTP-Request-based-Autoscaling-on-K8S-using-Prometheus-and-Keda-on-3Engines-Cloud.html.md b/docs/kubernetes/HTTP-Request-based-Autoscaling-on-K8S-using-Prometheus-and-Keda-on-connectVM-Cloud.html.md similarity index 94% rename from docs/kubernetes/HTTP-Request-based-Autoscaling-on-K8S-using-Prometheus-and-Keda-on-3Engines-Cloud.html.md rename to docs/kubernetes/HTTP-Request-based-Autoscaling-on-K8S-using-Prometheus-and-Keda-on-connectVM-Cloud.html.md index 09be5ec..aca6ef9 100644 --- a/docs/kubernetes/HTTP-Request-based-Autoscaling-on-K8S-using-Prometheus-and-Keda-on-3Engines-Cloud.html.md +++ b/docs/kubernetes/HTTP-Request-based-Autoscaling-on-K8S-using-Prometheus-and-Keda-on-connectVM-Cloud.html.md @@ -1,11 +1,11 @@ -HTTP Request-based Autoscaling on K8S using Prometheus and Keda on 3Engines Cloud[🔗](#http-request-based-autoscaling-on-k8s-using-prometheus-and-keda-on-brand-name "Permalink to this headline") +HTTP Request-based Autoscaling on K8S using Prometheus and Keda on connectVM Cloud[🔗](#http-request-based-autoscaling-on-k8s-using-prometheus-and-keda-on-brand-name "Permalink to this headline") =================================================================================================================================================================================================== Kubernetes pod autoscaler (HPA) natively utilizes CPU and RAM metrics as the default triggers for increasing or decreasing number of pods. While this is often sufficient, there can be use cases where scaling on custom metrics is preferred. [KEDA](https://keda.sh/) is a tool for autoscaling based on events/metrics provided from popular sources/technologies such as Prometheus, Kafka, Postgres and multiple others. -With this article we will deploy a sample app on 3Engines Cloud cloud. We will collect HTTP requests from NGINX Ingress on our Kubernetes cluster and, using Keda with Prometheus scaler, apply custom HTTP request-based scaling. +With this article we will deploy a sample app on connectVM Cloud cloud. We will collect HTTP requests from NGINX Ingress on our Kubernetes cluster and, using Keda with Prometheus scaler, apply custom HTTP request-based scaling. Note @@ -27,7 +27,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") ------------------------------------------------------------- No. 1 **Account** -: You need a 3Engines Cloud hosting account with access to the Horizon interface: . +: You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Create a new Kubernetes cluster without Magnum NGINX preinstalled from Horizon UI** @@ -37,7 +37,7 @@ No. 3 **kubectl pointed to the Kubernetes cluster** The following article gives options for creating a new cluster and activating the **kubectl** command: -[How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md). +[How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md). As mentioned, create the cluster **without** installing the NGINX ingress option. @@ -45,7 +45,7 @@ No. 4 **Familiarity with deploying Helm charts** This article will introduce you to Helm charts on Kubernetes: -[Deploying Helm Charts on Magnum Kubernetes Clusters on 3Engines Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md) +[Deploying Helm Charts on Magnum Kubernetes Clusters on connectVM Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md) Install NGINX ingress on Magnum cluster[🔗](#install-nginx-ingress-on-magnum-cluster "Permalink to this headline") ----------------------------------------------------------------------------------------------------------------- diff --git a/docs/kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md b/docs/kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md similarity index 82% rename from docs/kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md rename to docs/kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md index d8a41d7..7964ffe 100644 --- a/docs/kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md +++ b/docs/kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md @@ -1,12 +1,12 @@ -How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum[🔗](#how-to-access-kubernetes-cluster-post-deployment-using-kubectl-on-brand-name-3Engines-magnum "Permalink to this headline") +How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum[🔗](#how-to-access-kubernetes-cluster-post-deployment-using-kubectl-on-brand-name-connectVM-magnum "Permalink to this headline") =================================================================================================================================================================================================================================== -In this tutorial, you start with a freshly installed Kubernetes cluster on 3Engines 3Engines server and connect the main Kubernetes tool, **kubectl** to the cloud. +In this tutorial, you start with a freshly installed Kubernetes cluster on connectVM connectVM server and connect the main Kubernetes tool, **kubectl** to the cloud. What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- -> * How to connect **kubectl** to the 3Engines Magnum server +> * How to connect **kubectl** to the connectVM Magnum server > * How to access clusters with **kubectl** Prerequisites[🔗](#prerequisites "Permalink to this headline") @@ -14,7 +14,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . No. 2 **Installation of kubectl** @@ -24,13 +24,13 @@ No. 3 **A cluster already installed on Magnum site** You may already have a cluster installed if you have followed one of these articles: -> * With Horizon interface: [How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md). -> * With command line interface: [How To Use Command Line Interface for Kubernetes Clusters On 3Engines Cloud 3Engines Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-3Engines-Cloud-3Engines-Magnum.html.md). +> * With Horizon interface: [How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md). +> * With command line interface: [How To Use Command Line Interface for Kubernetes Clusters On connectVM Cloud connectVM Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-connectVM-Cloud-connectVM-Magnum.html.md). * Or, you may want to create a new cluster called *k8s-cluster*, just for this occasion – by using the following CLI command: ``` -3Engines coe cluster create \ +connectVM coe cluster create \ --cluster-template k8s-stable-1.23.5 \ --labels eodata_access_enabled=false,floating-ip-enabled=true,master-lb-enabled=true \ --merge-labels \ @@ -49,16 +49,16 @@ It takes some 10-20 minutes for the new cluster to form. In the rest of this text we shall use cluster name *k8s-cluster* – be sure to use the name of the existing cluster instead. -No. 4 **Connect 3Engines client to the cloud** +No. 4 **Connect connectVM client to the cloud** -Prepare **3Engines** and **magnum** clients by executing *Step 2 Connect 3Engines and Magnum Clients to Horizon Cloud* from article [How To Install 3Engines and Magnum Clients for Command Line Interface to 3Engines Cloud Horizon](How-To-Install-3Engines-and-Magnum-Clients-for-Command-Line-Interface-to-3Engines-Cloud-Horizon.html.md). +Prepare **connectVM** and **magnum** clients by executing *Step 2 Connect connectVM and Magnum Clients to Horizon Cloud* from article [How To Install connectVM and Magnum Clients for Command Line Interface to connectVM Cloud Horizon](How-To-Install-connectVM-and-Magnum-Clients-for-Command-Line-Interface-to-connectVM-Cloud-Horizon.html.md). The Plan[🔗](#the-plan "Permalink to this headline") --------------------------------------------------- > * Follow up the steps listed in Prerequisite No. 2 and install **kubectl** on the platform of your choice. -> * Use the existing Kubernetes cluster on 3Engines or install a new one using the methods outlined in Prerequisites Nos. 3. -> * Use Step 2 in Prerequisite No. 4 to enable connection of **3Engines** and **magnum** clients to the cloud. +> * Use the existing Kubernetes cluster on connectVM or install a new one using the methods outlined in Prerequisites Nos. 3. +> * Use Step 2 in Prerequisite No. 4 to enable connection of **connectVM** and **magnum** clients to the cloud. You are then going to connect **kubectl** to the Cloud. @@ -96,15 +96,15 @@ Step 2A Download Certificates From the Server using the CLI commands[🔗](#step You will use command ``` -3Engines coe cluster config +connectVM coe cluster config ``` to download the files that **kubectl** needs for authentication with the server. See its input parameters using the **–help** parameter: ``` -3Engines coe cluster config --help -usage: 3Engines coe cluster config [-h] +connectVM coe cluster config --help +usage: connectVM coe cluster config [-h] [--dir ] [--force] [--output-certs] [--use-certificate] [--use-keystone] @@ -127,7 +127,7 @@ optional arguments: Download the certificates into the *k8sdir* folder: ``` -3Engines coe cluster config \ +connectVM coe cluster config \ --dir k8sdir \ --force \ --output-certs \ @@ -232,4 +232,4 @@ With **kubectl** operational, you can > * list container images in the cluster > * use Services, Deployments and all other resources in a Kubernetes cluster. -Kubernetes dashboard is a visual alternative to **kubectl**. To install it, see [Using Dashboard To Access Kubernetes Cluster Post Deployment On 3Engines Cloud 3Engines Magnum](Using-Dashboard-To-Access-Kubernetes-Cluster-Post-Deployment-On-3Engines-Cloud-3Engines-Magnum.html.md). \ No newline at end of file +Kubernetes dashboard is a visual alternative to **kubectl**. To install it, see [Using Dashboard To Access Kubernetes Cluster Post Deployment On connectVM Cloud connectVM Magnum](Using-Dashboard-To-Access-Kubernetes-Cluster-Post-Deployment-On-connectVM-Cloud-connectVM-Magnum.html.md). \ No newline at end of file diff --git a/docs/kubernetes/How-To-Create-API-Server-LoadBalancer-for-Kubernetes-Cluster-On-3Engines-Cloud-3Engines-Magnum.html.md b/docs/kubernetes/How-To-Create-API-Server-LoadBalancer-for-Kubernetes-Cluster-On-connectVM-Cloud-connectVM-Magnum.html.md similarity index 83% rename from docs/kubernetes/How-To-Create-API-Server-LoadBalancer-for-Kubernetes-Cluster-On-3Engines-Cloud-3Engines-Magnum.html.md rename to docs/kubernetes/How-To-Create-API-Server-LoadBalancer-for-Kubernetes-Cluster-On-connectVM-Cloud-connectVM-Magnum.html.md index dba21eb..45ab872 100644 --- a/docs/kubernetes/How-To-Create-API-Server-LoadBalancer-for-Kubernetes-Cluster-On-3Engines-Cloud-3Engines-Magnum.html.md +++ b/docs/kubernetes/How-To-Create-API-Server-LoadBalancer-for-Kubernetes-Cluster-On-connectVM-Cloud-connectVM-Magnum.html.md @@ -1,4 +1,4 @@ -How To Create API Server LoadBalancer for Kubernetes Cluster on 3Engines Cloud 3Engines Magnum[🔗](#how-to-create-api-server-loadbalancer-for-kubernetes-cluster-on-brand-name-3Engines-magnum "Permalink to this headline") +How To Create API Server LoadBalancer for Kubernetes Cluster on connectVM Cloud connectVM Magnum[🔗](#how-to-create-api-server-loadbalancer-for-kubernetes-cluster-on-brand-name-connectVM-magnum "Permalink to this headline") =============================================================================================================================================================================================================================== Load balancer can be understood both as @@ -23,24 +23,24 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . -No. 2 **Installation of the 3Engines command** +No. 2 **Installation of the connectVM command** -To activate **kubectl** command, the 3Engines command from CLI 3Engines Interface must be operational. The first part of article [How To Use Command Line Interface for Kubernetes Clusters On 3Engines Cloud 3Engines Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-3Engines-Cloud-3Engines-Magnum.html.md) shows how to install it. +To activate **kubectl** command, the connectVM command from CLI connectVM Interface must be operational. The first part of article [How To Use Command Line Interface for Kubernetes Clusters On connectVM Cloud connectVM Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-connectVM-Cloud-connectVM-Magnum.html.md) shows how to install it. No. 3 **How to create Kubernetes cluster using Horizon commands** -The article [How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md) shows creation of clusters with Horizon visual interface. (In this article, you shall use it to create an exemplar cluster called *NoLoadBalancer*.) +The article [How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md) shows creation of clusters with Horizon visual interface. (In this article, you shall use it to create an exemplar cluster called *NoLoadBalancer*.) No. 4 **Connect to the Kubernetes Cluster in Order to Use kubectl** -Article [How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md) will show you how to connect your local machine to the existing Kubernetes cluster. +Article [How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md) will show you how to connect your local machine to the existing Kubernetes cluster. How To Enable or Disable Load Balancer for Master Nodes[🔗](#how-to-enable-or-disable-load-balancer-for-master-nodes "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------------------------------------- -A default state for the Kubernetes cluster in 3Engines Cloud 3Engines Magnum hosting is to have no load balancer set up in advance. You can decide to have a load balancer created together with the basic Kubernetes cluster by checking on option **Enable Load Balancer for Master Nodes** in window **Network** when creating a cluster through Horizon interface. (See **Prerequisite No. 3** for the complete procedure.) +A default state for the Kubernetes cluster in connectVM Cloud connectVM Magnum hosting is to have no load balancer set up in advance. You can decide to have a load balancer created together with the basic Kubernetes cluster by checking on option **Enable Load Balancer for Master Nodes** in window **Network** when creating a cluster through Horizon interface. (See **Prerequisite No. 3** for the complete procedure.) The check box to enable load balancer for master nodes has two completely different meanings when checked and not checked. @@ -63,8 +63,8 @@ One Master Node, No Load Balancer and the Problem It All Creates[🔗](#one-mast To show exactly what the problem is, use -> * Prerequisite No. 2 to install 3Engines client for the local machine, so that you can use the **3Engines** command. -> * Then use Prerequisite No. 4 to connect to the 3Engines cloud and start using **3Engines** command from the local terminal. +> * Prerequisite No. 2 to install connectVM client for the local machine, so that you can use the **connectVM** command. +> * Then use Prerequisite No. 4 to connect to the connectVM cloud and start using **connectVM** command from the local terminal. Then you can try a very usual command such as @@ -132,7 +132,7 @@ Step 3 **Create config File for Kubernetes Cluster**[🔗](#step-3-create-config You are now going to connect to *NoLoadBalancer* cluster in spite of it not having a load balancer from the very start. To that end, create a config file to connect to the cluster, with the following command: ``` -3Engines coe cluster config NoLoadBalancer --force +connectVM coe cluster config NoLoadBalancer --force ``` diff --git a/docs/kubernetes/How-To-Install-3Engines-and-Magnum-Clients-for-Command-Line-Interface-to-3Engines-Cloud-Horizon.html.md b/docs/kubernetes/How-To-Install-3Engines-and-Magnum-Clients-for-Command-Line-Interface-to-3Engines-Cloud-Horizon.html.md deleted file mode 100644 index bbf03c5..0000000 --- a/docs/kubernetes/How-To-Install-3Engines-and-Magnum-Clients-for-Command-Line-Interface-to-3Engines-Cloud-Horizon.html.md +++ /dev/null @@ -1,196 +0,0 @@ -How To Install 3Engines and Magnum Clients for Command Line Interface to 3Engines Cloud Horizon[🔗](#how-to-install-3Engines-and-magnum-clients-for-command-line-interface-to-brand-name-horizon "Permalink to this headline") -================================================================================================================================================================================================================================= - -How To Issue Commands to the 3Engines and Magnum Servers[🔗](#how-to-issue-commands-to-the-3Engines-and-magnum-servers "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------------------------------------------ - -There are three ways of working with Kubernetes clusters within 3Engines Magnum and Horizon modules: - -**Horizon Commands** - -You issue Horizon commands using mouse and keyboard, through predefined screen wizards. It is the easiest way to start but not the most productive in the long run. - -**Command Line Interface (CLI)** - -CLI commands are issued from desktop computer or server in the cloud. This approach allows you to save commands as text and repeat them afterwards. This is the preferred way for professionals. - -**HTTPS Requests to the Magnum Server** - -Both the Horizon and the CLI use HTTPS requests internally and in an interactive manner. You can, however, write your own software to automate and/or change the state of the server, in real time. - -What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") ---------------------------------------------------------------------------------------- - -> * How to install the CLI – 3Engines and Magnum clients -> * How to connect the CLI to the Horizon server -> * Basic examples of using 3Engines and Magnum clients - -Notes On Python Versions and Environments for Installation[🔗](#notes-on-python-versions-and-environments-for-installation "Permalink to this headline") -------------------------------------------------------------------------------------------------------------------------------------------------------- - -3Engines is written in Python so you need to first install a Python working environment and then install the 3Engines clients. Officially, 3Engines runs only on Python 2.7 but you will most likely only be able to install a version 3.x of Python. During the installation, adjust accordingly the numbers of Python versions mentioned in the documentation. - -You will be able to install Python on any of the popular platforms, such as Windows, MacOS, Linux on a desktop computer. Or, supposing you are logged into Horizon interface, you can use commands **Compute** => **Instances** to create an instance of a virtual machine. Then install the Python there. Ubuntu 18.04 or 20.04 would serve best in this regard. - -Warning - -Once you install Kubernetes cluster you will have also have installed instances with Fedora 33 or 35, say, for the master node of the control plane. You can install the Python and 3Engines clients there as well but Ubuntu is much easier to use and is the preferred solution in this case. - -You can install the Python and the clients on several environments at once, say, on a desktop computer and on a virtual machine on the server, at the same time. Following the instructions in this tutorial, they will all be connected to one and the same Kubernetes cluster anyway. - -Note - -If you decide to install Python and the 3Engines clients on a virtual machine, you will need SSH keys in order to be able to enter the working environment. See [How to create key pair in 3Engines Dashboard on 3Engines Cloud](../cloud/How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md). - -Prerequisites[🔗](#prerequisites "Permalink to this headline") -------------------------------------------------------------- - -No. 1 **Hosting** - -You need a 3Engines Cloud hosting account with Horizon interface . - -No. 2 **Installation of 3Engines CLI on Ubuntu 20.04 Server** - -The article [How to install 3EnginesClient for Linux on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md) shows how to install 3Engines client on Ubuntu server. That Ubuntu may be the desktop operating system, a virtual machine on some other operating system, or an Ubuntu server in the cloud. - -Installation on Mac OS will be similar to the installation on Ubuntu. - -No. 3 **Installation of 3Engines CLI on Windows** - -The article [How to install 3EnginesClient GitBash for Windows on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-GitBash-or-Cygwin-for-Windows-on-3Engines-Cloud.html.md) shows installation on Windows. - -No. 4 **General Instructions for Installation of 3Engines Clients** - -There are various ways of installing Python and the required clients. For instance, on MacOS, you can install the clients using Python PIP or install them natively, using *homebrew*. - -The article [Install the 3Engines command-line clients](https://docs.3Engines.org/newton/user-guide/common/cli-install-3Engines-command-line-clients.html.md) will give a systematic introduction to installation of 3Engines family of clients on various operating systems. - -Once installed, the CLI commands will be identical across various platforms and operating systems. - -No. 5 **Connect 3Engines command to the cloud** - -After the successful installation of **3Engines** command, it should be connected to the cloud. Follow this article for technical details: [How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md). - -Step 1 Install the CLI for Kubernetes on 3Engines Magnum[🔗](#step-1-install-the-cli-for-kubernetes-on-3Engines-magnum "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------------------------------------------ - -In this step, you are going to install clients for commands **3Engines** and **coe**, from modules 3Engines and Magnum, respectively. - -Follow the Prerequisites Nos. 2, 3 or 4 to install the main client for 3Engines. Its name is *python-3Enginesclient* and the installation described in those will typically contain a command such as - -``` -pip install python-3Enginesclient - -``` - -If you have installed 3EnginesClient using those prerequisite resources, we shall assume that the **3Engines** is available and connected to the cloud. - -At the end of installation from either of the prerequisite articles, install Magnum client by issuing this command: - -``` -pip install python-magnumclient - -``` - -Step 2 How to Use the 3Engines Client[🔗](#step-2-how-to-use-the-3Engines-client "Permalink to this headline") ---------------------------------------------------------------------------------------------------------------- - -In this step, you are going to start using the 3Engines client you have installed and connected to the cloud. - -There are two ways of using the 3EnginesClient. If you enter the word **3Engines** at the command prompt of the terminal, you will enter the special command line interface, like this: - -![3Engines_cli.png](../_images/3Engines_cli.png) - -The benefit would be that you do not have to type **3Engines** keyword for every command. - -Type **quit** to leave the **3Engines** internal command line prompt. - -The preferred way, however, is typing the keyword **3Engines**, followed by parameters and running from terminal command line. - -3Engines commands may have dozens of parameters so it is better to compose the command in an independent text editor and then copy and paste it into the terminal. - -The Help Command[🔗](#the-help-command "Permalink to this headline") -------------------------------------------------------------------- - -To learn about the available commands and their parameters, type **–help** after the command. If applied to the keyword **3Engines** itself, it will write out a very long list of commands, which may come useful as an orientation. It may start out like this: - -![3Engines_help.png](../_images/3Engines_help.png) - -This is how it ends: - -![3Engines_vim.png](../_images/3Engines_vim.png) - -The colon in the last line means that the output is in **vi** (or **vim**) editor. To leave it, type letter **q** and press Enter on the keyboard. - -Prerequisites No. 3 and 4 lead to official 3Engines user documentation. - -Here is what happens when you enter a wrong parameter, say, *networks* instead of *network*: - -``` -3Engines networks list - -``` - -![networks_list.png](../_images/networks_list.png) - -You get a list of commands similar to what you just typed. - -To list networks available in the system, use a singular version of the command: - -``` -3Engines network list - -``` - -![network_list.png](../_images/network_list.png) - -Step 4 How to Use the Magnum Client[🔗](#step-4-how-to-use-the-magnum-client "Permalink to this headline") ---------------------------------------------------------------------------------------------------------- - -OpensStack command for the server is **3Engines** but for Magnum, the command is not **magnum** as one would expect, but **coe**, for *container orchestration engine*. Therefore, the commands for clusters will always start with **3Engines coe**. - -See cluster commands by entering - -``` -3Engines coe - -``` - -into the command line: - -![3Engines_coe.png](../_images/3Engines_coe.png) - -You can see the existing clusters using the following command: - -``` -3Engines coe cluster list - -``` - -![3Engines_coe_cluster_list.png](../_images/3Engines_coe_cluster_list.png) - -This is more or less the same information that you can get from the Horizon interface: - -![cluster_list_horizon.png](../_images/cluster_list_horizon.png) - -after clicking on **Container Infra** => **Clusters**. - -Prerequisite No. 5 offers more technical info about the Magnum client. - -What To Do Next[🔗](#what-to-do-next "Permalink to this headline") ------------------------------------------------------------------ - -In this tutorial you have - -> * installed the *3Engines* and *Magnum* clients -> * connected them to the server, then used -> * **3Engines** command to access the server in general and -> * **coe** to access the clusters in particular. - -> The article [How To Use Command Line Interface for Kubernetes Clusters On 3Engines Cloud 3Engines Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-3Engines-Cloud-3Engines-Magnum.html.md) explains - -* the advantages of using the CLI instead of Horizon interface, showing -* how to create a cluster template as well as -* how to create a new cluster - -all via the CLI. \ No newline at end of file diff --git a/docs/kubernetes/How-To-Install-connectVM-and-Magnum-Clients-for-Command-Line-Interface-to-connectVM-Cloud-Horizon.html.md b/docs/kubernetes/How-To-Install-connectVM-and-Magnum-Clients-for-Command-Line-Interface-to-connectVM-Cloud-Horizon.html.md new file mode 100644 index 0000000..2a98650 --- /dev/null +++ b/docs/kubernetes/How-To-Install-connectVM-and-Magnum-Clients-for-Command-Line-Interface-to-connectVM-Cloud-Horizon.html.md @@ -0,0 +1,196 @@ +How To Install connectVM and Magnum Clients for Command Line Interface to connectVM Cloud Horizon[🔗](#how-to-install-connectVM-and-magnum-clients-for-command-line-interface-to-brand-name-horizon "Permalink to this headline") +================================================================================================================================================================================================================================= + +How To Issue Commands to the connectVM and Magnum Servers[🔗](#how-to-issue-commands-to-the-connectVM-and-magnum-servers "Permalink to this headline") +----------------------------------------------------------------------------------------------------------------------------------------------------- + +There are three ways of working with Kubernetes clusters within connectVM Magnum and Horizon modules: + +**Horizon Commands** + +You issue Horizon commands using mouse and keyboard, through predefined screen wizards. It is the easiest way to start but not the most productive in the long run. + +**Command Line Interface (CLI)** + +CLI commands are issued from desktop computer or server in the cloud. This approach allows you to save commands as text and repeat them afterwards. This is the preferred way for professionals. + +**HTTPS Requests to the Magnum Server** + +Both the Horizon and the CLI use HTTPS requests internally and in an interactive manner. You can, however, write your own software to automate and/or change the state of the server, in real time. + +What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") +--------------------------------------------------------------------------------------- + +> * How to install the CLI – connectVM and Magnum clients +> * How to connect the CLI to the Horizon server +> * Basic examples of using connectVM and Magnum clients + +Notes On Python Versions and Environments for Installation[🔗](#notes-on-python-versions-and-environments-for-installation "Permalink to this headline") +------------------------------------------------------------------------------------------------------------------------------------------------------- + +connectVM is written in Python so you need to first install a Python working environment and then install the connectVM clients. Officially, connectVM runs only on Python 2.7 but you will most likely only be able to install a version 3.x of Python. During the installation, adjust accordingly the numbers of Python versions mentioned in the documentation. + +You will be able to install Python on any of the popular platforms, such as Windows, MacOS, Linux on a desktop computer. Or, supposing you are logged into Horizon interface, you can use commands **Compute** => **Instances** to create an instance of a virtual machine. Then install the Python there. Ubuntu 18.04 or 20.04 would serve best in this regard. + +Warning + +Once you install Kubernetes cluster you will have also have installed instances with Fedora 33 or 35, say, for the master node of the control plane. You can install the Python and connectVM clients there as well but Ubuntu is much easier to use and is the preferred solution in this case. + +You can install the Python and the clients on several environments at once, say, on a desktop computer and on a virtual machine on the server, at the same time. Following the instructions in this tutorial, they will all be connected to one and the same Kubernetes cluster anyway. + +Note + +If you decide to install Python and the connectVM clients on a virtual machine, you will need SSH keys in order to be able to enter the working environment. See [How to create key pair in connectVM Dashboard on connectVM Cloud](../cloud/How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md). + +Prerequisites[🔗](#prerequisites "Permalink to this headline") +------------------------------------------------------------- + +No. 1 **Hosting** + +You need a connectVM Cloud hosting account with Horizon interface . + +No. 2 **Installation of connectVM CLI on Ubuntu 20.04 Server** + +The article [How to install connectVMClient for Linux on connectVM Cloud](../connectVMcli/How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md) shows how to install connectVM client on Ubuntu server. That Ubuntu may be the desktop operating system, a virtual machine on some other operating system, or an Ubuntu server in the cloud. + +Installation on Mac OS will be similar to the installation on Ubuntu. + +No. 3 **Installation of connectVM CLI on Windows** + +The article [How to install connectVMClient GitBash for Windows on connectVM Cloud](../connectVMcli/How-to-install-connectVMClient-GitBash-or-Cygwin-for-Windows-on-connectVM-Cloud.html.md) shows installation on Windows. + +No. 4 **General Instructions for Installation of connectVM Clients** + +There are various ways of installing Python and the required clients. For instance, on MacOS, you can install the clients using Python PIP or install them natively, using *homebrew*. + +The article [Install the connectVM command-line clients](https://docs.connectVM.org/newton/user-guide/common/cli-install-connectVM-command-line-clients.html.md) will give a systematic introduction to installation of connectVM family of clients on various operating systems. + +Once installed, the CLI commands will be identical across various platforms and operating systems. + +No. 5 **Connect connectVM command to the cloud** + +After the successful installation of **connectVM** command, it should be connected to the cloud. Follow this article for technical details: [How to activate connectVM CLI access to connectVM Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-connectVM-CLI-access-to-connectVM-Cloud-cloud-using-one-or-two-factor-authentication.html.md). + +Step 1 Install the CLI for Kubernetes on connectVM Magnum[🔗](#step-1-install-the-cli-for-kubernetes-on-connectVM-magnum "Permalink to this headline") +----------------------------------------------------------------------------------------------------------------------------------------------------- + +In this step, you are going to install clients for commands **connectVM** and **coe**, from modules connectVM and Magnum, respectively. + +Follow the Prerequisites Nos. 2, 3 or 4 to install the main client for connectVM. Its name is *python-connectVMclient* and the installation described in those will typically contain a command such as + +``` +pip install python-connectVMclient + +``` + +If you have installed connectVMClient using those prerequisite resources, we shall assume that the **connectVM** is available and connected to the cloud. + +At the end of installation from either of the prerequisite articles, install Magnum client by issuing this command: + +``` +pip install python-magnumclient + +``` + +Step 2 How to Use the connectVM Client[🔗](#step-2-how-to-use-the-connectVM-client "Permalink to this headline") +--------------------------------------------------------------------------------------------------------------- + +In this step, you are going to start using the connectVM client you have installed and connected to the cloud. + +There are two ways of using the connectVMClient. If you enter the word **connectVM** at the command prompt of the terminal, you will enter the special command line interface, like this: + +![connectVM_cli.png](../_images/connectVM_cli.png) + +The benefit would be that you do not have to type **connectVM** keyword for every command. + +Type **quit** to leave the **connectVM** internal command line prompt. + +The preferred way, however, is typing the keyword **connectVM**, followed by parameters and running from terminal command line. + +connectVM commands may have dozens of parameters so it is better to compose the command in an independent text editor and then copy and paste it into the terminal. + +The Help Command[🔗](#the-help-command "Permalink to this headline") +------------------------------------------------------------------- + +To learn about the available commands and their parameters, type **–help** after the command. If applied to the keyword **connectVM** itself, it will write out a very long list of commands, which may come useful as an orientation. It may start out like this: + +![connectVM_help.png](../_images/connectVM_help.png) + +This is how it ends: + +![connectVM_vim.png](../_images/connectVM_vim.png) + +The colon in the last line means that the output is in **vi** (or **vim**) editor. To leave it, type letter **q** and press Enter on the keyboard. + +Prerequisites No. 3 and 4 lead to official connectVM user documentation. + +Here is what happens when you enter a wrong parameter, say, *networks* instead of *network*: + +``` +connectVM networks list + +``` + +![networks_list.png](../_images/networks_list.png) + +You get a list of commands similar to what you just typed. + +To list networks available in the system, use a singular version of the command: + +``` +connectVM network list + +``` + +![network_list.png](../_images/network_list.png) + +Step 4 How to Use the Magnum Client[🔗](#step-4-how-to-use-the-magnum-client "Permalink to this headline") +--------------------------------------------------------------------------------------------------------- + +OpensStack command for the server is **connectVM** but for Magnum, the command is not **magnum** as one would expect, but **coe**, for *container orchestration engine*. Therefore, the commands for clusters will always start with **connectVM coe**. + +See cluster commands by entering + +``` +connectVM coe + +``` + +into the command line: + +![connectVM_coe.png](../_images/connectVM_coe.png) + +You can see the existing clusters using the following command: + +``` +connectVM coe cluster list + +``` + +![connectVM_coe_cluster_list.png](../_images/connectVM_coe_cluster_list.png) + +This is more or less the same information that you can get from the Horizon interface: + +![cluster_list_horizon.png](../_images/cluster_list_horizon.png) + +after clicking on **Container Infra** => **Clusters**. + +Prerequisite No. 5 offers more technical info about the Magnum client. + +What To Do Next[🔗](#what-to-do-next "Permalink to this headline") +----------------------------------------------------------------- + +In this tutorial you have + +> * installed the *connectVM* and *Magnum* clients +> * connected them to the server, then used +> * **connectVM** command to access the server in general and +> * **coe** to access the clusters in particular. + +> The article [How To Use Command Line Interface for Kubernetes Clusters On connectVM Cloud connectVM Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-connectVM-Cloud-connectVM-Magnum.html.md) explains + +* the advantages of using the CLI instead of Horizon interface, showing +* how to create a cluster template as well as +* how to create a new cluster + +all via the CLI. \ No newline at end of file diff --git a/docs/kubernetes/How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-3Engines-Cloud-3Engines-Magnum.html.md b/docs/kubernetes/How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-connectVM-Cloud-connectVM-Magnum.html.md similarity index 75% rename from docs/kubernetes/How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-3Engines-Cloud-3Engines-Magnum.html.md rename to docs/kubernetes/How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-connectVM-Cloud-connectVM-Magnum.html.md index 4615e99..4ea3daa 100644 --- a/docs/kubernetes/How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-3Engines-Cloud-3Engines-Magnum.html.md +++ b/docs/kubernetes/How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-connectVM-Cloud-connectVM-Magnum.html.md @@ -1,13 +1,13 @@ -How To Use Command Line Interface for Kubernetes Clusters On 3Engines Cloud 3Engines Magnum[🔗](#how-to-use-command-line-interface-for-kubernetes-clusters-on-brand-name-3Engines-magnum "Permalink to this headline") +How To Use Command Line Interface for Kubernetes Clusters On connectVM Cloud connectVM Magnum[🔗](#how-to-use-command-line-interface-for-kubernetes-clusters-on-brand-name-connectVM-magnum "Permalink to this headline") ========================================================================================================================================================================================================================= -In this article you shall use Command Line Interface (CLI) to speed up testing and creation of Kubernetes clusters on 3Engines Magnum servers. +In this article you shall use Command Line Interface (CLI) to speed up testing and creation of Kubernetes clusters on connectVM Magnum servers. What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- > * The advantages of using CLI over the Horizon graphical interface -> * Debugging 3Engines and Magnum commands +> * Debugging connectVM and Magnum commands > * How to create a new Kubernetes cluster template using CLI > * How to create a new Kubernetes cluster using CLI > * Reasons why the cluster may fail to create @@ -18,33 +18,33 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . No. 2 **Private and public keys** -An SSH key-pair created in 3Engines dashboard. To create it, follow this article [How to create key pair in 3Engines Dashboard on 3Engines Cloud](../cloud/How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md). You will have created keypair called *sshkey* and you will be able to use it for this tutorial as well. +An SSH key-pair created in connectVM dashboard. To create it, follow this article [How to create key pair in connectVM Dashboard on connectVM Cloud](../cloud/How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md). You will have created keypair called *sshkey* and you will be able to use it for this tutorial as well. -No. 3 **Command Structure of 3Engines Client Commands** +No. 3 **Command Structure of connectVM Client Commands** -Here is the manual for 3EnginesClient commands: [Command Structure Xena version](https://docs.3Engines.org/python-3Enginesclient/xena/cli/commands.html.md). +Here is the manual for connectVMClient commands: [Command Structure Xena version](https://docs.connectVM.org/python-connectVMclient/xena/cli/commands.html.md). -No. 4 **Command List of 3Engines Client Commands** +No. 4 **Command List of connectVM Client Commands** -These are all the commands supported by Xena release of 3EnginesClient: [Xena Command List](https://docs.3Engines.org/python-3Enginesclient/xena/cli/command-list.html.md). +These are all the commands supported by Xena release of connectVMClient: [Xena Command List](https://docs.connectVM.org/python-connectVMclient/xena/cli/command-list.html.md). No. 5 **Documentation for Magnum client** -These are all the commands supported by Xena release of MagnumClient: [Magnum User Guide](https://docs.3Engines.org/magnum/latest/user/). +These are all the commands supported by Xena release of MagnumClient: [Magnum User Guide](https://docs.connectVM.org/magnum/latest/user/). -No. 6 **How to install 3Engines and Magnum Clients** +No. 6 **How to install connectVM and Magnum Clients** -The step that directly precedes this article is: [How To Install 3Engines and Magnum Clients for Command Line Interface to 3Engines Cloud Horizon](How-To-Install-3Engines-and-Magnum-Clients-for-Command-Line-Interface-to-3Engines-Cloud-Horizon.html.md). +The step that directly precedes this article is: [How To Install connectVM and Magnum Clients for Command Line Interface to connectVM Cloud Horizon](How-To-Install-connectVM-and-Magnum-Clients-for-Command-Line-Interface-to-connectVM-Cloud-Horizon.html.md). -In that guide, you have installed the CLI and in this tutorial, you are going to use it to work with Kubernetes on 3Engines Magnum. +In that guide, you have installed the CLI and in this tutorial, you are going to use it to work with Kubernetes on connectVM Magnum. No. 7 **Autohealing of Kubernetes Clusters** -To learn more about autohealing of Kubernetes clusters, follow this official article [What is Magnum Autohealer?](https://github.com/kubernetes/cloud-provider-3Engines/blob/master/docs/magnum-auto-healer/using-magnum-auto-healer.md). +To learn more about autohealing of Kubernetes clusters, follow this official article [What is Magnum Autohealer?](https://github.com/kubernetes/cloud-provider-connectVM/blob/master/docs/magnum-auto-healer/using-magnum-auto-healer.md). The Advantages of Using the CLI[🔗](#the-advantages-of-using-the-cli "Permalink to this headline") ------------------------------------------------------------------------------------------------- @@ -56,7 +56,7 @@ You can use the CLI and Horizon interface interchangeably, but there are at leas Here is a command to list flavors in the system ``` -3Engines flavor list +connectVM flavor list ``` @@ -81,7 +81,7 @@ You can use available automation. The result of the following Ubuntu pipeline is There are two commands pipelined into one: ``` -KUBERNETES_URL=$(3Engines coe cluster show k8s-cluster +KUBERNETES_URL=$(connectVM coe cluster show k8s-cluster | awk '/ api_address /{print $4}') ``` @@ -89,7 +89,7 @@ KUBERNETES_URL=$(3Engines coe cluster show k8s-cluster The result of the first command ``` -3Engines coe cluster show k8s-cluster +connectVM coe cluster show k8s-cluster ``` @@ -106,37 +106,37 @@ awk '/ api_address /{print $4}') is searching for the line starting with *api\_address* and extracting its value *https://64.225.132.135:6443*. The final result is exported to the system variable KUBERNETES\_URL, thus automatically setting it up for use by Kubernetes cluster command **kubectl** when accessing the cloud. -### CLI Yields Access to All of the Existing 3Engines and Magnum Parameters[🔗](#cli-yields-access-to-all-of-the-existing-3Engines-and-magnum-parameters "Permalink to this headline") +### CLI Yields Access to All of the Existing connectVM and Magnum Parameters[🔗](#cli-yields-access-to-all-of-the-existing-connectVM-and-magnum-parameters "Permalink to this headline") CLI commands offer access to a larger set of parameters than is available through Horizon. For instance, in Horizon, the default length of time allowed for creation of a cluster is 60 minutes while in CLI, you can set it to other values of choice. -### Debugging 3Engines and Magnum Commands[🔗](#debugging-3Engines-and-magnum-commands "Permalink to this headline") +### Debugging connectVM and Magnum Commands[🔗](#debugging-connectVM-and-magnum-commands "Permalink to this headline") To see what is actually happening behind the scenes, when executing client commands, add parameter **–debug**: ``` -3Engines coe cluster list --debug +connectVM coe cluster list --debug ``` The output will be several screens long, consisting of GET and POST web calls, with dozens of parameters shown on screen. (The output is too voluminous to reproduce here.) -How to Enter 3Engines Commands[🔗](#how-to-enter-3Engines-commands "Permalink to this headline") +How to Enter connectVM Commands[🔗](#how-to-enter-connectVM-commands "Permalink to this headline") ------------------------------------------------------------------------------------------------- Note In the forthcoming example, a version **fedora-coreos-34.20210904.3.0** of fedora images is used. As the system is updated in time, the actual values may become different, for instance, any of values **fedora-coreos-35** or **fedora-coreos-33.20210426.3.0**. Use Horizon command Compute -> Images to see what images of fedora are currently available, then edit and replace as needed. -There are several ways to write down and enter 3Engines commands into the terminal command line interface. +There are several ways to write down and enter connectVM commands into the terminal command line interface. -One way is to enter command **3Engines** and press *Enter* on the keyboard. You enter the line mode of the **3Engines** command and can enter rows of various 3Engines parameters line after line. This is stricly for manual data entry and is difficult to automate. +One way is to enter command **connectVM** and press *Enter* on the keyboard. You enter the line mode of the **connectVM** command and can enter rows of various connectVM parameters line after line. This is stricly for manual data entry and is difficult to automate. -![ku_3Engines_line_entry.png](../_images/ku_3Engines_line_entry.png) +![ku_connectVM_line_entry.png](../_images/ku_connectVM_line_entry.png) Type **quit** and press *Enter* on keyboard to leave that mode. -The usual way of entering **3Engines** parameters is in one long line. Leave spaces between parameters but enter label values *without* any spaces inbetween. An example may be: +The usual way of entering **connectVM** parameters is in one long line. Leave spaces between parameters but enter label values *without* any spaces inbetween. An example may be: ![ku_long_line.png](../_images/ku_long_line.png) @@ -145,7 +145,7 @@ The line breaks and blanks have to be eradicated manually in this case. A more elegant way is to use backslash character, **\**, in line text. The character after backslash will not be taken into account so if you enter it at the very end of the line, the EOL character will be avoided and the first and the second line will be treated as one continuous line. That is exactly what you want, so here is what an entry line could look like with this approach: ``` -3Engines coe cluster template create kubecluster \ +connectVM coe cluster template create kubecluster \ --image "fedora-coreos-34.20210904.3.0" \ --external-network external \ --master-flavor eo1.large \ @@ -183,7 +183,7 @@ Warning If you are new to Kubernetes please, at first, create clusters only directly using the default cluster template. Once you get more experience, you can start creating your own cluster templates and here is how to do it using CLI. -3Engines Command for Creation of Cluster[🔗](#3Engines-command-for-creation-of-cluster "Permalink to this headline") +connectVM Command for Creation of Cluster[🔗](#connectVM-command-for-creation-of-cluster "Permalink to this headline") --------------------------------------------------------------------------------------------------------------------- In this step you can create a new cluster using either the default cluster template or any of the templates that you have already created. @@ -191,14 +191,14 @@ In this step you can create a new cluster using either the default cluster templ Enter ``` -3Engines coe cluster create -h +connectVM coe cluster create -h ``` to see the parameters. Provide all or almost all of the required parameters. ``` -usage: 3Engines coe cluster create +usage: connectVM coe cluster create [-h] --cluster-template [--discovery-url ] @@ -217,7 +217,7 @@ usage: 3Engines coe cluster create Here is what one such command might actually look like: ``` -3Engines coe cluster create +connectVM coe cluster create --cluster-template k8s-stable-1.23.5 --docker-volume-size 50 --labels eodata_access_enabled=false,floating-ip-enabled=true, @@ -242,7 +242,7 @@ Here are some special labels the functionality of which is only available throug Note -**Prerequisite No. 6** will show you how to enable command line interface with your cloud server. **Prerequisite No. 7** will give you a formal introduction to the notion of Kubernetes autohealing, as implemented in 3Engines Magnum. +**Prerequisite No. 6** will show you how to enable command line interface with your cloud server. **Prerequisite No. 7** will give you a formal introduction to the notion of Kubernetes autohealing, as implemented in connectVM Magnum. The only way to have auto healing turned on and guarantee at the same time that the cluster will be formed normally, is to set up the following label: @@ -257,11 +257,11 @@ Do not include the above label if you want to create a cluster that does not use Here is a variation of the CLI command to generate a cluster. It will use medium values instead of large for flavors, will have only one master and one worker node, will have auto healing turned on etc. -**3Engines coe cluster create –cluster-template k8s-stable-1.23.5 –labels floating-ip-enabled=true,master-lb-enabled=true,auto\_healing\_enabled=true –merge-labels –keypair sshkey –master-count 1 –node-count 1 –master-flavor eo1.medium –flavor eo1.medium newcluster** +**connectVM coe cluster create –cluster-template k8s-stable-1.23.5 –labels floating-ip-enabled=true,master-lb-enabled=true,auto\_healing\_enabled=true –merge-labels –keypair sshkey –master-count 1 –node-count 1 –master-flavor eo1.medium –flavor eo1.medium newcluster** **Execute the command for creation of a cluster** -Copy and paste the above command into the terminal where 3Engines and Magnum clients are active: +Copy and paste the above command into the terminal where connectVM and Magnum clients are active: ![cli_newcluster.png](../_images/cli_newcluster.png) @@ -271,7 +271,7 @@ How To Check Upon the Status of the Cluster[🔗](#how-to-check-upon-the-status- The command to show the status of clusters is ``` -3Engines coe cluster list +connectVM coe cluster list ``` @@ -288,7 +288,7 @@ Resource CREATE failed: OverQuotaClient: resources.secgroup_kube_master: Quota e The quota for the security group rules was exceeded. To verify, execute this command: ``` -3Engines quota show --default +connectVM quota show --default ``` @@ -325,7 +325,7 @@ CLI Commands to Delete a Cluster[🔗](#cli-commands-to-delete-a-cluster "Permal If the cluster failed to create, it is still taking up system resources. Delete it with command such as ``` -3Engines coe cluster delete +connectVM coe cluster delete ``` @@ -334,14 +334,14 @@ List the clusters and you will first see that the status is DELETE\_IN\_PROGRESS Now try to delete cluster *largecluster*. There are two of them, so putting up a command such as ``` -3Engines coe cluster delete largecluster +connectVM coe cluster delete largecluster ``` will not be accepted. Instead of the name, enter the *uuid* value: ``` -3Engines coe cluster delete e80c5815-d20b-4a2b-8588-49cf7a7e1aad +connectVM coe cluster delete e80c5815-d20b-4a2b-8588-49cf7a7e1aad ``` @@ -350,7 +350,7 @@ Again, the request will be accepted and then after a minute or two, the required Now there is only one *largecluster* so this will work: ``` -3Engines coe cluster delete largecluster +connectVM coe cluster delete largecluster ``` @@ -365,4 +365,4 @@ What To Do Next[🔗](#what-to-do-next "Permalink to this headline") In this tutorial, you have used the CLI commands to generate cluster templates as well as clusters themselves. Also, if the cluster process failed, how to free up the system resources and try again. -3Engines and Magnum did heavy lifting for you, letting you create full fledged Kubernetes clusters with only a handful of CLI commands. The next step is to start working with the Kubernetes clusters directly. That means installing the **kubectl** command with article [How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md) and using it to install the apps that you want to run on Kubernetes clusters. \ No newline at end of file +connectVM and Magnum did heavy lifting for you, letting you create full fledged Kubernetes clusters with only a handful of CLI commands. The next step is to start working with the Kubernetes clusters directly. That means installing the **kubectl** command with article [How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md) and using it to install the apps that you want to run on Kubernetes clusters. \ No newline at end of file diff --git a/docs/kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md b/docs/kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md similarity index 83% rename from docs/kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md rename to docs/kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md index 42c4708..795c4ac 100644 --- a/docs/kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md +++ b/docs/kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md @@ -1,4 +1,4 @@ -How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum[🔗](#how-to-create-a-kubernetes-cluster-using-brand-name-3Engines-magnum "Permalink to this headline") +How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum[🔗](#how-to-create-a-kubernetes-cluster-using-brand-name-connectVM-magnum "Permalink to this headline") ================================================================================================================================================================================= In this tutorial, you will start with an empty Horizon screen and end up running a full Kubernetes cluster. @@ -14,17 +14,17 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . -The resources that you require and use will reflect on the state of your account wallet. Check your account statistics at and if you are not going to use the cluster any more, remove them altogether to save resources costs. +The resources that you require and use will reflect on the state of your account wallet. Check your account statistics at and if you are not going to use the cluster any more, remove them altogether to save resources costs. -Magnum clusters created by certain users are bound together with an impersonation token and in the event of removing that user from the project, the cluster will lose authentication to 3Engines API making cluster non-operational. A typical scenario would be for the tenant manager to create user accounts and let them create Kubernetes clusters. Later on, in this scenario, when the cluster is operational, the user would be removed from the project. The cluster would be present but the user could not, say, create new clusters, or persistent volume claims would be dysfunctional and so on. +Magnum clusters created by certain users are bound together with an impersonation token and in the event of removing that user from the project, the cluster will lose authentication to connectVM API making cluster non-operational. A typical scenario would be for the tenant manager to create user accounts and let them create Kubernetes clusters. Later on, in this scenario, when the cluster is operational, the user would be removed from the project. The cluster would be present but the user could not, say, create new clusters, or persistent volume claims would be dysfunctional and so on. Therefore, good practice in creation of new Kubernetes clusters is to create a service account dedicated to creating a Magnum cluster. In essence, devote one account to one Kubernetes cluster, nothing more and nothing less. No. 2 **Private and public keys** -An SSH key-pair created in 3Engines dashboard. To create it, follow this article [How to create key pair in 3Engines Dashboard on 3Engines Cloud](../cloud/How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md). +An SSH key-pair created in connectVM dashboard. To create it, follow this article [How to create key pair in connectVM Dashboard on connectVM Cloud](../cloud/How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md). The key pair created in that article is called “sshkey”. You will use it as one of the parameters for creation of the Kubernetes cluster. @@ -59,7 +59,7 @@ You immediately see how the cluster template is applied: **Availability Zone** -**nova** is the name of the related module in 3Engines and is the only option offered here. +**nova** is the name of the related module in connectVM and is the only option offered here. **Keypair** @@ -69,11 +69,11 @@ Assuming you have used **Prerequisite No. 2**, choose *sshkey*. **Addon Software - Enable Access to EO Data** -This field is specific to 3Engines systems that are developed by [3Engines hosting company](https://3Engines.com/en/). *EODATA* here means **Earth Observation Data** and refers to data gained from scientific satelites monitoring the Earth. +This field is specific to connectVM systems that are developed by [connectVM hosting company](https://connectVM.com/en/). *EODATA* here means **Earth Observation Data** and refers to data gained from scientific satelites monitoring the Earth. Checking this field on, will install a network which will have access to the downloaded satelite data. -If you are just trying to learn about Kubernetes on 3Engines, leave this option unchecked. And vice versa: if you want to go into production and use satellite data, turn it on. +If you are just trying to learn about Kubernetes on connectVM, leave this option unchecked. And vice versa: if you want to go into production and use satellite data, turn it on. Note @@ -153,7 +153,7 @@ However, turning the checkbox off discloses an option to use an existing network **Use an Existing Network** -Using an existing network is a more advanced option. You would need to first create a network dedicated to this cluster in 3Engines along with the necessary adjustments. Creation of such a custom network is beyond the scope of this article. Note you should not use the network of another cluster, project network or EODATA network. +Using an existing network is a more advanced option. You would need to first create a network dedicated to this cluster in connectVM along with the necessary adjustments. Creation of such a custom network is beyond the scope of this article. Note you should not use the network of another cluster, project network or EODATA network. If you have an existing network and you would like to proceed, you will need to choose the network and the subnet from the dropdown below: @@ -197,7 +197,7 @@ If you **turn on** the field **I do want to override Template and Workflow Label Step 5 Forming of the Cluster[🔗](#step-5-forming-of-the-cluster "Permalink to this headline") --------------------------------------------------------------------------------------------- -Once you click on **Submit** button, 3Engines will start creating the Kubernetes cluster for you. It will show a cloud message with green background in the upper right corner of the windows, stating that the creation of the cluster has been started. +Once you click on **Submit** button, connectVM will start creating the Kubernetes cluster for you. It will show a cloud message with green background in the upper right corner of the windows, stating that the creation of the cluster has been started. Cluster generation usually takes from 10 to 15 minutes. It will be automatically abandoned if duration time is longer than 60 minutes. @@ -216,7 +216,7 @@ Click on the name of the cluster, *Kubernetes*, and see what it will look like i Step 6 Review cluster state[🔗](#step-6-review-cluster-state "Permalink to this headline") ----------------------------------------------------------------------------------------- -Here is what 3Engines Magnum created for you as the result of filling in the data in those three screens: +Here is what connectVM Magnum created for you as the result of filling in the data in those three screens: > * A new network called *Kubernetes*, complete with subnet, ready to connect further. > * New instances – virtual machines that serve as nodes. @@ -250,8 +250,8 @@ and so on. Here are some relevant articles: -Read more about ingress here: [Using Kubernetes Ingress on 3Engines Cloud 3Engines Magnum](Using-Kubernetes-Ingress-on-3Engines-Cloud-3Engines-Magnum.html.md) +Read more about ingress here: [Using Kubernetes Ingress on connectVM Cloud connectVM Magnum](Using-Kubernetes-Ingress-on-connectVM-Cloud-connectVM-Magnum.html.md) -Article [How To Use Command Line Interface for Kubernetes Clusters On 3Engines Cloud 3Engines Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-3Engines-Cloud-3Engines-Magnum.html.md) shows how to use command line interface to create Kubernetes clusters. +Article [How To Use Command Line Interface for Kubernetes Clusters On connectVM Cloud connectVM Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-connectVM-Cloud-connectVM-Magnum.html.md) shows how to use command line interface to create Kubernetes clusters. -To access your newly created cluster from command line, see article [How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md). \ No newline at end of file +To access your newly created cluster from command line, see article [How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md). \ No newline at end of file diff --git a/docs/kubernetes/How-to-create-Kubernetes-cluster-using-Terraform-on-3Engines-Cloud.html.md b/docs/kubernetes/How-to-create-Kubernetes-cluster-using-Terraform-on-connectVM-Cloud.html.md similarity index 65% rename from docs/kubernetes/How-to-create-Kubernetes-cluster-using-Terraform-on-3Engines-Cloud.html.md rename to docs/kubernetes/How-to-create-Kubernetes-cluster-using-Terraform-on-connectVM-Cloud.html.md index 5970543..4410320 100644 --- a/docs/kubernetes/How-to-create-Kubernetes-cluster-using-Terraform-on-3Engines-Cloud.html.md +++ b/docs/kubernetes/How-to-create-Kubernetes-cluster-using-Terraform-on-connectVM-Cloud.html.md @@ -1,56 +1,56 @@ -How to create Kubernetes cluster using Terraform on 3Engines Cloud[🔗](#how-to-create-kubernetes-cluster-using-terraform-on-brand-name "Permalink to this headline") +How to create Kubernetes cluster using Terraform on connectVM Cloud[🔗](#how-to-create-kubernetes-cluster-using-terraform-on-brand-name "Permalink to this headline") ===================================================================================================================================================================== -In this article we demonstrate using [Terraform](https://www.terraform.io/) to deploy an 3Engines Magnum Kubernetes cluster on 3Engines Cloud cloud. +In this article we demonstrate using [Terraform](https://www.terraform.io/) to deploy an connectVM Magnum Kubernetes cluster on connectVM Cloud cloud. Prerequisites[🔗](#prerequisites "Permalink to this headline") ------------------------------------------------------------- No. 1 **Hosting account** -You need an active 3Engines Cloud account . +You need an active connectVM Cloud account . -No. 2 **Active CLI session with 3EnginesClient for Linux** +No. 2 **Active CLI session with connectVMClient for Linux** -You need an 3Engines CLI installed and the respective Python virtual environment sourced. For guidelines see: +You need an connectVM CLI installed and the respective Python virtual environment sourced. For guidelines see: -[How to install 3EnginesClient for Linux on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md) +[How to install connectVMClient for Linux on connectVM Cloud](../connectVMcli/How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md) -It will show you how to install Python, create and activate a virtual environment, and then connect to the cloud by downloading and activating the proper RC file from the 3Engines Cloud cloud. +It will show you how to install Python, create and activate a virtual environment, and then connect to the cloud by downloading and activating the proper RC file from the connectVM Cloud cloud. No. 3 **Connect to the cloud via an RC file** -Another article, [How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md), deals with connecting to the cloud and is covering either of the one- or two-factor authentication procedures that are enabled on your account. It also covers all the main platforms: Linux, MacOS and Windows. +Another article, [How to activate connectVM CLI access to connectVM Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-connectVM-CLI-access-to-connectVM-Cloud-cloud-using-one-or-two-factor-authentication.html.md), deals with connecting to the cloud and is covering either of the one- or two-factor authentication procedures that are enabled on your account. It also covers all the main platforms: Linux, MacOS and Windows. You will use both the Python virtual environment and the downloaded RC file **after** Terraform has been installed. No. 4 **Familiarity with creating Kubernetes clusters** -Familiarity with creating Kubernetes clusters in a standard way e.g. using Horizon or 3Engines CLI: +Familiarity with creating Kubernetes clusters in a standard way e.g. using Horizon or connectVM CLI: -[How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md) +[How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md) -[How To Use Command Line Interface for Kubernetes Clusters On 3Engines Cloud 3Engines Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-3Engines-Cloud-3Engines-Magnum.html.md) +[How To Use Command Line Interface for Kubernetes Clusters On connectVM Cloud connectVM Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-connectVM-Cloud-connectVM-Magnum.html.md) No. 5 **Terraform operational** Have Terraform installed locally or on a cloud VM - installation guidelines along with further information can be found in this article: -[Generating and authorizing Terraform using Keycloak user on 3Engines Cloud](../3Enginesdev/Generating-and-authorizing-Terraform-using-Keycloak-user-on-3Engines-Cloud.html.md) +[Generating and authorizing Terraform using Keycloak user on connectVM Cloud](../connectVMdev/Generating-and-authorizing-Terraform-using-Keycloak-user-on-connectVM-Cloud.html.md) -After you finish working through that article, you will have access to the cloud via an active **3Engines** command. Also, special environmental (**env**) variables (**OS\_USERNAME**, **OS\_PASSWORD**, **OS\_AUTH\_URL** and others) will be set up so that various programs can use them – Terraform being the prime target here. +After you finish working through that article, you will have access to the cloud via an active **connectVM** command. Also, special environmental (**env**) variables (**OS\_USERNAME**, **OS\_PASSWORD**, **OS\_AUTH\_URL** and others) will be set up so that various programs can use them – Terraform being the prime target here. Define provider for Terraform[🔗](#define-provider-for-terraform "Permalink to this headline") --------------------------------------------------------------------------------------------- -Terraform uses the notion of *provider*, which represents your concrete cloud environment and covers authentication. 3Engines Cloud clouds are built complying with 3Engines technology and 3Engines is one of the standard types of providers for Terraform. +Terraform uses the notion of *provider*, which represents your concrete cloud environment and covers authentication. connectVM Cloud clouds are built complying with connectVM technology and connectVM is one of the standard types of providers for Terraform. We need to: -> * instruct Terraform to use 3Engines as a provider type +> * instruct Terraform to use connectVM as a provider type > * provide credentials which will to point to our own project and user in the cloud. -Assuming you have worked through Prerequisite No. 2 (download and source the RC file), several 3Engines-related environment variables will be populated in your local system. The ones pointing to your 3Engines environment start with OS, e.g. **OS\_USERNAME**, **OS\_PASSWORD**, **OS\_AUTH\_URL**. When we define 3Engines as TerraForm provider type, Terraform will know to automatically use these **env** variables to authenticate. +Assuming you have worked through Prerequisite No. 2 (download and source the RC file), several connectVM-related environment variables will be populated in your local system. The ones pointing to your connectVM environment start with OS, e.g. **OS\_USERNAME**, **OS\_PASSWORD**, **OS\_AUTH\_URL**. When we define connectVM as TerraForm provider type, Terraform will know to automatically use these **env** variables to authenticate. Let’s define the Terraform provider now by creating file **provider.tf** with the following contents: @@ -61,16 +61,16 @@ Let’s define the Terraform provider now by creating file **provider.tf** with terraform { required_version = ">= 0.14.0" required_providers { - 3Engines = { - source = "terraform-provider-3Engines/3Engines" + connectVM = { + source = "terraform-provider-connectVM/connectVM" version = "~> 1.35.0" } } } -# Configure the 3Engines Provider -provider "3Engines" { - auth_url = "https://keystone.3Engines.com:5000/v3" +# Configure the connectVM Provider +provider "connectVM" { + auth_url = "https://keystone.connectVM.com:5000/v3" # the rest of configuration parameters are taken from environment variables once RC file is correctly sourced } @@ -78,18 +78,18 @@ provider "3Engines" { The **auth\_url** is the only configuration option that shall be provided in the configuration file, despite it also being available within the environment variables. -Having this provider spec allows us to create a cluster in the following steps, but can also be reused to create other resources in your 3Engines environment e.g. virtual machines, volumes and many others. +Having this provider spec allows us to create a cluster in the following steps, but can also be reused to create other resources in your connectVM environment e.g. virtual machines, volumes and many others. Define cluster resource in Terraform[🔗](#define-cluster-resource-in-terraform "Permalink to this headline") ----------------------------------------------------------------------------------------------------------- -The second step is to define the exact specification of a resource that we want to create with Terraform. In our case we want to create a 3Engines Magnum cluster. In Terraform terminology, it will be an instance of **3Engines\_containerinfra\_cluster\_v1** resource type. To proceed, create file **cluster.tf** which contains the specification of our cluster: +The second step is to define the exact specification of a resource that we want to create with Terraform. In our case we want to create a connectVM Magnum cluster. In Terraform terminology, it will be an instance of **connectVM\_containerinfra\_cluster\_v1** resource type. To proceed, create file **cluster.tf** which contains the specification of our cluster: **cluster.tf** ``` # Create resource -resource "3Engines_containerinfra_cluster_v1" "k8s-cluster" { +resource "connectVM_containerinfra_cluster_v1" "k8s-cluster" { name = "k8s-cluster" cluster_template_id = "524535ed-9a0f-4b70-966f-6830cdc52604" node_count = 3 @@ -115,7 +115,7 @@ node\_count, node\_flavor, master\_node\_count, master\_node\_flavor : correspond intuitively to **count** and **flavor** of master and worker nodes in the cluster. keypair -: reflects the name of keypair used in our 3Engines project in the chosen cloud +: reflects the name of keypair used in our connectVM project in the chosen cloud labels and merge\_labels : We use two labels: @@ -144,7 +144,7 @@ terraform init ``` -This command will initialize our cluster deployment. It will capture any formal errors with authentication to 3Engines, which might need correcting before moving to the next stage. +This command will initialize our cluster deployment. It will capture any formal errors with authentication to connectVM, which might need correcting before moving to the next stage. ![image-2024-6-17_15-52-40.png](../_images/image-2024-6-17_15-52-40.png) diff --git a/docs/kubernetes/How-to-install-Rancher-RKE2-Kubernetes-on-3Engines-Cloud-cloud.html.md b/docs/kubernetes/How-to-install-Rancher-RKE2-Kubernetes-on-connectVM-Cloud-cloud.html.md similarity index 76% rename from docs/kubernetes/How-to-install-Rancher-RKE2-Kubernetes-on-3Engines-Cloud-cloud.html.md rename to docs/kubernetes/How-to-install-Rancher-RKE2-Kubernetes-on-connectVM-Cloud-cloud.html.md index 211be11..ceca206 100644 --- a/docs/kubernetes/How-to-install-Rancher-RKE2-Kubernetes-on-3Engines-Cloud-cloud.html.md +++ b/docs/kubernetes/How-to-install-Rancher-RKE2-Kubernetes-on-connectVM-Cloud-cloud.html.md @@ -1,13 +1,13 @@ -How to install Rancher RKE2 Kubernetes on 3Engines Cloud[🔗](#how-to-install-rancher-rke2-kubernetes-on-brand-name "Permalink to this headline") +How to install Rancher RKE2 Kubernetes on connectVM Cloud[🔗](#how-to-install-rancher-rke2-kubernetes-on-brand-name "Permalink to this headline") ================================================================================================================================================= -[RKE2](https://docs.rke2.io/) - Rancher Kubernetes Engine version 2 - is a Kubernetes distribution provided by SUSE. Running a self-managed RKE2 cluster in 3Engines Cloud cloud is a viable option, especially for those seeking smooth integration with Rancher platform and customization options. +[RKE2](https://docs.rke2.io/) - Rancher Kubernetes Engine version 2 - is a Kubernetes distribution provided by SUSE. Running a self-managed RKE2 cluster in connectVM Cloud cloud is a viable option, especially for those seeking smooth integration with Rancher platform and customization options. -An RKE2 cluster can be provisioned from Rancher GUI. However, in this article we use Terraform, which enables streamlined, automated cluster creation. We also use 3Engines Cloud Controller Manager (CCM) to integrate RKE2 cluster with the wider 3Engines environment. Using the customized version of CCM enables us to take advantage of 3Engines Cloud cloud-native features. The end result is +An RKE2 cluster can be provisioned from Rancher GUI. However, in this article we use Terraform, which enables streamlined, automated cluster creation. We also use connectVM Cloud Controller Manager (CCM) to integrate RKE2 cluster with the wider connectVM environment. Using the customized version of CCM enables us to take advantage of connectVM Cloud cloud-native features. The end result is > * a provisioned RKE2 cluster -> * running under 3Engines, with -> * an integrated 3Engines Cloud Controller Manager. +> * running under connectVM, with +> * an integrated connectVM Cloud Controller Manager. We also illustrate the coding techniques used, in case you want to enhance the RKE2 implementation further. @@ -21,7 +21,7 @@ What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this > > * Have keypair operational > > * Authenticate to the newly formed project > -> * Use Terraform configuration for RKE2 from 3Engines’s GitHub repository +> * Use Terraform configuration for RKE2 from connectVM’s GitHub repository > * Provision an RKE2 cluster > * Demonstrate the incorporated cloud-native load-balancing > * Implementation details @@ -34,61 +34,61 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Terraform available on your local command line** -See [Generating and authorizing Terraform using Keycloak user on 3Engines Cloud](../3Enginesdev/Generating-and-authorizing-Terraform-using-Keycloak-user-on-3Engines-Cloud.html.md) +See [Generating and authorizing Terraform using Keycloak user on connectVM Cloud](../connectVMdev/Generating-and-authorizing-Terraform-using-Keycloak-user-on-connectVM-Cloud.html.md) No. 3 **Python virtual environment sourced** -[How to install Python virtualenv or virtualenvwrapper on 3Engines Cloud](../cloud/How-to-install-Python-virtualenv-or-virtualenvwrapper-on-3Engines-Cloud.html.md) +[How to install Python virtualenv or virtualenvwrapper on connectVM Cloud](../cloud/How-to-install-Python-virtualenv-or-virtualenvwrapper-on-connectVM-Cloud.html.md) -No. 4 **3Engines CLI installed locally** +No. 4 **connectVM CLI installed locally** -When installed, you will have access to **3Engines** command and will be able to communicate with the 3Engines cloud: +When installed, you will have access to **connectVM** command and will be able to communicate with the connectVM cloud: -[How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md) +[How to activate connectVM CLI access to connectVM Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-connectVM-CLI-access-to-connectVM-Cloud-cloud-using-one-or-two-factor-authentication.html.md) No. 5 **kubectl tool installed locally** Standard types of **kubectl** installation are described on [Install Tools page](https://kubernetes.io/docs/tasks/tools/) of the official Kubernetes site. -No. 6 **Available key pair in 3Engines** +No. 6 **Available key pair in connectVM** -[How to create key pair in 3Engines Dashboard on 3Engines Cloud](../cloud/How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md). +[How to create key pair in connectVM Dashboard on connectVM Cloud](../cloud/How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md). No. 7 **Application credentials** The following article describes how to create and use application credentials, using CLI: -[How to generate or use Application Credentials via CLI on 3Engines Cloud](../cloud/How-to-generate-or-use-Application-Credentials-via-CLI-on-3Engines-Cloud.html.md) +[How to generate or use Application Credentials via CLI on connectVM Cloud](../cloud/How-to-generate-or-use-Application-Credentials-via-CLI-on-connectVM-Cloud.html.md) In this article, we shall create application credentials through Horizon but with a specific selection of user roles. No. 8 **Projects, roles, users and groups** -Option **Identity** lists available projects, roles, users and groups. See [What is an 3Engines project on 3Engines Cloud](../cloud/What-is-an-3Engines-project-on-3Engines-Cloud.html.md) +Option **Identity** lists available projects, roles, users and groups. See [What is an connectVM project on connectVM Cloud](../cloud/What-is-an-connectVM-project-on-connectVM-Cloud.html.md) No. 9 **Experience with Kubernetes and Helm** -To follow up on this article, you should know your way around Kubernetes in general. Having the actual experience of using it on 3Engines Cloud cloud, would be even better. For a series of article on Kubernetes, see [KUBERNETES](kubernetes.html.md). +To follow up on this article, you should know your way around Kubernetes in general. Having the actual experience of using it on connectVM Cloud cloud, would be even better. For a series of article on Kubernetes, see [KUBERNETES](kubernetes.html.md). -To perform the installation required in this article, one of the steps will be to create Helm CRD and use it. This article shows the basics of using Helm [Deploying Helm Charts on Magnum Kubernetes Clusters on 3Engines Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md). +To perform the installation required in this article, one of the steps will be to create Helm CRD and use it. This article shows the basics of using Helm [Deploying Helm Charts on Magnum Kubernetes Clusters on connectVM Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md). No. 10 **Cloud Controller Manager** Within a general Kubernetes environment, [the Cloud Controller Manager (CCM)](https://kubernetes.io/docs/concepts/architecture/cloud-controller/) allows Kubernetes to integrate with cloud provider APIs. It abstracts cloud-specific logic and manages and synchronizes resources between Kubernetes and the underlying cloud infrastructure. Also, it provides controllers for Nodes, Routes, Services and Volumes. -Under 3Engines, CCM integrates with 3Engines APIs. The code used here is from a concrete repository for Cloud Controller Manager – It implements the above mentioned (as well as) other 3Engines-Kubernetes integrations. +Under connectVM, CCM integrates with connectVM APIs. The code used here is from a concrete repository for Cloud Controller Manager – It implements the above mentioned (as well as) other connectVM-Kubernetes integrations. No. 11 **rke2-terraform repository** You will need to download the following repository -> +> -in order to install install Terraform manifests for provisioning of RKE2 on 3Engines Cloud using Terraform. +in order to install install Terraform manifests for provisioning of RKE2 on connectVM Cloud using Terraform. No. 12 **Customize the cloud configuration for Terraform** @@ -99,11 +99,11 @@ One of the files downloaded from the above link will be **variables.tf**. It con Step 1 Perform the preliminary setup[🔗](#step-1-perform-the-preliminary-setup "Permalink to this headline") ----------------------------------------------------------------------------------------------------------- -Our objective is to create a Kubernetes cluster, which runs in the cloud environment. RKE2 software packages will be installed on cloud virtual machines playing roles of Kubernetes master and worker nodes. Also, several other 3Engines resources will be created along. +Our objective is to create a Kubernetes cluster, which runs in the cloud environment. RKE2 software packages will be installed on cloud virtual machines playing roles of Kubernetes master and worker nodes. Also, several other connectVM resources will be created along. As part of the preliminary setup to provision these resources we will: -> * Create a dedicated 3Engines project to isolate all resources dedicated to the cluster +> * Create a dedicated connectVM project to isolate all resources dedicated to the cluster > * Create application credentials > * Ensure a key pair is enabled for the project > * Source locally the RC file for this project @@ -126,7 +126,7 @@ Then click on “Create Project”. Once the project is created, switch to the c ### Preparation step 2 Create application credentials[🔗](#preparation-step-2-create-application-credentials "Permalink to this headline") -The next step is to create an application credential that will be used to authenticate the 3Engines Cloud Controller Manager (used for automated load balancer provisioning). To create one, go to menu **Identity** → **Application Credentials**. Fill in the form as per the below example, passing all available roles (“member”, “load-balancer\_member”, “creator”, “reader”) roles to this credential. Set the expiry date to a date in the future. +The next step is to create an application credential that will be used to authenticate the connectVM Cloud Controller Manager (used for automated load balancer provisioning). To create one, go to menu **Identity** → **Application Credentials**. Fill in the form as per the below example, passing all available roles (“member”, “load-balancer\_member”, “creator”, “reader”) roles to this credential. Set the expiry date to a date in the future. ![image-2024-7-29_10-2-57.png](../_images/image-2024-7-29_10-2-57.png) @@ -144,10 +144,10 @@ Before continuing, ensure you have a keypair available. If you already had a key Lastly, download the RC file corresponding to the new project from Horizon GUI, then source this file in your local Linux terminal. See Prerequisite No. 4. -Step 2 Use Terraform configuration for RKE2 from 3Engines’s GitHub repository[🔗](#step-2-use-terraform-configuration-for-rke2-from-3Engines-s-github-repository "Permalink to this headline") +Step 2 Use Terraform configuration for RKE2 from connectVM’s GitHub repository[🔗](#step-2-use-terraform-configuration-for-rke2-from-connectVM-s-github-repository "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -We added folder **rke2-terraform** to 3Engines’s [K8s-samples GitHub repository](https://github.com/3Engines/K8s-samples/tree/main/rke2-terraform), from Prerequisite No. 11. This project includes configuration files to provision an RKE2 cluster on 3Engines clouds and can be used as a starter pack for further customizations to your specific requirements. +We added folder **rke2-terraform** to connectVM’s [K8s-samples GitHub repository](https://github.com/connectVM/K8s-samples/tree/main/rke2-terraform), from Prerequisite No. 11. This project includes configuration files to provision an RKE2 cluster on connectVM clouds and can be used as a starter pack for further customizations to your specific requirements. ![image-2024-7-26_12-36-54.png](../_images/image-2024-7-26_12-36-54.png) @@ -157,13 +157,13 @@ variables.tf : Contains key variables that specify configuration of our cluster e.g. **number of worker nodes**, **cloud region** where the cluster will be placed, **name of the cluster**. Most of these variables have their default values set and you can modify these defaults directly in the file. The variables with no defaults (secret, sensitive data) should have their values provided separately, via the use of **tfvars** file, which is explained in the next section. providers.tf -: Used for declaring and configuring Terraform providers. In our case, we only use 3Engines provider, which is provisioning cloud resources that form the cluster. +: Used for declaring and configuring Terraform providers. In our case, we only use connectVM provider, which is provisioning cloud resources that form the cluster. main.tf -: Contains declaration of resources to be created by Terraform. Several 3Engines resources are required to form a cluster e.g. a Network, Subnet, Router, Virtual Machines and others. Review the file for details and customize to your preference. +: Contains declaration of resources to be created by Terraform. Several connectVM resources are required to form a cluster e.g. a Network, Subnet, Router, Virtual Machines and others. Review the file for details and customize to your preference. security-groups.tf -: Contains declaration of security groups and security group rules used in 3Engines to open specific ports on virtual machines forming the cluster. Thus, the communication from selected sources gets enabled on each VM. Modify the file to customize. +: Contains declaration of security groups and security group rules used in connectVM to open specific ports on virtual machines forming the cluster. Thus, the communication from selected sources gets enabled on each VM. Modify the file to customize. cloud-init-masters.yml.tpl : and @@ -192,7 +192,7 @@ Let’s provision an RKE2 Kubernetes cluster now. This will consist of the follo The first step is to clone the github repository. We clone the entire repo but just leave the **rke2-terraform** folder with the below commands: ``` -git clone https://github.com/3Engines/K8s-samples +git clone https://github.com/connectVM/K8s-samples mkdir ~/rke2-terraform mv ~/K8s-samples/rke2-terraform/* ~/rke2-terraform rm K8s-samples/ -rf @@ -311,18 +311,18 @@ Explaining all of the techniques that went into production of RKE2 repository fr Let us examine the **cloud-init-masters.yml.tpl** file, concretely, the part between line numbers 53 and 79: ``` -- path: /var/lib/rancher/rke2/server/manifests/rke2-3Engines-cloud-controller-manager.yaml +- path: /var/lib/rancher/rke2/server/manifests/rke2-connectVM-cloud-controller-manager.yaml permissions: "0600" owner: root:root content: | apiVersion: helm.cattle.io/v1 kind: HelmChart metadata: - name: 3Engines-cloud-controller-manager + name: connectVM-cloud-controller-manager namespace: kube-system spec: - chart: 3Engines-cloud-controller-manager - repo: https://kubernetes.github.io/cloud-provider-3Engines + chart: connectVM-cloud-controller-manager + repo: https://kubernetes.github.io/cloud-provider-connectVM targetNamespace: kube-system bootstrap: True valuesContent: |- @@ -330,7 +330,7 @@ Let us examine the **cloud-init-masters.yml.tpl** file, concretely, the part bet node-role.kubernetes.io/control-plane: "true" cloudConfig: global: - auth-url: https://keystone.3Engines.com:5000 + auth-url: https://keystone.connectVM.com:5000 application-credential-id: "${application_credential_id}" application-credential-secret: "${application_credential_secret}" region: ${region} @@ -343,7 +343,7 @@ Let us examine the **cloud-init-masters.yml.tpl** file, concretely, the part bet It covers creating a yaml definition of a HelmChart CRD -*rke2-3Engines-cloud-controller-manager.yaml* +*rke2-connectVM-cloud-controller-manager.yaml* in location @@ -361,7 +361,7 @@ One of the entries is the aforementioned pod: ``` NAME READY STATUS RESTARTS AGE ... -3Engines-cloud-controller-manager-bz7zt 1/1 Running 1 (4h ago) 26h +connectVM-cloud-controller-manager-bz7zt 1/1 Running 1 (4h ago) 26h ... ``` @@ -384,6 +384,6 @@ What To Do Next[🔗](#what-to-do-next "Permalink to this headline") In this article, you have created a proper Kubernetes solution using RKE2 cluster as a foundation. -You can also consider creating Kubernetes clusters using Magnum within 3Engines: +You can also consider creating Kubernetes clusters using Magnum within connectVM: -[How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md) \ No newline at end of file +[How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md) \ No newline at end of file diff --git a/docs/kubernetes/Implementing-IP-Whitelisting-for-Load-Balancers-with-Security-Groups-on-3Engines-Cloud.html.md b/docs/kubernetes/Implementing-IP-Whitelisting-for-Load-Balancers-with-Security-Groups-on-connectVM-Cloud.html.md similarity index 78% rename from docs/kubernetes/Implementing-IP-Whitelisting-for-Load-Balancers-with-Security-Groups-on-3Engines-Cloud.html.md rename to docs/kubernetes/Implementing-IP-Whitelisting-for-Load-Balancers-with-Security-Groups-on-connectVM-Cloud.html.md index a97f6c2..2d0483e 100644 --- a/docs/kubernetes/Implementing-IP-Whitelisting-for-Load-Balancers-with-Security-Groups-on-3Engines-Cloud.html.md +++ b/docs/kubernetes/Implementing-IP-Whitelisting-for-Load-Balancers-with-Security-Groups-on-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -Implementing IP Whitelisting for Load Balancers with Security Groups on 3Engines Cloud[🔗](#implementing-ip-whitelisting-for-load-balancers-with-security-groups-on-brand-name "Permalink to this headline") +Implementing IP Whitelisting for Load Balancers with Security Groups on connectVM Cloud[🔗](#implementing-ip-whitelisting-for-load-balancers-with-security-groups-on-brand-name "Permalink to this headline") ============================================================================================================================================================================================================= -In this article we describe how to use commands in Horizon, CLI and Terraform to secure load balancers for Kubernetes clusters in 3Engines by implementing IP whitelisting. +In this article we describe how to use commands in Horizon, CLI and Terraform to secure load balancers for Kubernetes clusters in connectVM by implementing IP whitelisting. What Are We Going To Do[🔗](#what-are-we-going-to-do "Permalink to this headline") --------------------------------------------------------------------------------- @@ -16,7 +16,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **List of IP addresses/ranges to whitelist** @@ -24,19 +24,19 @@ This is the list of IP addresses that you want the load balancer to be able to l No. 3 **A preconfigured load balancer** -In 3Engines, each time you create a Kubernetes cluster, the corresponding load balancers are created automatically. +In connectVM, each time you create a Kubernetes cluster, the corresponding load balancers are created automatically. -See article [How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md) +See article [How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md) -No. 4 **3Engines command operational** +No. 4 **connectVM command operational** This is a necessary for CLI procedures. -This boils down to sourcing the proper RC file from Horizon. See [How To Use Command Line Interface for Kubernetes Clusters On 3Engines Cloud 3Engines Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-3Engines-Cloud-3Engines-Magnum.html.md) +This boils down to sourcing the proper RC file from Horizon. See [How To Use Command Line Interface for Kubernetes Clusters On connectVM Cloud connectVM Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-connectVM-Cloud-connectVM-Magnum.html.md) No. 5 **Python Octavia Client** -To operate Load Balancers with CLI, the Python Octavia Client (python-octaviaclient) is required. It is a command-line client for the 3Engines Load Balancing service. Install the load-balancer (Octavia) plugin with the following command from the Terminal window, on Ubuntu 22.04: +To operate Load Balancers with CLI, the Python Octavia Client (python-octaviaclient) is required. It is a command-line client for the connectVM Load Balancing service. Install the load-balancer (Octavia) plugin with the following command from the Terminal window, on Ubuntu 22.04: ``` pip install python-octaviaclient @@ -57,9 +57,9 @@ No. 6 **Terraform installed** You will need Terraform version 1.50 or higher to be operational. -For complete introduction and installation of Terrafom on 3Engines see article [Generating and authorizing Terraform using Keycloak user on 3Engines Cloud](../3Enginesdev/Generating-and-authorizing-Terraform-using-Keycloak-user-on-3Engines-Cloud.html.md) +For complete introduction and installation of Terrafom on connectVM see article [Generating and authorizing Terraform using Keycloak user on connectVM Cloud](../connectVMdev/Generating-and-authorizing-Terraform-using-Keycloak-user-on-connectVM-Cloud.html.md) -To use Terraform in this capacity, you will need to authenticate to the cloud using application credentials with **unrestricted** access. Check article [How to generate or use Application Credentials via CLI on 3Engines Cloud](../cloud/How-to-generate-or-use-Application-Credentials-via-CLI-on-3Engines-Cloud.html.md) +To use Terraform in this capacity, you will need to authenticate to the cloud using application credentials with **unrestricted** access. Check article [How to generate or use Application Credentials via CLI on connectVM Cloud](../cloud/How-to-generate-or-use-Application-Credentials-via-CLI-on-connectVM-Cloud.html.md) Horizon: Whitelisting Load Balancers[🔗](#horizon-whitelisting-load-balancers "Permalink to this headline") ---------------------------------------------------------------------------------------------------------- @@ -105,28 +105,28 @@ To confirm the configuration: CLI: Whitelisting Load Balancers[🔗](#cli-whitelisting-load-balancers "Permalink to this headline") -------------------------------------------------------------------------------------------------- -The 3Engines CLI provides a command-line method for implementing IP whitelisting. +The connectVM CLI provides a command-line method for implementing IP whitelisting. -Be sure to work through Prerequisites Nos 4 and 5 in order to have **3Engines** command fully operational. +Be sure to work through Prerequisites Nos 4 and 5 in order to have **connectVM** command fully operational. List the security groups associated with the load balancer: ``` -3Engines loadbalancer show +connectVM loadbalancer show ``` Identify the pool associated with the load balancer: ``` -3Engines loadbalancer pool list +connectVM loadbalancer pool list ``` Show details of the pool to list its members: ``` -3Engines loadbalancer pool show +connectVM loadbalancer pool show ``` @@ -135,14 +135,14 @@ Note the IP addresses of the pool members and identify the instances hosting the Create a security group for IP whitelisting: ``` -3Engines security group create +connectVM security group create ``` Add rules to the security group: ``` -3Engines security group rule create \ +connectVM security group rule create \ --ingress \ --ethertype IPv4 \ --protocol tcp \ @@ -155,7 +155,7 @@ Add rules to the security group: Apply the security group to the instances hosting the pool members: ``` -3Engines server add security group +connectVM server add security group ``` @@ -164,14 +164,14 @@ Apply the security group to the instances hosting the pool members: Verify the applied security group rules: ``` -3Engines security group show +connectVM security group show ``` Confirm the security group is attached to the appropriate instances: ``` -3Engines server show +connectVM server show ``` @@ -186,40 +186,40 @@ Create a security group and whitelist rule in **main.tf**: # main.tf # Security Group to Whitelist IPs -resource "3Engines_networking_secgroup_v2" "whitelist_secgroup" { +resource "connectVM_networking_secgroup_v2" "whitelist_secgroup" { name = "loadbalancer_whitelist" description = "Security group for load balancer IP whitelisting" } # Add Whitelist Rule for Specific IPs -resource "3Engines_networking_secgroup_rule_v2" "allow_whitelist" { +resource "connectVM_networking_secgroup_rule_v2" "allow_whitelist" { direction = "ingress" ethertype = "IPv4" protocol = "tcp" port_range_min = 80 # Replace with actual port range port_range_max = 80 remote_ip_prefix = "192.168.1.0/24" # Replace with actual CIDR - security_group_id = 3Engines_networking_secgroup_v2.whitelist_secgroup.id + security_group_id = connectVM_networking_secgroup_v2.whitelist_secgroup.id } # Existing Instances Associated with Pool Members -resource "3Engines_compute_instance_v2" "instances" { +resource "connectVM_compute_instance_v2" "instances" { count = 2 # Adjust to the number of pool member instances name = "pool_member_${count.index + 1}" flavor_id = "m1.small" # Replace with an appropriate flavor image_id = "image-id" # Replace with a valid image ID key_pair = "your-key-pair" - security_groups = [3Engines_networking_secgroup_v2.whitelist_secgroup.name] + security_groups = [connectVM_networking_secgroup_v2.whitelist_secgroup.name] network { uuid = "network-uuid" # Replace with the UUID of your network } } # Associate the Load Balancer with Security Group via Instances -resource "3Engines_lb_loadbalancer_v2" "loadbalancer" { +resource "connectVM_lb_loadbalancer_v2" "loadbalancer" { name = "my_loadbalancer" vip_subnet_id = "subnet-id" # Replace with the subnet ID - depends_on = [3Engines_compute_instance_v2.instances] + depends_on = [connectVM_compute_instance_v2.instances] } ``` @@ -238,8 +238,8 @@ Use Terraform to review the applied state: ``` terraform show -3Engines server show -3Engines security group show +connectVM server show +connectVM security group show ``` @@ -334,6 +334,6 @@ What To Do Next[🔗](#what-to-do-next "Permalink to this headline") Compare with articles: -[Configuring IP Whitelisting for 3Engines Load Balancer using Horizon and CLI on 3Engines Cloud](Configuring-IP-Whitelisting-for-3Engines-Load-Balancer-using-Horizon-and-CLI-on-3Engines-Cloud.html.md) +[Configuring IP Whitelisting for connectVM Load Balancer using Horizon and CLI on connectVM Cloud](Configuring-IP-Whitelisting-for-connectVM-Load-Balancer-using-Horizon-and-CLI-on-connectVM-Cloud.html.md) -[Configuring IP Whitelisting for 3Engines Load Balancer using Terraform on 3Engines Cloud](Configuring-IP-Whitelisting-for-3Engines-Load-Balancer-using-Terraform-on-3Engines-Cloud.html.md) \ No newline at end of file +[Configuring IP Whitelisting for connectVM Load Balancer using Terraform on connectVM Cloud](Configuring-IP-Whitelisting-for-connectVM-Load-Balancer-using-Terraform-on-connectVM-Cloud.html.md) \ No newline at end of file diff --git a/docs/kubernetes/Install-GitLab-on-3Engines-Cloud-Kubernetes.html.md b/docs/kubernetes/Install-GitLab-on-connectVM-Cloud-Kubernetes.html.md similarity index 88% rename from docs/kubernetes/Install-GitLab-on-3Engines-Cloud-Kubernetes.html.md rename to docs/kubernetes/Install-GitLab-on-connectVM-Cloud-Kubernetes.html.md index 10f5363..26f7af4 100644 --- a/docs/kubernetes/Install-GitLab-on-3Engines-Cloud-Kubernetes.html.md +++ b/docs/kubernetes/Install-GitLab-on-connectVM-Cloud-Kubernetes.html.md @@ -1,11 +1,11 @@ -Install GitLab on 3Engines Cloud Kubernetes[🔗](#install-gitlab-on-brand-name-kubernetes "Permalink to this headline") +Install GitLab on connectVM Cloud Kubernetes[🔗](#install-gitlab-on-brand-name-kubernetes "Permalink to this headline") ======================================================================================================================= Source control is essential for building professional software. Git has become synonym of a modern source control system and GitLab is one of most popular tools based on Git. GitLab can be deployed as your local instance to ensure privacy of the stored artifacts. It is also the tool of choice for its rich automation capabilities. -In this article, we will install GitLab on a Kubernetes cluster in 3Engines Cloud cloud. +In this article, we will install GitLab on a Kubernetes cluster in connectVM Cloud cloud. What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -20,13 +20,13 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Understand Helm deployments** To install GitLab on Kubernetes cluster, we will use the appropriate Helm chart. The following article explains the procedure: -[Deploying Helm Charts on Magnum Kubernetes Clusters on 3Engines Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md) +[Deploying Helm Charts on Magnum Kubernetes Clusters on connectVM Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md) No. 3 **Kubernetes cluster without ingress controller already installed** @@ -39,7 +39,7 @@ The Helm chart for installation of GitHub client will install its own ingress co General explanation of how to create a Kubernetes cluster is here: -[How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md) +[How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md) Be sure to use cluster template for at least version 1.25, like this: @@ -47,9 +47,9 @@ Be sure to use cluster template for at least version 1.25, like this: No. 4 **Have your own domain and be able to manage it** -You will be able to manage the records of a domain associated with your gitlab instance at your domain registrar. Alternatively 3Engines on 3Engines Cloud hosting lets you manage DNS as a service: +You will be able to manage the records of a domain associated with your gitlab instance at your domain registrar. Alternatively connectVM on connectVM Cloud hosting lets you manage DNS as a service: -[DNS as a Service on 3Engines Cloud Hosting](../cloud/DNS-as-a-Service-on-3Engines-Cloud-Hosting.html.md) +[DNS as a Service on connectVM Cloud Hosting](../cloud/DNS-as-a-Service-on-connectVM-Cloud-Hosting.html.md) No. 5 **Proof of concept vs. production ready version of GitLab client** @@ -67,14 +67,14 @@ We will first create a Floating IP (FIP) using Horizon GUI. This FIP will be lat ![image-2024-4-30_14-0-23.png](../_images/image-2024-4-30_14-0-23.png) -After closing the form, your new floating IP will appear on the list and let us say that for the sake of this article, its value is **64.225.134.173**. The next step is to create an A record that will associate the subdomain **gitlab.** with this IP address. In our case, it might look like this if you are using DNS as a Service under 3Engines Horizon UI on your 3Engines Cloud cloud: +After closing the form, your new floating IP will appear on the list and let us say that for the sake of this article, its value is **64.225.134.173**. The next step is to create an A record that will associate the subdomain **gitlab.** with this IP address. In our case, it might look like this if you are using DNS as a Service under connectVM Horizon UI on your connectVM Cloud cloud: ![a_record_in_dns.png](../_images/a_record_in_dns.png) Step 2 Apply preliminary configuration[🔗](#step-2-apply-preliminary-configuration "Permalink to this headline") --------------------------------------------------------------------------------------------------------------- -A condition to ensure compatibility with Kubernetes setup on 3Engines Cloud clouds is to enable the Service Accounts provisioned by GitLab Helm chart to have sufficient access to reading scaling metrics. This can be done by creating an appropriate *rolebinding*. +A condition to ensure compatibility with Kubernetes setup on connectVM Cloud clouds is to enable the Service Accounts provisioned by GitLab Helm chart to have sufficient access to reading scaling metrics. This can be done by creating an appropriate *rolebinding*. First, create a namespace gitlab where we will deploy the Helm chart: diff --git a/docs/kubernetes/Install-and-run-Argo-Workflows-on-3Engines-Cloud-Magnum-Kubernetes.html.md b/docs/kubernetes/Install-and-run-Argo-Workflows-on-connectVM-Cloud-Magnum-Kubernetes.html.md similarity index 92% rename from docs/kubernetes/Install-and-run-Argo-Workflows-on-3Engines-Cloud-Magnum-Kubernetes.html.md rename to docs/kubernetes/Install-and-run-Argo-Workflows-on-connectVM-Cloud-Magnum-Kubernetes.html.md index e2633f2..7b7f0df 100644 --- a/docs/kubernetes/Install-and-run-Argo-Workflows-on-3Engines-Cloud-Magnum-Kubernetes.html.md +++ b/docs/kubernetes/Install-and-run-Argo-Workflows-on-connectVM-Cloud-Magnum-Kubernetes.html.md @@ -1,4 +1,4 @@ -Install and run Argo Workflows on 3Engines Cloud Magnum Kubernetes[🔗](#install-and-run-argo-workflows-on-brand-name-cloud-name-magnum-kubernetes "Permalink to this headline") +Install and run Argo Workflows on connectVM Cloud Magnum Kubernetes[🔗](#install-and-run-argo-workflows-on-brand-name-cloud-name-magnum-kubernetes "Permalink to this headline") ================================================================================================================================================================================ [Argo Workflows](https://argoproj.github.io/argo-workflows/) enable running complex job workflows on Kubernetes. It can @@ -25,10 +25,10 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") ------------------------------------------------------------- No. 1 **Account** -: You need a 3Engines Cloud hosting account with access to the Horizon interface: . +: You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **kubectl pointed to the Kubernetes cluster** -: If you are creating a new cluster, for the purposes of this article, call it *argo-cluster*. See [How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md) +: If you are creating a new cluster, for the purposes of this article, call it *argo-cluster*. See [How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md) Authenticate to the cluster[🔗](#authenticate-to-the-cluster "Permalink to this headline") ----------------------------------------------------------------------------------------- @@ -36,7 +36,7 @@ Authenticate to the cluster[🔗](#authenticate-to-the-cluster "Permalink to thi Let us authenticate to *argo-cluster*. Run from your local machine the following command to create a config file in the present working directory: ``` -3Engines coe cluster config argo-cluster +connectVM coe cluster config argo-cluster ``` @@ -52,7 +52,7 @@ Run this command. Apply preliminary configuration[🔗](#apply-preliminary-configuration "Permalink to this headline") ------------------------------------------------------------------------------------------------- -3Engines Magnum by default applies certain security restrictions for pods running on the cluster, in line with “least privileges” practice. Argo Workflows will require some additional privileges in order to run correctly. +connectVM Magnum by default applies certain security restrictions for pods running on the cluster, in line with “least privileges” practice. Argo Workflows will require some additional privileges in order to run correctly. First create a dedicated namespace for Argo Workflows artifacts: diff --git a/docs/kubernetes/Install-and-run-Dask-on-a-Kubernetes-cluster-in-3Engines-Cloud-cloud.html.md b/docs/kubernetes/Install-and-run-Dask-on-a-Kubernetes-cluster-in-connectVM-Cloud-cloud.html.md similarity index 92% rename from docs/kubernetes/Install-and-run-Dask-on-a-Kubernetes-cluster-in-3Engines-Cloud-cloud.html.md rename to docs/kubernetes/Install-and-run-Dask-on-a-Kubernetes-cluster-in-connectVM-Cloud-cloud.html.md index 6ce36f5..92693c8 100644 --- a/docs/kubernetes/Install-and-run-Dask-on-a-Kubernetes-cluster-in-3Engines-Cloud-cloud.html.md +++ b/docs/kubernetes/Install-and-run-Dask-on-a-Kubernetes-cluster-in-connectVM-Cloud-cloud.html.md @@ -1,4 +1,4 @@ -Install and run Dask on a Kubernetes cluster in 3Engines Cloud cloud[🔗](#install-and-run-dask-on-a-kubernetes-cluster-in-brand-name-cloud "Permalink to this headline") +Install and run Dask on a Kubernetes cluster in connectVM Cloud cloud[🔗](#install-and-run-dask-on-a-kubernetes-cluster-in-brand-name-cloud "Permalink to this headline") ========================================================================================================================================================================= [Dask](https://www.dask.org/) enables scaling computation tasks either as multiple processes on a single machine, or on Dask clusters that consist of multiple worker machines. Dask provides a scalable alternative to popular Python libraries e.g. Numpy, Pandas or SciKit Learn, but still using a compact and very similar API. @@ -21,19 +21,19 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . -No. 2 **Kubernetes cluster on 3Engines cloud** +No. 2 **Kubernetes cluster on connectVM cloud** -To create Kubernetes cluster on cloud refer to this guide: [How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md) +To create Kubernetes cluster on cloud refer to this guide: [How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md) No. 3 **Access to kubectl command line** -The instructions for activation of **kubectl** are provided in: [How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md) +The instructions for activation of **kubectl** are provided in: [How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md) No. 4 **Familiarity with Helm** -For more information on using Helm and installing apps with Helm on Kubernetes, refer to [Deploying Helm Charts on Magnum Kubernetes Clusters on 3Engines Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md) +For more information on using Helm and installing apps with Helm on Kubernetes, refer to [Deploying Helm Charts on Magnum Kubernetes Clusters on connectVM Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md) No. 5 **Python3 available on your machine** diff --git a/docs/kubernetes/Install-and-run-NooBaa-on-Kubernetes-cluster-in-single-and-multicloud-environment-on-3Engines-Cloud.html.md b/docs/kubernetes/Install-and-run-NooBaa-on-Kubernetes-cluster-in-single-and-multicloud-environment-on-connectVM-Cloud.html.md similarity index 90% rename from docs/kubernetes/Install-and-run-NooBaa-on-Kubernetes-cluster-in-single-and-multicloud-environment-on-3Engines-Cloud.html.md rename to docs/kubernetes/Install-and-run-NooBaa-on-Kubernetes-cluster-in-single-and-multicloud-environment-on-connectVM-Cloud.html.md index 65cf0c1..78c5e83 100644 --- a/docs/kubernetes/Install-and-run-NooBaa-on-Kubernetes-cluster-in-single-and-multicloud-environment-on-3Engines-Cloud.html.md +++ b/docs/kubernetes/Install-and-run-NooBaa-on-Kubernetes-cluster-in-single-and-multicloud-environment-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -Install and run NooBaa on Kubernetes cluster in single- and multicloud-environment on 3Engines Cloud[🔗](#install-and-run-noobaa-on-kubernetes-cluster-in-single-and-multicloud-environment-on-brand-name "Permalink to this headline") +Install and run NooBaa on Kubernetes cluster in single- and multicloud-environment on connectVM Cloud[🔗](#install-and-run-noobaa-on-kubernetes-cluster-in-single-and-multicloud-environment-on-brand-name "Permalink to this headline") ======================================================================================================================================================================================================================================== [NooBaa](https://www.noobaa.io/) enables creating an abstracted S3 backend on Kubernetes. Such backend can be connected to multiple S3 backing stores e.g. in a multi-cloud setup, allowing for storage expandability or High Availability among other beneficial features. @@ -6,7 +6,7 @@ Install and run NooBaa on Kubernetes cluster in single- and multicloud-environme In this article you will learn the basics of using NooBaa > * how to install it on Kubernetes cluster -> * how to create a NooBaa bucket backed by S3 object storage in the 3Engines Cloud cloud +> * how to create a NooBaa bucket backed by S3 object storage in the connectVM Cloud cloud > * how to create a NooBaa bucket mirroring data on two different clouds What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") @@ -27,29 +27,29 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . No. 2 **Access to Kubernetes cluster on WAW3-1 cloud** -A cluster on WAW3-1 cloud, where we will run our NooBaa installation - follow guidelines in this article [How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md). +A cluster on WAW3-1 cloud, where we will run our NooBaa installation - follow guidelines in this article [How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md). -No. 3 **Familiarity with using Object Storage on 3Engines clouds** +No. 3 **Familiarity with using Object Storage on connectVM clouds** -More information in [How to use Object Storage on 3Engines Cloud](../s3/How-to-use-Object-Storage-on-3Engines-Cloud.html.md) +More information in [How to use Object Storage on connectVM Cloud](../s3/How-to-use-Object-Storage-on-connectVM-Cloud.html.md) -Traditional 3Engines term for imported or downloaded files is *Containers* in main menu option *Object Store*. We will use the term “bucket” for object storage containers, to differentiate vs. container term in Docker/Kubernetes sense. +Traditional connectVM term for imported or downloaded files is *Containers* in main menu option *Object Store*. We will use the term “bucket” for object storage containers, to differentiate vs. container term in Docker/Kubernetes sense. No. 4 **kubectl operational** -**kubectl** CLI tool installed and pointing to your cluster via KUBECONFIG env. variable - more information in [How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md). +**kubectl** CLI tool installed and pointing to your cluster via KUBECONFIG env. variable - more information in [How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md). No. 5 **Access to private S3 keys in WAW3-1 cloud** -You may also use access to 3Engines CLI to generate and read the private S3 keys - [How to generate and manage EC2 credentials on 3Engines Cloud](../cloud/How-to-generate-ec2-credentials-on-3Engines-Cloud.html.md). +You may also use access to connectVM CLI to generate and read the private S3 keys - [How to generate and manage EC2 credentials on connectVM Cloud](../cloud/How-to-generate-ec2-credentials-on-connectVM-Cloud.html.md). No. 6 **Familiarity with s3cmd for accessing object storage** -For more info on **s3cmd**, see [How to access private object storage using S3cmd or boto3 on 3Engines Cloud](../s3/How-to-access-private-object-storage-using-S3cmd-or-boto3-on-3Engines-Cloud.html.md). +For more info on **s3cmd**, see [How to access private object storage using S3cmd or boto3 on connectVM Cloud](../s3/How-to-access-private-object-storage-using-S3cmd-or-boto3-on-connectVM-Cloud.html.md). No. 7 **Access to WAW3-2 cloud** @@ -83,7 +83,7 @@ This will result in an output similar to the below: Apply preliminary configuration[🔗](#apply-preliminary-configuration "Permalink to this headline") ------------------------------------------------------------------------------------------------- -We will need to apply additional configuration on a Magnum cluster to avoid PodSecurityPolicy exception. For a refresher, see article [Installing JupyterHub on Magnum Kubernetes Cluster in 3Engines Cloud Cloud](Installing-JupyterHub-on-Magnum-Kubernetes-cluster-in-3Engines-Cloud-cloud.html.md). +We will need to apply additional configuration on a Magnum cluster to avoid PodSecurityPolicy exception. For a refresher, see article [Installing JupyterHub on Magnum Kubernetes Cluster in connectVM Cloud Cloud](Installing-JupyterHub-on-Magnum-Kubernetes-cluster-in-connectVM-Cloud-cloud.html.md). Let’s start by creating a dedicated namespace for Noobaa artifacts: @@ -139,7 +139,7 @@ noobaa status -n noobaa It outputs several useful insights about the NooBaa installation, with the “key facts” available towards the end of this status: -> * NooBaa created a default backing store called *noobaa-default-backing-store*, backed by a block volume created in 3Engines. +> * NooBaa created a default backing store called *noobaa-default-backing-store*, backed by a block volume created in connectVM. > * S3 credentials are provided to access the bucket created with the default backing store. Such volume-based backing store has its use e.g. for utilizing the S3 access method to our block storage. For the purpose of this article, we will not use the default backing store, but rather learn to create a new backing store based on cloud S3 object storage. Such setup can be then easily extended so that we can end up with separate backing stores for different clouds. In the second part of this article you will create one store on WAW3-1 cloud, another one on WAW3-2 cloud and they will be available through one abstracted S3 bucket in NooBaa. @@ -167,7 +167,7 @@ You need to create a bucket with a different name and use this generated name to If you have properly set up the EC2 (S3) keys for your WAW3-1 object storage, take note of them with the following command: ``` -3Engines ec2 credentials list +connectVM ec2 credentials list ``` @@ -176,7 +176,7 @@ If you have properly set up the EC2 (S3) keys for your WAW3-1 object storage, ta With the above in place, we can create a new NooBaa backing store called *custom-bs* by running the command below. Make sure to replace the access-key XXXXXX and the secret-key YYYYYYY with your own EC2 keys and the *bucket* with your own bucket name: ``` -noobaa -n noobaa backingstore create s3-compatible custom-bs --endpoint https://s3.waw3-1.3Engines.com --signature-version v4 --access-key XXXXXX \ +noobaa -n noobaa backingstore create s3-compatible custom-bs --endpoint https://s3.waw3-1.connectVM.com --signature-version v4 --access-key XXXXXX \ --secret-key YYYYYYY --target-bucket noobaademo-waw3-1 ``` @@ -396,11 +396,11 @@ To proceed, first create two additional buckets from the Horizon interface. Repl ### Step 1 Multi-cloud. Create bucket on WAW3-1[🔗](#step-1-multi-cloud-create-bucket-on-waw3-1 "Permalink to this headline") -Go to WAW3-1 Horizon interface and create a bucket we call *noobaamirror-waw3-1* (supply your own bucket name here and adhere to it in the rest of the article). It will be the available on endpoint . +Go to WAW3-1 Horizon interface and create a bucket we call *noobaamirror-waw3-1* (supply your own bucket name here and adhere to it in the rest of the article). It will be the available on endpoint . ### Step 1 Multi-cloud. Create bucket on WAW3-2[🔗](#step-1-multi-cloud-create-bucket-on-waw3-2 "Permalink to this headline") -Next, go to WAW3-2 Horizon interface and create a bucket we call *noobaamirror-waw3-2* (again, supply your own bucket name here and adhere to it in the rest of the article). It will be available on endpoint +Next, go to WAW3-2 Horizon interface and create a bucket we call *noobaamirror-waw3-2* (again, supply your own bucket name here and adhere to it in the rest of the article). It will be available on endpoint ### Step 2 Multi-cloud. Set up EC2 credentials[🔗](#step-2-multi-cloud-set-up-ec2-credentials "Permalink to this headline") @@ -411,7 +411,7 @@ Use the existing pair of EC2 credentials or first create a new pair and then use Apply the following command to create *mirror-bs1* backing store (change names of: bucket name, S3 access key, S3 secret key to your own): ``` -noobaa -n noobaa backingstore create s3-compatible mirror-bs1 --endpoint https://s3.waw3-1.3Engines.com --signature-version v4 --access-key XXXXXX --secret-key YYYYYY --target-bucket noobaamirror-waw3-1 +noobaa -n noobaa backingstore create s3-compatible mirror-bs1 --endpoint https://s3.waw3-1.connectVM.com --signature-version v4 --access-key XXXXXX --secret-key YYYYYY --target-bucket noobaamirror-waw3-1 ``` @@ -420,7 +420,7 @@ noobaa -n noobaa backingstore create s3-compatible mirror-bs1 --endpoint https:/ Apply the following command to create *mirror-bs2* backing store (change names of: bucket name, S3 access key, S3 secret key to your own): ``` -noobaa -n noobaa backingstore create s3-compatible mirror-bs2 --endpoint https://s3.waw3-2.3Engines.com --signature-version v4 --access-key XXXXXX --secret-key YYYYYY --target-bucket noobaamirror-waw3-2 +noobaa -n noobaa backingstore create s3-compatible mirror-bs2 --endpoint https://s3.waw3-2.connectVM.com --signature-version v4 --access-key XXXXXX --secret-key YYYYYY --target-bucket noobaamirror-waw3-2 ``` diff --git a/docs/kubernetes/Installing-HashiCorp-Vault-on-3Engines-Cloud-Magnum.html.md b/docs/kubernetes/Installing-HashiCorp-Vault-on-connectVM-Cloud-Magnum.html.md similarity index 95% rename from docs/kubernetes/Installing-HashiCorp-Vault-on-3Engines-Cloud-Magnum.html.md rename to docs/kubernetes/Installing-HashiCorp-Vault-on-connectVM-Cloud-Magnum.html.md index 24ddb66..566f8e2 100644 --- a/docs/kubernetes/Installing-HashiCorp-Vault-on-3Engines-Cloud-Magnum.html.md +++ b/docs/kubernetes/Installing-HashiCorp-Vault-on-connectVM-Cloud-Magnum.html.md @@ -1,4 +1,4 @@ -Installing HashiCorp Vault on 3Engines Cloud Magnum[🔗](#installing-hashicorp-vault-on-brand-name-cloud-name-magnum "Permalink to this headline") +Installing HashiCorp Vault on connectVM Cloud Magnum[🔗](#installing-hashicorp-vault-on-brand-name-cloud-name-magnum "Permalink to this headline") ================================================================================================================================================== In Kubernetes, a *Secret* is an object that contains passwords, tokens, keys or any other small pieces of data. Using *Secrets* ensures that the probability of exposing confidential data while creating, running and editing Pods is much smaller. The main problem is that *Secrets* are stored unencrypted in *etcd* so anyone with @@ -18,7 +18,7 @@ You can apply a number of strategies to improve the security of the cluster or y > * revoking or deleting any key or secret, > * setting automated secret rotation – for administrators and users alike. -In this article, we shall install HashiCorp Vault within a Magnum Kubernetes cluster, on 3Engines Cloud cloud. +In this article, we shall install HashiCorp Vault within a Magnum Kubernetes cluster, on connectVM Cloud cloud. What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -38,17 +38,17 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Familiarity with kubectl** -You should have an appropriate Kubernetes cluster up and running, with **kubectl** pointing to it [How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md) +You should have an appropriate Kubernetes cluster up and running, with **kubectl** pointing to it [How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md) No. 3 **Familiarity with deploying Helm charts** This article will introduce you to Helm charts on Kubernetes: -[Deploying Helm Charts on Magnum Kubernetes Clusters on 3Engines Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md) +[Deploying Helm Charts on Magnum Kubernetes Clusters on connectVM Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md) Step 1 Install CFSSL[🔗](#step-1-install-cfssl "Permalink to this headline") --------------------------------------------------------------------------- @@ -547,4 +547,4 @@ Now you have Vault server as a part of the cluster and you can also use it from Another way to improve Kubernetes security is securing applications with HTTPS using ingress: -[Deploying HTTPS Services on Magnum Kubernetes in 3Engines Cloud Cloud](Deploying-HTTPS-Services-on-Magnum-Kubernetes-in-3Engines-Cloud-Cloud.html.md). \ No newline at end of file +[Deploying HTTPS Services on Magnum Kubernetes in connectVM Cloud Cloud](Deploying-HTTPS-Services-on-Magnum-Kubernetes-in-connectVM-Cloud-Cloud.html.md). \ No newline at end of file diff --git a/docs/kubernetes/Installing-JupyterHub-on-Magnum-Kubernetes-cluster-in-3Engines-Cloud-cloud.html.md b/docs/kubernetes/Installing-JupyterHub-on-Magnum-Kubernetes-cluster-in-connectVM-Cloud-cloud.html.md similarity index 89% rename from docs/kubernetes/Installing-JupyterHub-on-Magnum-Kubernetes-cluster-in-3Engines-Cloud-cloud.html.md rename to docs/kubernetes/Installing-JupyterHub-on-Magnum-Kubernetes-cluster-in-connectVM-Cloud-cloud.html.md index ba52912..e911973 100644 --- a/docs/kubernetes/Installing-JupyterHub-on-Magnum-Kubernetes-cluster-in-3Engines-Cloud-cloud.html.md +++ b/docs/kubernetes/Installing-JupyterHub-on-Magnum-Kubernetes-cluster-in-connectVM-Cloud-cloud.html.md @@ -1,4 +1,4 @@ -Installing JupyterHub on Magnum Kubernetes Cluster in 3Engines Cloud Cloud[🔗](#installing-jupyterhub-on-magnum-kubernetes-cluster-in-brand-name-cloud-name-cloud "Permalink to this headline") +Installing JupyterHub on Magnum Kubernetes Cluster in connectVM Cloud Cloud[🔗](#installing-jupyterhub-on-magnum-kubernetes-cluster-in-brand-name-cloud-name-cloud "Permalink to this headline") ================================================================================================================================================================================================ Jupyter notebooks are a popular method of presenting application code, as well as running exploratory experiments and analysis, conveniently, from a web browser. From a Jupyter notebook, one can run code, see the generated results in attractive visual form, and often also interactively interact with the generated output. @@ -20,17 +20,17 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **kubectl up and running** -For further instructions refer to [How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md) +For further instructions refer to [How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md) No. 3 **Helm up and running** Helm is package manager for Kubernetes as explained in article -[Deploying Helm Charts on Magnum Kubernetes Clusters on 3Engines Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md) +[Deploying Helm Charts on Magnum Kubernetes Clusters on connectVM Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md) No. 4 **A registered domain name available** @@ -44,7 +44,7 @@ First of all, we need to authenticate to the cluster. It may so happen that you You may also create a new cluster and call it, say, *jupyter-cluster*, as explained in Prerequisite No. 2. In that case, run from your local machine the following command to create config file in the present working directory: ``` -3Engines coe cluster config jupyter-cluster +connectVM coe cluster config jupyter-cluster ``` @@ -60,7 +60,7 @@ Run this command. Step 2 Apply preliminary configuration[🔗](#step-2-apply-preliminary-configuration "Permalink to this headline") --------------------------------------------------------------------------------------------------------------- -3Engines Magnum by default applies certain security restrictions for pods running on the cluster, in line with “least privileges” practice. JupyterHub will require some additional privileges in order to run correctly. +connectVM Magnum by default applies certain security restrictions for pods running on the cluster, in line with “least privileges” practice. JupyterHub will require some additional privileges in order to run correctly. We will start by creating a dedicated namespace for our JupyterHub Helm artifacts: diff --git a/docs/kubernetes/Kubernetes-cluster-observability-with-Prometheus-and-Grafana-on-3Engines-Cloud.html.md b/docs/kubernetes/Kubernetes-cluster-observability-with-Prometheus-and-Grafana-on-connectVM-Cloud.html.md similarity index 93% rename from docs/kubernetes/Kubernetes-cluster-observability-with-Prometheus-and-Grafana-on-3Engines-Cloud.html.md rename to docs/kubernetes/Kubernetes-cluster-observability-with-Prometheus-and-Grafana-on-connectVM-Cloud.html.md index d01396d..4492fc7 100644 --- a/docs/kubernetes/Kubernetes-cluster-observability-with-Prometheus-and-Grafana-on-3Engines-Cloud.html.md +++ b/docs/kubernetes/Kubernetes-cluster-observability-with-Prometheus-and-Grafana-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -Kubernetes cluster observability with Prometheus and Grafana on 3Engines Cloud[🔗](#kubernetes-cluster-observability-with-prometheus-and-grafana-on-brand-name "Permalink to this headline") +Kubernetes cluster observability with Prometheus and Grafana on connectVM Cloud[🔗](#kubernetes-cluster-observability-with-prometheus-and-grafana-on-brand-name "Permalink to this headline") ============================================================================================================================================================================================= Complex systems deployed on Kubernetes take advantage of multiple Kubernetes resources. Such deployments often consist of a number of namespaces, pods and many other entities, which contribute to consuming the cluster resources. @@ -20,19 +20,19 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . No. 2 **A cluster created on** **cloud** -Kubernetes cluster available. For guideline on creating a Kubernetes cluster refer to [How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md). +Kubernetes cluster available. For guideline on creating a Kubernetes cluster refer to [How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md). No. 3 **Familiarity with Helm** -For more information on using Helm and installing apps with Helm on Kubernetes, refer to [Deploying Helm Charts on Magnum Kubernetes Clusters on 3Engines Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md) +For more information on using Helm and installing apps with Helm on Kubernetes, refer to [Deploying Helm Charts on Magnum Kubernetes Clusters on connectVM Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md) No. 4 **Access to kubectl command line** -The instructions for activation of **kubectl** are provided in: [How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md) +The instructions for activation of **kubectl** are provided in: [How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md) 1. Install Prometheus with Helm[🔗](#install-prometheus-with-helm "Permalink to this headline") ---------------------------------------------------------------------------------------------- @@ -209,4 +209,4 @@ You can find and import many other dashboards for Kubernetes observability by br The following article shows another approach to creating a Kubernetes dashboard: -[Using Dashboard To Access Kubernetes Cluster Post Deployment On 3Engines Cloud 3Engines Magnum](Using-Dashboard-To-Access-Kubernetes-Cluster-Post-Deployment-On-3Engines-Cloud-3Engines-Magnum.html.md) \ No newline at end of file +[Using Dashboard To Access Kubernetes Cluster Post Deployment On connectVM Cloud connectVM Magnum](Using-Dashboard-To-Access-Kubernetes-Cluster-Post-Deployment-On-connectVM-Cloud-connectVM-Magnum.html.md) \ No newline at end of file diff --git a/docs/kubernetes/Private-container-registries-with-Harbor-on-3Engines-Cloud-Kubernetes.html.md b/docs/kubernetes/Private-container-registries-with-Harbor-on-connectVM-Cloud-Kubernetes.html.md similarity index 93% rename from docs/kubernetes/Private-container-registries-with-Harbor-on-3Engines-Cloud-Kubernetes.html.md rename to docs/kubernetes/Private-container-registries-with-Harbor-on-connectVM-Cloud-Kubernetes.html.md index 5d3be09..8c7e23c 100644 --- a/docs/kubernetes/Private-container-registries-with-Harbor-on-3Engines-Cloud-Kubernetes.html.md +++ b/docs/kubernetes/Private-container-registries-with-Harbor-on-connectVM-Cloud-Kubernetes.html.md @@ -1,4 +1,4 @@ -Private container registries with Harbor on 3Engines Cloud Kubernetes[🔗](#private-container-registries-with-harbor-on-brand-name-kubernetes "Permalink to this headline") +Private container registries with Harbor on connectVM Cloud Kubernetes[🔗](#private-container-registries-with-harbor-on-brand-name-kubernetes "Permalink to this headline") =========================================================================================================================================================================== A fundamental component of the container-based ecosystem are *container registries*, used for storing and distributing container images. There are a few popular public container registries, which serve this purpose in a software-as-a-service model and the most popular is [DockerHub](https://hub.docker.com/). @@ -34,21 +34,21 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . -No. 2 **A cluster on 3Engines-Cloud cloud** +No. 2 **A cluster on connectVM-Cloud cloud** -A Kubernetes cluster on 3Engines Cloud cloud. Follow guidelines in this article [How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md). +A Kubernetes cluster on connectVM Cloud cloud. Follow guidelines in this article [How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md). No. 3 **kubectl operational** -**kubectl** CLI tool installed and pointing to your cluster via KUBECONFIG environment variable. Article [How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md) provides further guidance. +**kubectl** CLI tool installed and pointing to your cluster via KUBECONFIG environment variable. Article [How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md) provides further guidance. No. 4 **Familiarity with deploying Helm charts** See this article: -[Deploying Helm Charts on Magnum Kubernetes Clusters on 3Engines Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md) +[Deploying Helm Charts on Magnum Kubernetes Clusters on connectVM Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md) No. 5 **Domain purchased from a registrar** @@ -58,11 +58,11 @@ No. 6 **Use DNS service in Horizon to link Harbor service to the domain name** This is optional. Here is the article with detailed information: -[DNS as a Service on 3Engines Cloud Hosting](../cloud/DNS-as-a-Service-on-3Engines-Cloud-Hosting.html.md) +[DNS as a Service on connectVM Cloud Hosting](../cloud/DNS-as-a-Service-on-connectVM-Cloud-Hosting.html.md) No. 7 **Docker installed on your machine** -See [How to install and use Docker on Ubuntu 24.04](../cloud/How-to-use-Docker-on-3Engines-Cloud.html.md). +See [How to install and use Docker on Ubuntu 24.04](../cloud/How-to-use-Docker-on-connectVM-Cloud.html.md). Deploy Harbor private registry with Bitnami-Harbor Helm chart[🔗](#deploy-harbor-private-registry-with-bitnami-harbor-helm-chart "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------------------------------------------------- @@ -199,7 +199,7 @@ The final step is to associate the A record of your domain to the Harbor’s IP Create or edit the A record through your domain registrar : The exact steps will vary from one registrar to another so explaining them is out of scope of this article. -Create or edit the A record through the DNS as a service available in your 3Engines Cloud account +Create or edit the A record through the DNS as a service available in your connectVM Cloud account : This is explained in Prerequisite No. 6. Use commands **DNS** –> **Zones** and select the name of the site you are using instead of *mysampledomain.info*, then click on **Record Sets**. In column **Type**, there will be type **A - Address record** and click on **Update** field on the right side to enter or change the value in that row: ![image2023-8-2_16-7-51.png](../_images/image2023-8-2_16-7-51.png) diff --git a/docs/kubernetes/Sealed-Secrets-on-3Engines-Cloud-Kubernetes.html.md b/docs/kubernetes/Sealed-Secrets-on-connectVM-Cloud-Kubernetes.html.md similarity index 88% rename from docs/kubernetes/Sealed-Secrets-on-3Engines-Cloud-Kubernetes.html.md rename to docs/kubernetes/Sealed-Secrets-on-connectVM-Cloud-Kubernetes.html.md index 811696b..f7ba31e 100644 --- a/docs/kubernetes/Sealed-Secrets-on-3Engines-Cloud-Kubernetes.html.md +++ b/docs/kubernetes/Sealed-Secrets-on-connectVM-Cloud-Kubernetes.html.md @@ -1,9 +1,9 @@ -Sealed Secrets on 3Engines Cloud Kubernetes[🔗](#sealed-secrets-on-brand-name-kubernetes "Permalink to this headline") +Sealed Secrets on connectVM Cloud Kubernetes[🔗](#sealed-secrets-on-brand-name-kubernetes "Permalink to this headline") ======================================================================================================================= Sealed Secrets improve security of our Kubernetes deployments by enabling encrypted Kubernetes secrets. This allows to store such secrets in source control and follow GitOps practices of storing all configuration in code. -In this article we will install tools to work with Sealed Secrets and demonstrate using Sealed Secrets on 3Engines Cloud cloud. +In this article we will install tools to work with Sealed Secrets and demonstrate using Sealed Secrets on connectVM Cloud cloud. What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -19,25 +19,25 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Understand Helm deployments** To install Sealed Secrets on Kubernetes cluster, we will use the appropriate Helm chart. The following article explains the procedure: -[Deploying Helm Charts on Magnum Kubernetes Clusters on 3Engines Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md) +[Deploying Helm Charts on Magnum Kubernetes Clusters on connectVM Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md) No. 3 **Kubernetes cluster** General explanation of how to create a Kubernetes cluster is here: -[How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md) +[How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md) For new cluster, using the latest version of the cluster template is always recommended. This article was tested with Kubernetes 1.25. No. 4 **Access to cluster with kubectl** -[How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md) +[How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md) Step 1 Install the Sealed Secrets controller[🔗](#step-1-install-the-sealed-secrets-controller "Permalink to this headline") --------------------------------------------------------------------------------------------------------------------------- @@ -174,4 +174,4 @@ The command prompt will change to **#**, meaning the command you enter is execut What To Do Next[🔗](#what-to-do-next "Permalink to this headline") ----------------------------------------------------------------- -Sealed Secrets present a viable alternative to secret management using additional tools such as HashiCorp-Vault. For additional information, see [Installing HashiCorp Vault on 3Engines Cloud Magnum](Installing-HashiCorp-Vault-on-3Engines-Cloud-Magnum.html.md). \ No newline at end of file +Sealed Secrets present a viable alternative to secret management using additional tools such as HashiCorp-Vault. For additional information, see [Installing HashiCorp Vault on connectVM Cloud Magnum](Installing-HashiCorp-Vault-on-connectVM-Cloud-Magnum.html.md). \ No newline at end of file diff --git a/docs/kubernetes/Using-Dashboard-To-Access-Kubernetes-Cluster-Post-Deployment-On-3Engines-Cloud-3Engines-Magnum.html.md b/docs/kubernetes/Using-Dashboard-To-Access-Kubernetes-Cluster-Post-Deployment-On-connectVM-Cloud-connectVM-Magnum.html.md similarity index 94% rename from docs/kubernetes/Using-Dashboard-To-Access-Kubernetes-Cluster-Post-Deployment-On-3Engines-Cloud-3Engines-Magnum.html.md rename to docs/kubernetes/Using-Dashboard-To-Access-Kubernetes-Cluster-Post-Deployment-On-connectVM-Cloud-connectVM-Magnum.html.md index ec27099..d37002d 100644 --- a/docs/kubernetes/Using-Dashboard-To-Access-Kubernetes-Cluster-Post-Deployment-On-3Engines-Cloud-3Engines-Magnum.html.md +++ b/docs/kubernetes/Using-Dashboard-To-Access-Kubernetes-Cluster-Post-Deployment-On-connectVM-Cloud-connectVM-Magnum.html.md @@ -1,4 +1,4 @@ -Using Dashboard To Access Kubernetes Cluster Post Deployment On 3Engines Cloud 3Engines Magnum[🔗](#using-dashboard-to-access-kubernetes-cluster-post-deployment-on-brand-name-3Engines-magnum "Permalink to this headline") +Using Dashboard To Access Kubernetes Cluster Post Deployment On connectVM Cloud connectVM Magnum[🔗](#using-dashboard-to-access-kubernetes-cluster-post-deployment-on-brand-name-connectVM-magnum "Permalink to this headline") =============================================================================================================================================================================================================================== After the Kubernetes cluster has been created, you can access it through command line tool, **kubectl**, or you can access it through a visual interface, called the **Kubernetes dashboard**. *Dashboard* is a GUI interface to Kubernetes cluster, much the same as **kubectl** as a CLI interface to the Kubernetes cluster. @@ -20,11 +20,11 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . No. 2 **Cluster and kubectl should be already operational** -To eventually set up a cluster and connect it to the **kubectl** tool, see this article [How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md). +To eventually set up a cluster and connect it to the **kubectl** tool, see this article [How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md). The important intermediary result of that article is a command like this: diff --git a/docs/kubernetes/Using-Kubernetes-Ingress-on-3Engines-Cloud-3Engines-Magnum.html.md b/docs/kubernetes/Using-Kubernetes-Ingress-on-connectVM-Cloud-connectVM-Magnum.html.md similarity index 92% rename from docs/kubernetes/Using-Kubernetes-Ingress-on-3Engines-Cloud-3Engines-Magnum.html.md rename to docs/kubernetes/Using-Kubernetes-Ingress-on-connectVM-Cloud-connectVM-Magnum.html.md index 0626502..8985877 100644 --- a/docs/kubernetes/Using-Kubernetes-Ingress-on-3Engines-Cloud-3Engines-Magnum.html.md +++ b/docs/kubernetes/Using-Kubernetes-Ingress-on-connectVM-Cloud-connectVM-Magnum.html.md @@ -1,4 +1,4 @@ -Using Kubernetes Ingress on 3Engines Cloud 3Engines Magnum[🔗](#using-kubernetes-ingress-on-brand-name-cloud-name-3Engines-magnum "Permalink to this headline") +Using Kubernetes Ingress on connectVM Cloud connectVM Magnum[🔗](#using-kubernetes-ingress-on-brand-name-cloud-name-connectVM-magnum "Permalink to this headline") ================================================================================================================================================================== The Ingress feature in Kubernetes can be associated with routing the traffic from outside of the cluster to the services within the cluster. With Ingress, multiple Kubernetes services can be exposed using a single Load Balancer. @@ -21,7 +21,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Basic knowledge of Kubernetes fundamentals** @@ -29,7 +29,7 @@ Basic knowledge of Kubernetes fundamentals will come handy: cluster creation, po No. 3 **Access to kubectl command** -To install necessary software (if you haven’t done so already), see article [How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md). +To install necessary software (if you haven’t done so already), see article [How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md). The net result of following instructions in that and the related articles will be @@ -39,7 +39,7 @@ The net result of following instructions in that and the related articles will b Step 1 Create a Magnum Kubernetes cluster with NGINX Ingress enabled[🔗](#step-1-create-a-magnum-kubernetes-cluster-with-nginx-ingress-enabled "Permalink to this headline") --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -When we create a Kubernetes cluster on the cloud, we can deploy it with a preconfigured ingress setup. This requires minimal setting and is described in this help section: [How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md). +When we create a Kubernetes cluster on the cloud, we can deploy it with a preconfigured ingress setup. This requires minimal setting and is described in this help section: [How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md). Such a cluster is deployed with an NGINX *ingress controller* and the default *ingress backend*. The role of the controller is to enable the provisioning of the infrastructure e.g. the (virtual) load balancer. The role of the backend is to provide access to this infrastructure in line with the rules defined by the **ingress resource** (explained later). @@ -117,7 +117,7 @@ nginx-web NodePort 10.254.101.230 80:32532/TCP The services were created with the type *NodePort*, which is a required type to work with ingress. Therefore, they are not yet exposed under a public IP. The servers are, however, already running and serving their default welcome pages. -You could verify that by assigning a floating IP to one of the nodes (see [How to Add or Remove Floating IP’s to your VM on 3Engines Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md)). Then SSH to the node and run the following command: +You could verify that by assigning a floating IP to one of the nodes (see [How to Add or Remove Floating IP’s to your VM on connectVM Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md)). Then SSH to the node and run the following command: ``` curl : diff --git a/docs/kubernetes/Volume-based-vs-Ephemeral-based-Storage-for-Kubernetes-Clusters-on-3Engines-Cloud-3Engines-Magnum.html.md b/docs/kubernetes/Volume-based-vs-Ephemeral-based-Storage-for-Kubernetes-Clusters-on-connectVM-Cloud-connectVM-Magnum.html.md similarity index 88% rename from docs/kubernetes/Volume-based-vs-Ephemeral-based-Storage-for-Kubernetes-Clusters-on-3Engines-Cloud-3Engines-Magnum.html.md rename to docs/kubernetes/Volume-based-vs-Ephemeral-based-Storage-for-Kubernetes-Clusters-on-connectVM-Cloud-connectVM-Magnum.html.md index e7a987c..c2938b5 100644 --- a/docs/kubernetes/Volume-based-vs-Ephemeral-based-Storage-for-Kubernetes-Clusters-on-3Engines-Cloud-3Engines-Magnum.html.md +++ b/docs/kubernetes/Volume-based-vs-Ephemeral-based-Storage-for-Kubernetes-Clusters-on-connectVM-Cloud-connectVM-Magnum.html.md @@ -1,4 +1,4 @@ -Volume-based vs Ephemeral-based Storage for Kubernetes Clusters on 3Engines Cloud 3Engines Magnum[🔗](#volume-based-vs-ephemeral-based-storage-for-kubernetes-clusters-on-brand-name-3Engines-magnum "Permalink to this headline") +Volume-based vs Ephemeral-based Storage for Kubernetes Clusters on connectVM Cloud connectVM Magnum[🔗](#volume-based-vs-ephemeral-based-storage-for-kubernetes-clusters-on-brand-name-connectVM-magnum "Permalink to this headline") ===================================================================================================================================================================================================================================== Containers in Kubernetes store files on-disk and if the container crashes, the data will be lost. A new container can replace the old one but the data will not survive. Another problem that appears is when containers running in a pod need to share files. @@ -8,10 +8,10 @@ That is why Kubernetes has another type of file storage, called *volumes*. They > * Ephemeral volumes are deleted when the pod is deleted, while > * Persistent volumes continue to exist even if the pod it is attached to does not exist any more. -The concept of volumes was first popularized by Docker, where it was a directory on disk, or within a container. In 3Engines Cloud 3Engines hosting, the default docker storage is configured to use ephemeral disk of the instance. This can be changed by specifying docker volume size during cluster creation, symbolically like this (see below for the full command to generate a new cluster using **–docker-volume-size**): +The concept of volumes was first popularized by Docker, where it was a directory on disk, or within a container. In connectVM Cloud connectVM hosting, the default docker storage is configured to use ephemeral disk of the instance. This can be changed by specifying docker volume size during cluster creation, symbolically like this (see below for the full command to generate a new cluster using **–docker-volume-size**): ``` -3Engines coe cluster create --docker-volume-size 50 +connectVM coe cluster create --docker-volume-size 50 ``` @@ -32,15 +32,15 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . 2 **Creating clusters with CLI** -The article [How To Use Command Line Interface for Kubernetes Clusters On 3Engines Cloud 3Engines Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-3Engines-Cloud-3Engines-Magnum.html.md) will introduce you to creation of clusters using a command line interface. +The article [How To Use Command Line Interface for Kubernetes Clusters On connectVM Cloud connectVM Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-connectVM-Cloud-connectVM-Magnum.html.md) will introduce you to creation of clusters using a command line interface. -3 **Connect 3Engines client to the cloud** +3 **Connect connectVM client to the cloud** -Prepare **3Engines** and **magnum** clients by executing *Step 2 Connect 3Engines and Magnum Clients to Horizon Cloud* from article [How To Install 3Engines and Magnum Clients for Command Line Interface to 3Engines Cloud Horizon](How-To-Install-3Engines-and-Magnum-Clients-for-Command-Line-Interface-to-3Engines-Cloud-Horizon.html.md) +Prepare **connectVM** and **magnum** clients by executing *Step 2 Connect connectVM and Magnum Clients to Horizon Cloud* from article [How To Install connectVM and Magnum Clients for Command Line Interface to connectVM Cloud Horizon](How-To-Install-connectVM-and-Magnum-Clients-for-Command-Line-Interface-to-connectVM-Cloud-Horizon.html.md) 4 **Check available quotas** @@ -48,7 +48,7 @@ Before creating additional cluster check the state of the resources with Horizon 5 **Private and public keys** -An SSH key-pair created in 3Engines dashboard. To create it, follow this article [How to create key pair in 3Engines Dashboard on 3Engines Cloud](../cloud/How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md). You will have created keypair called “sshkey” and you will be able to use it for this tutorial as well. +An SSH key-pair created in connectVM dashboard. To create it, follow this article [How to create key pair in connectVM Dashboard on connectVM Cloud](../cloud/How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md). You will have created keypair called “sshkey” and you will be able to use it for this tutorial as well. 6 **Types of Volumes** @@ -60,7 +60,7 @@ Step 1 - Create Cluster Using **–docker-volume-size**[🔗](#step-1-create-clu You are going to create a new cluster called *dockerspace* that will use parameter **–docker-volume-size** using the following command: ``` -3Engines coe cluster create dockerspace +connectVM coe cluster create dockerspace --cluster-template k8s-1.23.16-cilium-v1.0.3 --keypair sshkey --master-count 1 @@ -165,7 +165,7 @@ That will happen in case you did not set up the kubectl parameters as specified ``` mkdir dockerspacedir -3Engines coe cluster config +connectVM coe cluster config --dir dockerspacedir --force --output-certs @@ -176,7 +176,7 @@ dockerspace First create a new directory, *dockerspacedir*, where the config file for access to the cluster will reside, then execute the **cluster config** command. The output will be a line like this: ``` -export KUBECONFIG=/Users/duskosavic/3EnginesDocs/dockerspacedir/config +export KUBECONFIG=/Users/duskosavic/connectVMDocs/dockerspacedir/config ``` diff --git a/docs/kubernetes/kubernetes.html.md b/docs/kubernetes/kubernetes.html.md index e5ed3d3..fb27ce7 100644 --- a/docs/kubernetes/kubernetes.html.md +++ b/docs/kubernetes/kubernetes.html.md @@ -2,39 +2,39 @@ ## Available Documentation -* [How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md) -* [Default Kubernetes cluster templates in 3Engines Cloud Cloud](Default-Kubernetes-cluster-templates-in-3Engines-Cloud-Cloud.html.md) -* [How To Install 3Engines and Magnum Clients for Command Line Interface to 3Engines Cloud Horizon](How-To-Install-3Engines-and-Magnum-Clients-for-Command-Line-Interface-to-3Engines-Cloud-Horizon.html.md) -* [How To Use Command Line Interface for Kubernetes Clusters On 3Engines Cloud 3Engines Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-3Engines-Cloud-3Engines-Magnum.html.md) -* [How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md) -* [Using Dashboard To Access Kubernetes Cluster Post Deployment On 3Engines Cloud 3Engines Magnum](Using-Dashboard-To-Access-Kubernetes-Cluster-Post-Deployment-On-3Engines-Cloud-3Engines-Magnum.html.md) -* [How To Create API Server LoadBalancer for Kubernetes Cluster on 3Engines Cloud 3Engines Magnum](How-To-Create-API-Server-LoadBalancer-for-Kubernetes-Cluster-On-3Engines-Cloud-3Engines-Magnum.html.md) -* [Creating Additional Nodegroups in Kubernetes Cluster on 3Engines Cloud 3Engines Magnum](Creating-Additional-Nodegroups-in-Kubernetes-Cluster-on-3Engines-Cloud-3Engines-Magnum.html.md) -* [Autoscaling Kubernetes Cluster Resources on 3Engines Cloud 3Engines Magnum](Autoscaling-Kubernetes-Cluster-Resources-on-3Engines-Cloud-3Engines-Magnum.html.md) -* [Volume-based vs Ephemeral-based Storage for Kubernetes Clusters on 3Engines Cloud 3Engines Magnum](Volume-based-vs-Ephemeral-based-Storage-for-Kubernetes-Clusters-on-3Engines-Cloud-3Engines-Magnum.html.md) +* [How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md) +* [Default Kubernetes cluster templates in connectVM Cloud Cloud](Default-Kubernetes-cluster-templates-in-connectVM-Cloud-Cloud.html.md) +* [How To Install connectVM and Magnum Clients for Command Line Interface to connectVM Cloud Horizon](How-To-Install-connectVM-and-Magnum-Clients-for-Command-Line-Interface-to-connectVM-Cloud-Horizon.html.md) +* [How To Use Command Line Interface for Kubernetes Clusters On connectVM Cloud connectVM Magnum](How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-connectVM-Cloud-connectVM-Magnum.html.md) +* [How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md) +* [Using Dashboard To Access Kubernetes Cluster Post Deployment On connectVM Cloud connectVM Magnum](Using-Dashboard-To-Access-Kubernetes-Cluster-Post-Deployment-On-connectVM-Cloud-connectVM-Magnum.html.md) +* [How To Create API Server LoadBalancer for Kubernetes Cluster on connectVM Cloud connectVM Magnum](How-To-Create-API-Server-LoadBalancer-for-Kubernetes-Cluster-On-connectVM-Cloud-connectVM-Magnum.html.md) +* [Creating Additional Nodegroups in Kubernetes Cluster on connectVM Cloud connectVM Magnum](Creating-Additional-Nodegroups-in-Kubernetes-Cluster-on-connectVM-Cloud-connectVM-Magnum.html.md) +* [Autoscaling Kubernetes Cluster Resources on connectVM Cloud connectVM Magnum](Autoscaling-Kubernetes-Cluster-Resources-on-connectVM-Cloud-connectVM-Magnum.html.md) +* [Volume-based vs Ephemeral-based Storage for Kubernetes Clusters on connectVM Cloud connectVM Magnum](Volume-based-vs-Ephemeral-based-Storage-for-Kubernetes-Clusters-on-connectVM-Cloud-connectVM-Magnum.html.md) * [Backup of Kubernetes Cluster using Velero](Backup-of-Kubernetes-Cluster-using-Velero.html.md) -* [Using Kubernetes Ingress on 3Engines Cloud 3Engines Magnum](Using-Kubernetes-Ingress-on-3Engines-Cloud-3Engines-Magnum.html.md) -* [Deploying Helm Charts on Magnum Kubernetes Clusters on 3Engines Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md) -* [Deploying HTTPS Services on Magnum Kubernetes in 3Engines Cloud Cloud](Deploying-HTTPS-Services-on-Magnum-Kubernetes-in-3Engines-Cloud-Cloud.html.md) -* [Installing JupyterHub on Magnum Kubernetes Cluster in 3Engines Cloud Cloud](Installing-JupyterHub-on-Magnum-Kubernetes-cluster-in-3Engines-Cloud-cloud.html.md) -* [Install and run Argo Workflows on 3Engines Cloud Magnum Kubernetes](Install-and-run-Argo-Workflows-on-3Engines-Cloud-Magnum-Kubernetes.html.md) -* [Installing HashiCorp Vault on 3Engines Cloud Magnum](Installing-HashiCorp-Vault-on-3Engines-Cloud-Magnum.html.md) -* [HTTP Request-based Autoscaling on K8S using Prometheus and Keda on 3Engines Cloud](HTTP-Request-based-Autoscaling-on-K8S-using-Prometheus-and-Keda-on-3Engines-Cloud.html.md) -* [Create and access NFS server from Kubernetes on 3Engines Cloud](Create-and-access-NFS-server-from-Kubernetes-on-3Engines-Cloud.html.md) -* [Deploy Keycloak on Kubernetes with a sample app on 3Engines Cloud](Deploy-Keycloak-on-Kubernetes-with-a-sample-app-on-3Engines-Cloud.html.md) -* [Install and run Dask on a Kubernetes cluster in 3Engines Cloud cloud](Install-and-run-Dask-on-a-Kubernetes-cluster-in-3Engines-Cloud-cloud.html.md) -* [Install and run NooBaa on Kubernetes cluster in single- and multicloud-environment on 3Engines Cloud](Install-and-run-NooBaa-on-Kubernetes-cluster-in-single-and-multicloud-environment-on-3Engines-Cloud.html.md) -* [Private container registries with Harbor on 3Engines Cloud Kubernetes](Private-container-registries-with-Harbor-on-3Engines-Cloud-Kubernetes.html.md) -* [Deploying vGPU workloads on 3Engines Cloud Kubernetes](Deploying-vGPU-workloads-on-3Engines-Cloud-Kubernetes.html.md) -* [Kubernetes cluster observability with Prometheus and Grafana on 3Engines Cloud](Kubernetes-cluster-observability-with-Prometheus-and-Grafana-on-3Engines-Cloud.html.md) -* [Enable Kubeapps app launcher on 3Engines Cloud Magnum Kubernetes cluster](Enable-Kubeapps-app-launcher-on-3Engines-Cloud-Magnum-Kubernetes-cluster.html.md) -* [Install GitLab on 3Engines Cloud Kubernetes](Install-GitLab-on-3Engines-Cloud-Kubernetes.html.md) -* [Sealed Secrets on 3Engines Cloud Kubernetes](Sealed-Secrets-on-3Engines-Cloud-Kubernetes.html.md) -* [CI/CD pipelines with GitLab on 3Engines Cloud Kubernetes - building a Docker image](CICD-pipelines-with-GitLab-on-3Engines-Cloud-Kubernetes-building-a-Docker-image.html.md) -* [How to create Kubernetes cluster using Terraform on 3Engines Cloud](How-to-create-Kubernetes-cluster-using-Terraform-on-3Engines-Cloud.html.md) -* [GitOps with Argo CD on 3Engines Cloud Kubernetes](GitOps-with-Argo-CD-on-3Engines-Cloud-Kubernetes.html.md) -* [Configuring IP Whitelisting for 3Engines Load Balancer using Horizon and CLI on 3Engines Cloud](Configuring-IP-Whitelisting-for-3Engines-Load-Balancer-using-Horizon-and-CLI-on-3Engines-Cloud.html.md) -* [Configuring IP Whitelisting for 3Engines Load Balancer using Terraform on 3Engines Cloud](Configuring-IP-Whitelisting-for-3Engines-Load-Balancer-using-Terraform-on-3Engines-Cloud.html.md) -* [Implementing IP Whitelisting for Load Balancers with Security Groups on 3Engines Cloud](Implementing-IP-Whitelisting-for-Load-Balancers-with-Security-Groups-on-3Engines-Cloud.html.md) -* [How to install Rancher RKE2 Kubernetes on 3Engines Cloud](How-to-install-Rancher-RKE2-Kubernetes-on-3Engines-Cloud-cloud.html.md) -* [Automatic Kubernetes cluster upgrade on 3Engines Cloud 3Engines Magnum](Automatic-Kubernetes-cluster-upgrade-on-3Engines-Cloud-3Engines-Magnum.html.md) +* [Using Kubernetes Ingress on connectVM Cloud connectVM Magnum](Using-Kubernetes-Ingress-on-connectVM-Cloud-connectVM-Magnum.html.md) +* [Deploying Helm Charts on Magnum Kubernetes Clusters on connectVM Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md) +* [Deploying HTTPS Services on Magnum Kubernetes in connectVM Cloud Cloud](Deploying-HTTPS-Services-on-Magnum-Kubernetes-in-connectVM-Cloud-Cloud.html.md) +* [Installing JupyterHub on Magnum Kubernetes Cluster in connectVM Cloud Cloud](Installing-JupyterHub-on-Magnum-Kubernetes-cluster-in-connectVM-Cloud-cloud.html.md) +* [Install and run Argo Workflows on connectVM Cloud Magnum Kubernetes](Install-and-run-Argo-Workflows-on-connectVM-Cloud-Magnum-Kubernetes.html.md) +* [Installing HashiCorp Vault on connectVM Cloud Magnum](Installing-HashiCorp-Vault-on-connectVM-Cloud-Magnum.html.md) +* [HTTP Request-based Autoscaling on K8S using Prometheus and Keda on connectVM Cloud](HTTP-Request-based-Autoscaling-on-K8S-using-Prometheus-and-Keda-on-connectVM-Cloud.html.md) +* [Create and access NFS server from Kubernetes on connectVM Cloud](Create-and-access-NFS-server-from-Kubernetes-on-connectVM-Cloud.html.md) +* [Deploy Keycloak on Kubernetes with a sample app on connectVM Cloud](Deploy-Keycloak-on-Kubernetes-with-a-sample-app-on-connectVM-Cloud.html.md) +* [Install and run Dask on a Kubernetes cluster in connectVM Cloud cloud](Install-and-run-Dask-on-a-Kubernetes-cluster-in-connectVM-Cloud-cloud.html.md) +* [Install and run NooBaa on Kubernetes cluster in single- and multicloud-environment on connectVM Cloud](Install-and-run-NooBaa-on-Kubernetes-cluster-in-single-and-multicloud-environment-on-connectVM-Cloud.html.md) +* [Private container registries with Harbor on connectVM Cloud Kubernetes](Private-container-registries-with-Harbor-on-connectVM-Cloud-Kubernetes.html.md) +* [Deploying vGPU workloads on connectVM Cloud Kubernetes](Deploying-vGPU-workloads-on-connectVM-Cloud-Kubernetes.html.md) +* [Kubernetes cluster observability with Prometheus and Grafana on connectVM Cloud](Kubernetes-cluster-observability-with-Prometheus-and-Grafana-on-connectVM-Cloud.html.md) +* [Enable Kubeapps app launcher on connectVM Cloud Magnum Kubernetes cluster](Enable-Kubeapps-app-launcher-on-connectVM-Cloud-Magnum-Kubernetes-cluster.html.md) +* [Install GitLab on connectVM Cloud Kubernetes](Install-GitLab-on-connectVM-Cloud-Kubernetes.html.md) +* [Sealed Secrets on connectVM Cloud Kubernetes](Sealed-Secrets-on-connectVM-Cloud-Kubernetes.html.md) +* [CI/CD pipelines with GitLab on connectVM Cloud Kubernetes - building a Docker image](CICD-pipelines-with-GitLab-on-connectVM-Cloud-Kubernetes-building-a-Docker-image.html.md) +* [How to create Kubernetes cluster using Terraform on connectVM Cloud](How-to-create-Kubernetes-cluster-using-Terraform-on-connectVM-Cloud.html.md) +* [GitOps with Argo CD on connectVM Cloud Kubernetes](GitOps-with-Argo-CD-on-connectVM-Cloud-Kubernetes.html.md) +* [Configuring IP Whitelisting for connectVM Load Balancer using Horizon and CLI on connectVM Cloud](Configuring-IP-Whitelisting-for-connectVM-Load-Balancer-using-Horizon-and-CLI-on-connectVM-Cloud.html.md) +* [Configuring IP Whitelisting for connectVM Load Balancer using Terraform on connectVM Cloud](Configuring-IP-Whitelisting-for-connectVM-Load-Balancer-using-Terraform-on-connectVM-Cloud.html.md) +* [Implementing IP Whitelisting for Load Balancers with Security Groups on connectVM Cloud](Implementing-IP-Whitelisting-for-Load-Balancers-with-Security-Groups-on-connectVM-Cloud.html.md) +* [How to install Rancher RKE2 Kubernetes on connectVM Cloud](How-to-install-Rancher-RKE2-Kubernetes-on-connectVM-Cloud-cloud.html.md) +* [Automatic Kubernetes cluster upgrade on connectVM Cloud connectVM Magnum](Automatic-Kubernetes-cluster-upgrade-on-connectVM-Cloud-connectVM-Magnum.html.md) diff --git a/docs/networking/Cannot-access-VM-with-SSH-or-PING-on-3Engines-Cloud.html.md b/docs/networking/Cannot-access-VM-with-SSH-or-PING-on-connectVM-Cloud.html.md similarity index 78% rename from docs/networking/Cannot-access-VM-with-SSH-or-PING-on-3Engines-Cloud.html.md rename to docs/networking/Cannot-access-VM-with-SSH-or-PING-on-connectVM-Cloud.html.md index e50ef23..8d19490 100644 --- a/docs/networking/Cannot-access-VM-with-SSH-or-PING-on-3Engines-Cloud.html.md +++ b/docs/networking/Cannot-access-VM-with-SSH-or-PING-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -Cannot access VM with SSH or PING on 3Engines Cloud[🔗](#cannot-access-vm-with-ssh-or-ping-on-brand-name "Permalink to this headline") +Cannot access VM with SSH or PING on connectVM Cloud[🔗](#cannot-access-vm-with-ssh-or-ping-on-brand-name "Permalink to this headline") ======================================================================================================================================= Before contacting the Support, please make sure that the port 22 (SSH) is allowed in the Security Groups associated with your instance. If this is configured correctly, please try to perform a soft or hard reboot of your VM. Lack of connection could have been caused by the expired DHCP. Rebooting will allow you to get a fresh DHCP session and everything should work fine. \ No newline at end of file diff --git a/docs/networking/Cannot-ping-VM-on-3Engines-Cloud.html.md b/docs/networking/Cannot-ping-VM-on-connectVM-Cloud.html.md similarity index 90% rename from docs/networking/Cannot-ping-VM-on-3Engines-Cloud.html.md rename to docs/networking/Cannot-ping-VM-on-connectVM-Cloud.html.md index 79ec84f..3d75759 100644 --- a/docs/networking/Cannot-ping-VM-on-3Engines-Cloud.html.md +++ b/docs/networking/Cannot-ping-VM-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -Cannot ping VM on 3Engines Cloud[🔗](#cannot-ping-vm-on-brand-name "Permalink to this headline") +Cannot ping VM on connectVM Cloud[🔗](#cannot-ping-vm-on-brand-name "Permalink to this headline") ================================================================================================= If you have problems with access to your VM - ping is not responding. Try the following: diff --git a/docs/networking/Generating-a-SSH-keypair-in-Linux-on-3Engines-Cloud.html.md b/docs/networking/Generating-a-SSH-keypair-in-Linux-on-connectVM-Cloud.html.md similarity index 92% rename from docs/networking/Generating-a-SSH-keypair-in-Linux-on-3Engines-Cloud.html.md rename to docs/networking/Generating-a-SSH-keypair-in-Linux-on-connectVM-Cloud.html.md index 1ae16f1..86d1281 100644 --- a/docs/networking/Generating-a-SSH-keypair-in-Linux-on-3Engines-Cloud.html.md +++ b/docs/networking/Generating-a-SSH-keypair-in-Linux-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -Generating an SSH keypair in Linux on 3Engines Cloud[🔗](#generating-an-ssh-keypair-in-linux-on-brand-name "Permalink to this headline") +Generating an SSH keypair in Linux on connectVM Cloud[🔗](#generating-an-ssh-keypair-in-linux-on-brand-name "Permalink to this headline") ========================================================================================================================================= In order to generate an SSH keypair in Linux, we recommend using the command **ssh-keygen**. diff --git a/docs/networking/How-can-I-access-my-VMs-using-names-instead-of-IP-addresses-on-3Engines-Cloud.html.md b/docs/networking/How-can-I-access-my-VMs-using-names-instead-of-IP-addresses-on-connectVM-Cloud.html.md similarity index 87% rename from docs/networking/How-can-I-access-my-VMs-using-names-instead-of-IP-addresses-on-3Engines-Cloud.html.md rename to docs/networking/How-can-I-access-my-VMs-using-names-instead-of-IP-addresses-on-connectVM-Cloud.html.md index e4c58aa..24444d8 100644 --- a/docs/networking/How-can-I-access-my-VMs-using-names-instead-of-IP-addresses-on-3Engines-Cloud.html.md +++ b/docs/networking/How-can-I-access-my-VMs-using-names-instead-of-IP-addresses-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How can I access my VMs using names instead of IP addresses on 3Engines Cloud[🔗](#how-can-i-access-my-vms-using-names-instead-of-ip-addresses-on-brand-name "Permalink to this headline") +How can I access my VMs using names instead of IP addresses on connectVM Cloud[🔗](#how-can-i-access-my-vms-using-names-instead-of-ip-addresses-on-brand-name "Permalink to this headline") =========================================================================================================================================================================================== The VMs are seen simultaneously in several networks, at least in your “private” LAN and in the public Internet. By default the public addresses (Floating IPs, 185.48.x.x) have no associated names. You may assign such names from your DNS domain or you may request a name from us (as an additional service). The names provided by us have the following format: diff --git a/docs/networking/How-can-I-open-new-ports-port-80-for-http-for-my-service-or-instance-on-3Engines-Cloud.html.md b/docs/networking/How-can-I-open-new-ports-port-80-for-http-for-my-service-or-instance-on-connectVM-Cloud.html.md similarity index 87% rename from docs/networking/How-can-I-open-new-ports-port-80-for-http-for-my-service-or-instance-on-3Engines-Cloud.html.md rename to docs/networking/How-can-I-open-new-ports-port-80-for-http-for-my-service-or-instance-on-connectVM-Cloud.html.md index 8a1ccfa..ee4cd77 100644 --- a/docs/networking/How-can-I-open-new-ports-port-80-for-http-for-my-service-or-instance-on-3Engines-Cloud.html.md +++ b/docs/networking/How-can-I-open-new-ports-port-80-for-http-for-my-service-or-instance-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How can I open new ports for http for my service or instance on 3Engines Cloud[🔗](#how-can-i-open-new-ports-for-http-for-my-service-or-instance-on-brand-name "Permalink to this headline") +How can I open new ports for http for my service or instance on connectVM Cloud[🔗](#how-can-i-open-new-ports-for-http-for-my-service-or-instance-on-brand-name "Permalink to this headline") ============================================================================================================================================================================================= To open a new port for a service on an instance, click Project -> Network -> Security Groups and click “Create Security Group”. diff --git a/docs/networking/How-is-my-VM-visible-in-the-internet-with-no-Floating-IP-attached-on-3Engines-Cloud.html.md b/docs/networking/How-is-my-VM-visible-in-the-internet-with-no-Floating-IP-attached-on-connectVM-Cloud.html.md similarity index 91% rename from docs/networking/How-is-my-VM-visible-in-the-internet-with-no-Floating-IP-attached-on-3Engines-Cloud.html.md rename to docs/networking/How-is-my-VM-visible-in-the-internet-with-no-Floating-IP-attached-on-connectVM-Cloud.html.md index 67aa253..212e9cc 100644 --- a/docs/networking/How-is-my-VM-visible-in-the-internet-with-no-Floating-IP-attached-on-3Engines-Cloud.html.md +++ b/docs/networking/How-is-my-VM-visible-in-the-internet-with-no-Floating-IP-attached-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How is my VM visible in the internet with no Floating IP attached on 3Engines Cloud[🔗](#how-is-my-vm-visible-in-the-internet-with-no-floating-ip-attached-on-brand-name "Permalink to this headline") +How is my VM visible in the internet with no Floating IP attached on connectVM Cloud[🔗](#how-is-my-vm-visible-in-the-internet-with-no-floating-ip-attached-on-brand-name "Permalink to this headline") ======================================================================================================================================================================================================= This article is written for clarification how an instance without a floating IP address would respond if we were to search for it it from an external machine. @@ -28,4 +28,4 @@ Yes. If you want to send data from your VM to an external server, you should als Is my VM accessible from the outside without floating IP?[🔗](#is-my-vm-accessible-from-the-outside-without-floating-ip "Permalink to this headline") ---------------------------------------------------------------------------------------------------------------------------------------------------- -No. If a VM needs to be accessible from the Internet, a floating IP address must be attached to the instance. For more information on assigning Floating IPs to the instance, please see the following article: [How to Add or Remove Floating IP’s to your VM on 3Engines Cloud](How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md). \ No newline at end of file +No. If a VM needs to be accessible from the Internet, a floating IP address must be attached to the instance. For more information on assigning Floating IPs to the instance, please see the following article: [How to Add or Remove Floating IP’s to your VM on connectVM Cloud](How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md). \ No newline at end of file diff --git a/docs/networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md b/docs/networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md similarity index 81% rename from docs/networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md rename to docs/networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md index ba73a41..71817fa 100644 --- a/docs/networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md +++ b/docs/networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -How to Add or Remove Floating IP’s to your VM on 3Engines Cloud[🔗](#how-to-add-or-remove-floating-ips-to-your-vm-on-brand-name "Permalink to this headline") +How to Add or Remove Floating IP’s to your VM on connectVM Cloud[🔗](#how-to-add-or-remove-floating-ips-to-your-vm-on-brand-name "Permalink to this headline") ============================================================================================================================================================== -In order to make your VM accessible from the Internet, you need to use Floating IPs. Floating IPs in 3Engines are public IP addresses assigned to your Virtual Machines. Assignment of a Floating IP allows you (if you have your Security Groups set properly) to host services like SSH or HTTP over the Internet. +In order to make your VM accessible from the Internet, you need to use Floating IPs. Floating IPs in connectVM are public IP addresses assigned to your Virtual Machines. Assignment of a Floating IP allows you (if you have your Security Groups set properly) to host services like SSH or HTTP over the Internet. How to assign a Floating IP to your VM?[🔗](#how-to-assign-a-floating-ip-to-your-vm "Permalink to this headline") ---------------------------------------------------------------------------------------------------------------- @@ -59,9 +59,9 @@ If you no longer need a public IP address you may disassociate it from your VM. How to release a Floating IP (return it to the pool)?[🔗](#how-to-release-a-floating-ip-return-it-to-the-pool "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------------------------------ -Floating IPs (just like any other 3Engines resource) have their cost when kept reserved and not used. +Floating IPs (just like any other connectVM resource) have their cost when kept reserved and not used. -If you don’t want to keep your Floating IP’s reserved for your project you may release them to the 3Engines pool for other users which will also reduce the costs of your project. +If you don’t want to keep your Floating IP’s reserved for your project you may release them to the connectVM pool for other users which will also reduce the costs of your project. Go to Project → Network → Floating IPs diff --git a/docs/networking/How-to-Import-SSH-Public-Key-to-3Engines-Horizon-on-3Engines-Cloud.html.md b/docs/networking/How-to-Import-SSH-Public-Key-to-connectVM-Horizon-on-connectVM-Cloud.html.md similarity index 73% rename from docs/networking/How-to-Import-SSH-Public-Key-to-3Engines-Horizon-on-3Engines-Cloud.html.md rename to docs/networking/How-to-Import-SSH-Public-Key-to-connectVM-Horizon-on-connectVM-Cloud.html.md index 5c543b6..25f4057 100644 --- a/docs/networking/How-to-Import-SSH-Public-Key-to-3Engines-Horizon-on-3Engines-Cloud.html.md +++ b/docs/networking/How-to-Import-SSH-Public-Key-to-connectVM-Horizon-on-connectVM-Cloud.html.md @@ -1,13 +1,13 @@ -How to import SSH public key to 3Engines Horizon on 3Engines Cloud[🔗](#how-to-import-ssh-public-key-to-3Engines-horizon-on-brand-name "Permalink to this headline") +How to import SSH public key to connectVM Horizon on connectVM Cloud[🔗](#how-to-import-ssh-public-key-to-connectVM-horizon-on-brand-name "Permalink to this headline") ======================================================================================================================================================================= If you already have an SSH key pair on your computer, you can import your public key to the Horizon dashboard. Then, you will be able to use that imported key when launching a new instance. -By importing it directly to Horizon, you will eliminate the need to use tools like **ssh-copy-id** or manually edit the **authorized\_keys** file. Also, your key will be available in 3Engines CLI. +By importing it directly to Horizon, you will eliminate the need to use tools like **ssh-copy-id** or manually edit the **authorized\_keys** file. Also, your key will be available in connectVM CLI. Warning -After uploading your public key, you will not be able to apply it to an already created virtual machine. If you need to add a key to an existing VM, please follow this article instead: [How to add SSH key from Horizon web console on 3Engines Cloud](How-to-add-SSH-key-from-Horizon-web-console-on-3Engines-Cloud.html.md). +After uploading your public key, you will not be able to apply it to an already created virtual machine. If you need to add a key to an existing VM, please follow this article instead: [How to add SSH key from Horizon web console on connectVM Cloud](How-to-add-SSH-key-from-Horizon-web-console-on-connectVM-Cloud.html.md). Note @@ -24,7 +24,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Generated SSH key pair** diff --git a/docs/networking/How-to-add-SSH-key-from-Horizon-web-console-on-3Engines-Cloud.html.md b/docs/networking/How-to-add-SSH-key-from-Horizon-web-console-on-connectVM-Cloud.html.md similarity index 89% rename from docs/networking/How-to-add-SSH-key-from-Horizon-web-console-on-3Engines-Cloud.html.md rename to docs/networking/How-to-add-SSH-key-from-Horizon-web-console-on-connectVM-Cloud.html.md index 05b9586..75e23db 100644 --- a/docs/networking/How-to-add-SSH-key-from-Horizon-web-console-on-3Engines-Cloud.html.md +++ b/docs/networking/How-to-add-SSH-key-from-Horizon-web-console-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How to add SSH key from Horizon web console on 3Engines Cloud[🔗](#how-to-add-ssh-key-from-horizon-web-console-on-brand-name "Permalink to this headline") +How to add SSH key from Horizon web console on connectVM Cloud[🔗](#how-to-add-ssh-key-from-horizon-web-console-on-brand-name "Permalink to this headline") =========================================================================================================================================================== While using web console on your VM, you may face situation when you will have to enter SSH public key. diff --git a/docs/networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-3Engines-Cloud.html.md b/docs/networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-connectVM-Cloud.html.md similarity index 85% rename from docs/networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-3Engines-Cloud.html.md rename to docs/networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-connectVM-Cloud.html.md index 396432d..0a3d36b 100644 --- a/docs/networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-3Engines-Cloud.html.md +++ b/docs/networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How to connect to your virtual machine via SSH in Linux on 3Engines Cloud[🔗](#how-to-connect-to-your-virtual-machine-via-ssh-in-linux-on-brand-name "Permalink to this headline") +How to connect to your virtual machine via SSH in Linux on connectVM Cloud[🔗](#how-to-connect-to-your-virtual-machine-via-ssh-in-linux-on-brand-name "Permalink to this headline") =================================================================================================================================================================================== **1. Prerequisites:** @@ -13,7 +13,7 @@ For example, when you create an SSH key named “**testkey**” in the Horizon d **2. Connecting to a virtual machine via SSH:** -2.1. If your virtual machine has already been assigned a Floating IP (the instances menu next to your virtual machine lists the IP address) you can proceed to the next step. If not, please follow the guide: [How to Add or Remove Floating IP’s to your VM on 3Engines Cloud](How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md). +2.1. If your virtual machine has already been assigned a Floating IP (the instances menu next to your virtual machine lists the IP address) you can proceed to the next step. If not, please follow the guide: [How to Add or Remove Floating IP’s to your VM on connectVM Cloud](How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md). 2.2. Go to the **~/.ssh** folder where your SSH keys were saved to. Start your terminal (right click and click “Open in Terminal”). diff --git a/docs/networking/How-to-create-a-network-with-router-in-Horizon-Dashboard-on-3Engines-Cloud.html.md b/docs/networking/How-to-create-a-network-with-router-in-Horizon-Dashboard-on-connectVM-Cloud.html.md similarity index 87% rename from docs/networking/How-to-create-a-network-with-router-in-Horizon-Dashboard-on-3Engines-Cloud.html.md rename to docs/networking/How-to-create-a-network-with-router-in-Horizon-Dashboard-on-connectVM-Cloud.html.md index a1a13d9..44c7827 100644 --- a/docs/networking/How-to-create-a-network-with-router-in-Horizon-Dashboard-on-3Engines-Cloud.html.md +++ b/docs/networking/How-to-create-a-network-with-router-in-Horizon-Dashboard-on-connectVM-Cloud.html.md @@ -1,9 +1,9 @@ -How to create a network with router in Horizon Dashboard on 3Engines Cloud[🔗](#how-to-create-a-network-with-router-in-horizon-dashboard-on-brand-name "Permalink to this headline") +How to create a network with router in Horizon Dashboard on connectVM Cloud[🔗](#how-to-create-a-network-with-router-in-horizon-dashboard-on-brand-name "Permalink to this headline") ===================================================================================================================================================================================== When you create a new project in Horizon, its content is empty. You have to manually configure your private network. In order to complete this task, please follow those steps. -1. Log in to your 3Engines dashboard and choose **Network** tab, then choose **Networks** sub-label. +1. Log in to your connectVM dashboard and choose **Network** tab, then choose **Networks** sub-label. ![net1.png](../_images/net1.png) diff --git a/docs/networking/How-to-run-and-configure-Firewall-as-a-service-and-VPN-as-a-service-on-3Engines-Cloud.html.md b/docs/networking/How-to-run-and-configure-Firewall-as-a-service-and-VPN-as-a-service-on-connectVM-Cloud.html.md similarity index 95% rename from docs/networking/How-to-run-and-configure-Firewall-as-a-service-and-VPN-as-a-service-on-3Engines-Cloud.html.md rename to docs/networking/How-to-run-and-configure-Firewall-as-a-service-and-VPN-as-a-service-on-connectVM-Cloud.html.md index 737a6ae..ae2f77d 100644 --- a/docs/networking/How-to-run-and-configure-Firewall-as-a-service-and-VPN-as-a-service-on-3Engines-Cloud.html.md +++ b/docs/networking/How-to-run-and-configure-Firewall-as-a-service-and-VPN-as-a-service-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How to run and configure Firewall as a service and VPN as a service on 3Engines Cloud[🔗](#how-to-run-and-configure-firewall-as-a-service-and-vpn-as-a-service-on-brand-name "Permalink to this headline") +How to run and configure Firewall as a service and VPN as a service on connectVM Cloud[🔗](#how-to-run-and-configure-firewall-as-a-service-and-vpn-as-a-service-on-brand-name "Permalink to this headline") =========================================================================================================================================================================================================== Note @@ -12,7 +12,7 @@ The sequence of steps will be described below. **Creating and configuring local networks** -1. Log in to your 3Engines dashboard and choose **Network** tab, then choose **Networks** sub-label. +1. Log in to your connectVM dashboard and choose **Network** tab, then choose **Networks** sub-label. ![screen1.png](../_images/screen1.png) @@ -145,7 +145,7 @@ Choose **launch instance**. **Configuring VPN service** -Prerequisities: For configuring your VPN server using Graphical Interface you need a VM with preinstalled GUI (for example MINT, XFCE etc.) and connected to **Internal** network. Click here for instructions how to install GUI on Ubuntu 20.04 VM: [How to Use GUI in Linux VM on 3Engines Cloud and access it From Local Linux Computer](../cloud/How-to-use-GUI-in-Linux-VM-on-3Engines-Cloud-and-access-it-from-local-Linux-computer.html.md). +Prerequisities: For configuring your VPN server using Graphical Interface you need a VM with preinstalled GUI (for example MINT, XFCE etc.) and connected to **Internal** network. Click here for instructions how to install GUI on Ubuntu 20.04 VM: [How to Use GUI in Linux VM on connectVM Cloud and access it From Local Linux Computer](../cloud/How-to-use-GUI-in-Linux-VM-on-connectVM-Cloud-and-access-it-from-local-Linux-computer.html.md). 27. In your default WEB browser open IP **10.200.200.1**. diff --git a/docs/networking/networking.html.md b/docs/networking/networking.html.md index c1d1167..9ffc2cb 100644 --- a/docs/networking/networking.html.md +++ b/docs/networking/networking.html.md @@ -2,15 +2,15 @@ ## Available Documentation -* [How can I access my VMs using names instead of IP addresses on 3Engines Cloud](How-can-I-access-my-VMs-using-names-instead-of-IP-addresses-on-3Engines-Cloud.html.md) -* [How to Add or Remove Floating IP’s to your VM on 3Engines Cloud](How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md) -* [Cannot access VM with SSH or PING on 3Engines Cloud](Cannot-access-VM-with-SSH-or-PING-on-3Engines-Cloud.html.md) -* [Cannot ping VM on 3Engines Cloud](Cannot-ping-VM-on-3Engines-Cloud.html.md) -* [How to connect to your virtual machine via SSH in Linux on 3Engines Cloud](How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-3Engines-Cloud.html.md) -* [How to create a network with router in Horizon Dashboard on 3Engines Cloud](How-to-create-a-network-with-router-in-Horizon-Dashboard-on-3Engines-Cloud.html.md) -* [How can I open new ports for http for my service or instance on 3Engines Cloud](How-can-I-open-new-ports-port-80-for-http-for-my-service-or-instance-on-3Engines-Cloud.html.md) -* [Generating an SSH keypair in Linux on 3Engines Cloud](Generating-a-SSH-keypair-in-Linux-on-3Engines-Cloud.html.md) -* [How to add SSH key from Horizon web console on 3Engines Cloud](How-to-add-SSH-key-from-Horizon-web-console-on-3Engines-Cloud.html.md) -* [How is my VM visible in the internet with no Floating IP attached on 3Engines Cloud](How-is-my-VM-visible-in-the-internet-with-no-Floating-IP-attached-on-3Engines-Cloud.html.md) -* [How to run and configure Firewall as a service and VPN as a service on 3Engines Cloud](How-to-run-and-configure-Firewall-as-a-service-and-VPN-as-a-service-on-3Engines-Cloud.html.md) -* [How to import SSH public key to 3Engines Horizon on 3Engines Cloud](How-to-Import-SSH-Public-Key-to-3Engines-Horizon-on-3Engines-Cloud.html.md) +* [How can I access my VMs using names instead of IP addresses on connectVM Cloud](How-can-I-access-my-VMs-using-names-instead-of-IP-addresses-on-connectVM-Cloud.html.md) +* [How to Add or Remove Floating IP’s to your VM on connectVM Cloud](How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md) +* [Cannot access VM with SSH or PING on connectVM Cloud](Cannot-access-VM-with-SSH-or-PING-on-connectVM-Cloud.html.md) +* [Cannot ping VM on connectVM Cloud](Cannot-ping-VM-on-connectVM-Cloud.html.md) +* [How to connect to your virtual machine via SSH in Linux on connectVM Cloud](How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-connectVM-Cloud.html.md) +* [How to create a network with router in Horizon Dashboard on connectVM Cloud](How-to-create-a-network-with-router-in-Horizon-Dashboard-on-connectVM-Cloud.html.md) +* [How can I open new ports for http for my service or instance on connectVM Cloud](How-can-I-open-new-ports-port-80-for-http-for-my-service-or-instance-on-connectVM-Cloud.html.md) +* [Generating an SSH keypair in Linux on connectVM Cloud](Generating-a-SSH-keypair-in-Linux-on-connectVM-Cloud.html.md) +* [How to add SSH key from Horizon web console on connectVM Cloud](How-to-add-SSH-key-from-Horizon-web-console-on-connectVM-Cloud.html.md) +* [How is my VM visible in the internet with no Floating IP attached on connectVM Cloud](How-is-my-VM-visible-in-the-internet-with-no-Floating-IP-attached-on-connectVM-Cloud.html.md) +* [How to run and configure Firewall as a service and VPN as a service on connectVM Cloud](How-to-run-and-configure-Firewall-as-a-service-and-VPN-as-a-service-on-connectVM-Cloud.html.md) +* [How to import SSH public key to connectVM Horizon on connectVM Cloud](How-to-Import-SSH-Public-Key-to-connectVM-Horizon-on-connectVM-Cloud.html.md) diff --git a/docs/openstackcli/3Enginescli.html.md b/docs/openstackcli/3Enginescli.html.md deleted file mode 100644 index 0913f27..0000000 --- a/docs/openstackcli/3Enginescli.html.md +++ /dev/null @@ -1,19 +0,0 @@ -# 3Engines CLI - -## Available Documentation - -* [How to Backup an Instance and Download it to the Desktop on 3Engines Cloud 3Engines Hosting](How-to-backup-an-instance-and-download-it-to-the-desktop-on-3Engines-Cloud.html.md) -* [How to create a set of VMs using 3Engines Heat Orchestration on 3Engines Cloud](How-to-create-a-set-of-VMs-using-3Engines-Heat-Orchestration-on-3Engines-Cloud.html.md) -* [How to Create and Configure New 3Engines Project Through Horizon on 3Engines Cloud Cloud](How-To-Create-and-Configure-New-Project-on-3Engines-Cloud-Cloud.html.md) -* [How to install 3EnginesClient for Linux on 3Engines Cloud](How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md) -* [How to install 3EnginesClient GitBash for Windows on 3Engines Cloud](How-to-install-3EnginesClient-GitBash-or-Cygwin-for-Windows-on-3Engines-Cloud.html.md) -* [How to share private container from object storage to another user on 3Engines Cloud](How-to-share-private-container-from-object-storage-to-another-user-on-3Engines-Cloud.html.md) -* [How to install 3EnginesClient on Windows using Windows Subsystem for Linux on 3Engines Cloud 3Engines Hosting](How-to-install-3EnginesClient-on-Windows-using-Windows-Subsystem-for-Linux-on-3Engines-Cloud-3Engines-Hosting.html.md) -* [How to move data volume between VMs using 3Engines CLI on 3Engines Cloud](How-to-move-data-volume-between-two-VMs-using-3Engines-CLI-on-3Engines-Cloud.html.md) -* [How to access object storage using 3Engines CLI on 3Engines Cloud](How-to-access-object-storage-using-3Engines-CLI-on-3Engines-Cloud.html.md) -* [How to transfer volumes between domains and projects using 3Engines CLI client on 3Engines Cloud](How-to-transfer-volumes-between-domains-and-projects-using-3Engines-CLI-client-on-3Engines-Cloud.html.md) -* [How to start a VM from instance snapshot using 3Engines CLI on 3Engines Cloud](How-to-start-a-VM-from-instance-snapshot-using-3Engines-CLI-on-3Engines-Cloud.html.md) -* [How to create instance snapshot using 3Engines CLI on 3Engines Cloud](How-to-create-instance-snapshot-using-3Engines-CLI-on-3Engines-Cloud.html.md) -* [Resizing a virtual machine using 3Engines CLI on 3Engines Cloud](Resizing-a-virtual-machine-using-3Engines-CLI-on-3Engines-Cloud.html.md) -* [Use backup command to create rotating backups of virtual machines on 3Engines Cloud cloud](Use-backup-command-to-create-rotating-backups-of-virtual-machines-on-3Engines-Cloud.html.md) -* [Use script to create daily weekly and monthly rotating backups of virtual machines on 3Engines Cloud](Use-script-to-create-daily-weekly-and-monthly-rotating-backups-of-virtual-machines-using-on-3Engines-Cloud.html.md) diff --git a/docs/openstackcli/How-To-Create-and-Configure-New-Project-on-3Engines-Cloud-Cloud.html.md b/docs/openstackcli/How-To-Create-and-Configure-New-Project-on-connectVM-Cloud-Cloud.html.md similarity index 84% rename from docs/openstackcli/How-To-Create-and-Configure-New-Project-on-3Engines-Cloud-Cloud.html.md rename to docs/openstackcli/How-To-Create-and-Configure-New-Project-on-connectVM-Cloud-Cloud.html.md index ed2a43f..b6aa277 100644 --- a/docs/openstackcli/How-To-Create-and-Configure-New-Project-on-3Engines-Cloud-Cloud.html.md +++ b/docs/openstackcli/How-To-Create-and-Configure-New-Project-on-connectVM-Cloud-Cloud.html.md @@ -1,17 +1,17 @@ -How to Create and Configure New 3Engines Project Through Horizon on 3Engines Cloud Cloud[🔗](#how-to-create-and-configure-new-3Engines-project-through-horizon-on-brand-name-cloud-name-cloud "Permalink to this headline") +How to Create and Configure New connectVM Project Through Horizon on connectVM Cloud Cloud[🔗](#how-to-create-and-configure-new-connectVM-project-through-horizon-on-brand-name-cloud-name-cloud "Permalink to this headline") ============================================================================================================================================================================================================================== Default elements of the account[🔗](#default-elements-of-the-account "Permalink to this headline") ------------------------------------------------------------------------------------------------- -When you first create your account at 3Engines Cloud hosting, default values for the account will be applied. Among others, you will +When you first create your account at connectVM Cloud hosting, default values for the account will be applied. Among others, you will > * become owner of a *tenant manager* account and > * have a default project created along with > * three networks and > * two security groups. -In 3Engines terminology, the role of **tenant manager** is to be an administrator of the account. As a tenant manager, you can +In connectVM terminology, the role of **tenant manager** is to be an administrator of the account. As a tenant manager, you can > * use the account directly but can also > * create other users od the account. @@ -30,21 +30,21 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . -No. 2 **Introduction to 3Engines Projects** +No. 2 **Introduction to connectVM Projects** -The article [What is an 3Engines project on 3Engines Cloud](../cloud/What-is-an-3Engines-project-on-3Engines-Cloud.html.md) will define basic elements of an 3Engines project – groups, projects, roles and so on. +The article [What is an connectVM project on connectVM Cloud](../cloud/What-is-an-connectVM-project-on-connectVM-Cloud.html.md) will define basic elements of an connectVM project – groups, projects, roles and so on. No. 3 **Security groups** -The article [How to use Security Groups in Horizon on 3Engines Cloud](../cloud/How-to-use-Security-Groups-in-Horizon-on-3Engines-Cloud.html.md) describes how to create and edit security groups. They enable ports through which the virtual machine communicates with other networks, in particular, with the Internet at large. +The article [How to use Security Groups in Horizon on connectVM Cloud](../cloud/How-to-use-Security-Groups-in-Horizon-on-connectVM-Cloud.html.md) describes how to create and edit security groups. They enable ports through which the virtual machine communicates with other networks, in particular, with the Internet at large. No. 4 **Create network with router** Here is how to create a network with router: -[How to create a network with router in Horizon Dashboard on 3Engines Cloud](../networking/How-to-create-a-network-with-router-in-Horizon-Dashboard-on-3Engines-Cloud.html.md) +[How to create a network with router in Horizon Dashboard on connectVM Cloud](../networking/How-to-create-a-network-with-router-in-Horizon-Dashboard-on-connectVM-Cloud.html.md) Default values in the tenant manager account[🔗](#default-values-in-the-tenant-manager-account "Permalink to this headline") --------------------------------------------------------------------------------------------------------------------------- @@ -161,9 +161,9 @@ What To Do Next[🔗](#what-to-do-next "Permalink to this headline") Your **testproject** is ready for creating new instances. For example, see articles: -[How to create a Linux VM and access it from Windows desktop on 3Engines Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md) +[How to create a Linux VM and access it from Windows desktop on connectVM Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-connectVM-Cloud.html.md) -[How to create a Linux VM and access it from Linux command line on 3Engines Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md) +[How to create a Linux VM and access it from Linux command line on connectVM Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md) If you want a new user to have access to **testproject**, the following articles will come handy: diff --git a/docs/openstackcli/How-to-access-object-storage-using-3Engines-CLI-on-3Engines-Cloud.html.md b/docs/openstackcli/How-to-access-object-storage-using-3Engines-CLI-on-3Engines-Cloud.html.md deleted file mode 100644 index 68107c8..0000000 --- a/docs/openstackcli/How-to-access-object-storage-using-3Engines-CLI-on-3Engines-Cloud.html.md +++ /dev/null @@ -1,49 +0,0 @@ -How to access object storage using 3Engines CLI on 3Engines Cloud[🔗](#how-to-access-object-storage-using-3Engines-cli-on-brand-name "Permalink to this headline") -===================================================================================================================================================================== - -Cloud computing offers the ability to handle large chunks of data, directly on the remote server. 3Engines module [Swift](https://docs.3Engines.org/swift/latest/) was created expressly to enable access to unstructured data that can grow without bounds, with the following design goals in mind : - -> * durability, -> * scalability, -> * concurrency across the entire data set, -> * all while keeping the API simple. - -**Swift** is installed as an independent module but on the syntax level, it is used through the parameters of **3Engines** command. - -What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") ---------------------------------------------------------------------------------------- - -> * How to install Swift -> * How to connect Swift to 3Engines cloud -> * Basic 3Engines operations with containers -> * Basic 3Engines operations with objects - -Prerequisites[🔗](#prerequisites "Permalink to this headline") -------------------------------------------------------------- - -No. 1 **Hosting** - -You need a 3Engines Cloud hosting account, available at . If you want to follow up with articles about object storage on Horizon, you will this link too: . - -No. 2 **Install or activate 3Engines command** - -To be able to connect to the cloud, **3Engines** command must be operational. If not installed already, use article [How to install 3EnginesClient for Linux on 3Engines Cloud](How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md) - -No. 3 **Authenticate to 3Engines using application credentials** - -Then you have to authenticate your account to the cloud. The usual way is to activate **3Engines** command using an RC file for on- or two-factor -authentication. That will not work in case of Swift module. It is authenticated with application credentials, as explained in article - -[How to generate or use Application Credentials via CLI on 3Engines Cloud](../cloud/How-to-generate-or-use-Application-Credentials-via-CLI-on-3Engines-Cloud.html.md). - -No. 4 **Familiarity with object storage on** 3Engines Cloud **3Engines** - -This article is explaining the basics, using the Horizon interface: - -[How to use Object Storage on 3Engines Cloud](../s3/How-to-use-Object-Storage-on-3Engines-Cloud.html.md). - -Swift can be understood as the CLI tool for accessing object storage under 3Engines. - -No. 5 **Python installed** - -The following articles contain sections on how to install Python: \ No newline at end of file diff --git a/docs/openstackcli/How-to-access-object-storage-using-connectVM-CLI-on-connectVM-Cloud.html.md b/docs/openstackcli/How-to-access-object-storage-using-connectVM-CLI-on-connectVM-Cloud.html.md new file mode 100644 index 0000000..de4a74b --- /dev/null +++ b/docs/openstackcli/How-to-access-object-storage-using-connectVM-CLI-on-connectVM-Cloud.html.md @@ -0,0 +1,49 @@ +How to access object storage using connectVM CLI on connectVM Cloud[🔗](#how-to-access-object-storage-using-connectVM-cli-on-brand-name "Permalink to this headline") +===================================================================================================================================================================== + +Cloud computing offers the ability to handle large chunks of data, directly on the remote server. connectVM module [Swift](https://docs.connectVM.org/swift/latest/) was created expressly to enable access to unstructured data that can grow without bounds, with the following design goals in mind : + +> * durability, +> * scalability, +> * concurrency across the entire data set, +> * all while keeping the API simple. + +**Swift** is installed as an independent module but on the syntax level, it is used through the parameters of **connectVM** command. + +What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") +--------------------------------------------------------------------------------------- + +> * How to install Swift +> * How to connect Swift to connectVM cloud +> * Basic connectVM operations with containers +> * Basic connectVM operations with objects + +Prerequisites[🔗](#prerequisites "Permalink to this headline") +------------------------------------------------------------- + +No. 1 **Hosting** + +You need a connectVM Cloud hosting account, available at . If you want to follow up with articles about object storage on Horizon, you will this link too: . + +No. 2 **Install or activate connectVM command** + +To be able to connect to the cloud, **connectVM** command must be operational. If not installed already, use article [How to install connectVMClient for Linux on connectVM Cloud](How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md) + +No. 3 **Authenticate to connectVM using application credentials** + +Then you have to authenticate your account to the cloud. The usual way is to activate **connectVM** command using an RC file for on- or two-factor +authentication. That will not work in case of Swift module. It is authenticated with application credentials, as explained in article + +[How to generate or use Application Credentials via CLI on connectVM Cloud](../cloud/How-to-generate-or-use-Application-Credentials-via-CLI-on-connectVM-Cloud.html.md). + +No. 4 **Familiarity with object storage on** connectVM Cloud **connectVM** + +This article is explaining the basics, using the Horizon interface: + +[How to use Object Storage on connectVM Cloud](../s3/How-to-use-Object-Storage-on-connectVM-Cloud.html.md). + +Swift can be understood as the CLI tool for accessing object storage under connectVM. + +No. 5 **Python installed** + +The following articles contain sections on how to install Python: \ No newline at end of file diff --git a/docs/openstackcli/How-to-backup-an-instance-and-download-it-to-the-desktop-on-3Engines-Cloud.html.md b/docs/openstackcli/How-to-backup-an-instance-and-download-it-to-the-desktop-on-connectVM-Cloud.html.md similarity index 66% rename from docs/openstackcli/How-to-backup-an-instance-and-download-it-to-the-desktop-on-3Engines-Cloud.html.md rename to docs/openstackcli/How-to-backup-an-instance-and-download-it-to-the-desktop-on-connectVM-Cloud.html.md index fe14b33..def468b 100644 --- a/docs/openstackcli/How-to-backup-an-instance-and-download-it-to-the-desktop-on-3Engines-Cloud.html.md +++ b/docs/openstackcli/How-to-backup-an-instance-and-download-it-to-the-desktop-on-connectVM-Cloud.html.md @@ -1,15 +1,15 @@ -How to Backup an Instance and Download it to the Desktop on 3Engines Cloud 3Engines Hosting[🔗](#how-to-backup-an-instance-and-download-it-to-the-desktop-on-brand-name-3Engines-hosting "Permalink to this headline") +How to Backup an Instance and Download it to the Desktop on connectVM Cloud connectVM Hosting[🔗](#how-to-backup-an-instance-and-download-it-to-the-desktop-on-brand-name-connectVM-hosting "Permalink to this headline") ========================================================================================================================================================================================================================= -First, you will need to setup the 3Engines CLI environment on the computer to which you want to download your instance. Depending on the operating system you are using, follow one of the links below: +First, you will need to setup the connectVM CLI environment on the computer to which you want to download your instance. Depending on the operating system you are using, follow one of the links below: -[How to install 3EnginesClient for Linux on 3Engines Cloud](How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md) +[How to install connectVMClient for Linux on connectVM Cloud](How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md) -[How to install 3EnginesClient GitBash for Windows on 3Engines Cloud](How-to-install-3EnginesClient-GitBash-or-Cygwin-for-Windows-on-3Engines-Cloud.html.md) +[How to install connectVMClient GitBash for Windows on connectVM Cloud](How-to-install-connectVMClient-GitBash-or-Cygwin-for-Windows-on-connectVM-Cloud.html.md) Assume that you are -> * logged into your 3Engines Cloud hosting account with Horizon interface and that +> * logged into your connectVM Cloud hosting account with Horizon interface and that > * you have created an instance called *vm-john-01*. ![backupinst1.png](../_images/backupinst1.png) @@ -20,7 +20,7 @@ List Instances in Your Project[🔗](#list-instances-in-your-project "Permalink List instances in your project using the following CLI command: ``` -user@ubuntu:~$ 3Engines server list +user@ubuntu:~$ connectVM server list ``` @@ -37,7 +37,7 @@ Create a Backup[🔗](#create-a-backup "Permalink to this headline") Now you can create a backup from command line interface (CLI) in the terminal (replace **72170eb7-cee4-41a3-beea-c7d208446130** with the ID of your instance): ``` -user@ubuntu:~$ 3Engines server backup create --name backup-01 72170eb7-cee4-41a3-beea-c7d208446130 +user@ubuntu:~$ connectVM server backup create --name backup-01 72170eb7-cee4-41a3-beea-c7d208446130 ``` @@ -46,18 +46,18 @@ Note You can also add the **–rotate** parameter to the above command if you want to have control over the number of stored backups: ``` -user@ubuntu:~$ 3Engines server backup create --name backup-01 --rotate 2 72170eb7-cee4-41a3-beea-c7d208446130 +user@ubuntu:~$ connectVM server backup create --name backup-01 --rotate 2 72170eb7-cee4-41a3-beea-c7d208446130 ``` -You can see the backup “backup-01” in +You can see the backup “backup-01” in ![backupinst2.png](../_images/backupinst2.png) or with CLI command: ``` -user@ubuntu:~$ 3Engines image list --private +user@ubuntu:~$ connectVM image list --private ``` @@ -78,7 +78,7 @@ Download the Backup File[🔗](#download-the-backup-file "Permalink to this head Disk image is a raw copy of the hard drive of your virtual machine. You can download it using the following command (replace **72170eb7-cee4-41a3-beea-c7d208446130** with the ID of your disk image): ``` -user@ubuntu:~$ 3Engines image save --file backup-on-the-desktop 747d720d-a6f4-4554-bf56-16183e5fb7fa +user@ubuntu:~$ connectVM image save --file backup-on-the-desktop 747d720d-a6f4-4554-bf56-16183e5fb7fa ``` @@ -102,6 +102,6 @@ On this panel you must insert image name, choose backup file and backup format. You can also use CLI commands to upload the backup file: ``` -user@ubuntu:~$ 3Engines image create --file path/to/backup +user@ubuntu:~$ connectVM image create --file path/to/backup ``` \ No newline at end of file diff --git a/docs/openstackcli/How-to-create-a-set-of-VMs-using-3Engines-Heat-Orchestration-on-3Engines-Cloud.html.md b/docs/openstackcli/How-to-create-a-set-of-VMs-using-connectVM-Heat-Orchestration-on-connectVM-Cloud.html.md similarity index 83% rename from docs/openstackcli/How-to-create-a-set-of-VMs-using-3Engines-Heat-Orchestration-on-3Engines-Cloud.html.md rename to docs/openstackcli/How-to-create-a-set-of-VMs-using-connectVM-Heat-Orchestration-on-connectVM-Cloud.html.md index c4dcab0..570ba5c 100644 --- a/docs/openstackcli/How-to-create-a-set-of-VMs-using-3Engines-Heat-Orchestration-on-3Engines-Cloud.html.md +++ b/docs/openstackcli/How-to-create-a-set-of-VMs-using-connectVM-Heat-Orchestration-on-connectVM-Cloud.html.md @@ -1,9 +1,9 @@ -How to create a set of VMs using 3Engines Heat Orchestration on 3Engines Cloud[🔗](#how-to-create-a-set-of-vms-using-3Engines-heat-orchestration-on-brand-name "Permalink to this headline") +How to create a set of VMs using connectVM Heat Orchestration on connectVM Cloud[🔗](#how-to-create-a-set-of-vms-using-connectVM-heat-orchestration-on-brand-name "Permalink to this headline") =============================================================================================================================================================================================== -Heat is an 3Engines component responsible for Orchestration. Its purpose is to deliver automation engine and optimize processes. +Heat is an connectVM component responsible for Orchestration. Its purpose is to deliver automation engine and optimize processes. -Heat receives commands through templates which are text files in *yaml* format. A template describes the entire infrastructure that you want to deploy. The deployed environment is called a *stack* and can consist of any combination out of the **102** different resources that are available in 3Engines. +Heat receives commands through templates which are text files in *yaml* format. A template describes the entire infrastructure that you want to deploy. The deployed environment is called a *stack* and can consist of any combination out of the **102** different resources that are available in connectVM. What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -20,20 +20,20 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Installed Python and its virtualenv** -If you want to use Heat through CLI commands, Python must be installed and its virtual environment activated. See article [How to install Python virtualenv or virtualenvwrapper on 3Engines Cloud](../cloud/How-to-install-Python-virtualenv-or-virtualenvwrapper-on-3Engines-Cloud.html.md). +If you want to use Heat through CLI commands, Python must be installed and its virtual environment activated. See article [How to install Python virtualenv or virtualenvwrapper on connectVM Cloud](../cloud/How-to-install-Python-virtualenv-or-virtualenvwrapper-on-connectVM-Cloud.html.md). -If you have never installed one of the 3Engines clients, see :[How To Install 3Engines and Magnum Clients for Command Line Interface to 3Engines Cloud Horizon](../kubernetes/How-To-Install-3Engines-and-Magnum-Clients-for-Command-Line-Interface-to-3Engines-Cloud-Horizon.html.md). +If you have never installed one of the connectVM clients, see :[How To Install connectVM and Magnum Clients for Command Line Interface to connectVM Cloud Horizon](../kubernetes/How-To-Install-connectVM-and-Magnum-Clients-for-Command-Line-Interface-to-connectVM-Cloud-Horizon.html.md). Always use the latest value of image id[🔗](#always-use-the-latest-value-of-image-id "Permalink to this headline") ----------------------------------------------------------------------------------------------------------------- -From time to time, the default images of operating systems in the 3Engines Cloud cloud are upgraded to the new versions. As a consequence, their **image id** will change. Let’s say that the image id for Ubuntu 20.04 LTS was **574fe1db-8099-4db4-a543-9e89526d20ae** at the time of writing of this article. While working through the article, you would normally take the **current** value of image id, and would use it to replace **574fe1db-8099-4db4-a543-9e89526d20ae** throughout the text. +From time to time, the default images of operating systems in the connectVM Cloud cloud are upgraded to the new versions. As a consequence, their **image id** will change. Let’s say that the image id for Ubuntu 20.04 LTS was **574fe1db-8099-4db4-a543-9e89526d20ae** at the time of writing of this article. While working through the article, you would normally take the **current** value of image id, and would use it to replace **574fe1db-8099-4db4-a543-9e89526d20ae** throughout the text. -Now, suppose you wanted to automate processes under 3Engines, perhaps using Heat, Terraform, Ansible or any other tool for 3Engines automation; if you use the value of **574fe1db-8099-4db4-a543-9e89526d20ae** for image id, it would remain **hardcoded** and once this value gets changed during the upgrade, the automated process may stop to execute. +Now, suppose you wanted to automate processes under connectVM, perhaps using Heat, Terraform, Ansible or any other tool for connectVM automation; if you use the value of **574fe1db-8099-4db4-a543-9e89526d20ae** for image id, it would remain **hardcoded** and once this value gets changed during the upgrade, the automated process may stop to execute. Warning @@ -82,7 +82,7 @@ Here are the basic elements of a Heat template: : Name of resource (you can type in anything on your own). **type** -: Definition of an 3Engines component (a comprehensive list is under **Orchestration** -> **Resource Types**) +: Definition of an connectVM component (a comprehensive list is under **Orchestration** -> **Resource Types**) **properties** : Required parameters for deploying a component. @@ -94,7 +94,7 @@ Your account will normally have a network starting with **cloud\_** but it may a How to get data for Heat template[🔗](#how-to-get-data-for-heat-template "Permalink to this headline") ----------------------------------------------------------------------------------------------------- -Templates need data for images, flavor networks, key pairs, security groups and so on. You would normally know all these elements in advance, or you could “look around” at various parts of 3Engines environment: +Templates need data for images, flavor networks, key pairs, security groups and so on. You would normally know all these elements in advance, or you could “look around” at various parts of connectVM environment: | | | | --- | --- | @@ -127,7 +127,7 @@ pip install python-heatclient To run a prepared template in order to deploy a stack, this is what a general command would look like: ``` -3Engines stack create -t template.yaml +connectVM stack create -t template.yaml ``` @@ -136,7 +136,7 @@ where **-t** assigns template for deployment and **** defines name fo As a result, a new Stack would be executed and a new instance would be created. For example, the command ``` -3Engines stack create -t template.yaml heat-test2 +connectVM stack create -t template.yaml heat-test2 ``` @@ -169,7 +169,7 @@ Enter the text of the template you copied from file **template.yaml** directly i ![select_template_yaml.png](../_images/select_template_yaml.png) -Provide a name of your stack and your 3Engines password: +Provide a name of your stack and your connectVM password: ![launch_stack.png](../_images/launch_stack.png) @@ -199,7 +199,7 @@ parameters: default: image_id: type: string - description: Image to be used. Check all available options in Horizon dashboard or, with CLI, use 3Engines image list command. + description: Image to be used. Check all available options in Horizon dashboard or, with CLI, use connectVM image list command. default: Ubuntu 18.04 LTS private_net_id: type: string @@ -279,12 +279,12 @@ The first step is to create a real volume (called VOL\_FAQ) and the second is to : Property to define a bootable Cinder volume for instance. **outputs** -: Additional information concerning deployed elements of the stack. In this case it returns a “show” attribute output. You can examine this kind of information by using 3Engines stack output list. Available attributes for every component [can be found here.](https://docs.3Engines.org/heat/latest/template_guide/3Engines.html.md). +: Additional information concerning deployed elements of the stack. In this case it returns a “show” attribute output. You can examine this kind of information by using connectVM stack output list. Available attributes for every component [can be found here.](https://docs.connectVM.org/heat/latest/template_guide/connectVM.html.md). Execute the template with the following command: ``` -3Engines stack create -t template4.yaml four +connectVM stack create -t template4.yaml four ``` diff --git a/docs/openstackcli/How-to-create-instance-snapshot-using-3Engines-CLI-on-3Engines-Cloud.html.md b/docs/openstackcli/How-to-create-instance-snapshot-using-connectVM-CLI-on-connectVM-Cloud.html.md similarity index 74% rename from docs/openstackcli/How-to-create-instance-snapshot-using-3Engines-CLI-on-3Engines-Cloud.html.md rename to docs/openstackcli/How-to-create-instance-snapshot-using-connectVM-CLI-on-connectVM-Cloud.html.md index 11e8b8a..809da5f 100644 --- a/docs/openstackcli/How-to-create-instance-snapshot-using-3Engines-CLI-on-3Engines-Cloud.html.md +++ b/docs/openstackcli/How-to-create-instance-snapshot-using-connectVM-CLI-on-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -How to create instance snapshot using 3Engines CLI on 3Engines Cloud[🔗](#how-to-create-instance-snapshot-using-3Engines-cli-on-brand-name "Permalink to this headline") +How to create instance snapshot using connectVM CLI on connectVM Cloud[🔗](#how-to-create-instance-snapshot-using-connectVM-cli-on-brand-name "Permalink to this headline") =========================================================================================================================================================================== -In this article, you will learn how to create instance snapshot on 3Engines Cloud cloud, using 3Engines CLI. +In this article, you will learn how to create instance snapshot on connectVM Cloud cloud, using connectVM CLI. Instance snapshots allow you to archive the state of the virtual machine. You can, then, use them for @@ -33,22 +33,22 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Ephemeral storage vs. persistent storage** -Please see article [Ephemeral vs Persistent storage option Create New Volume on 3Engines Cloud](../datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-3Engines-Cloud.html.md) to understand the basic difference between ephemeral and persistent types of storage in 3Engines. +Please see article [Ephemeral vs Persistent storage option Create New Volume on connectVM Cloud](../datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-connectVM-Cloud.html.md) to understand the basic difference between ephemeral and persistent types of storage in connectVM. No. 3 **Instance with ephemeral storage** -You need a virtual machine hosted on 3Engines Cloud cloud. +You need a virtual machine hosted on connectVM Cloud cloud. -You can create an instance with ephemeral storage by following this article: [How to create a VM using the 3Engines CLI client on 3Engines Cloud cloud](../cloud/How-to-create-a-VM-using-the-3Engines-CLI-client-on-3Engines-Cloud-cloud.html.md) +You can create an instance with ephemeral storage by following this article: [How to create a VM using the connectVM CLI client on connectVM Cloud cloud](../cloud/How-to-create-a-VM-using-the-connectVM-CLI-client-on-connectVM-Cloud-cloud.html.md) The actual command used to create an instance from that article was ``` -3Engines server create \ +connectVM server create \ --image Debian-custom-upload \ --flavor eo1.small \ --key-name ssh-key \ @@ -73,7 +73,7 @@ When creating an instance with persistent storage, you just add one new option t Make sure to enter the amount of storage sufficient for your needs. -You can also look at storage size available with your chosen virtual machine flavor for guidance (**3Engines flavor list** command, column **Disk**) +You can also look at storage size available with your chosen virtual machine flavor for guidance (**connectVM flavor list** command, column **Disk**) For instance, if you want your boot volume to have 16 GB, add the following: @@ -85,7 +85,7 @@ For instance, if you want your boot volume to have 16 GB, add the following: The complete command would, then, look like this: ``` -3Engines server create \ +connectVM server create \ --image Debian-custom-upload \ --flavor eo1.small \ --key-name ssh-key \ @@ -111,12 +111,12 @@ Otherwise, an instance can have two or more volumes attached to it, however, onl No. 5 **How to delete resources** -If you want to learn how to delete instances, snapshots, volumes and other 3Engines objects, please have a look at the following articles: +If you want to learn how to delete instances, snapshots, volumes and other connectVM objects, please have a look at the following articles: -/networking/How-to-correctly-delete-all-the-resources-in-the-project-via-3Engines-commandline-Clients-on-3Engines-Cloud. +/networking/How-to-correctly-delete-all-the-resources-in-the-project-via-connectVM-commandline-Clients-on-connectVM-Cloud. -[How to create or delete volume snapshot on 3Engines Cloud](../datavolume/How-to-create-or-delete-volume-snapshot-on-3Engines-Cloud.html.md). +[How to create or delete volume snapshot on connectVM Cloud](../datavolume/How-to-create-or-delete-volume-snapshot-on-connectVM-Cloud.html.md). -No. 6 **3Engines CLI client** +No. 6 **connectVM CLI client** -You need to have 3Engines CLI client installed. One of the following articles should help you: \ No newline at end of file +You need to have connectVM CLI client installed. One of the following articles should help you: \ No newline at end of file diff --git a/docs/openstackcli/How-to-install-3EnginesClient-GitBash-or-Cygwin-for-Windows-on-3Engines-Cloud.html.md b/docs/openstackcli/How-to-install-connectVMClient-GitBash-or-Cygwin-for-Windows-on-connectVM-Cloud.html.md similarity index 70% rename from docs/openstackcli/How-to-install-3EnginesClient-GitBash-or-Cygwin-for-Windows-on-3Engines-Cloud.html.md rename to docs/openstackcli/How-to-install-connectVMClient-GitBash-or-Cygwin-for-Windows-on-connectVM-Cloud.html.md index b3058bc..2da469e 100644 --- a/docs/openstackcli/How-to-install-3EnginesClient-GitBash-or-Cygwin-for-Windows-on-3Engines-Cloud.html.md +++ b/docs/openstackcli/How-to-install-connectVMClient-GitBash-or-Cygwin-for-Windows-on-connectVM-Cloud.html.md @@ -1,9 +1,9 @@ -How to install 3EnginesClient GitBash for Windows on 3Engines Cloud[🔗](#how-to-install-3Enginesclient-gitbash-for-windows-on-brand-name "Permalink to this headline") +How to install connectVMClient GitBash for Windows on connectVM Cloud[🔗](#how-to-install-connectVMclient-gitbash-for-windows-on-brand-name "Permalink to this headline") ========================================================================================================================================================================= -In this tutorial, you start with a standard Windows installation, then install the 3Engines CLI client and end up connecting to your project on 3Engines Cloud cloud. +In this tutorial, you start with a standard Windows installation, then install the connectVM CLI client and end up connecting to your project on connectVM Cloud cloud. -> For another way of installing 3Engines CLI on Windows, see article [How to install 3EnginesClient on Windows using Windows Subsystem for Linux on 3Engines Cloud 3Engines Hosting](How-to-install-3EnginesClient-on-Windows-using-Windows-Subsystem-for-Linux-on-3Engines-Cloud-3Engines-Hosting.html.md). However: +> For another way of installing connectVM CLI on Windows, see article [How to install connectVMClient on Windows using Windows Subsystem for Linux on connectVM Cloud connectVM Hosting](How-to-install-connectVMClient-on-Windows-using-Windows-Subsystem-for-Linux-on-connectVM-Cloud-connectVM-Hosting.html.md). However: * using Git Bash is simpler than using Windows Subsystem for Linux and is * providing a more straightforward access to your local file system. @@ -12,9 +12,9 @@ What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this --------------------------------------------------------------------------------------- > * Installing the required software (Python 3, PIP, Git for Windows and the appropriate compilers) -> * Creating an isolated Python environment for installing the 3Engines CLI client -> * Installing the 3Engines CLI client -> * Authenticating the 3Engines CLI client to the cloud +> * Creating an isolated Python environment for installing the connectVM CLI client +> * Installing the connectVM CLI client +> * Authenticating the connectVM CLI client to the cloud > * Executing a simple command to test whether the process was successful Prerequisites[🔗](#prerequisites "Permalink to this headline") @@ -22,7 +22,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . No. 2 **Computer running Microsoft Windows** @@ -38,14 +38,14 @@ You will need basic knowledge of Linux command line. No. 4 **RC file downloaded** -You need to download the RC file from your Horizon dashboard. To do that, follow section **How to download the RC file** of the following article: /gettingstarted/How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication. +You need to download the RC file from your Horizon dashboard. To do that, follow section **How to download the RC file** of the following article: /gettingstarted/How-to-activate-connectVM-CLI-access-to-connectVM-Cloud-cloud-using-one-or-two-factor-authentication. -This file must be present on the machine on which you intend to use the 3Engines CLI client. +This file must be present on the machine on which you intend to use the connectVM CLI client. Step 1: Download and Install Python[🔗](#step-1-download-and-install-python "Permalink to this headline") -------------------------------------------------------------------------------------------------------- -There are two ways of obtaining Python on 3Engines Cloud cloud: +There are two ways of obtaining Python on connectVM Cloud cloud: > * It may come preinstalled on virtual machines that were created using one of the default Windows images. > * You may download and install the latest version from the Internet. @@ -143,7 +143,7 @@ pip install -U requests[security] Step 4: Install Microsoft C++ Build Tools[🔗](#step-4-install-microsoft-c-build-tools "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------ -Microsoft C++ Build Tools are required to install the 3Engines CLI client using **pip** on Windows. +Microsoft C++ Build Tools are required to install the connectVM CLI client using **pip** on Windows. Enter the following website: @@ -161,7 +161,7 @@ The installation process might take a long time. Reboot your computer if the installer prompts you to do so. -Step 5: Install virtualenv and the 3Engines CLI client[🔗](#step-5-install-virtualenv-and-the-3Engines-cli-client "Permalink to this headline") +Step 5: Install virtualenv and the connectVM CLI client[🔗](#step-5-install-virtualenv-and-the-connectVM-cli-client "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------------------------------------ **virtualenv** allows you to perform Python operations in an isolated environment. In order to install it, open Git Bash if you previously closed it or rebooted your computer, and execute the following command: @@ -171,32 +171,32 @@ pip install virtualenv ``` -With **cd** command enter the directory in which you want to store the environment in which the 3Engines CLI client will be running. You will need it later on, so make it easily accessible, for example: +With **cd** command enter the directory in which you want to store the environment in which the connectVM CLI client will be running. You will need it later on, so make it easily accessible, for example: ``` cd C:/Users/Administrator ``` -Execute the following command to create the virtual environment **3Engines\_cli** which will be used for the 3Engines CLI client: +Execute the following command to create the virtual environment **connectVM\_cli** which will be used for the connectVM CLI client: ``` -virtualenv 3Engines_cli +virtualenv connectVM_cli ``` Note -You must supply the name of the environment (here, **3Engines\_cli**) but what it will be is completely up to you. +You must supply the name of the environment (here, **connectVM\_cli**) but what it will be is completely up to you. -A directory called **3Engines\_cli** should appear in the current folder. It will contain files needed for your isolated environment. In order to enter that environment, run **source** command on the **activate** file which is in the **Scripts** folder found in the folder with your virtual environment: +A directory called **connectVM\_cli** should appear in the current folder. It will contain files needed for your isolated environment. In order to enter that environment, run **source** command on the **activate** file which is in the **Scripts** folder found in the folder with your virtual environment: ``` -source 3Engines_cli/Scripts/activate +source connectVM_cli/Scripts/activate ``` -From now on, the name of your isolated environment - **3Engines\_cli** - will be in brackets before each command prompt, indicating that you are inside it. +From now on, the name of your isolated environment - **connectVM\_cli** - will be in brackets before each command prompt, indicating that you are inside it. ![git-bash12_creodias.png](../_images/git-bash12_creodias.png) @@ -216,7 +216,7 @@ Git Bash emulates UNIX-based systems so while you are in it, use forward slashes Step 6: Download and prepare jq[🔗](#step-6-download-and-prepare-jq "Permalink to this headline") ------------------------------------------------------------------------------------------------ -To authenticate the 3Engines CLI client in the next step, a program called **jq** will be needed. It is a JSON preprocessor, running from command line. To install, navigate to using your Internet browser. +To authenticate the connectVM CLI client in the next step, a program called **jq** will be needed. It is a JSON preprocessor, running from command line. To install, navigate to using your Internet browser. Download the latest 64-bit executable version of **jq** for Windows. @@ -231,17 +231,17 @@ mv jq.exe /usr/bin This should allow you to use **jq** with the RC file easily. -Step 7: Install and configure the 3Engines CLI client[🔗](#step-7-install-and-configure-the-3Engines-cli-client "Permalink to this headline") +Step 7: Install and configure the connectVM CLI client[🔗](#step-7-install-and-configure-the-connectVM-cli-client "Permalink to this headline") ---------------------------------------------------------------------------------------------------------------------------------------------- -Without leaving Git Bash, while still inside the **3Engines\_cli** virtual environment, execute the following command: +Without leaving Git Bash, while still inside the **connectVM\_cli** virtual environment, execute the following command: ``` -pip install python-3Enginesclient +pip install python-connectVMclient ``` -Wait until the process is completed. As the result, you will be able to run **3Engines** command on terminal prompt. It, however, won’t have access to the 3Engines Cloud cloud, so the next step is to authenticate to the cloud. +Wait until the process is completed. As the result, you will be able to run **connectVM** command on terminal prompt. It, however, won’t have access to the connectVM Cloud cloud, so the next step is to authenticate to the cloud. Navigate to the location of the RC file which you downloaded while following Prerequisite No. 4 and execute the **source** command on it. It could look like this (if the name of your RC file is **main-openrc.sh**): @@ -260,10 +260,10 @@ Here is what the two step process of authentication looks like for an RC file ca On the screenshot above, the username and project name were hidden for privacy reasons. -In order to test whether the 3Engines CLI client works, list virtual machines you currently operate. The command is: +In order to test whether the connectVM CLI client works, list virtual machines you currently operate. The command is: ``` -3Engines server list +connectVM server list ``` @@ -272,11 +272,11 @@ The output should contain a table containing virtual machines from your project. Reentering the Isolated Python Environment[🔗](#reentering-the-isolated-python-environment "Permalink to this headline") ----------------------------------------------------------------------------------------------------------------------- -To run the 3Engines CLI client again, say, after you might have closed the Git Bash window, or have had shut down or restarted Windows, you would have to repeat the same commands you entered above (replace **C:/Users/Administrator** with the path containing your **3Engines\_cli** folder). +To run the connectVM CLI client again, say, after you might have closed the Git Bash window, or have had shut down or restarted Windows, you would have to repeat the same commands you entered above (replace **C:/Users/Administrator** with the path containing your **connectVM\_cli** folder). ``` cd C:/Users/Administrator -source 3Engines_cli/Scripts/activate +source connectVM_cli/Scripts/activate ``` @@ -287,18 +287,18 @@ You can also create a batch file to automate reentering the Python environment. What To Do Next[🔗](#what-to-do-next "Permalink to this headline") ----------------------------------------------------------------- -The article [How To Install 3Engines and Magnum Clients for Command Line Interface to 3Engines Cloud Horizon](../kubernetes/How-To-Install-3Engines-and-Magnum-Clients-for-Command-Line-Interface-to-3Engines-Cloud-Horizon.html.md) will give you another procedure to install CLI and connect it to the cloud. It also contains several examples of using the CLI commands. +The article [How To Install connectVM and Magnum Clients for Command Line Interface to connectVM Cloud Horizon](../kubernetes/How-To-Install-connectVM-and-Magnum-Clients-for-Command-Line-Interface-to-connectVM-Cloud-Horizon.html.md) will give you another procedure to install CLI and connect it to the cloud. It also contains several examples of using the CLI commands. Other articles of interest: -[How to Create and Configure New 3Engines Project Through Horizon on 3Engines Cloud Cloud](How-To-Create-and-Configure-New-Project-on-3Engines-Cloud-Cloud.html.md) +[How to Create and Configure New connectVM Project Through Horizon on connectVM Cloud Cloud](How-To-Create-and-Configure-New-Project-on-connectVM-Cloud-Cloud.html.md) -[How to create a set of VMs using 3Engines Heat Orchestration on 3Engines Cloud](How-to-create-a-set-of-VMs-using-3Engines-Heat-Orchestration-on-3Engines-Cloud.html.md) +[How to create a set of VMs using connectVM Heat Orchestration on connectVM Cloud](How-to-create-a-set-of-VMs-using-connectVM-Heat-Orchestration-on-connectVM-Cloud.html.md) Using CLI interface for Kubernetes clusters: -[How To Use Command Line Interface for Kubernetes Clusters On 3Engines Cloud 3Engines Magnum](../kubernetes/How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-3Engines-Cloud-3Engines-Magnum.html.md) +[How To Use Command Line Interface for Kubernetes Clusters On connectVM Cloud connectVM Magnum](../kubernetes/How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-connectVM-Cloud-connectVM-Magnum.html.md) Also see -[How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md) \ No newline at end of file +[How to activate connectVM CLI access to connectVM Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-connectVM-CLI-access-to-connectVM-Cloud-cloud-using-one-or-two-factor-authentication.html.md) \ No newline at end of file diff --git a/docs/openstackcli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md b/docs/openstackcli/How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md similarity index 60% rename from docs/openstackcli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md rename to docs/openstackcli/How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md index 9e0cc44..bf0dff5 100644 --- a/docs/openstackcli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md +++ b/docs/openstackcli/How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -How to install 3EnginesClient for Linux on 3Engines Cloud[🔗](#how-to-install-3Enginesclient-for-linux-on-brand-name "Permalink to this headline") +How to install connectVMClient for Linux on connectVM Cloud[🔗](#how-to-install-connectVMclient-for-linux-on-brand-name "Permalink to this headline") ===================================================================================================================================================== -The 3Engines CLI client allows you to manage 3Engines environments using the command line interface. Its functions include: +The connectVM CLI client allows you to manage connectVM environments using the command line interface. Its functions include: > * Creating, starting, shutting down, shelving, deleting, rebooting virtual machines > * Assigning a floating IP to your virtual machine @@ -11,19 +11,19 @@ You can also automate these operations using scripts. This article covers two methods of installing this piece of software on Ubuntu. The first method should be more convenient and sufficient for most needs. The second method is for advanced use cases, such as: -> * keeping multiple versions of the 3Engines CLI client ready to use on the same computer or +> * keeping multiple versions of the connectVM CLI client ready to use on the same computer or > * needing more advanced features than what Ubuntu packages provide and -> * having to use the 3Engines CLI client on a Linux distribution which does not support the installation method described in the first method. +> * having to use the connectVM CLI client on a Linux distribution which does not support the installation method described in the first method. Prerequisites[🔗](#prerequisites "Permalink to this headline") ------------------------------------------------------------- No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . No. 2 **Linux installed on your computer** You need to have Linux installed on your local computer or a virtual machine. This article was written for Ubuntu 22.04 LTS and Python 3. Instructions for other Linux distributions might be different. -If you choose a virtual machine, you can run it yourself, or it can be, say, a virtual machine running on 3Engines Cloud cloud. If you choose this latter option, the following articles might be of help for you: \ No newline at end of file +If you choose a virtual machine, you can run it yourself, or it can be, say, a virtual machine running on connectVM Cloud cloud. If you choose this latter option, the following articles might be of help for you: \ No newline at end of file diff --git a/docs/openstackcli/How-to-install-3EnginesClient-on-Windows-using-Windows-Subsystem-for-Linux-on-3Engines-Cloud-3Engines-Hosting.html.md b/docs/openstackcli/How-to-install-connectVMClient-on-Windows-using-Windows-Subsystem-for-Linux-on-connectVM-Cloud-connectVM-Hosting.html.md similarity index 71% rename from docs/openstackcli/How-to-install-3EnginesClient-on-Windows-using-Windows-Subsystem-for-Linux-on-3Engines-Cloud-3Engines-Hosting.html.md rename to docs/openstackcli/How-to-install-connectVMClient-on-Windows-using-Windows-Subsystem-for-Linux-on-connectVM-Cloud-connectVM-Hosting.html.md index ec9846b..c3e3957 100644 --- a/docs/openstackcli/How-to-install-3EnginesClient-on-Windows-using-Windows-Subsystem-for-Linux-on-3Engines-Cloud-3Engines-Hosting.html.md +++ b/docs/openstackcli/How-to-install-connectVMClient-on-Windows-using-Windows-Subsystem-for-Linux-on-connectVM-Cloud-connectVM-Hosting.html.md @@ -1,7 +1,7 @@ -How to install 3EnginesClient on Windows using Windows Subsystem for Linux on 3Engines Cloud 3Engines Hosting[🔗](#how-to-install-3Enginesclient-on-windows-using-windows-subsystem-for-linux-on-brand-name-3Engines-hosting "Permalink to this headline") +How to install connectVMClient on Windows using Windows Subsystem for Linux on connectVM Cloud connectVM Hosting[🔗](#how-to-install-connectVMclient-on-windows-using-windows-subsystem-for-linux-on-brand-name-connectVM-hosting "Permalink to this headline") =============================================================================================================================================================================================================================================================== -In this tutorial, you will control your 3Engines environment in a deeper and more precise way using the CLI (Command Line Interface). Of course, you can use the Horizon GUI (Graphical User Interface) running in your browser, but the CLI includes additional features like the ability to use scripts for more automated management of your environment. +In this tutorial, you will control your connectVM environment in a deeper and more precise way using the CLI (Command Line Interface). Of course, you can use the Horizon GUI (Graphical User Interface) running in your browser, but the CLI includes additional features like the ability to use scripts for more automated management of your environment. The instructions for installing Windows Subsystem for Linux are based on the official Windows documentation found at . @@ -9,14 +9,14 @@ What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this --------------------------------------------------------------------------------------- > * Installing Windows Subsystem for Linux on Microsoft Windows -> * Installing the 3Engines CLI client and authenticating +> * Installing the connectVM CLI client and authenticating Prerequisites[🔗](#prerequisites "Permalink to this headline") ------------------------------------------------------------- No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . No. 2 **Computer running Microsoft Windows** @@ -28,7 +28,7 @@ Your computer must be running Microsoft Windows. This article is written for Win No. 3 **Optional – software for 2FA authentication** -Your account at 3Engines Cloud cloud may have two-factor authentication enabled. It means that apart from the usual username and password combination, you also need software to generate the TOTP – the six-digit code for the additional, second step of authentication. This article will provide additional technical details: [How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md). +Your account at connectVM Cloud cloud may have two-factor authentication enabled. It means that apart from the usual username and password combination, you also need software to generate the TOTP – the six-digit code for the additional, second step of authentication. This article will provide additional technical details: [How to activate connectVM CLI access to connectVM Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-connectVM-CLI-access-to-connectVM-Cloud-cloud-using-one-or-two-factor-authentication.html.md). Step 1: Check the version of Windows[🔗](#step-1-check-the-version-of-windows "Permalink to this headline") ---------------------------------------------------------------------------------------------------------- @@ -158,10 +158,10 @@ Wait for a short time. Eventually your Linux environment will be ready: ![wsl19_creodias.png](../_images/wsl19_creodias.png) -Step 3: Install 3Engines CLI in an isolated Python environment[🔗](#step-3-install-3Engines-cli-in-an-isolated-python-environment "Permalink to this headline") +Step 3: Install connectVM CLI in an isolated Python environment[🔗](#step-3-install-connectVM-cli-in-an-isolated-python-environment "Permalink to this headline") ---------------------------------------------------------------------------------------------------------------------------------------------------------------- -Now that you have installed Windows Subsystem on Linux running Ubuntu on your Windows computer, it is time to install 3Engines CLI. +Now that you have installed Windows Subsystem on Linux running Ubuntu on your Windows computer, it is time to install connectVM CLI. Update the software running on your Ubuntu: @@ -177,17 +177,17 @@ sudo apt install python3-venv ``` -Create a virtual environment in which you will have 3Engines CLI installed: +Create a virtual environment in which you will have connectVM CLI installed: ``` -python3 -m venv 3Engines_cli +python3 -m venv connectVM_cli ``` Enter your new virtual environment: ``` -source 3Engines_cli/bin/activate +source connectVM_cli/bin/activate ``` @@ -198,34 +198,34 @@ pip install --upgrade pip ``` -Install the **python-3Enginesclient** package: +Install the **python-connectVMclient** package: ``` -pip install python-3Enginesclient +pip install python-connectVMclient ``` -Verify that the 3Engines CLI works by viewing its help: +Verify that the connectVM CLI works by viewing its help: ``` -3Engines --help +connectVM --help ``` If the command shows its output using a pager, you should be able to use the arrows (or vim keys - **J** and **K**) to scroll and **Q** to exit. -If everything seems to work, time to move to the next step - authentication to your user account on 3Engines Cloud. +If everything seems to work, time to move to the next step - authentication to your user account on connectVM Cloud. -Step 4: Download your 3Engines RC File[🔗](#step-4-download-your-3Engines-rc-file "Permalink to this headline") +Step 4: Download your connectVM RC File[🔗](#step-4-download-your-connectVM-rc-file "Permalink to this headline") ---------------------------------------------------------------------------------------------------------------- -Login to 3Engines Cloud hosting account with Horizon interface . +Login to connectVM Cloud hosting account with Horizon interface . Click on your username in the upper right corner. You will see the following menu: ![wsl20_creodias.png](../_images/wsl20_creodias.png) -If your account has two factor authentication enabled, click the option **3Engines RC File (2FA)**. If, however, it does not have it enabled, use the **3Engines RC File** option. +If your account has two factor authentication enabled, click the option **connectVM RC File (2FA)**. If, however, it does not have it enabled, use the **connectVM RC File** option. The RC file will be downloaded. Memorize or write somewhere down the name of that file. Move this file to the root location of your **C:** drive. @@ -255,7 +255,7 @@ source main-openrc.sh ``` -You will see the prompt for password to your 3Engines Cloud account. Type your password there and press Enter (the password is still being accepted even if you do not see the characters being typed). +You will see the prompt for password to your connectVM Cloud account. Type your password there and press Enter (the password is still being accepted even if you do not see the characters being typed). If your account has two factor authentication enabled, you will also see the prompt for your six-digit code. Open software which you use for generating such codes (for example KeePassXC or FreeOTP) and find your code there, as usual. Make sure that you enter it before it expires. If you think that you will not manage to enter your current code, wait until a new one is generated. @@ -264,19 +264,19 @@ After having entered your code, press Enter. Now you can test whether you have successfully authenticated by listing your VMs: ``` -3Engines server list +connectVM server list ``` How to run this environment later?[🔗](#how-to-run-this-environment-later "Permalink to this headline") ------------------------------------------------------------------------------------------------------ -If you close the window with Ubuntu and reopen it, you will see that you are no longer in the **3Engines\_cli** environment you created and thus no longer have access to 3Engines. You will need to reenter the **3Engines\_cli** environment and reauthenticate. +If you close the window with Ubuntu and reopen it, you will see that you are no longer in the **connectVM\_cli** environment you created and thus no longer have access to connectVM. You will need to reenter the **connectVM\_cli** environment and reauthenticate. -After reopening the Ubuntu Window, execute the **source** command on the file used for entering you **3Engines\_cli** environment, just like previously: +After reopening the Ubuntu Window, execute the **source** command on the file used for entering you **connectVM\_cli** environment, just like previously: ``` -source 3Engines_cli/bin/activate +source connectVM_cli/bin/activate ``` @@ -287,19 +287,19 @@ source main-openrc.sh ``` -Type your password and press Enter. You should now be able execute the 3Engines CLI commands as usual. +Type your password and press Enter. You should now be able execute the connectVM CLI commands as usual. What To Do Next[🔗](#what-to-do-next "Permalink to this headline") ----------------------------------------------------------------- -After installing the 3Engines CLI client and activating your new RC file, you can use other articles to perform operations on 3Engines Cloud cloud: +After installing the connectVM CLI client and activating your new RC file, you can use other articles to perform operations on connectVM Cloud cloud: -[How to create a set of VMs using 3Engines Heat Orchestration on 3Engines Cloud](How-to-create-a-set-of-VMs-using-3Engines-Heat-Orchestration-on-3Engines-Cloud.html.md) +[How to create a set of VMs using connectVM Heat Orchestration on connectVM Cloud](How-to-create-a-set-of-VMs-using-connectVM-Heat-Orchestration-on-connectVM-Cloud.html.md) -[Generating and authorizing Terraform using Keycloak user on 3Engines Cloud](../3Enginesdev/Generating-and-authorizing-Terraform-using-Keycloak-user-on-3Engines-Cloud.html.md) +[Generating and authorizing Terraform using Keycloak user on connectVM Cloud](../connectVMdev/Generating-and-authorizing-Terraform-using-Keycloak-user-on-connectVM-Cloud.html.md) -[How to upload your custom image using 3Engines CLI on 3Engines Cloud](../cloud/How-to-upload-your-custom-image-using-3Engines-CLI-on-3Engines-Cloud.html.md) +[How to upload your custom image using connectVM CLI on connectVM Cloud](../cloud/How-to-upload-your-custom-image-using-connectVM-CLI-on-connectVM-Cloud.html.md) -[How to create a VM using the 3Engines CLI client on 3Engines Cloud cloud](../cloud/How-to-create-a-VM-using-the-3Engines-CLI-client-on-3Engines-Cloud-cloud.html.md) +[How to create a VM using the connectVM CLI client on connectVM Cloud cloud](../cloud/How-to-create-a-VM-using-the-connectVM-CLI-client-on-connectVM-Cloud-cloud.html.md) -[How To Use Command Line Interface for Kubernetes Clusters On 3Engines Cloud 3Engines Magnum](../kubernetes/How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-3Engines-Cloud-3Engines-Magnum.html.md) \ No newline at end of file +[How To Use Command Line Interface for Kubernetes Clusters On connectVM Cloud connectVM Magnum](../kubernetes/How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-connectVM-Cloud-connectVM-Magnum.html.md) \ No newline at end of file diff --git a/docs/openstackcli/How-to-move-data-volume-between-two-VMs-using-3Engines-CLI-on-3Engines-Cloud.html.md b/docs/openstackcli/How-to-move-data-volume-between-two-VMs-using-connectVM-CLI-on-connectVM-Cloud.html.md similarity index 54% rename from docs/openstackcli/How-to-move-data-volume-between-two-VMs-using-3Engines-CLI-on-3Engines-Cloud.html.md rename to docs/openstackcli/How-to-move-data-volume-between-two-VMs-using-connectVM-CLI-on-connectVM-Cloud.html.md index fa6cdf1..2a04482 100644 --- a/docs/openstackcli/How-to-move-data-volume-between-two-VMs-using-3Engines-CLI-on-3Engines-Cloud.html.md +++ b/docs/openstackcli/How-to-move-data-volume-between-two-VMs-using-connectVM-CLI-on-connectVM-Cloud.html.md @@ -1,17 +1,17 @@ -How to move data volume between VMs using 3Engines CLI on 3Engines Cloud[🔗](#how-to-move-data-volume-between-vms-using-3Engines-cli-on-brand-name "Permalink to this headline") +How to move data volume between VMs using connectVM CLI on connectVM Cloud[🔗](#how-to-move-data-volume-between-vms-using-connectVM-cli-on-brand-name "Permalink to this headline") =================================================================================================================================================================================== Volumes are used to store data and those data can be accessed from a virtual machine to which the volume is attached. To access data stored on a volume from another virtual machine, you need to disconnect that volume from virtual machine to which it is currently connected, and connect it to another instance. -This article uses 3Engines CLI client to transfer volumes between virtual machines which are in the same project. +This article uses connectVM CLI client to transfer volumes between virtual machines which are in the same project. Prerequisites[🔗](#prerequisites "Permalink to this headline") ------------------------------------------------------------- No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . -No. 2 **3Engines CLI client** +No. 2 **connectVM CLI client** -To be able to use the 3Engines CLI client, you need to have it installed. One of these articles should help: \ No newline at end of file +To be able to use the connectVM CLI client, you need to have it installed. One of these articles should help: \ No newline at end of file diff --git a/docs/openstackcli/How-to-share-private-container-from-object-storage-to-another-user-on-3Engines-Cloud.html.md b/docs/openstackcli/How-to-share-private-container-from-object-storage-to-another-user-on-connectVM-Cloud.html.md similarity index 76% rename from docs/openstackcli/How-to-share-private-container-from-object-storage-to-another-user-on-3Engines-Cloud.html.md rename to docs/openstackcli/How-to-share-private-container-from-object-storage-to-another-user-on-connectVM-Cloud.html.md index ef0d964..6f11ff3 100644 --- a/docs/openstackcli/How-to-share-private-container-from-object-storage-to-another-user-on-3Engines-Cloud.html.md +++ b/docs/openstackcli/How-to-share-private-container-from-object-storage-to-another-user-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How to share private container from object storage to another user on 3Engines Cloud[🔗](#how-to-share-private-container-from-object-storage-to-another-user-on-brand-name "Permalink to this headline") +How to share private container from object storage to another user on connectVM Cloud[🔗](#how-to-share-private-container-from-object-storage-to-another-user-on-brand-name "Permalink to this headline") ========================================================================================================================================================================================================= You can create your own private containers in Object Store of your projects and you can grant access to other users. @@ -14,23 +14,23 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Hosting** -You need a 3Engines Cloud hosting account with Horizon interface . +You need a connectVM Cloud hosting account with Horizon interface . -No. 2 **3Engines client installed and connected to the cloud** +No. 2 **connectVM client installed and connected to the cloud** -The following article will help you install Python and 3Engines client called **3Engines** and will also help you connect to the cloud [How to install 3EnginesClient for Linux on 3Engines Cloud](How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md)). +The following article will help you install Python and connectVM client called **connectVM** and will also help you connect to the cloud [How to install connectVMClient for Linux on connectVM Cloud](How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md)). No. 3 **Knowledge of downloading and working with RC files** To be able to share private containers, you will have to manipulate RC files from the cloud. The following article will provide technical details: -[How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md) +[How to activate connectVM CLI access to connectVM Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-connectVM-CLI-access-to-connectVM-Cloud-cloud-using-one-or-two-factor-authentication.html.md) -No. 4. **Using 3Engines Swift module** +No. 4. **Using connectVM Swift module** -The 3Engines Object Store module, known as *Swift*, allows you to store and retrieve data with a simple API. It’s built for scale and is optimized for durability, availability, and concurrency across the entire data set. Swift is ideal for storing unstructured data that can grow without bound. +The connectVM Object Store module, known as *Swift*, allows you to store and retrieve data with a simple API. It’s built for scale and is optimized for durability, availability, and concurrency across the entire data set. Swift is ideal for storing unstructured data that can grow without bound. -See [How to access object storage using 3Engines CLI on 3Engines Cloud](How-to-access-object-storage-using-3Engines-CLI-on-3Engines-Cloud.html.md) +See [How to access object storage using connectVM CLI on connectVM Cloud](How-to-access-object-storage-using-connectVM-CLI-on-connectVM-Cloud.html.md) Setting up the test example[🔗](#setting-up-the-test-example "Permalink to this headline") ----------------------------------------------------------------------------------------- @@ -87,7 +87,7 @@ Then, they should choose the main project: ![owner_main.png](../_images/owner_main.png) -After that, they should download the “3Engines RC File” for the user “owner” and the project “main”: +After that, they should download the “connectVM RC File” for the user “owner” and the project “main”: ![owner_rc.png](../_images/owner_rc.png) @@ -106,7 +106,7 @@ $ cat main-openrc.sh ``` #!/usr/bin/env bash -# To use an 3Engines cloud you need to authenticate against the Identity +# To use an connectVM cloud you need to authenticate against the Identity # service named keystone, which returns a **Token** and **Service Catalog**. # The catalog contains the endpoints for all services the user/tenant has # access to - such as Compute, Image Service, Identity, Object Storage, Block @@ -114,12 +114,12 @@ $ cat main-openrc.sh # cinder, and neutron). # # *NOTE*: Using the 3 *Identity API* does not necessarily mean any other -# 3Engines API is version 3. For example, your cloud provider may implement +# connectVM API is version 3. For example, your cloud provider may implement # Image API v1.1, Block Storage API v2, and Compute API v2.0. OS_AUTH_URL is # only for the Identity API served through keystone. unset OS_TENANT_ID unset OS_TENANT_NAME -export OS_AUTH_URL=https://keystone.3Engines.com:5000/v3 +export OS_AUTH_URL=https://keystone.connectVM.com:5000/v3 export OS_INTERFACE=public export OS_IDENTITY_API_VERSION=3 export OS_USERNAME="owner" @@ -130,7 +130,7 @@ export OS_PROJECT_DOMAIN_ID="119f4676f307434eaf28daab5ba3cc92" if [ -z "$OS_REGION_NAME" ]; then unset OS_REGION_NAME; fi if [ -z "$OS_USER_DOMAIN_NAME" ]; then unset OS_USER_DOMAIN_NAME; fi if [ -z "$OS_PROJECT_DOMAIN_ID" ]; then unset OS_PROJECT_DOMAIN_ID; fi -echo "Please enter your 3Engines Password for project $OS_PROJECT_NAME as user $OS_USERNAME: " +echo "Please enter your connectVM Password for project $OS_PROJECT_NAME as user $OS_USERNAME: " read -sr OS_PASSWORD_INPUT export OS_PASSWORD=$OS_PASSWORD_INPUT export OS_AUTH_TYPE=password @@ -146,13 +146,13 @@ Copy the file **main-openrc.sh** to your CLI directory. The user called “user\_1” should do the same procedure: 1. login to their “project\_1” -2. download the “3Engines RC File” for user “user\_1” and project “project\_1” +2. download the “connectVM RC File” for user “user\_1” and project “project\_1” project\_1-openrc.sh ``` #!/usr/bin/env bash -# To use an 3Engines cloud you need to authenticate against the Identity +# To use an connectVM cloud you need to authenticate against the Identity # service named keystone, which returns a **Token** and **Service Catalog**. # The catalog contains the endpoints for all services the user/tenant has # access to - such as Compute, Image Service, Identity, Object Storage, Block @@ -160,12 +160,12 @@ project\_1-openrc.sh # cinder, and neutron). # # *NOTE*: Using the 3 *Identity API* does not necessarily mean any other -# 3Engines API is version 3. For example, your cloud provider may implement +# connectVM API is version 3. For example, your cloud provider may implement # Image API v1.1, Block Storage API v2, and Compute API v2.0. OS_AUTH_URL is # only for the Identity API served through keystone. unset OS_TENANT_ID unset OS_TENANT_NAME -export OS_AUTH_URL=https://keystone.3Engines.com:5000/v3 +export OS_AUTH_URL=https://keystone.connectVM.com:5000/v3 export OS_INTERFACE=public export OS_IDENTITY_API_VERSION=3 export OS_USERNAME="user_1" @@ -176,7 +176,7 @@ export OS_PROJECT_DOMAIN_ID="119f4676f307434eaf28daab5ba3cc92" if [ -z "$OS_REGION_NAME" ]; then unset OS_REGION_NAME; fi if [ -z "$OS_USER_DOMAIN_NAME" ]; then unset OS_USER_DOMAIN_NAME; fi if [ -z "$OS_PROJECT_DOMAIN_ID" ]; then unset OS_PROJECT_DOMAIN_ID; fi -echo "Please enter your 3Engines Password for project $OS_PROJECT_NAME as user $OS_USERNAME: " +echo "Please enter your connectVM Password for project $OS_PROJECT_NAME as user $OS_USERNAME: " read -sr OS_PASSWORD_INPUT export OS_PASSWORD=$OS_PASSWORD_INPUT export OS_AUTH_TYPE=password @@ -195,7 +195,7 @@ terminal of user “owner” ``` $ source main-openrc.sh -Please enter your 3Engines Password for project main as user owner: +Please enter your connectVM Password for project main as user owner: (owner) $ swift list c-main-a @@ -211,7 +211,7 @@ terminal of user “user\_1”: ``` $ source project_1-openrc.sh -Please enter your 3Engines Password for project project_1 as user user_1: +Please enter your connectVM Password for project project_1 as user user_1: (user_1) $ swift list @@ -227,7 +227,7 @@ terminal of user “user\_2”: ``` $ source project_2-openrc.sh -Please enter your 3Engines Password for project project_2 as user user_2: +Please enter your connectVM Password for project project_2 as user user_2: (user_2) $ swift list c-project_2-a @@ -273,7 +273,7 @@ test-main-d.txt Check the id of user\_1: ``` -(user_1) $ 3Engines user show --format json "${OS_USERNAME}" | jq -r .id +(user_1) $ connectVM user show --format json "${OS_USERNAME}" | jq -r .id 3de5f40b4e6d433792ac387896729ec8 ``` @@ -281,7 +281,7 @@ Check the id of user\_1: Check the id of user\_2: ``` -(user_2) $ 3Engines user show --format json "${OS_USERNAME}" | jq -r .id +(user_2) $ connectVM user show --format json "${OS_USERNAME}" | jq -r .id fb4ec0de674d4c5ba608ee75cc6da918 ``` @@ -306,7 +306,7 @@ X-Container-Bytes-Used-Actual: 8192 X-Storage-Class: STANDARD Last-Modified: Tue, 14 Jun 2022 13:41:32 GMT X-Trans-Id: tx000000000000003964e44-0062b17ebb-17404e6b-default - X-3Engines-Request-Id: tx000000000000003964e44-0062b17ebb-17404e6b-default + X-connectVM-Request-Id: tx000000000000003964e44-0062b17ebb-17404e6b-default Accept-Ranges: bytes Content-Type: text/plain; charset=utf-8 @@ -326,14 +326,14 @@ Get the credentials to access Object Store in “main”: ``` (owner) $ swift auth | awk -F = '/OS_STORAGE_URL/ {print $2}' -https://s3.waw3-1.3Engines.com/swift/v1 +https://s3.waw3-1.connectVM.com/swift/v1 ``` Pass the link: ``` -https://s3.waw3-1.3Engines.com/swift/v1 +https://s3.waw3-1.connectVM.com/swift/v1 ``` @@ -342,7 +342,7 @@ to “user\_1” “user\_1” should create an environmental variable “SURL” ``` -(user_1) $ SURL=https://s3.waw3-1.3Engines.com/swift/v1 +(user_1) $ SURL=https://s3.waw3-1.connectVM.com/swift/v1 ``` @@ -359,7 +359,7 @@ But the user “user\_1” has no access to other containers in the “main” p ``` (user_1) $ swift --os-storage-url="${SURL}" list c-main-b -Container GET failed: https://s3.waw3-1.3Engines.com/swift/v1/c-main-b?format=json 403 Forbidden [first 60 +Container GET failed: https://s3.waw3-1.connectVM.com/swift/v1/c-main-b?format=json 403 Forbidden [first 60 chars of response] b'{"Code":"AccessDenied","BucketName":"c-main-b","RequestId":"' Failed Transaction ID: tx00000000000000397edda-0062b186ef-17379d9b-default @@ -377,6 +377,6 @@ What To Do Next[🔗](#what-to-do-next "Permalink to this headline") These articles can also be of interest: -[How to use Object Storage on 3Engines Cloud](../s3/How-to-use-Object-Storage-on-3Engines-Cloud.html.md). +[How to use Object Storage on connectVM Cloud](../s3/How-to-use-Object-Storage-on-connectVM-Cloud.html.md). -[Bucket sharing using s3 bucket policy on 3Engines Cloud](../s3/Bucket-sharing-using-s3-bucket-policy-on-3Engines-Cloud.html.md) \ No newline at end of file +[Bucket sharing using s3 bucket policy on connectVM Cloud](../s3/Bucket-sharing-using-s3-bucket-policy-on-connectVM-Cloud.html.md) \ No newline at end of file diff --git a/docs/openstackcli/How-to-start-a-VM-from-instance-snapshot-using-3Engines-CLI-on-3Engines-Cloud.html.md b/docs/openstackcli/How-to-start-a-VM-from-instance-snapshot-using-3Engines-CLI-on-3Engines-Cloud.html.md deleted file mode 100644 index 8fd008e..0000000 --- a/docs/openstackcli/How-to-start-a-VM-from-instance-snapshot-using-3Engines-CLI-on-3Engines-Cloud.html.md +++ /dev/null @@ -1,15 +0,0 @@ -How to start a VM from instance snapshot using 3Engines CLI on 3Engines Cloud[🔗](#how-to-start-a-vm-from-instance-snapshot-using-3Engines-cli-on-brand-name "Permalink to this headline") -============================================================================================================================================================================================= - -In this article, you will learn how to create a virtual machine from an instance snapshot using 3Engines CLI client. - -Prerequisites[🔗](#prerequisites "Permalink to this headline") -------------------------------------------------------------- - -No. 1 **Account** - -You need a 3Engines Cloud hosting account with access to the Horizon interface: . - -No. 2 **3Engines CLI client** - -You need to have 3Engines CLI client installed. One of the following articles should help you: \ No newline at end of file diff --git a/docs/openstackcli/How-to-start-a-VM-from-instance-snapshot-using-connectVM-CLI-on-connectVM-Cloud.html.md b/docs/openstackcli/How-to-start-a-VM-from-instance-snapshot-using-connectVM-CLI-on-connectVM-Cloud.html.md new file mode 100644 index 0000000..a76e31c --- /dev/null +++ b/docs/openstackcli/How-to-start-a-VM-from-instance-snapshot-using-connectVM-CLI-on-connectVM-Cloud.html.md @@ -0,0 +1,15 @@ +How to start a VM from instance snapshot using connectVM CLI on connectVM Cloud[🔗](#how-to-start-a-vm-from-instance-snapshot-using-connectVM-cli-on-brand-name "Permalink to this headline") +============================================================================================================================================================================================= + +In this article, you will learn how to create a virtual machine from an instance snapshot using connectVM CLI client. + +Prerequisites[🔗](#prerequisites "Permalink to this headline") +------------------------------------------------------------- + +No. 1 **Account** + +You need a connectVM Cloud hosting account with access to the Horizon interface: . + +No. 2 **connectVM CLI client** + +You need to have connectVM CLI client installed. One of the following articles should help you: \ No newline at end of file diff --git a/docs/openstackcli/How-to-transfer-volumes-between-domains-and-projects-using-3Engines-CLI-client-on-3Engines-Cloud.html.md b/docs/openstackcli/How-to-transfer-volumes-between-domains-and-projects-using-connectVM-CLI-client-on-connectVM-Cloud.html.md similarity index 65% rename from docs/openstackcli/How-to-transfer-volumes-between-domains-and-projects-using-3Engines-CLI-client-on-3Engines-Cloud.html.md rename to docs/openstackcli/How-to-transfer-volumes-between-domains-and-projects-using-connectVM-CLI-client-on-connectVM-Cloud.html.md index 2559d81..b597ec2 100644 --- a/docs/openstackcli/How-to-transfer-volumes-between-domains-and-projects-using-3Engines-CLI-client-on-3Engines-Cloud.html.md +++ b/docs/openstackcli/How-to-transfer-volumes-between-domains-and-projects-using-connectVM-CLI-client-on-connectVM-Cloud.html.md @@ -1,11 +1,11 @@ -How to transfer volumes between domains and projects using 3Engines CLI client on 3Engines Cloud[🔗](#how-to-transfer-volumes-between-domains-and-projects-using-3Engines-cli-client-on-brand-name "Permalink to this headline") +How to transfer volumes between domains and projects using connectVM CLI client on connectVM Cloud[🔗](#how-to-transfer-volumes-between-domains-and-projects-using-connectVM-cli-client-on-brand-name "Permalink to this headline") =================================================================================================================================================================================================================================== -Volumes in 3Engines can be used to store data. They are visible to virtual machines like drives. +Volumes in connectVM can be used to store data. They are visible to virtual machines like drives. Such a volume is usually available to just the project in which it was created. Transferring data stored on it between projects might take a long time, especially if such a volume contains lots of data, like, say, hundreds or thousands of gigabytes (or even more). -This article covers changing the assignment of a volume to a project. This allows you to move a volume directly from one project (which we will call *source* project) to another (which we will call *destination* project) using the 3Engines CLI in a way that does **not** require you to physically transfer the data. +This article covers changing the assignment of a volume to a project. This allows you to move a volume directly from one project (which we will call *source* project) to another (which we will call *destination* project) using the connectVM CLI in a way that does **not** require you to physically transfer the data. The *source* project and *destination* project must both be on the same cloud (for example WAW3-2). They can (but don’t have to) belong to different users from different domains and organizations. @@ -21,8 +21,8 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: +You need a connectVM Cloud hosting account with access to the Horizon interface: -No. 2 **3Engines CLI Client** +No. 2 **connectVM CLI Client** -To use the 3Engines CLI client, you need to have it installed. See one of these articles to learn how to do it: \ No newline at end of file +To use the connectVM CLI client, you need to have it installed. See one of these articles to learn how to do it: \ No newline at end of file diff --git a/docs/openstackcli/Resizing-a-virtual-machine-using-3Engines-CLI-on-3Engines-Cloud.html.md b/docs/openstackcli/Resizing-a-virtual-machine-using-connectVM-CLI-on-connectVM-Cloud.html.md similarity index 68% rename from docs/openstackcli/Resizing-a-virtual-machine-using-3Engines-CLI-on-3Engines-Cloud.html.md rename to docs/openstackcli/Resizing-a-virtual-machine-using-connectVM-CLI-on-connectVM-Cloud.html.md index 9f667a4..cedea34 100644 --- a/docs/openstackcli/Resizing-a-virtual-machine-using-3Engines-CLI-on-3Engines-Cloud.html.md +++ b/docs/openstackcli/Resizing-a-virtual-machine-using-connectVM-CLI-on-connectVM-Cloud.html.md @@ -1,10 +1,10 @@ -Resizing a virtual machine using 3Engines CLI on 3Engines Cloud[🔗](#resizing-a-virtual-machine-using-3Engines-cli-on-brand-name "Permalink to this headline") +Resizing a virtual machine using connectVM CLI on connectVM Cloud[🔗](#resizing-a-virtual-machine-using-connectVM-cli-on-brand-name "Permalink to this headline") ================================================================================================================================================================= Introduction[🔗](#introduction "Permalink to this headline") ----------------------------------------------------------- -When creating a new virtual machine under 3Engines, one of the options you choose is the *flavor*. A flavor is a predefined combination of CPU, memory and disk size and there usually is a number of such flavors for you to choose from. +When creating a new virtual machine under connectVM, one of the options you choose is the *flavor*. A flavor is a predefined combination of CPU, memory and disk size and there usually is a number of such flavors for you to choose from. After the instance is spawned, it is possible to change one flavor for another, and that process is called *resizing*. You might want to resize an already existing VM in order to: @@ -14,28 +14,28 @@ After the instance is spawned, it is possible to change one flavor for another, > * seamlessly transition from testing to production environment, > * change application workload byt scaling the VM up or down. -In this article, we are going to resize VMs using CLI commands in 3Engines. +In this article, we are going to resize VMs using CLI commands in connectVM. Prerequisites[🔗](#prerequisites "Permalink to this headline") ------------------------------------------------------------- No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . -If you are a normal user of 3Engines Cloud hosting, you will have all prerogatives needed to resize the VM. Make sure that the VM you are about to resize belongs to a project you have access to. +If you are a normal user of connectVM Cloud hosting, you will have all prerogatives needed to resize the VM. Make sure that the VM you are about to resize belongs to a project you have access to. -[How to create a VM using the 3Engines CLI client on 3Engines Cloud cloud](../cloud/How-to-create-a-VM-using-the-3Engines-CLI-client-on-3Engines-Cloud-cloud.html.md) +[How to create a VM using the connectVM CLI client on connectVM Cloud cloud](../cloud/How-to-create-a-VM-using-the-connectVM-CLI-client-on-connectVM-Cloud-cloud.html.md) No. 2 **Awareness of existing quotas and flavors limits** -For general introduction to quotas and flavors, see [Dashboard Overview – Project Quotas And Flavors Limits on 3Engines Cloud](../cloud/Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-3Engines-Cloud.html.md). +For general introduction to quotas and flavors, see [Dashboard Overview – Project Quotas And Flavors Limits on connectVM Cloud](../cloud/Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-connectVM-Cloud.html.md). Also: > * The VM you want to resize is in an active or shut down state. > * A flavor with the desired resource configuration exists. -> * Adequate resources are available in your 3Engines environment to accommodate the resize. +> * Adequate resources are available in your connectVM environment to accommodate the resize. Creating a new VM[🔗](#creating-a-new-vm "Permalink to this headline") --------------------------------------------------------------------- @@ -45,7 +45,7 @@ To illustrate the commands in this article, let us create a new VM in order to s To see all flavors: ``` -3Engines flavor list +connectVM flavor list ``` @@ -54,7 +54,7 @@ To see all flavors: This is the command to create a new VM called **ResizingCLI**: ``` -3Engines server create \ +connectVM server create \ --image "Ubuntu 22.04 LTS" \ --flavor eo2a.large \ --key-name sshkey \ @@ -74,7 +74,7 @@ The **id** for **ResizingCLI** is **82bba971-8ff1-4f85-93d6-9d56bb7b185d** and w To see all currently available VMs, use command ``` -3Engines server list +connectVM server list ``` @@ -84,7 +84,7 @@ Steps to Resize the VM[🔗](#steps-to-resize-the-vm "Permalink to this headline To resize a VM with CLI, there is a general command ``` -3Engines server resize --flavor +connectVM server resize --flavor ``` @@ -93,14 +93,14 @@ We need flavor ID or name as well as VM’s name or id. In this example we want to scale up the existing VM **ResizingCLI**, using **eo2.xlarge** flavor. The command will be: ``` -3Engines server resize --flavor eo2.xlarge ResizingCLI +connectVM server resize --flavor eo2.xlarge ResizingCLI ``` To verify the resize, check the status of the VM: ``` -3Engines server show ResizingCLI +connectVM server show ResizingCLI ``` @@ -109,14 +109,14 @@ To verify the resize, check the status of the VM: When the VM has **VERIFY\_RESIZE** status, we are able to confirm the resize. The command is: ``` -3Engines server resize confirm ResizingCLI +connectVM server resize confirm ResizingCLI ``` Execute once again: ``` -3Engines server show ResizingCLI +connectVM server show ResizingCLI ``` @@ -130,13 +130,13 @@ Reverting a resize switches the VM back to its original flavor and cleans up tem It is only possible to revert a resize if the status is **VERIFY\_RESIZE**. The command would be: ``` -3Engines server resize revert ResizingCLI +connectVM server resize revert ResizingCLI ``` -If status is not **VERIFY\_RESIZE**, we will get message stating that it is not possible to revert resize while it is in an active state (HTTP 409). In that case, perform the “regular” resizing with **3Engines server resize**. +If status is not **VERIFY\_RESIZE**, we will get message stating that it is not possible to revert resize while it is in an active state (HTTP 409). In that case, perform the “regular” resizing with **connectVM server resize**. What To Do Next[🔗](#what-to-do-next "Permalink to this headline") ----------------------------------------------------------------- -You can also resize the virtual machine using only 3Engines CLI. More details here: /3Enginescli/Resizing-a-virtual-machine-using-3Engines-Horizon-on-3Engines-Cloud \ No newline at end of file +You can also resize the virtual machine using only connectVM CLI. More details here: /connectVMcli/Resizing-a-virtual-machine-using-connectVM-Horizon-on-connectVM-Cloud \ No newline at end of file diff --git a/docs/openstackcli/Use-backup-command-to-create-rotating-backups-of-virtual-machines-on-3Engines-Cloud.html.md b/docs/openstackcli/Use-backup-command-to-create-rotating-backups-of-virtual-machines-on-connectVM-Cloud.html.md similarity index 71% rename from docs/openstackcli/Use-backup-command-to-create-rotating-backups-of-virtual-machines-on-3Engines-Cloud.html.md rename to docs/openstackcli/Use-backup-command-to-create-rotating-backups-of-virtual-machines-on-connectVM-Cloud.html.md index 431054e..3299edd 100644 --- a/docs/openstackcli/Use-backup-command-to-create-rotating-backups-of-virtual-machines-on-3Engines-Cloud.html.md +++ b/docs/openstackcli/Use-backup-command-to-create-rotating-backups-of-virtual-machines-on-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -Use backup command to create rotating backups of virtual machines on 3Engines Cloud cloud[🔗](#use-backup-command-to-create-rotating-backups-of-virtual-machines-on-brand-name-cloud "Permalink to this headline") +Use backup command to create rotating backups of virtual machines on connectVM Cloud cloud[🔗](#use-backup-command-to-create-rotating-backups-of-virtual-machines-on-brand-name-cloud "Permalink to this headline") =================================================================================================================================================================================================================== -**Rotating backups** in 3Engines refer to a backup strategy where older backups are automatically deleted after a predefined number of backups are created. This ensures that storage does not grow indefinitely while still maintaining a set number of recent backups for disaster recovery. +**Rotating backups** in connectVM refer to a backup strategy where older backups are automatically deleted after a predefined number of backups are created. This ensures that storage does not grow indefinitely while still maintaining a set number of recent backups for disaster recovery. The rotating backup algorithm[🔗](#the-rotating-backup-algorithm "Permalink to this headline") --------------------------------------------------------------------------------------------- @@ -20,15 +20,15 @@ Delete older backups backup create vs. image create[🔗](#backup-create-vs-image-create "Permalink to this headline") ---------------------------------------------------------------------------------------------- -There are two ways of creating backups under 3Engines, using one of these two commands: +There are two ways of creating backups under connectVM, using one of these two commands: -**3Engines server backup create** and **3Engines server image create** +**connectVM server backup create** and **connectVM server image create** Here is how they compare: Table 3 Comparison of Backup and Image Creation Commands[🔗](#id1 "Permalink to this table") -| Feature | `3Engines server backup create` | `3Engines server image create` | +| Feature | `connectVM server backup create` | `connectVM server image create` | | --- | --- | --- | | Association with VM | Associated using **backup** image property | Associated using backup name | | Rotation support | Rotation with `--backup-type` and incremental backups | No built-in rotation support | @@ -40,14 +40,14 @@ Table 3 Comparison of Backup and Image Creation Commands[🔗](#id1 "Permalink t | Best usage scenario | Automated backup strategies with rotation | Capturing the current state of a VM for cloning or rollback | | Can be scripted? | Yes | Yes | -In this article we are going to use a **3Engines server backup create** command under 3Engines to create rotating backups of virtual machines. +In this article we are going to use a **connectVM server backup create** command under connectVM to create rotating backups of virtual machines. Prerequisites[🔗](#prerequisites "Permalink to this headline") ------------------------------------------------------------- No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: +You need a connectVM Cloud hosting account with access to the Horizon interface: No. 2 **VM which will be backed up** diff --git a/docs/openstackcli/Use-script-to-create-daily-weekly-and-monthly-rotating-backups-of-virtual-machines-using-on-3Engines-Cloud.html.md b/docs/openstackcli/Use-script-to-create-daily-weekly-and-monthly-rotating-backups-of-virtual-machines-using-on-connectVM-Cloud.html.md similarity index 66% rename from docs/openstackcli/Use-script-to-create-daily-weekly-and-monthly-rotating-backups-of-virtual-machines-using-on-3Engines-Cloud.html.md rename to docs/openstackcli/Use-script-to-create-daily-weekly-and-monthly-rotating-backups-of-virtual-machines-using-on-connectVM-Cloud.html.md index daea52b..6933b5b 100644 --- a/docs/openstackcli/Use-script-to-create-daily-weekly-and-monthly-rotating-backups-of-virtual-machines-using-on-3Engines-Cloud.html.md +++ b/docs/openstackcli/Use-script-to-create-daily-weekly-and-monthly-rotating-backups-of-virtual-machines-using-on-connectVM-Cloud.html.md @@ -1,20 +1,20 @@ -Use script to create daily weekly and monthly rotating backups of virtual machines on 3Engines Cloud[🔗](#use-script-to-create-daily-weekly-and-monthly-rotating-backups-of-virtual-machines-on-brand-name "Permalink to this headline") +Use script to create daily weekly and monthly rotating backups of virtual machines on connectVM Cloud[🔗](#use-script-to-create-daily-weekly-and-monthly-rotating-backups-of-virtual-machines-on-brand-name "Permalink to this headline") ========================================================================================================================================================================================================================================= -**Rotating backups** in 3Engines refer to a backup strategy where older backups are automatically deleted after a predefined number of backups are created. This ensures that storage does not grow indefinitely while still maintaining a set number of recent backups for disaster recovery. +**Rotating backups** in connectVM refer to a backup strategy where older backups are automatically deleted after a predefined number of backups are created. This ensures that storage does not grow indefinitely while still maintaining a set number of recent backups for disaster recovery. backup create vs. image create[🔗](#backup-create-vs-image-create "Permalink to this headline") ---------------------------------------------------------------------------------------------- -There are two ways of creating backups under 3Engines, using one of these two commands: +There are two ways of creating backups under connectVM, using one of these two commands: -**3Engines server backup create** and **3Engines server image create** +**connectVM server backup create** and **connectVM server image create** Here is how they compare: Table 4 Comparison of Backup and Image Creation Commands[🔗](#id1 "Permalink to this table") -| Feature | `3Engines server backup create` | `3Engines server image create` | +| Feature | `connectVM server backup create` | `connectVM server image create` | | --- | --- | --- | | Association with VM | Associated using **backup** image property | Associated using backup name | | Rotation support | Rotation with `--backup-type` and incremental backups | No built-in rotation support | @@ -26,14 +26,14 @@ Table 4 Comparison of Backup and Image Creation Commands[🔗](#id1 "Permalink t | Best usage scenario | Automated backup strategies with rotation | Capturing the current state of a VM for cloning or rollback | | Can be scripted? | Yes | Yes | -In this article, you will learn how to create multiple series of rotating backups with a script which uses multiple **3EnginesClient** commands to achieve this goal. +In this article, you will learn how to create multiple series of rotating backups with a script which uses multiple **connectVMClient** commands to achieve this goal. Prerequisites[🔗](#prerequisites "Permalink to this headline") ------------------------------------------------------------- No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: +You need a connectVM Cloud hosting account with access to the Horizon interface: No. 2 **VM which will be backed up** diff --git a/docs/openstackcli/connectVMcli.html.md b/docs/openstackcli/connectVMcli.html.md new file mode 100644 index 0000000..2bc3f3b --- /dev/null +++ b/docs/openstackcli/connectVMcli.html.md @@ -0,0 +1,19 @@ +# connectVM CLI + +## Available Documentation + +* [How to Backup an Instance and Download it to the Desktop on connectVM Cloud connectVM Hosting](How-to-backup-an-instance-and-download-it-to-the-desktop-on-connectVM-Cloud.html.md) +* [How to create a set of VMs using connectVM Heat Orchestration on connectVM Cloud](How-to-create-a-set-of-VMs-using-connectVM-Heat-Orchestration-on-connectVM-Cloud.html.md) +* [How to Create and Configure New connectVM Project Through Horizon on connectVM Cloud Cloud](How-To-Create-and-Configure-New-Project-on-connectVM-Cloud-Cloud.html.md) +* [How to install connectVMClient for Linux on connectVM Cloud](How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md) +* [How to install connectVMClient GitBash for Windows on connectVM Cloud](How-to-install-connectVMClient-GitBash-or-Cygwin-for-Windows-on-connectVM-Cloud.html.md) +* [How to share private container from object storage to another user on connectVM Cloud](How-to-share-private-container-from-object-storage-to-another-user-on-connectVM-Cloud.html.md) +* [How to install connectVMClient on Windows using Windows Subsystem for Linux on connectVM Cloud connectVM Hosting](How-to-install-connectVMClient-on-Windows-using-Windows-Subsystem-for-Linux-on-connectVM-Cloud-connectVM-Hosting.html.md) +* [How to move data volume between VMs using connectVM CLI on connectVM Cloud](How-to-move-data-volume-between-two-VMs-using-connectVM-CLI-on-connectVM-Cloud.html.md) +* [How to access object storage using connectVM CLI on connectVM Cloud](How-to-access-object-storage-using-connectVM-CLI-on-connectVM-Cloud.html.md) +* [How to transfer volumes between domains and projects using connectVM CLI client on connectVM Cloud](How-to-transfer-volumes-between-domains-and-projects-using-connectVM-CLI-client-on-connectVM-Cloud.html.md) +* [How to start a VM from instance snapshot using connectVM CLI on connectVM Cloud](How-to-start-a-VM-from-instance-snapshot-using-connectVM-CLI-on-connectVM-Cloud.html.md) +* [How to create instance snapshot using connectVM CLI on connectVM Cloud](How-to-create-instance-snapshot-using-connectVM-CLI-on-connectVM-Cloud.html.md) +* [Resizing a virtual machine using connectVM CLI on connectVM Cloud](Resizing-a-virtual-machine-using-connectVM-CLI-on-connectVM-Cloud.html.md) +* [Use backup command to create rotating backups of virtual machines on connectVM Cloud cloud](Use-backup-command-to-create-rotating-backups-of-virtual-machines-on-connectVM-Cloud.html.md) +* [Use script to create daily weekly and monthly rotating backups of virtual machines on connectVM Cloud](Use-script-to-create-daily-weekly-and-monthly-rotating-backups-of-virtual-machines-using-on-connectVM-Cloud.html.md) diff --git a/docs/openstackdev/3Enginesdev.html.md b/docs/openstackdev/3Enginesdev.html.md deleted file mode 100644 index efe23bb..0000000 --- a/docs/openstackdev/3Enginesdev.html.md +++ /dev/null @@ -1,6 +0,0 @@ -# 3Engines Development - -## Available Documentation - -* [Authenticating with 3EnginesSDK using Keycloak Credentials on 3Engines Cloud](Authenticating-to-3EnginesSDK-using-Keycloak-Credentials-on-3Engines-Cloud.html.md) -* [Generating and authorizing Terraform using Keycloak user on 3Engines Cloud](Generating-and-authorizing-Terraform-using-Keycloak-user-on-3Engines-Cloud.html.md) diff --git a/docs/openstackdev/Authenticating-to-3EnginesSDK-using-Keycloak-Credentials-on-3Engines-Cloud.html.md b/docs/openstackdev/Authenticating-to-connectVMSDK-using-Keycloak-Credentials-on-connectVM-Cloud.html.md similarity index 63% rename from docs/openstackdev/Authenticating-to-3EnginesSDK-using-Keycloak-Credentials-on-3Engines-Cloud.html.md rename to docs/openstackdev/Authenticating-to-connectVMSDK-using-Keycloak-Credentials-on-connectVM-Cloud.html.md index 9ef49bf..d95eaf8 100644 --- a/docs/openstackdev/Authenticating-to-3EnginesSDK-using-Keycloak-Credentials-on-3Engines-Cloud.html.md +++ b/docs/openstackdev/Authenticating-to-connectVMSDK-using-Keycloak-Credentials-on-connectVM-Cloud.html.md @@ -1,11 +1,11 @@ -Authenticating with 3EnginesSDK using Keycloak Credentials on 3Engines Cloud[🔗](#authenticating-with-3Enginessdk-using-keycloak-credentials-on-brand-name "Permalink to this headline") +Authenticating with connectVMSDK using Keycloak Credentials on connectVM Cloud[🔗](#authenticating-with-connectVMsdk-using-keycloak-credentials-on-brand-name "Permalink to this headline") =========================================================================================================================================================================================== -If you are using 3EnginesSDK to write your own script for 3Engines, the code in this tutorial will **enable the user to automatically log into your app**. When the user normally tries to log into the 3Engines Cloud account using , they have to log in manually. A screen like this appears: +If you are using connectVMSDK to write your own script for connectVM, the code in this tutorial will **enable the user to automatically log into your app**. When the user normally tries to log into the connectVM Cloud account using , they have to log in manually. A screen like this appears: -[![register_3Enginescloud1.png](../_images/register_3Enginescloud1.png)](../_images/register_3Enginescloud1.png) +[![register_connectVMcloud1.png](../_images/register_connectVMcloud1.png)](../_images/register_connectVMcloud1.png) -If they already have an account, they will be logged in after clicking on Login button. The code in this article will avoid exposing the user to such a procedure and if they had ever been authenticated to 3Engines, **the user will be able to log in with your code without even seeing the login screen**. +If they already have an account, they will be logged in after clicking on Login button. The code in this article will avoid exposing the user to such a procedure and if they had ever been authenticated to connectVM, **the user will be able to log in with your code without even seeing the login screen**. What Are We Going To Do[🔗](#what-are-we-going-to-do "Permalink to this headline") --------------------------------------------------------------------------------- @@ -20,11 +20,11 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") **No. 1 Install Python and its environment** -The following article will help you install Python and **pip**, as well as **Venv**: [How to install Python virtualenv or virtualenvwrapper on 3Engines Cloud](../cloud/How-to-install-Python-virtualenv-or-virtualenvwrapper-on-3Engines-Cloud.html.md). +The following article will help you install Python and **pip**, as well as **Venv**: [How to install Python virtualenv or virtualenvwrapper on connectVM Cloud](../cloud/How-to-install-Python-virtualenv-or-virtualenvwrapper-on-connectVM-Cloud.html.md). **No. 2 RC File** -RC file is available from the 3Engines Horizon module and serves as a source of authentication for the user. For technical details how to get it and activate, see [How To Install 3Engines and Magnum Clients for Command Line Interface to 3Engines Cloud Horizon](../kubernetes/How-To-Install-3Engines-and-Magnum-Clients-for-Command-Line-Interface-to-3Engines-Cloud-Horizon.html.md). +RC file is available from the connectVM Horizon module and serves as a source of authentication for the user. For technical details how to get it and activate, see [How To Install connectVM and Magnum Clients for Command Line Interface to connectVM Cloud Horizon](../kubernetes/How-To-Install-connectVM-and-Magnum-Clients-for-Command-Line-Interface-to-connectVM-Cloud-Horizon.html.md). Step 1 Source Your RC File[🔗](#step-1-source-your-rc-file "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -34,7 +34,7 @@ Using **Prerequisite No. 2**, download the corresponding RC file. That file can Here are the system variables (their names all start with **OS\_**) that the **source** command will set up as well: ``` -export OS_AUTH_URL=https://keystone.3Engines.com:5000/v3 +export OS_AUTH_URL=https://keystone.connectVM.com:5000/v3 export OS_INTERFACE=public export OS_IDENTITY_API_VERSION=3 export OS_USERNAME="Your E-mail Adress" @@ -45,9 +45,9 @@ export OS_PROJECT_DOMAIN_ID="Your Domain ID" export OS_AUTH_TYPE=v3oidcpassword export OS_PROTOCOL=openid -export OS_DISCOVERY_ENDPOINT=https://identity.3Engines.com/auth/realms/Creodias-new/.well-known/openid-configuration +export OS_DISCOVERY_ENDPOINT=https://identity.connectVM.com/auth/realms/Creodias-new/.well-known/openid-configuration export OS_IDENTITY_PROVIDER=ident_creodias-new_provider -export OS_CLIENT_ID=3Engines +export OS_CLIENT_ID=connectVM export OS_CLIENT_SECRET=50xx4972-546x-46x9-8x72-x91x401x8x30 ``` @@ -58,34 +58,34 @@ Step 2 Create Python Code that Will Perform Keycloak Authentication Within Your In this step you will copy the values from RC file to your Python code. For instance, variable ``` -OS_DISCOVERY_ENDPOINT=https://identity.3Engines.com/auth/realms/Creodias-new/.well-known/openid-configuration +OS_DISCOVERY_ENDPOINT=https://identity.connectVM.com/auth/realms/Creodias-new/.well-known/openid-configuration ``` from RC file will become the value of the eponymous variable in your code: ``` -auth['discovery_endpoint'] = "https://identity.3Engines.com/auth/realms/Creodias-new/.well-known/openid-configuration" +auth['discovery_endpoint'] = "https://identity.connectVM.com/auth/realms/Creodias-new/.well-known/openid-configuration" ``` Here is what your code should look like in the end: ``` -from 3Engines import connection +from connectVM import connection import sys import os -from 3Engines import enable_logging +from connectVM import enable_logging auth = {} -auth['auth_url'] = "https://keystone.3Engines.com:5000/v3" +auth['auth_url'] = "https://keystone.connectVM.com:5000/v3" auth['username'] = "Your E-mail Adress" auth['password'] = os.getenv('OS_PASSWORD') auth['project_domain_id'] = "Your Domain ID" auth['project_name'] = "Your Project Name" auth['project_id'] = "Your Project ID" -auth['discovery_endpoint'] = "https://identity.3Engines.com/auth/realms/Creodias-new/.well-known/openid-configuration" -auth['client_id'] = "3Engines" +auth['discovery_endpoint'] = "https://identity.connectVM.com/auth/realms/Creodias-new/.well-known/openid-configuration" +auth['client_id'] = "connectVM" auth['identity_provider'] = 'ident_creodias-new_provider' auth['client_secret'] = os.getenv('OS_CLIENT_SECRET') auth['protocol'] = 'openid' diff --git a/docs/openstackdev/Generating-and-authorizing-Terraform-using-Keycloak-user-on-3Engines-Cloud.html.md b/docs/openstackdev/Generating-and-authorizing-Terraform-using-Keycloak-user-on-connectVM-Cloud.html.md similarity index 72% rename from docs/openstackdev/Generating-and-authorizing-Terraform-using-Keycloak-user-on-3Engines-Cloud.html.md rename to docs/openstackdev/Generating-and-authorizing-Terraform-using-Keycloak-user-on-connectVM-Cloud.html.md index a8ece62..b228a43 100644 --- a/docs/openstackdev/Generating-and-authorizing-Terraform-using-Keycloak-user-on-3Engines-Cloud.html.md +++ b/docs/openstackdev/Generating-and-authorizing-Terraform-using-Keycloak-user-on-connectVM-Cloud.html.md @@ -1,13 +1,13 @@ -Generating and authorizing Terraform using Keycloak user on 3Engines Cloud[🔗](#generating-and-authorizing-terraform-using-keycloak-user-on-brand-name "Permalink to this headline") +Generating and authorizing Terraform using Keycloak user on connectVM Cloud[🔗](#generating-and-authorizing-terraform-using-keycloak-user-on-brand-name "Permalink to this headline") ===================================================================================================================================================================================== -Clicking in Horizon and entering CLI commands are two main ways of using an 3Engines system. They are well suited to interactively executing one command at a time but do not scale up easily. A tool such as [Terraform, by HashiCorp corporation,](https://www.terraform.io/) provides an alternative to manual ways of introducing cascading changes. Here is how you could, say, create several instances at once: +Clicking in Horizon and entering CLI commands are two main ways of using an connectVM system. They are well suited to interactively executing one command at a time but do not scale up easily. A tool such as [Terraform, by HashiCorp corporation,](https://www.terraform.io/) provides an alternative to manual ways of introducing cascading changes. Here is how you could, say, create several instances at once: > * Define parameters for the creation of one instance, > * save them in a Terraform configuration file and > * let Terraform automatically repeat it the prescribed number of times. -The plan is to install Terraform, get 3Engines token, enter it into the configuration file and execute. You will then be able to effectively use Terraform within the 3Engines Cloud cloud. For instance, with Terraform you can +The plan is to install Terraform, get connectVM token, enter it into the configuration file and execute. You will then be able to effectively use Terraform within the connectVM Cloud cloud. For instance, with Terraform you can > * automate creation of a multitude of virtual machines, each with their own floating IPs, DNS and network functions or > * automate creation of Kubernetes clusters @@ -19,7 +19,7 @@ What We Are Going To Do[🔗](#what-we-are-going-to-do "Permalink to this headli > * Install Terraform as a root user > * Reconnect to the cloud -> * Download 3Engines token +> * Download connectVM token > * Set up the configuration file and initialize Terraform > * Create Terraform code > * Explain the meaning of the variables used @@ -30,25 +30,25 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . In particular, you will need the password for the account so have it ready in advance. +You need a connectVM Cloud hosting account with access to the Horizon interface: . In particular, you will need the password for the account so have it ready in advance. No. 2 **Installed version of Linux** You can use your current Linux installation, however, in this article we shall start with a clean slate. Create a new VM with Ubuntu as defined in this article: -[How to create a Linux VM and access it from Linux command line on 3Engines Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md). +[How to create a Linux VM and access it from Linux command line on connectVM Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md). -No. 3 **Installed 3EnginesClient for Linux** +No. 3 **Installed connectVMClient for Linux** To get token from the cloud, you will first need to enable access from the Ubuntu VM you just created: -[How to install 3EnginesClient for Linux on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md) +[How to install connectVMClient for Linux on connectVM Cloud](../connectVMcli/How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md) -It will show you how to install Python, create and activate a virtual environment, and then connect to the cloud by downloading and activating the proper RC file from the 3Engines Cloud cloud. +It will show you how to install Python, create and activate a virtual environment, and then connect to the cloud by downloading and activating the proper RC file from the connectVM Cloud cloud. No. 4 **Connect to the cloud via an RC file** -Another article, [How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md), deals with connecting to the cloud and is covering either of the one- or two-factor authentication procedures that are enabled on your account. It also covers all the main platforms: Linux, MacOS and Windows. +Another article, [How to activate connectVM CLI access to connectVM Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-connectVM-CLI-access-to-connectVM-Cloud-cloud-using-one-or-two-factor-authentication.html.md), deals with connecting to the cloud and is covering either of the one- or two-factor authentication procedures that are enabled on your account. It also covers all the main platforms: Linux, MacOS and Windows. You will use both the Python virtual environment and the downloaded RC file **after** Terraform has been installed. @@ -98,10 +98,10 @@ su eouser # Exit root mode Step 2 Reconnect to the cloud[🔗](#step-2-reconnect-to-the-cloud "Permalink to this headline") --------------------------------------------------------------------------------------------- -Working through Prerequisites Nos. 2 and 3, you ended up being connected up to the cloud. That connection is now lost because you have switched to **root** user and back again, to the normal **eouser** for the 3Engines Cloud cloud. Refer to **Prerequisite No. 4 Activate the RC file** to reconnect to the cloud again. The following command will act as a test: +Working through Prerequisites Nos. 2 and 3, you ended up being connected up to the cloud. That connection is now lost because you have switched to **root** user and back again, to the normal **eouser** for the connectVM Cloud cloud. Refer to **Prerequisite No. 4 Activate the RC file** to reconnect to the cloud again. The following command will act as a test: ``` -3Engines flavor list +connectVM flavor list ``` @@ -111,13 +111,13 @@ and should present a start of a list of flavors available in the system: **You are now ready to receive token from the cloud you are working with.** The “token” is actually a very long string of characters which serves as kind of password for your code. -Step 3 Download 3Engines token[🔗](#step-3-download-3Engines-token "Permalink to this headline") +Step 3 Download connectVM token[🔗](#step-3-download-connectVM-token "Permalink to this headline") ------------------------------------------------------------------------------------------------- Get token with the following command: ``` -3Engines token issue -f shell -c id +connectVM token issue -f shell -c id ``` @@ -151,11 +151,11 @@ sudo nano yourconffile.tf # Name it as you want Paste the following into the file: ``` -# Configure the 3Engines Provider +# Configure the connectVM Provider terraform { required_providers { - 3Engines = { - source = "terraform-provider-3Engines/3Engines" + connectVM = { + source = "terraform-provider-connectVM/connectVM" } } } @@ -164,7 +164,7 @@ Paste the following into the file: Save the file (for Nano, use **Ctrl-X** and **Y**). -These commands inform Terraform it will work with 3Engines. +These commands inform Terraform it will work with connectVM. Use the following command to initialize Terraform: @@ -186,7 +186,7 @@ The screen after initialization would look like this: ![terraform_init.png](../_images/terraform_init.png) -Terraform has been initialized and is working properly with your 3Engines cloud. Now add code to perform some useful tasks. +Terraform has been initialized and is working properly with your connectVM cloud. Now add code to perform some useful tasks. Note @@ -198,24 +198,24 @@ Step 5 Create Terraform code[🔗](#step-5-create-terraform-code "Permalink to t Append code to the contents of the **yourconffile.tf**. It will generate four virtual machines as specified in the value of variable **count**. The entire file **yourconffile.tf** should now look like this: ``` -# Configure the 3Engines Provider +# Configure the connectVM Provider terraform { required_providers { - 3Engines = { - source = "terraform-provider-3Engines/3Engines" + connectVM = { + source = "terraform-provider-connectVM/connectVM" } } } -provider "3Engines" { +provider "connectVM" { user_name = "[email protected]" tenant_name = "cloud_00aaa_1" - auth_url = "https://keystone.3Engines.com:5000/v3" + auth_url = "https://keystone.connectVM.com:5000/v3" domain_name = "cloud_00aaa_1" token = "gAAAAABj1VTWP_CFhfKv4zWVH7avFUnHYf5J4TvuKG_Md1EdSpBIBZqTVErqVNWCnO-kYq9D7fi33aRCABadsp23-e-lrDFwyZGkfv-d83UkOTsoIuWogupmwx-3gr4wPcsikBvkAMMBD0-XMIkUONAPst6C35QnztSzZmVSeuXOJ33DaGr6yWbY-tNAOpNsk0C9c13U6ROI" } -resource "3Engines_compute_instance_v2" "test-terra" { +resource "connectVM_compute_instance_v2" "test-terra" { count = 4 name = "test-instance-${count.index}" image_id = "d7ba6aa0-d5d8-41ed-b29b-3f5336d87340" @@ -235,9 +235,9 @@ name = "cloud_00aaa_3" Always use the latest value of image id[🔗](#always-use-the-latest-value-of-image-id "Permalink to this headline") ----------------------------------------------------------------------------------------------------------------- -From time to time, the default images of operating systems in the 3Engines Cloud cloud are upgraded to the new versions. As a consequence, their **image id** will change. Let’s say that the image id for Ubuntu 20.04 LTS was **574fe1db-8099-4db4-a543-9e89526d20ae** at the time of writing of this article. While working through the article, you would normally take the **current** value of image id, and would use it to replace **574fe1db-8099-4db4-a543-9e89526d20ae** throughout the text. +From time to time, the default images of operating systems in the connectVM Cloud cloud are upgraded to the new versions. As a consequence, their **image id** will change. Let’s say that the image id for Ubuntu 20.04 LTS was **574fe1db-8099-4db4-a543-9e89526d20ae** at the time of writing of this article. While working through the article, you would normally take the **current** value of image id, and would use it to replace **574fe1db-8099-4db4-a543-9e89526d20ae** throughout the text. -Now, suppose you wanted to automate processes under 3Engines, perhaps using Heat, Terraform, Ansible or any other tool for 3Engines automation; if you use the value of **574fe1db-8099-4db4-a543-9e89526d20ae** for image id, it would remain **hardcoded** and once this value gets changed during the upgrade, the automated process may stop to execute. +Now, suppose you wanted to automate processes under connectVM, perhaps using Heat, Terraform, Ansible or any other tool for connectVM automation; if you use the value of **574fe1db-8099-4db4-a543-9e89526d20ae** for image id, it would remain **hardcoded** and once this value gets changed during the upgrade, the automated process may stop to execute. Warning @@ -249,7 +249,7 @@ The meaning of the variables used[🔗](#the-meaning-of-the-variables-used "Perm The meaning of the variables used is as follows: **user\_name** -: User name with which you log in into the 3Engines Cloud account. You can use email address here as well. +: User name with which you log in into the connectVM Cloud account. You can use email address here as well. **tenant\_name** : Starts with **cloud\_00**. You can see it in the upper left corner of the Horizon window. @@ -258,7 +258,7 @@ The meaning of the variables used is as follows: : If you have only one project in the domain, this will be identical to the **tenant\_name** from above. **token** -: The **id** value you got from command **3Engines token issue**. +: The **id** value you got from command **connectVM token issue**. **count** : How many times to repeat the operation (in this case, four new virtual machines to create) @@ -270,7 +270,7 @@ The meaning of the variables used is as follows: : The name or **ID** code for an operating systems image you get with command **Compute** -> **Images**. For example, if you choose *Ubuntu 20.04 LTS* image, its **ID** is *d7ba6aa0-d5d8-41ed-b29b-3f5336d87340*. **flavor\_id** -: Name of the flavor that each VM will have. You get these names from command **3Engines flavor list**. +: Name of the flavor that each VM will have. You get these names from command **connectVM flavor list**. **security\_groups** : Here, it is an array of two security groups – **default** and **allow\_ping\_ssh\_icmp\_rdp**. These are the basic security groups that should be used as a start for all VMs. @@ -342,4 +342,4 @@ to learn other commands Terraform can offer. What To Do Next[🔗](#id1 "Permalink to this headline") ----------------------------------------------------- -Article [How to create a set of VMs using 3Engines Heat Orchestration on 3Engines Cloud](../3Enginescli/How-to-create-a-set-of-VMs-using-3Engines-Heat-Orchestration-on-3Engines-Cloud.html.md) uses orchestration capabilities of 3Engines to automate creation of virtual machines. It is a different approach compared to Terraform but both can lead to automation under 3Engines. \ No newline at end of file +Article [How to create a set of VMs using connectVM Heat Orchestration on connectVM Cloud](../connectVMcli/How-to-create-a-set-of-VMs-using-connectVM-Heat-Orchestration-on-connectVM-Cloud.html.md) uses orchestration capabilities of connectVM to automate creation of virtual machines. It is a different approach compared to Terraform but both can lead to automation under connectVM. \ No newline at end of file diff --git a/docs/openstackdev/connectVMdev.html.md b/docs/openstackdev/connectVMdev.html.md new file mode 100644 index 0000000..34a1912 --- /dev/null +++ b/docs/openstackdev/connectVMdev.html.md @@ -0,0 +1,6 @@ +# connectVM Development + +## Available Documentation + +* [Authenticating with connectVMSDK using Keycloak Credentials on connectVM Cloud](Authenticating-to-connectVMSDK-using-Keycloak-Credentials-on-connectVM-Cloud.html.md) +* [Generating and authorizing Terraform using Keycloak user on connectVM Cloud](Generating-and-authorizing-Terraform-using-Keycloak-user-on-connectVM-Cloud.html.md) diff --git a/docs/s3/Bucket-sharing-using-s3-bucket-policy-on-3Engines-Cloud.html.md b/docs/s3/Bucket-sharing-using-s3-bucket-policy-on-connectVM-Cloud.html.md similarity index 87% rename from docs/s3/Bucket-sharing-using-s3-bucket-policy-on-3Engines-Cloud.html.md rename to docs/s3/Bucket-sharing-using-s3-bucket-policy-on-connectVM-Cloud.html.md index 735c7de..7b9bde2 100644 --- a/docs/s3/Bucket-sharing-using-s3-bucket-policy-on-3Engines-Cloud.html.md +++ b/docs/s3/Bucket-sharing-using-s3-bucket-policy-on-connectVM-Cloud.html.md @@ -1,19 +1,19 @@ -Bucket sharing using s3 bucket policy on 3Engines Cloud[🔗](#bucket-sharing-using-s3-bucket-policy-on-brand-name "Permalink to this headline") +Bucket sharing using s3 bucket policy on connectVM Cloud[🔗](#bucket-sharing-using-s3-bucket-policy-on-brand-name "Permalink to this headline") =============================================================================================================================================== S3 bucket policy[🔗](#s3-bucket-policy "Permalink to this headline") ------------------------------------------------------------------- -**Ceph** - the Software Defined Storage used in 3Engines Cloud cloud, providing object storage compatibility with a subset of Amazon S3 API. Bucket policy in Ceph is part of the S3 API and allows for a selective access sharing to object storage buckets between users of different projects, in the same cloud. +**Ceph** - the Software Defined Storage used in connectVM Cloud cloud, providing object storage compatibility with a subset of Amazon S3 API. Bucket policy in Ceph is part of the S3 API and allows for a selective access sharing to object storage buckets between users of different projects, in the same cloud. Naming conventions used in this document[🔗](#naming-conventions-used-in-this-document "Permalink to this headline") ------------------------------------------------------------------------------------------------------------------- Bucket Owner -: 3Engines tenant who created an object storage bucket in their project, intending to share to their bucket or a subset of objects in the bucket to another tenant in the same cloud. +: connectVM tenant who created an object storage bucket in their project, intending to share to their bucket or a subset of objects in the bucket to another tenant in the same cloud. Bucket User -: 3Engines tenant who wants to gain access to a Bucket Owner’s object storage bucket. +: connectVM tenant who wants to gain access to a Bucket Owner’s object storage bucket. Bucket Owner’s Project : A project in which a shared bucket is created. @@ -22,7 +22,7 @@ Bucket User’s Project : A project which gets access to Bucket Owner’s object storage bucket. Tenant Admin -: A tenant’s administrator user who can create 3Engines projects and manage users and roles within their domain. +: A tenant’s administrator user who can create connectVM projects and manage users and roles within their domain. In code examples, values typed in all-capital letters, such as BUCKET\_OWNER\_PROJECT\_ID, are placeholders which should be replaced with actual values matching your use-case. @@ -40,7 +40,7 @@ Ceph S3 implementation S3cmd CONFIGURATION[🔗](#s3cmd-configuration "Permalink to this headline") ------------------------------------------------------------------------- -To share bucket using S3 bucket policy you have to configure s3cmd first using this tutorial [How to access private object storage using S3cmd or boto3 on 3Engines Cloud](How-to-access-private-object-storage-using-S3cmd-or-boto3-on-3Engines-Cloud.html.md) +To share bucket using S3 bucket policy you have to configure s3cmd first using this tutorial [How to access private object storage using S3cmd or boto3 on connectVM Cloud](How-to-access-private-object-storage-using-S3cmd-or-boto3-on-connectVM-Cloud.html.md) Declaring bucket policy[🔗](#declaring-bucket-policy "Permalink to this headline") --------------------------------------------------------------------------------- @@ -253,7 +253,7 @@ s3cmd ls s3://MY_SHARED_BUCKET A Bucket Owner wants to grant read/write access to Bucket Users which access the bucket from specific IP ranges. -(In this case, we are setting AWS to “\*” which will theoretically grant access to every Project in 3Engines Cloud, then however we are going to filter access to only one IP) +(In this case, we are setting AWS to “\*” which will theoretically grant access to every Project in connectVM Cloud, then however we are going to filter access to only one IP) ``` { diff --git a/docs/s3/Configuration-files-for-s3cmd-command-on-3Engines-Cloud.html.md b/docs/s3/Configuration-files-for-s3cmd-command-on-connectVM-Cloud.html.md similarity index 77% rename from docs/s3/Configuration-files-for-s3cmd-command-on-3Engines-Cloud.html.md rename to docs/s3/Configuration-files-for-s3cmd-command-on-connectVM-Cloud.html.md index 56768f6..44ad30a 100644 --- a/docs/s3/Configuration-files-for-s3cmd-command-on-3Engines-Cloud.html.md +++ b/docs/s3/Configuration-files-for-s3cmd-command-on-connectVM-Cloud.html.md @@ -1,11 +1,11 @@ -Configuration files for s3cmd command on 3Engines Cloud[🔗](#configuration-files-for-s3cmd-command-on-brand-name "Permalink to this headline") +Configuration files for s3cmd command on connectVM Cloud[🔗](#configuration-files-for-s3cmd-command-on-brand-name "Permalink to this headline") =============================================================================================================================================== -[s3cmd](https://github.com/s3tools/s3cmd) can access remote data using the S3 protocol. This includes **EODATA** repository and object storage on the 3Engines Cloud cloud. +[s3cmd](https://github.com/s3tools/s3cmd) can access remote data using the S3 protocol. This includes **EODATA** repository and object storage on the connectVM Cloud cloud. To connect to S3 storage, **s3cmd** uses several parameters, such as an access key, secret key, S3 endpoint, and others. During configuration, you can enter this data interactively, and the command saves it into a configuration file. This file can then be passed to **s3cmd** when issuing commands using the connection described within. -If you want to use multiple connections from a single virtual machine (such as connecting both to the **EODATA** repository and to object storage on 3Engines Cloud cloud), you can create and store multiple configuration files — one per connection. +If you want to use multiple connections from a single virtual machine (such as connecting both to the **EODATA** repository and to object storage on connectVM Cloud cloud), you can create and store multiple configuration files — one per connection. This article provides examples of how to create and save these configuration files under various circumstances and describes some potential problems you may encounter. diff --git a/docs/s3/How-To-Install-boto3-In-Windows-on-3Engines-Cloud.html.md b/docs/s3/How-To-Install-boto3-In-Windows-on-connectVM-Cloud.html.md similarity index 65% rename from docs/s3/How-To-Install-boto3-In-Windows-on-3Engines-Cloud.html.md rename to docs/s3/How-To-Install-boto3-In-Windows-on-connectVM-Cloud.html.md index 79cda5d..63e6845 100644 --- a/docs/s3/How-To-Install-boto3-In-Windows-on-3Engines-Cloud.html.md +++ b/docs/s3/How-To-Install-boto3-In-Windows-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How to Install Boto3 in Windows on 3Engines Cloud[🔗](#how-to-install-boto3-in-windows-on-brand-name "Permalink to this headline") +How to Install Boto3 in Windows on connectVM Cloud[🔗](#how-to-install-boto3-in-windows-on-brand-name "Permalink to this headline") =================================================================================================================================== **boto3** library for Python serves for listing and downloading items from specified bucket or repository. In this article, you will install it in a Windows system. @@ -8,15 +8,15 @@ Step 1 Ensure That Python3 is Preinstalled[🔗](#step-1-ensure-that-python3-is- **On a Desktop Windows System** -To run **boto3**, you need to have Python preinstalled. If you are running Windows on a desktop computer, the first step of this article shows how to do it: [How to install 3EnginesClient GitBash for Windows on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-GitBash-or-Cygwin-for-Windows-on-3Engines-Cloud.html.md). +To run **boto3**, you need to have Python preinstalled. If you are running Windows on a desktop computer, the first step of this article shows how to do it: [How to install connectVMClient GitBash for Windows on connectVM Cloud](../connectVMcli/How-to-install-connectVMClient-GitBash-or-Cygwin-for-Windows-on-connectVM-Cloud.html.md). -**On a Virtual Machine Running in 3Engines Cloud Cloud** +**On a Virtual Machine Running in connectVM Cloud Cloud** -Virtual machines created in the 3Engines Cloud cloud will have Python3 already preinstalled. If you want to spawn your own Windows VM, two steps will be involved: +Virtual machines created in the connectVM Cloud cloud will have Python3 already preinstalled. If you want to spawn your own Windows VM, two steps will be involved: -1. Log into your 3Engines Cloud hosting account with access to the Horizon interface: . +1. Log into your connectVM Cloud hosting account with access to the Horizon interface: . -2. Use or create a new instance in the cloud. See article: [Connecting to a Windows VM via RDP through a Linux bastion host port forwarding on 3Engines Cloud](../windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-3Engines-Cloud.html.md). +2. Use or create a new instance in the cloud. See article: [Connecting to a Windows VM via RDP through a Linux bastion host port forwarding on connectVM Cloud](../windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-connectVM-Cloud.html.md). Step 2 Install boto3 on Windows[🔗](#step-2-install-boto3-on-windows "Permalink to this headline") ------------------------------------------------------------------------------------------------- diff --git a/docs/s3/How-to-access-object-storage-from-3Engines-Cloud-using-boto3.html.md b/docs/s3/How-to-access-object-storage-from-connectVM-Cloud-using-boto3.html.md similarity index 54% rename from docs/s3/How-to-access-object-storage-from-3Engines-Cloud-using-boto3.html.md rename to docs/s3/How-to-access-object-storage-from-connectVM-Cloud-using-boto3.html.md index 71459da..9192381 100644 --- a/docs/s3/How-to-access-object-storage-from-3Engines-Cloud-using-boto3.html.md +++ b/docs/s3/How-to-access-object-storage-from-connectVM-Cloud-using-boto3.html.md @@ -1,6 +1,6 @@ -How to access object storage from 3Engines Cloud using boto3[🔗](#how-to-access-object-storage-from-brand-name-using-boto3 "Permalink to this headline") +How to access object storage from connectVM Cloud using boto3[🔗](#how-to-access-object-storage-from-brand-name-using-boto3 "Permalink to this headline") ========================================================================================================================================================= -In this article, you will learn how to access object storage from 3Engines Cloud using Python library **boto3**. +In this article, you will learn how to access object storage from connectVM Cloud using Python library **boto3**. What We Are Going To Cover \ No newline at end of file diff --git a/docs/s3/How-to-access-object-storage-from-3Engines-Cloud-using-s3cmd.html.md b/docs/s3/How-to-access-object-storage-from-connectVM-Cloud-using-s3cmd.html.md similarity index 66% rename from docs/s3/How-to-access-object-storage-from-3Engines-Cloud-using-s3cmd.html.md rename to docs/s3/How-to-access-object-storage-from-connectVM-Cloud-using-s3cmd.html.md index eb57f5e..4dd1601 100644 --- a/docs/s3/How-to-access-object-storage-from-3Engines-Cloud-using-s3cmd.html.md +++ b/docs/s3/How-to-access-object-storage-from-connectVM-Cloud-using-s3cmd.html.md @@ -1,7 +1,7 @@ -How to access object storage from 3Engines Cloud using s3cmd[🔗](#how-to-access-object-storage-from-brand-name-using-s3cmd "Permalink to this headline") +How to access object storage from connectVM Cloud using s3cmd[🔗](#how-to-access-object-storage-from-brand-name-using-s3cmd "Permalink to this headline") ========================================================================================================================================================= -In this article, you will learn how to access object storage from 3Engines Cloud on Linux using [s3cmd](https://github.com/s3tools/s3cmd), without mounting it as a file system. This can be done on a virtual machine on 3Engines Cloud cloud or on a local Linux computer. +In this article, you will learn how to access object storage from connectVM Cloud on Linux using [s3cmd](https://github.com/s3tools/s3cmd), without mounting it as a file system. This can be done on a virtual machine on connectVM Cloud cloud or on a local Linux computer. What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -25,14 +25,14 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Generated EC2 credentials** -You need generate EC2 credentials. Learn more here: [How to generate and manage EC2 credentials on 3Engines Cloud](../cloud/How-to-generate-ec2-credentials-on-3Engines-Cloud.html.md) +You need generate EC2 credentials. Learn more here: [How to generate and manage EC2 credentials on connectVM Cloud](../cloud/How-to-generate-ec2-credentials-on-connectVM-Cloud.html.md) No. 3 **A Linux computer or virtual machine** You need a Linux virtual machine or local computer. This article was written for Ubuntu 22.04. Other operating systems might work, but are out of scope of this article and might require adjusting of commands. -If you want to use a virtual machine hosted on 3Engines Cloud cloud and you don’t have it yet, one of these articles can help: \ No newline at end of file +If you want to use a virtual machine hosted on connectVM Cloud cloud and you don’t have it yet, one of these articles can help: \ No newline at end of file diff --git a/docs/s3/How-to-access-private-object-storage-using-S3cmd-or-boto3-on-3Engines-Cloud.html.md b/docs/s3/How-to-access-private-object-storage-using-S3cmd-or-boto3-on-connectVM-Cloud.html.md similarity index 82% rename from docs/s3/How-to-access-private-object-storage-using-S3cmd-or-boto3-on-3Engines-Cloud.html.md rename to docs/s3/How-to-access-private-object-storage-using-S3cmd-or-boto3-on-connectVM-Cloud.html.md index 50b3764..c26d9da 100644 --- a/docs/s3/How-to-access-private-object-storage-using-S3cmd-or-boto3-on-3Engines-Cloud.html.md +++ b/docs/s3/How-to-access-private-object-storage-using-S3cmd-or-boto3-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How to access private object storage using S3cmd or boto3 on 3Engines Cloud[🔗](#how-to-access-private-object-storage-using-s3cmd-or-boto3-on-brand-name "Permalink to this headline") +How to access private object storage using S3cmd or boto3 on connectVM Cloud[🔗](#how-to-access-private-object-storage-using-s3cmd-or-boto3-on-brand-name "Permalink to this headline") ======================================================================================================================================================================================= LEGACY ARTICLE @@ -6,9 +6,9 @@ LEGACY ARTICLE This article is marked as a legacy document and may not reflect the latest information. Please refer to the following articles: -[How to access object storage from 3Engines Cloud using boto3](How-to-access-object-storage-from-3Engines-Cloud-using-boto3.html.md) +[How to access object storage from connectVM Cloud using boto3](How-to-access-object-storage-from-connectVM-Cloud-using-boto3.html.md) -[How to access object storage from 3Engines Cloud using s3cmd](How-to-access-object-storage-from-3Engines-Cloud-using-s3cmd.html.md) +[How to access object storage from connectVM Cloud using s3cmd](How-to-access-object-storage-from-connectVM-Cloud-using-s3cmd.html.md) **Introduction** @@ -16,7 +16,7 @@ Private object storage (buckets within user’s project) can be used in various **S3cmd** -In order to acquire access to Object Storage buckets via S3cmd, first you have to generate your own EC2 credentials with this tutorial [How to generate and manage EC2 credentials on 3Engines Cloud](../cloud/How-to-generate-ec2-credentials-on-3Engines-Cloud.html.md). +In order to acquire access to Object Storage buckets via S3cmd, first you have to generate your own EC2 credentials with this tutorial [How to generate and manage EC2 credentials on connectVM Cloud](../cloud/How-to-generate-ec2-credentials-on-connectVM-Cloud.html.md). Once EC2 credentials are generated, ensure that your instance or local machine is equipped with S3cmd: @@ -48,8 +48,8 @@ New settings: Access Key: (your EC2 credentials) Secret Key: (your EC2 credentials) Default Region: default -S3 Endpoint: s3.waw4-1.3Engines.com -DNS-style bucket+hostname:port template for accessing a bucket: s3.waw4-1.3Engines.com +S3 Endpoint: s3.waw4-1.connectVM.com +DNS-style bucket+hostname:port template for accessing a bucket: s3.waw4-1.connectVM.com Encryption password: (your password) Path to GPG program: /usr/bin/gpg Use HTTPS protocol: Yes @@ -63,8 +63,8 @@ New settings: Access Key: (your EC2 credentials) Secret Key: (your EC2 credentials) Default Region: waw3-1 -S3 Endpoint: s3.waw3-1.3Engines.com -DNS-style bucket+hostname:port template for accessing a bucket: s3.waw3-1.3Engines.com +S3 Endpoint: s3.waw3-1.connectVM.com +DNS-style bucket+hostname:port template for accessing a bucket: s3.waw3-1.connectVM.com Encryption password: (your password) Path to GPG program: /usr/bin/gpg Use HTTPS protocol: Yes @@ -78,8 +78,8 @@ New settings: Access Key: (your EC2 credentials) Secret Key: (your EC2 credentials) Default Region: default -S3 Endpoint: s3.waw3-2.3Engines.com -DNS-style bucket+hostname:port template for accessing a bucket: s3.waw3-2.3Engines.com +S3 Endpoint: s3.waw3-2.connectVM.com +DNS-style bucket+hostname:port template for accessing a bucket: s3.waw3-2.connectVM.com Encryption password: (your password) Path to GPG program: /usr/bin/gpg Use HTTPS protocol: Yes @@ -93,8 +93,8 @@ New settings: Access Key: (your EC2 credentials) Secret Key: (your EC2 credentials) Default Region: default -S3 Endpoint: s3.fra1-2.3Engines.com -DNS-style bucket+hostname:port template for accessing a bucket: s3.fra1-2.3Engines.co +S3 Endpoint: s3.fra1-2.connectVM.com +DNS-style bucket+hostname:port template for accessing a bucket: s3.fra1-2.connectVM.co Encryption password: (your password) Path to GPG program: /usr/bin/gpg Use HTTPS protocol: Yes @@ -124,7 +124,7 @@ s3cmd -h Warning -We strongly recommend using virtualenv for isolating python packages. Configuration tutorial is this: [How to install Python virtualenv or virtualenvwrapper on 3Engines Cloud](../cloud/How-to-install-Python-virtualenv-or-virtualenvwrapper-on-3Engines-Cloud.html.md) +We strongly recommend using virtualenv for isolating python packages. Configuration tutorial is this: [How to install Python virtualenv or virtualenvwrapper on connectVM Cloud](../cloud/How-to-install-Python-virtualenv-or-virtualenvwrapper-on-connectVM-Cloud.html.md) If virtualenv is activated: @@ -148,7 +148,7 @@ WAW4-1WAW3-1WAW3-2FRA1-2 import boto3 def boto3connection(access_key,secret_key,bucketname): -host='https://s3.waw4-1.3Engines.com' +host='https://s3.waw4-1.connectVM.com' s3=boto3.resource('s3',aws_access_key_id=access_key, aws_secret_access_key=secret_key, endpoint_url=host,) @@ -169,7 +169,7 @@ boto3connection(x,y,z) import boto3 def boto3connection(access_key,secret_key,bucketname): -host='https://s3.waw3-1.3Engines.com' +host='https://s3.waw3-1.connectVM.com' s3=boto3.resource('s3',aws_access_key_id=access_key, aws_secret_access_key=secret_key, endpoint_url=host,) @@ -190,7 +190,7 @@ boto3connection(x,y,z) import boto3 def boto3connection(access_key,secret_key,bucketname): -host='https://s3.waw3-2.3Engines.com' +host='https://s3.waw3-2.connectVM.com' s3=boto3.resource('s3',aws_access_key_id=access_key, aws_secret_access_key=secret_key, endpoint_url=host,) @@ -211,7 +211,7 @@ boto3connection(x,y,z) import boto3 def boto3connection(access_key,secret_key,bucketname): -host='https://s3.fra1-2.3Engines.com' +host='https://s3.fra1-2.connectVM.com' s3=boto3.resource('s3',aws_access_key_id=access_key, aws_secret_access_key=secret_key, endpoint_url=host,) diff --git a/docs/s3/How-to-delete-large-S3-bucket-on-3Engines-Cloud.html.md b/docs/s3/How-to-delete-large-S3-bucket-on-connectVM-Cloud.html.md similarity index 75% rename from docs/s3/How-to-delete-large-S3-bucket-on-3Engines-Cloud.html.md rename to docs/s3/How-to-delete-large-S3-bucket-on-connectVM-Cloud.html.md index e044e01..3a81783 100644 --- a/docs/s3/How-to-delete-large-S3-bucket-on-3Engines-Cloud.html.md +++ b/docs/s3/How-to-delete-large-S3-bucket-on-connectVM-Cloud.html.md @@ -1,12 +1,12 @@ -How to Delete Large S3 Bucket on 3Engines Cloud[🔗](#how-to-delete-large-s3-bucket-on-brand-name "Permalink to this headline") +How to Delete Large S3 Bucket on connectVM Cloud[🔗](#how-to-delete-large-s3-bucket-on-brand-name "Permalink to this headline") =============================================================================================================================== **Introduction** -Due to an *3Engines-cli* limitation, removing S3 buckets with more then 10 000 objects will fail when using the command: +Due to an *connectVM-cli* limitation, removing S3 buckets with more then 10 000 objects will fail when using the command: ``` -3Engines container delete --recursive <> +connectVM container delete --recursive <> ``` @@ -21,9 +21,9 @@ Conflict (HTTP 409) (Request-ID: tx00000000000001bb5e8e5-006135c488-35bc5d520-di To delete a large S3 bucket we can use **s3cmd**. -In order to acquire access to your Object Storage buckets via s3cmd, first you have to generate your own EC2 credentials with the following tutorial: [How to generate and manage EC2 credentials on 3Engines Cloud](../cloud/How-to-generate-ec2-credentials-on-3Engines-Cloud.html.md) +In order to acquire access to your Object Storage buckets via s3cmd, first you have to generate your own EC2 credentials with the following tutorial: [How to generate and manage EC2 credentials on connectVM Cloud](../cloud/How-to-generate-ec2-credentials-on-connectVM-Cloud.html.md) -After that, you have to configure s3cmd as explained in the following article: [How to access private object storage using S3cmd or boto3 on 3Engines Cloud](How-to-access-private-object-storage-using-S3cmd-or-boto3-on-3Engines-Cloud.html.md) +After that, you have to configure s3cmd as explained in the following article: [How to access private object storage using S3cmd or boto3 on connectVM Cloud](How-to-access-private-object-storage-using-S3cmd-or-boto3-on-connectVM-Cloud.html.md) After this, you should be able to list and access your Object Storage. diff --git a/docs/s3/How-to-install-s3cmd-on-Linux-on-3Engines-Cloud.html.md b/docs/s3/How-to-install-s3cmd-on-Linux-on-connectVM-Cloud.html.md similarity index 72% rename from docs/s3/How-to-install-s3cmd-on-Linux-on-3Engines-Cloud.html.md rename to docs/s3/How-to-install-s3cmd-on-Linux-on-connectVM-Cloud.html.md index 72fc644..b0cc361 100644 --- a/docs/s3/How-to-install-s3cmd-on-Linux-on-3Engines-Cloud.html.md +++ b/docs/s3/How-to-install-s3cmd-on-Linux-on-connectVM-Cloud.html.md @@ -1,10 +1,10 @@ -How to install s3cmd on Linux on 3Engines Cloud[🔗](#how-to-install-s3cmd-on-linux-on-brand-name "Permalink to this headline") +How to install s3cmd on Linux on connectVM Cloud[🔗](#how-to-install-s3cmd-on-linux-on-brand-name "Permalink to this headline") =============================================================================================================================== In this article you will learn how to install [s3cmd](https://github.com/s3tools/s3cmd) on Linux. **s3cmd** can be used, among other things, to: > * download files from EODATA repositories as well as to -> * store files in object storage available on 3Engines Cloud, +> * store files in object storage available on connectVM Cloud, without mounting these resources as a file system. @@ -19,12 +19,12 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **A virtual machine or local computer** -These instructions are for Ubuntu 22.04, either on a local computer or on a virtual machine hosted on 3Engines Cloud cloud. +These instructions are for Ubuntu 22.04, either on a local computer or on a virtual machine hosted on connectVM Cloud cloud. Other operating systems and environments are outside of scope of this article and might require adjusting of the instructions accordingly. -If you want to install **s3cmd** on a virtual machine hosted on 3Engines Cloud cloud, follow one of these articles: \ No newline at end of file +If you want to install **s3cmd** on a virtual machine hosted on connectVM Cloud cloud, follow one of these articles: \ No newline at end of file diff --git a/docs/s3/How-to-mount-object-storage-container-as-a-file-system-in-Linux-using-s3fs-on-3Engines-Cloud.html.md b/docs/s3/How-to-mount-object-storage-container-as-a-file-system-in-Linux-using-s3fs-on-connectVM-Cloud.html.md similarity index 90% rename from docs/s3/How-to-mount-object-storage-container-as-a-file-system-in-Linux-using-s3fs-on-3Engines-Cloud.html.md rename to docs/s3/How-to-mount-object-storage-container-as-a-file-system-in-Linux-using-s3fs-on-connectVM-Cloud.html.md index ceca6ad..edd9106 100644 --- a/docs/s3/How-to-mount-object-storage-container-as-a-file-system-in-Linux-using-s3fs-on-3Engines-Cloud.html.md +++ b/docs/s3/How-to-mount-object-storage-container-as-a-file-system-in-Linux-using-s3fs-on-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -How to Mount Object Storage Container as a File System in Linux Using s3fs on 3Engines Cloud[🔗](#how-to-mount-object-storage-container-as-a-file-system-in-linux-using-s3fs-on-brand-name "Permalink to this headline") +How to Mount Object Storage Container as a File System in Linux Using s3fs on connectVM Cloud[🔗](#how-to-mount-object-storage-container-as-a-file-system-in-linux-using-s3fs-on-brand-name "Permalink to this headline") ========================================================================================================================================================================================================================= -The following article covers mounting of object storage containers using **s3fs** on Linux. One of possible use cases is having easy access to content of such containers on different computers and virtual machines. For access, you can use your local Linux computer or virtual machines running on 3Engines Cloud cloud. All users of the operating system should have read, write and execute privileges on contents of these containers. +The following article covers mounting of object storage containers using **s3fs** on Linux. One of possible use cases is having easy access to content of such containers on different computers and virtual machines. For access, you can use your local Linux computer or virtual machines running on connectVM Cloud cloud. All users of the operating system should have read, write and execute privileges on contents of these containers. What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -21,17 +21,17 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Machine running Linux** -You need a machine running Linux. It can be a virtual machine running on 3Engines Cloud cloud or your local Linux computer. +You need a machine running Linux. It can be a virtual machine running on connectVM Cloud cloud or your local Linux computer. This article was written for Ubuntu 22.04. If you are running a different distribution, adjust the commands from this article accordingly. No. 3 **Object storage container** -You need at least one object storage container on 3Engines Cloud cloud. The following article shows how to create one: [How to use Object Storage on 3Engines Cloud](How-to-use-Object-Storage-on-3Engines-Cloud.html.md). +You need at least one object storage container on connectVM Cloud cloud. The following article shows how to create one: [How to use Object Storage on connectVM Cloud](How-to-use-Object-Storage-on-connectVM-Cloud.html.md). As a concrete example, let’s say that the container is named **my-files** and that it contains two items. This is what it could look like in the Horizon dashboard: @@ -41,7 +41,7 @@ With the proper **s3fs** command from this article, you will be able to access t No. 4 **Generated EC2 credentials** -You need to have EC2 credentials for your object storage containers generated. The following article will tell you how to do it: [How to generate and manage EC2 credentials on 3Engines Cloud](../cloud/How-to-generate-ec2-credentials-on-3Engines-Cloud.html.md). +You need to have EC2 credentials for your object storage containers generated. The following article will tell you how to do it: [How to generate and manage EC2 credentials on connectVM Cloud](../cloud/How-to-generate-ec2-credentials-on-connectVM-Cloud.html.md). No. 5 **Knowledge of the Linux command line** @@ -50,7 +50,7 @@ Basic knowledge of the Linux command line is required. Step 1: Sign in to your Linux machine[🔗](#step-1-sign-in-to-your-linux-machine "Permalink to this headline") ------------------------------------------------------------------------------------------------------------ -Sign in to an Ubuntu account which has **sudo** privileges. If you are using SSH to connect to a virtual machine running on 3Engines Cloud cloud, the username will likely be **eouser**. +Sign in to an Ubuntu account which has **sudo** privileges. If you are using SSH to connect to a virtual machine running on connectVM Cloud cloud, the username will likely be **eouser**. Step 2: Install s3fs[🔗](#step-2-install-s3fs "Permalink to this headline") -------------------------------------------------------------------------- @@ -119,7 +119,7 @@ Step 5: Mount a container[🔗](#step-5-mount-a-container "Permalink to this hea Here is a typical command to mount a container: ``` -sudo s3fs my-files /mnt/mount-point -o passwd_file=~/.passwd-s3fs -o url=https://s3.waw3-1.3Engines.com -o endpoint="waw3-1" -o use_path_request_style -o umask=0000 -o allow_other +sudo s3fs my-files /mnt/mount-point -o passwd_file=~/.passwd-s3fs -o url=https://s3.waw3-1.connectVM.com -o endpoint="waw3-1" -o use_path_request_style -o umask=0000 -o allow_other ``` @@ -191,7 +191,7 @@ which s3fs ``` -The output should contain the full location of the **s3fs** binary on your system. On Ubuntu virtual machines created using default images on 3Engines Cloud cloud, it will likely be: +The output should contain the full location of the **s3fs** binary on your system. On Ubuntu virtual machines created using default images on connectVM Cloud cloud, it will likely be: ``` /usr/local/bin/s3fs @@ -210,7 +210,7 @@ sudo nano /etc/fstab Append the following line to it: ``` -/usr/local/bin/s3fs#my-files /mnt/mount-point fuse passwd_file=/home/eouser/.passwd-s3fs,_netdev,allow_other,use_path_request_style,uid=0,umask=0000,mp_umask=0000,gid=0,url=https://s3.waw3-1.3Engines.com,region=waw3-1 0 0 +/usr/local/bin/s3fs#my-files /mnt/mount-point fuse passwd_file=/home/eouser/.passwd-s3fs,_netdev,allow_other,use_path_request_style,uid=0,umask=0000,mp_umask=0000,gid=0,url=https://s3.waw3-1.connectVM.com,region=waw3-1 0 0 ``` @@ -274,6 +274,6 @@ Another potential problem is that some changes to the object storage might not b What To Do Next[🔗](#what-to-do-next "Permalink to this headline") ----------------------------------------------------------------- -You can also access object storage from 3Engines Cloud without mounting it as a file system. +You can also access object storage from connectVM Cloud without mounting it as a file system. Check the following articles for more information: \ No newline at end of file diff --git a/docs/s3/How-to-mount-object-storage-container-from-3Engines-Cloud-as-file-system-on-local-Windows-computer.html.md b/docs/s3/How-to-mount-object-storage-container-from-connectVM-Cloud-as-file-system-on-local-Windows-computer.html.md similarity index 52% rename from docs/s3/How-to-mount-object-storage-container-from-3Engines-Cloud-as-file-system-on-local-Windows-computer.html.md rename to docs/s3/How-to-mount-object-storage-container-from-connectVM-Cloud-as-file-system-on-local-Windows-computer.html.md index 86bb23b..704770a 100644 --- a/docs/s3/How-to-mount-object-storage-container-from-3Engines-Cloud-as-file-system-on-local-Windows-computer.html.md +++ b/docs/s3/How-to-mount-object-storage-container-from-connectVM-Cloud-as-file-system-on-local-Windows-computer.html.md @@ -1,7 +1,7 @@ -How to mount object storage container from 3Engines Cloud as file system on local Windows computer[🔗](#how-to-mount-object-storage-container-from-brand-name-as-file-system-on-local-windows-computer "Permalink to this headline") +How to mount object storage container from connectVM Cloud as file system on local Windows computer[🔗](#how-to-mount-object-storage-container-from-brand-name-as-file-system-on-local-windows-computer "Permalink to this headline") ===================================================================================================================================================================================================================================== -This article describes how to configure direct access to object storage containers from 3Engines Cloud cloud in **This PC** window on your local Windows computer. Such containers will be mounted as network drives, for example: +This article describes how to configure direct access to object storage containers from connectVM Cloud cloud in **This PC** window on your local Windows computer. Such containers will be mounted as network drives, for example: ![object-storage-windows-example1_creodias.png](../_images/object-storage-windows-example1_creodias.png) @@ -12,16 +12,16 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface . +You need a connectVM Cloud hosting account with access to the Horizon interface . No. 2. **Object storage container** -You need at least one object storage container on the 3Engines Cloud cloud. If you do not have one yet, please follow this article: [How to use Object Storage on 3Engines Cloud](How-to-use-Object-Storage-on-3Engines-Cloud.html.md) +You need at least one object storage container on the connectVM Cloud cloud. If you do not have one yet, please follow this article: [How to use Object Storage on connectVM Cloud](How-to-use-Object-Storage-on-connectVM-Cloud.html.md) No. 3. **Generated EC2 Credentials** You need to generate EC2 credentials for your account. -The following article contains information how to do it on Linux: [How to generate and manage EC2 credentials on 3Engines Cloud](../cloud/How-to-generate-ec2-credentials-on-3Engines-Cloud.html.md). +The following article contains information how to do it on Linux: [How to generate and manage EC2 credentials on connectVM Cloud](../cloud/How-to-generate-ec2-credentials-on-connectVM-Cloud.html.md). -If instead you want to do it on Windows, you will need to install the 3Engines CLI client first. Check one of these articles to learn more. \ No newline at end of file +If instead you want to do it on Windows, you will need to install the connectVM CLI client first. Check one of these articles to learn more. \ No newline at end of file diff --git a/docs/s3/How-to-use-Object-Storage-on-3Engines-Cloud.html.md b/docs/s3/How-to-use-Object-Storage-on-connectVM-Cloud.html.md similarity index 96% rename from docs/s3/How-to-use-Object-Storage-on-3Engines-Cloud.html.md rename to docs/s3/How-to-use-Object-Storage-on-connectVM-Cloud.html.md index bb5200d..07b8ad5 100644 --- a/docs/s3/How-to-use-Object-Storage-on-3Engines-Cloud.html.md +++ b/docs/s3/How-to-use-Object-Storage-on-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -How to use Object Storage on 3Engines Cloud[🔗](#how-to-use-object-storage-on-brand-name "Permalink to this headline") +How to use Object Storage on connectVM Cloud[🔗](#how-to-use-object-storage-on-brand-name "Permalink to this headline") ======================================================================================================================= -Object storage on 3Engines Cloud cloud can be used to store your files in *containers*. In this article, you will create a basic container and perform basic operations on it, using a web browser. +Object storage on connectVM Cloud cloud can be used to store your files in *containers*. In this article, you will create a basic container and perform basic operations on it, using a web browser. What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -20,7 +20,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . Creating a new object storage container[🔗](#creating-a-new-object-storage-container "Permalink to this headline") ----------------------------------------------------------------------------------------------------------------- @@ -66,7 +66,7 @@ In this example, we will use the name **file-container** for our object storage Section **Container Access** has two options: **Public** -: It will generate a link. Anyone who has it will be able to access files stored on that object storage container, even if not being a member of 3Engines Cloud cloud. +: It will generate a link. Anyone who has it will be able to access files stored on that object storage container, even if not being a member of connectVM Cloud cloud. **Not Public** : This will not generate a link explained above. The container will only be available from within your project unless you set a bucket sharing policy (not covered in this article). diff --git a/docs/s3/S3-bucket-object-versioning-on-3Engines-Cloud.html.md b/docs/s3/S3-bucket-object-versioning-on-connectVM-Cloud.html.md similarity index 86% rename from docs/s3/S3-bucket-object-versioning-on-3Engines-Cloud.html.md rename to docs/s3/S3-bucket-object-versioning-on-connectVM-Cloud.html.md index 18639d8..dbed741 100644 --- a/docs/s3/S3-bucket-object-versioning-on-3Engines-Cloud.html.md +++ b/docs/s3/S3-bucket-object-versioning-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -S3 bucket object versioning on 3Engines Cloud[🔗](#s3-bucket-object-versioning-on-brand-name "Permalink to this headline") +S3 bucket object versioning on connectVM Cloud[🔗](#s3-bucket-object-versioning-on-brand-name "Permalink to this headline") =========================================================================================================================== S3 bucket versioning allows you to keep different versions of the file stored on object storage. Here are some typical use cases: @@ -12,7 +12,7 @@ S3 bucket versioning allows you to keep different versions of the file stored on In this article, you will learn how to -> * set up S3 bucket object versioning on 3Engines Cloud 3Engines +> * set up S3 bucket object versioning on connectVM Cloud connectVM > * download different versions of files and > * set up automatic removal of previous versions. @@ -21,11 +21,11 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to Horizon interface: . +You need a connectVM Cloud hosting account with access to Horizon interface: . No. 2 **AWS CLI installed on your local computer or virtual machine** -[AWS CLI](https://aws.amazon.com/cli/) is a free and open source software which can manage different clouds, not only those hosted by Amazon Web Services. In this article, you will use it to control your resources hosted on 3Engines Cloud cloud. +[AWS CLI](https://aws.amazon.com/cli/) is a free and open source software which can manage different clouds, not only those hosted by Amazon Web Services. In this article, you will use it to control your resources hosted on connectVM Cloud cloud. This article was written for Ubuntu 22.04. The commands may work on other operating systems, but might require adjusting. @@ -38,15 +38,15 @@ sudo apt install awscli No. 3 **Generated EC2 credentials** -To authenticate to 3Engines Cloud cloud when using AWS CLI, you need to use EC2 credentials. If you don’t have them yet, check [How to generate and manage EC2 credentials on 3Engines Cloud](../cloud/How-to-generate-ec2-credentials-on-3Engines-Cloud.html.md) +To authenticate to connectVM Cloud cloud when using AWS CLI, you need to use EC2 credentials. If you don’t have them yet, check [How to generate and manage EC2 credentials on connectVM Cloud](../cloud/How-to-generate-ec2-credentials-on-connectVM-Cloud.html.md) No. 4 **Bucket naming rules** -Over the course of this article, you will create several buckets. Make sure that you know the rules regarding what characters are allowed in bucket names. See section **Creating a new object storage container** of [How to use Object Storage on 3Engines Cloud](How-to-use-Object-Storage-on-3Engines-Cloud.html.md) to learn more. +Over the course of this article, you will create several buckets. Make sure that you know the rules regarding what characters are allowed in bucket names. See section **Creating a new object storage container** of [How to use Object Storage on connectVM Cloud](How-to-use-Object-Storage-on-connectVM-Cloud.html.md) to learn more. No. 5 **Terminology: container vs. bucket** -In this article, both “container” and “bucket” represent the same category of resources hosted on 3Engines Cloud cloud. The former term is more often used by the Horizon dashboard and the latter term is more often used by AWS CLI. +In this article, both “container” and “bucket” represent the same category of resources hosted on connectVM Cloud cloud. The former term is more often used by the Horizon dashboard and the latter term is more often used by AWS CLI. What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline") --------------------------------------------------------------------------------------- @@ -145,25 +145,25 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api list-buckets \ ---endpoint-url https://s3.waw4-1.3Engines.com +--endpoint-url https://s3.waw4-1.connectVM.com ``` ``` aws s3api list-buckets \ ---endpoint-url https://s3.waw3-1.3Engines.com +--endpoint-url https://s3.waw3-1.connectVM.com ``` ``` aws s3api list-buckets \ ---endpoint-url https://s3.waw3-2.3Engines.com +--endpoint-url https://s3.waw3-2.connectVM.com ``` ``` aws s3api list-buckets \ ---endpoint-url https://s3.fra1-2.3Engines.com +--endpoint-url https://s3.fra1-2.connectVM.com ``` @@ -304,28 +304,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api create-bucket \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api create-bucket \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api create-bucket \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api create-bucket \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 ``` @@ -341,7 +341,7 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api put-bucket-versioning \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 \ --versioning-configuration MFADelete=Disabled,Status=Enabled @@ -349,7 +349,7 @@ aws s3api put-bucket-versioning \ ``` aws s3api put-bucket-versioning \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 \ --versioning-configuration MFADelete=Disabled,Status=Enabled @@ -357,7 +357,7 @@ aws s3api put-bucket-versioning \ ``` aws s3api put-bucket-versioning \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 \ --versioning-configuration MFADelete=Disabled,Status=Enabled @@ -365,7 +365,7 @@ aws s3api put-bucket-versioning \ ``` aws s3api put-bucket-versioning \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 \ --versioning-configuration MFADelete=Disabled,Status=Enabled @@ -390,7 +390,7 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api put-object \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 \ --body something.txt \ --key something.txt @@ -399,7 +399,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 \ --body something.txt \ --key something.txt @@ -408,7 +408,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 \ --body something.txt \ --key something.txt @@ -417,7 +417,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 \ --body something.txt \ --key something.txt @@ -477,28 +477,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api create-bucket \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name2 ``` ``` aws s3api create-bucket \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name2 ``` ``` aws s3api create-bucket \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name2 ``` ``` aws s3api create-bucket \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name2 ``` @@ -509,7 +509,7 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api put-object \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name2 \ --body myfile.txt \ --key place1/place2/myfile.txt @@ -518,7 +518,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name2 \ --body myfile.txt \ --key place1/place2/myfile.txt @@ -527,7 +527,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name2 \ --body myfile.txt \ --key place1/place2/myfile.txt @@ -536,7 +536,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name2 \ --body myfile.txt \ --key place1/place2/myfile.txt @@ -560,7 +560,7 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api put-object \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --body something.txt @@ -569,7 +569,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --body something.txt @@ -578,7 +578,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --body something.txt @@ -587,7 +587,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --body something.txt @@ -611,28 +611,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api list-objects \ --bucket $bucket_name1 \ ---endpoint-url https://s3.waw4-1.3Engines.com +--endpoint-url https://s3.waw4-1.connectVM.com ``` ``` aws s3api list-objects \ --bucket $bucket_name1 \ ---endpoint-url https://s3.waw3-1.3Engines.com +--endpoint-url https://s3.waw3-1.connectVM.com ``` ``` aws s3api list-objects \ --bucket $bucket_name1 \ ---endpoint-url https://s3.waw3-2.3Engines.com +--endpoint-url https://s3.waw3-2.connectVM.com ``` ``` aws s3api list-objects \ --bucket $bucket_name1 \ ---endpoint-url https://s3.fra1-2.3Engines.com +--endpoint-url https://s3.fra1-2.connectVM.com ``` @@ -691,28 +691,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 ``` @@ -842,7 +842,7 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api get-object \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --version-id whrj2pDFrrFq0WLdH0zGzprfkebQykf \ @@ -852,7 +852,7 @@ aws s3api get-object \ ``` aws s3api get-object \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --version-id whrj2pDFrrFq0WLdH0zGzprfkebQykf \ @@ -862,7 +862,7 @@ aws s3api get-object \ ``` aws s3api get-object \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --version-id whrj2pDFrrFq0WLdH0zGzprfkebQykf \ @@ -872,7 +872,7 @@ aws s3api get-object \ ``` aws s3api get-object \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --version-id whrj2pDFrrFq0WLdH0zGzprfkebQykf \ @@ -940,7 +940,7 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api delete-object \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 \ --key something.txt @@ -948,7 +948,7 @@ aws s3api delete-object \ ``` aws s3api delete-object \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 \ --key something.txt @@ -956,7 +956,7 @@ aws s3api delete-object \ ``` aws s3api delete-object \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 \ --key something.txt @@ -964,7 +964,7 @@ aws s3api delete-object \ ``` aws s3api delete-object \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 \ --key something.txt @@ -988,28 +988,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api list-objects \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api list-objects \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api list-objects \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api list-objects \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 ``` @@ -1033,28 +1033,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 ``` @@ -1128,7 +1128,7 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api delete-object \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --version-id A0hVZCX0z6yMrlmoYymeaGPT4nzInS2 @@ -1137,7 +1137,7 @@ aws s3api delete-object \ ``` aws s3api delete-object \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --version-id A0hVZCX0z6yMrlmoYymeaGPT4nzInS2 @@ -1146,7 +1146,7 @@ aws s3api delete-object \ ``` aws s3api delete-object \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --version-id A0hVZCX0z6yMrlmoYymeaGPT4nzInS2 @@ -1155,7 +1155,7 @@ aws s3api delete-object \ ``` aws s3api delete-object \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --version-id A0hVZCX0z6yMrlmoYymeaGPT4nzInS2 @@ -1187,28 +1187,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 ``` @@ -1257,28 +1257,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api list-objects \ --bucket $bucket_name1 \ ---endpoint-url https://s3.waw4-1.3Engines.com +--endpoint-url https://s3.waw4-1.connectVM.com ``` ``` aws s3api list-objects \ --bucket $bucket_name1 \ ---endpoint-url https://s3.waw3-1.3Engines.com +--endpoint-url https://s3.waw3-1.connectVM.com ``` ``` aws s3api list-objects \ --bucket $bucket_name1 \ ---endpoint-url https://s3.waw3-2.3Engines.com +--endpoint-url https://s3.waw3-2.connectVM.com ``` ``` aws s3api list-objects \ --bucket $bucket_name1 \ ---endpoint-url https://s3.fra1-2.3Engines.com +--endpoint-url https://s3.fra1-2.connectVM.com ``` @@ -1322,7 +1322,7 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api delete-object \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --version-id t22ZzEq6kt5ILKFfLZgoeSzW.I9HVtN @@ -1331,7 +1331,7 @@ aws s3api delete-object \ ``` aws s3api delete-object \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --version-id t22ZzEq6kt5ILKFfLZgoeSzW.I9HVtN @@ -1340,7 +1340,7 @@ aws s3api delete-object \ ``` aws s3api delete-object \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --version-id t22ZzEq6kt5ILKFfLZgoeSzW.I9HVtN @@ -1349,7 +1349,7 @@ aws s3api delete-object \ ``` aws s3api delete-object \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --version-id t22ZzEq6kt5ILKFfLZgoeSzW.I9HVtN @@ -1371,28 +1371,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 ``` @@ -1431,7 +1431,7 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api delete-object \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --version-id whrj2pDFrrFq0WLdH0zGzprfkebQykf @@ -1440,7 +1440,7 @@ aws s3api delete-object \ ``` aws s3api delete-object \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --version-id whrj2pDFrrFq0WLdH0zGzprfkebQykf @@ -1449,7 +1449,7 @@ aws s3api delete-object \ ``` aws s3api delete-object \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --version-id whrj2pDFrrFq0WLdH0zGzprfkebQykf @@ -1458,7 +1458,7 @@ aws s3api delete-object \ ``` aws s3api delete-object \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 \ --key something.txt \ --version-id whrj2pDFrrFq0WLdH0zGzprfkebQykf @@ -1475,28 +1475,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 ``` @@ -1527,11 +1527,11 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api create-bucket \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name3 aws s3api put-bucket-versioning \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name3 \ --versioning-configuration MFADelete=Disabled,Status=Enabled @@ -1539,11 +1539,11 @@ aws s3api put-bucket-versioning \ ``` aws s3api create-bucket \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name3 aws s3api put-bucket-versioning \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name3 \ --versioning-configuration MFADelete=Disabled,Status=Enabled @@ -1555,7 +1555,7 @@ aws s3api create-bucket \ --bucket $bucket_name3 aws s3api put-bucket-versioning \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name3 \ --versioning-configuration MFADelete=Disabled,Status=Enabled @@ -1563,11 +1563,11 @@ aws s3api put-bucket-versioning \ ``` aws s3api create-bucket \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name3 aws s3api put-bucket-versioning \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name3 \ --versioning-configuration MFADelete=Disabled,Status=Enabled @@ -1586,13 +1586,13 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api put-object \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 \ --body mycode.py \ --key mycode.py aws s3api put-object \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 \ --body announcement.md \ --key announcement.md @@ -1601,13 +1601,13 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 \ --body mycode.py \ --key mycode.py aws s3api put-object \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 \ --body announcement.md \ --key announcement.md @@ -1616,13 +1616,13 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 \ --body mycode.py \ --key mycode.py aws s3api put-object \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 \ --body announcement.md \ --key announcement.md @@ -1631,13 +1631,13 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 \ --body mycode.py \ --key mycode.py aws s3api put-object \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 \ --body announcement.md \ --key announcement.md @@ -1650,28 +1650,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name3 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name3 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name3 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name3 ``` @@ -1719,7 +1719,7 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api put-object \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name3 \ --body mycode.py \ --key mycode.py @@ -1728,7 +1728,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name3 \ --body mycode.py \ --key mycode.py @@ -1737,7 +1737,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name3 \ --body mycode.py \ --key mycode.py @@ -1746,7 +1746,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name3 \ --body mycode.py \ --key mycode.py @@ -1759,28 +1759,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name3 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name3 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name3 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name3 ``` @@ -1867,7 +1867,7 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api put-bucket-lifecycle-configuration \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name3 \ --lifecycle-configuration file://noncurrent-policy.json @@ -1875,7 +1875,7 @@ aws s3api put-bucket-lifecycle-configuration \ ``` aws s3api put-bucket-lifecycle-configuration \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name3 \ --lifecycle-configuration file://noncurrent-policy.json @@ -1883,7 +1883,7 @@ aws s3api put-bucket-lifecycle-configuration \ ``` aws s3api put-bucket-lifecycle-configuration \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name3 \ --lifecycle-configuration file://noncurrent-policy.json @@ -1891,7 +1891,7 @@ aws s3api put-bucket-lifecycle-configuration \ ``` aws s3api put-bucket-lifecycle-configuration \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name3 \ --lifecycle-configuration file://noncurrent-policy.json @@ -1905,28 +1905,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api get-bucket-lifecycle-configuration \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name3 ``` ``` aws s3api get-bucket-lifecycle-configuration \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name3 ``` ``` aws s3api get-bucket-lifecycle-configuration \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name3 ``` ``` aws s3api get-bucket-lifecycle-configuration \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name3 ``` @@ -1959,28 +1959,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name3 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name3 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name3 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name3 ``` @@ -2030,28 +2030,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api delete-bucket-lifecycle \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name3 ``` ``` aws s3api delete-bucket-lifecycle \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name3 ``` ``` aws s3api delete-bucket-lifecycle \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name3 ``` ``` aws s3api delete-bucket-lifecycle \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name3 ``` @@ -2064,28 +2064,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api get-bucket-lifecycle-configuration \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name3 ``` ``` aws s3api get-bucket-lifecycle-configuration \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name3 ``` ``` aws s3api get-bucket-lifecycle-configuration \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name3 ``` ``` aws s3api get-bucket-lifecycle-configuration \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name3 ``` @@ -2120,28 +2120,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api create-bucket \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name4 ``` ``` aws s3api create-bucket \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name4 ``` ``` aws s3api create-bucket \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name4 ``` ``` aws s3api create-bucket \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name4 ``` @@ -2163,19 +2163,19 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api put-object \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 \ --body document.odt \ --key document.odt aws s3api put-object \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 \ --body screenshot1.png \ --key screenshot1.png aws s3api put-object \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name1 \ --body script.sh \ --key script.sh @@ -2184,19 +2184,19 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 \ --body document.odt \ --key document.odt aws s3api put-object \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 \ --body screenshot1.png \ --key screenshot1.png aws s3api put-object \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name1 \ --body script.sh \ --key script.sh @@ -2205,19 +2205,19 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 \ --body document.odt \ --key document.odt aws s3api put-object \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 \ --body screenshot1.png \ --key screenshot1.png aws s3api put-object \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name1 \ --body script.sh \ --key script.sh @@ -2226,19 +2226,19 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 \ --body document.odt \ --key document.odt aws s3api put-object \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 \ --body screenshot1.png \ --key screenshot1.png aws s3api put-object \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name1 \ --body script.sh \ --key script.sh @@ -2251,28 +2251,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name4 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name4 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name4 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name4 ``` @@ -2337,7 +2337,7 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api put-object \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name4 \ --body script.sh \ --key script.sh @@ -2346,7 +2346,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name4 \ --body script.sh \ --key script.sh @@ -2355,7 +2355,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name4 \ --body script.sh \ --key script.sh @@ -2364,7 +2364,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name4 \ --body script.sh \ --key script.sh @@ -2386,28 +2386,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name4 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name4 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name4 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name4 ``` @@ -2485,28 +2485,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api create-bucket \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name5 ``` ``` aws s3api create-bucket \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name5 ``` ``` aws s3api create-bucket \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name5 ``` ``` aws s3api create-bucket \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name5 ``` @@ -2517,7 +2517,7 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api put-bucket-versioning \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name5 \ --versioning-configuration MFADelete=Disabled,Status=Enabled @@ -2525,7 +2525,7 @@ aws s3api put-bucket-versioning \ ``` aws s3api put-bucket-versioning \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name5 \ --versioning-configuration MFADelete=Disabled,Status=Enabled @@ -2533,7 +2533,7 @@ aws s3api put-bucket-versioning \ ``` aws s3api put-bucket-versioning \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name5 \ --versioning-configuration MFADelete=Disabled,Status=Enabled @@ -2541,7 +2541,7 @@ aws s3api put-bucket-versioning \ ``` aws s3api put-bucket-versioning \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name5 \ --versioning-configuration MFADelete=Disabled,Status=Enabled @@ -2566,28 +2566,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name5 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name5 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name5 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name5 ``` @@ -2648,7 +2648,7 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api put-bucket-versioning \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name5 \ --versioning-configuration MFADelete=Disabled,Status=Suspended @@ -2656,7 +2656,7 @@ aws s3api put-bucket-versioning \ ``` aws s3api put-bucket-versioning \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name5 \ --versioning-configuration MFADelete=Disabled,Status=Suspended @@ -2664,7 +2664,7 @@ aws s3api put-bucket-versioning \ ``` aws s3api put-bucket-versioning \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name5 \ --versioning-configuration MFADelete=Disabled,Status=Suspended @@ -2672,7 +2672,7 @@ aws s3api put-bucket-versioning \ ``` aws s3api put-bucket-versioning \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name5 \ --versioning-configuration MFADelete=Disabled,Status=Suspended @@ -2686,28 +2686,28 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name5 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name5 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name5 ``` ``` aws s3api list-object-versions \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name5 ``` @@ -2771,7 +2771,7 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api put-object \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name5 \ --body file1.txt \ --key file1.txt @@ -2780,7 +2780,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name5 \ --body file1.txt \ --key file1.txt @@ -2789,7 +2789,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name5 \ --body file1.txt \ --key file1.txt @@ -2798,7 +2798,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name5 \ --body file1.txt \ --key file1.txt @@ -2881,7 +2881,7 @@ WAW4-1WAW3-1WAW3-2FRA1-2 ``` aws s3api put-object \ ---endpoint-url https://s3.waw4-1.3Engines.com \ +--endpoint-url https://s3.waw4-1.connectVM.com \ --bucket $bucket_name5 \ --body file1.txt \ --key file1.txt @@ -2890,7 +2890,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.waw3-1.3Engines.com \ +--endpoint-url https://s3.waw3-1.connectVM.com \ --bucket $bucket_name5 \ --body file1.txt \ --key file1.txt @@ -2899,7 +2899,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.waw3-2.3Engines.com \ +--endpoint-url https://s3.waw3-2.connectVM.com \ --bucket $bucket_name5 \ --body file1.txt \ --key file1.txt @@ -2908,7 +2908,7 @@ aws s3api put-object \ ``` aws s3api put-object \ ---endpoint-url https://s3.fra1-2.3Engines.com \ +--endpoint-url https://s3.fra1-2.connectVM.com \ --bucket $bucket_name5 \ --body file1.txt \ --key file1.txt @@ -2986,13 +2986,13 @@ What To Do Next[🔗](#what-to-do-next "Permalink to this headline") AWS CLI is not the only available way of interacting with object storage. Other ways include: Horizon dashboard -: [How to use Object Storage on 3Engines Cloud](How-to-use-Object-Storage-on-3Engines-Cloud.html.md) +: [How to use Object Storage on connectVM Cloud](How-to-use-Object-Storage-on-connectVM-Cloud.html.md) s3fs -: [How to Mount Object Storage Container as a File System in Linux Using s3fs on 3Engines Cloud](How-to-mount-object-storage-container-as-a-file-system-in-Linux-using-s3fs-on-3Engines-Cloud.html.md) +: [How to Mount Object Storage Container as a File System in Linux Using s3fs on connectVM Cloud](How-to-mount-object-storage-container-as-a-file-system-in-Linux-using-s3fs-on-connectVM-Cloud.html.md) Rclone -: [How to mount object storage container from 3Engines Cloud as file system on local Windows computer](How-to-mount-object-storage-container-from-3Engines-Cloud-as-file-system-on-local-Windows-computer.html.md) +: [How to mount object storage container from connectVM Cloud as file system on local Windows computer](How-to-mount-object-storage-container-from-connectVM-Cloud-as-file-system-on-local-Windows-computer.html.md) s3cmd -: [How to access object storage from 3Engines Cloud using s3cmd](How-to-access-object-storage-from-3Engines-Cloud-using-s3cmd.html.md) \ No newline at end of file +: [How to access object storage from connectVM Cloud using s3cmd](How-to-access-object-storage-from-connectVM-Cloud-using-s3cmd.html.md) \ No newline at end of file diff --git a/docs/s3/Server-Side-Encryption-with-Customer-Managed-Keys-SSE-C-on-3Engines-Cloud.html.md b/docs/s3/Server-Side-Encryption-with-Customer-Managed-Keys-SSE-C-on-connectVM-Cloud.html.md similarity index 89% rename from docs/s3/Server-Side-Encryption-with-Customer-Managed-Keys-SSE-C-on-3Engines-Cloud.html.md rename to docs/s3/Server-Side-Encryption-with-Customer-Managed-Keys-SSE-C-on-connectVM-Cloud.html.md index 5a7e1e3..3b43f8a 100644 --- a/docs/s3/Server-Side-Encryption-with-Customer-Managed-Keys-SSE-C-on-3Engines-Cloud.html.md +++ b/docs/s3/Server-Side-Encryption-with-Customer-Managed-Keys-SSE-C-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -Server-Side Encryption with Customer-Managed Keys (SSE-C) on 3Engines Cloud[🔗](#server-side-encryption-with-customer-managed-keys-sse-c-on-brand-name "Permalink to this headline") +Server-Side Encryption with Customer-Managed Keys (SSE-C) on connectVM Cloud[🔗](#server-side-encryption-with-customer-managed-keys-sse-c-on-brand-name "Permalink to this headline") ===================================================================================================================================================================================== Introduction[🔗](#introduction "Permalink to this headline") @@ -13,10 +13,10 @@ SSE-C is working as on the moment of uploading an object. Server uses the encryp Requirements[🔗](#requirements "Permalink to this headline") ----------------------------------------------------------- -* A bucket ([How to use Object Storage on 3Engines Cloud](How-to-use-Object-Storage-on-3Engines-Cloud.html.md)) +* A bucket ([How to use Object Storage on connectVM Cloud](How-to-use-Object-Storage-on-connectVM-Cloud.html.md)) * A user with the required access rights on the bucket -* EC2 credentials ([How to generate and manage EC2 credentials on 3Engines Cloud](../cloud/How-to-generate-ec2-credentials-on-3Engines-Cloud.html.md)) +* EC2 credentials ([How to generate and manage EC2 credentials on connectVM Cloud](../cloud/How-to-generate-ec2-credentials-on-connectVM-Cloud.html.md)) * Have installed and configured aws If you have not used aws before: @@ -107,7 +107,7 @@ aws s3api put-object \ --sse-customer-algorithm AES256 \ --sse-customer-key $key \ --sse-customer-key-md5 $keymd5 \ - --endpoint-url https://s3.waw3-1.3Engines.com + --endpoint-url https://s3.waw3-1.connectVM.com ``` @@ -118,7 +118,7 @@ Example No 3 aws-cli (s3)[🔗](#example-no-3-aws-cli-s3 "Permalink to this head aws s3 cp file.txt s3://bucket-name/ \ --sse-c-key $secret \ --sse-c AES256 \ - --endpoint https://s3.waw3-1.3Engines.com + --endpoint https://s3.waw3-1.connectVM.com ``` @@ -129,7 +129,7 @@ Example No 4 aws-cli (s3 blob)[🔗](#example-no-4-aws-cli-s3-blob "Permalink to aws s3 cp file.txt s3://bucket/ \ --sse-c-key fileb://sse-c.key \ --sse-c AES256 \ ---endpoint https://s3.waw3-1.3Engines.com +--endpoint https://s3.waw3-1.connectVM.com ``` @@ -145,7 +145,7 @@ aws s3api get-object --bucket \ --key \ --sse-customer-key $secret \ --sse-customer-algorithm AES256 \ - --endpoint https://s3.waw3-1.3Engines.com + --endpoint https://s3.waw3-1.connectVM.com ``` @@ -156,6 +156,6 @@ aws s3api get-object --bucket \ --key \ --sse-customer-key fileb:// \ --sse-customer-algorithm AES256 \ - --endpoint https://s3.waw3-1.3Engines.com + --endpoint https://s3.waw3-1.connectVM.com ``` \ No newline at end of file diff --git a/docs/s3/s3.html.md b/docs/s3/s3.html.md index 27a5c63..a07cd2d 100644 --- a/docs/s3/s3.html.md +++ b/docs/s3/s3.html.md @@ -2,16 +2,16 @@ ## Available Documentation -* [How to Delete Large S3 Bucket on 3Engines Cloud](How-to-delete-large-S3-bucket-on-3Engines-Cloud.html.md) -* [How to Mount Object Storage Container as a File System in Linux Using s3fs on 3Engines Cloud](How-to-mount-object-storage-container-as-a-file-system-in-Linux-using-s3fs-on-3Engines-Cloud.html.md) -* [Bucket sharing using s3 bucket policy on 3Engines Cloud](Bucket-sharing-using-s3-bucket-policy-on-3Engines-Cloud.html.md) -* [How to use Object Storage on 3Engines Cloud](How-to-use-Object-Storage-on-3Engines-Cloud.html.md) -* [How to access private object storage using S3cmd or boto3 on 3Engines Cloud](How-to-access-private-object-storage-using-S3cmd-or-boto3-on-3Engines-Cloud.html.md) -* [How to Install Boto3 in Windows on 3Engines Cloud](How-To-Install-boto3-In-Windows-on-3Engines-Cloud.html.md) -* [Server-Side Encryption with Customer-Managed Keys (SSE-C) on 3Engines Cloud](Server-Side-Encryption-with-Customer-Managed-Keys-SSE-C-on-3Engines-Cloud.html.md) -* [How to mount object storage container from 3Engines Cloud as file system on local Windows computer](How-to-mount-object-storage-container-from-3Engines-Cloud-as-file-system-on-local-Windows-computer.html.md) -* [How to install s3cmd on Linux on 3Engines Cloud](How-to-install-s3cmd-on-Linux-on-3Engines-Cloud.html.md) -* [How to access object storage from 3Engines Cloud using boto3](How-to-access-object-storage-from-3Engines-Cloud-using-boto3.html.md) -* [How to access object storage from 3Engines Cloud using s3cmd](How-to-access-object-storage-from-3Engines-Cloud-using-s3cmd.html.md) -* [Configuration files for s3cmd command on 3Engines Cloud](Configuration-files-for-s3cmd-command-on-3Engines-Cloud.html.md) -* [S3 bucket object versioning on 3Engines Cloud](S3-bucket-object-versioning-on-3Engines-Cloud.html.md) +* [How to Delete Large S3 Bucket on connectVM Cloud](How-to-delete-large-S3-bucket-on-connectVM-Cloud.html.md) +* [How to Mount Object Storage Container as a File System in Linux Using s3fs on connectVM Cloud](How-to-mount-object-storage-container-as-a-file-system-in-Linux-using-s3fs-on-connectVM-Cloud.html.md) +* [Bucket sharing using s3 bucket policy on connectVM Cloud](Bucket-sharing-using-s3-bucket-policy-on-connectVM-Cloud.html.md) +* [How to use Object Storage on connectVM Cloud](How-to-use-Object-Storage-on-connectVM-Cloud.html.md) +* [How to access private object storage using S3cmd or boto3 on connectVM Cloud](How-to-access-private-object-storage-using-S3cmd-or-boto3-on-connectVM-Cloud.html.md) +* [How to Install Boto3 in Windows on connectVM Cloud](How-To-Install-boto3-In-Windows-on-connectVM-Cloud.html.md) +* [Server-Side Encryption with Customer-Managed Keys (SSE-C) on connectVM Cloud](Server-Side-Encryption-with-Customer-Managed-Keys-SSE-C-on-connectVM-Cloud.html.md) +* [How to mount object storage container from connectVM Cloud as file system on local Windows computer](How-to-mount-object-storage-container-from-connectVM-Cloud-as-file-system-on-local-Windows-computer.html.md) +* [How to install s3cmd on Linux on connectVM Cloud](How-to-install-s3cmd-on-Linux-on-connectVM-Cloud.html.md) +* [How to access object storage from connectVM Cloud using boto3](How-to-access-object-storage-from-connectVM-Cloud-using-boto3.html.md) +* [How to access object storage from connectVM Cloud using s3cmd](How-to-access-object-storage-from-connectVM-Cloud-using-s3cmd.html.md) +* [Configuration files for s3cmd command on connectVM Cloud](Configuration-files-for-s3cmd-command-on-connectVM-Cloud.html.md) +* [S3 bucket object versioning on connectVM Cloud](S3-bucket-object-versioning-on-connectVM-Cloud.html.md) diff --git a/docs/windows/Can-I-change-my-password-through-RDP-on-3Engines-Cloud.html.md b/docs/windows/Can-I-change-my-password-through-RDP-on-connectVM-Cloud.html.md similarity index 92% rename from docs/windows/Can-I-change-my-password-through-RDP-on-3Engines-Cloud.html.md rename to docs/windows/Can-I-change-my-password-through-RDP-on-connectVM-Cloud.html.md index 951535b..97968cc 100644 --- a/docs/windows/Can-I-change-my-password-through-RDP-on-3Engines-Cloud.html.md +++ b/docs/windows/Can-I-change-my-password-through-RDP-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -Can I change my password through RDP on 3Engines Cloud?[🔗](#can-i-change-my-password-through-rdp-on-brand-name "Permalink to this headline") +Can I change my password through RDP on connectVM Cloud?[🔗](#can-i-change-my-password-through-rdp-on-brand-name "Permalink to this headline") ============================================================================================================================================== In short: No, this is not possible. You have to be logged in when you want to change your password. Security measures requiring you to change your password on first login are not working with RDP and have to be disabled on administrative level. @@ -15,7 +15,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline") No. 1 **Account** -You need a 3Engines Cloud hosting account with access to the Horizon interface: . +You need a connectVM Cloud hosting account with access to the Horizon interface: . No. 2 **Windows VM** diff --git a/docs/windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-3Engines-Cloud.html.md b/docs/windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-connectVM-Cloud.html.md similarity index 88% rename from docs/windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-3Engines-Cloud.html.md rename to docs/windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-connectVM-Cloud.html.md index 5aa2e0a..46a9bfe 100644 --- a/docs/windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-3Engines-Cloud.html.md +++ b/docs/windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -Connecting to a Windows VM via RDP through a Linux bastion host port forwarding on 3Engines Cloud[🔗](#connecting-to-a-windows-vm-via-rdp-through-a-linux-bastion-host-port-forwarding-on-brand-name "Permalink to this headline") +Connecting to a Windows VM via RDP through a Linux bastion host port forwarding on connectVM Cloud[🔗](#connecting-to-a-windows-vm-via-rdp-through-a-linux-bastion-host-port-forwarding-on-brand-name "Permalink to this headline") =================================================================================================================================================================================================================================== If you want to increase the security of your Windows VMs while connecting to them via RDP, you might want to use the method described in this article. It involves connecting to your Windows VM not directly through RDP, but through another virtual machine running Linux known as the “bastion host”. In this case, the RDP connection gets tunneled through SSH and is not directly visible to others. @@ -11,9 +11,9 @@ This method is especially useful if you fear that your RDP connection might be c * Linux virtual machine with SSH access - bastion host * Windows virtual machine located in the same network as the bastion host -* The private key downloaded from 3Engines dashboard converted from .pem to .ppk format (using “PuTTYgen”) - for information on how to do this please see [How to access a VM from Windows PuTTY on 3Engines Cloud](How-to-access-a-VM-from-Windows-PuTTY-on-3Engines-Cloud.html.md) +* The private key downloaded from connectVM dashboard converted from .pem to .ppk format (using “PuTTYgen”) - for information on how to do this please see [How to access a VM from Windows PuTTY on connectVM Cloud](How-to-access-a-VM-from-Windows-PuTTY-on-connectVM-Cloud.html.md) -* The password for the Administrator account has been changed via the 3Engines dashboard console +* The password for the Administrator account has been changed via the connectVM dashboard console * Your VMs are assigned the following security group: allow\_ping\_ssh\_icmp\_rdp ![conn01.png](../_images/conn01.png) @@ -65,7 +65,7 @@ Set the username as “Administrator”. ![conn07b.png](../_images/conn07b.png) -Click “Connect” and enter your VM’s administrator password (the one you’ve set in the 3Engines console). +Click “Connect” and enter your VM’s administrator password (the one you’ve set in the connectVM console). ![conn08b.png](../_images/conn08b.png) diff --git a/docs/windows/How-To-Create-SSH-Key-Pair-In-Windows-11-On-3Engines-Cloud.html.md b/docs/windows/How-To-Create-SSH-Key-Pair-In-Windows-11-On-connectVM-Cloud.html.md similarity index 89% rename from docs/windows/How-To-Create-SSH-Key-Pair-In-Windows-11-On-3Engines-Cloud.html.md rename to docs/windows/How-To-Create-SSH-Key-Pair-In-Windows-11-On-connectVM-Cloud.html.md index e5cd337..5fa7796 100644 --- a/docs/windows/How-To-Create-SSH-Key-Pair-In-Windows-11-On-3Engines-Cloud.html.md +++ b/docs/windows/How-To-Create-SSH-Key-Pair-In-Windows-11-On-connectVM-Cloud.html.md @@ -1,7 +1,7 @@ -How to Create SSH Key Pair in Windows 11 On 3Engines Cloud[🔗](#how-to-create-ssh-key-pair-in-windows-11-on-brand-name "Permalink to this headline") +How to Create SSH Key Pair in Windows 11 On connectVM Cloud[🔗](#how-to-create-ssh-key-pair-in-windows-11-on-brand-name "Permalink to this headline") ===================================================================================================================================================== -This guide will show you how to generate an SSH key pair in Windows 11 using OpenSSH. You will then be able to use that key pair to control appropriately configured virtual machines hosted on 3Engines Cloud cloud. +This guide will show you how to generate an SSH key pair in Windows 11 using OpenSSH. You will then be able to use that key pair to control appropriately configured virtual machines hosted on connectVM Cloud cloud. This article only covers the basics of this function and assumes that you will not change the names of generated keys. @@ -151,16 +151,16 @@ If you want to see the full extensions of files, including **.pub**, click **Vie What To Do Next[🔗](#what-to-do-next "Permalink to this headline") ----------------------------------------------------------------- -For Windows 10, see this guide: [How to Create SSH Key Pair in Windows 10 On 3Engines Cloud](How-To-Create-SSH-Key-Pair-In-Windows-On-3Engines-Cloud.html.md) +For Windows 10, see this guide: [How to Create SSH Key Pair in Windows 10 On connectVM Cloud](How-To-Create-SSH-Key-Pair-In-Windows-On-connectVM-Cloud.html.md) -To be able to easily add your new public key to VMs you might create in the future, upload it to 3Engines. Thanks to that, you will be able to use it to authenticate to VMs which support it. +To be able to easily add your new public key to VMs you might create in the future, upload it to connectVM. Thanks to that, you will be able to use it to authenticate to VMs which support it. Learn more here: -[How to add SSH key from Horizon web console on 3Engines Cloud](../networking/How-to-add-SSH-key-from-Horizon-web-console-on-3Engines-Cloud.html.md) +[How to add SSH key from Horizon web console on connectVM Cloud](../networking/How-to-add-SSH-key-from-Horizon-web-console-on-connectVM-Cloud.html.md) -Once you’ve done it, you can create a new virtual machine on 3Engines Cloud cloud and authenticate with your key pair: +Once you’ve done it, you can create a new virtual machine on connectVM Cloud cloud and authenticate with your key pair: -[How to create a Linux VM and access it from Windows desktop on 3Engines Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md) +[How to create a Linux VM and access it from Windows desktop on connectVM Cloud](../cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-connectVM-Cloud.html.md) The following articles cover how to connect to virtual machines via SSH once they’ve already been created: \ No newline at end of file diff --git a/docs/windows/How-To-Create-SSH-Key-Pair-In-Windows-On-3Engines-Cloud.html.md b/docs/windows/How-To-Create-SSH-Key-Pair-In-Windows-On-connectVM-Cloud.html.md similarity index 82% rename from docs/windows/How-To-Create-SSH-Key-Pair-In-Windows-On-3Engines-Cloud.html.md rename to docs/windows/How-To-Create-SSH-Key-Pair-In-Windows-On-connectVM-Cloud.html.md index e0908b6..385eca2 100644 --- a/docs/windows/How-To-Create-SSH-Key-Pair-In-Windows-On-3Engines-Cloud.html.md +++ b/docs/windows/How-To-Create-SSH-Key-Pair-In-Windows-On-connectVM-Cloud.html.md @@ -1,4 +1,4 @@ -How to Create SSH Key Pair in Windows 10 On 3Engines Cloud[🔗](#how-to-create-ssh-key-pair-in-windows-10-on-brand-name "Permalink to this headline") +How to Create SSH Key Pair in Windows 10 On connectVM Cloud[🔗](#how-to-create-ssh-key-pair-in-windows-10-on-brand-name "Permalink to this headline") ===================================================================================================================================================== This guide will show you how to generate an SSH key pair in Windows 10 using OpenSSH. @@ -45,7 +45,7 @@ Step 2: Open Command Prompt[🔗](#step-2-open-command-prompt "Permalink to this Step 3: Use OpenSSH to Generate an SSH Key Pair[🔗](#step-3-use-openssh-to-generate-an-ssh-key-pair "Permalink to this headline") -------------------------------------------------------------------------------------------------------------------------------- -Finally, run **ssh-keygen** to generate the public and private keys for SSH access to the 3Engines Cloud server. +Finally, run **ssh-keygen** to generate the public and private keys for SSH access to the connectVM Cloud server. 1. In command prompt, type the following: @@ -79,14 +79,14 @@ The image shows default values of files for private and public keys, in files ** What To Do Next[🔗](#what-to-do-next "Permalink to this headline") ----------------------------------------------------------------- -For Windows 11, see this guide: [How to Create SSH Key Pair in Windows 11 On 3Engines Cloud](How-To-Create-SSH-Key-Pair-In-Windows-11-On-3Engines-Cloud.html.md) +For Windows 11, see this guide: [How to Create SSH Key Pair in Windows 11 On connectVM Cloud](How-To-Create-SSH-Key-Pair-In-Windows-11-On-connectVM-Cloud.html.md) Put your public key on remote server and use your private key to authorize to your VM. To add the public key to remote server see -[How to add SSH key from Horizon web console on 3Engines Cloud](../networking/How-to-add-SSH-key-from-Horizon-web-console-on-3Engines-Cloud.html.md) +[How to add SSH key from Horizon web console on connectVM Cloud](../networking/How-to-add-SSH-key-from-Horizon-web-console-on-connectVM-Cloud.html.md) To connect to the server from Windows: -[How to connect to a virtual machine via SSH from Windows 10 Command Prompt on 3Engines Cloud](How-to-connect-to-a-virtual-machine-via-SSH-from-Windows-10-Command-Prompt-on-3Engines-Cloud.html.md) +[How to connect to a virtual machine via SSH from Windows 10 Command Prompt on connectVM Cloud](How-to-connect-to-a-virtual-machine-via-SSH-from-Windows-10-Command-Prompt-on-connectVM-Cloud.html.md) -[How to access a VM from Windows PuTTY on 3Engines Cloud](How-to-access-a-VM-from-Windows-PuTTY-on-3Engines-Cloud.html.md) \ No newline at end of file +[How to access a VM from Windows PuTTY on connectVM Cloud](How-to-access-a-VM-from-Windows-PuTTY-on-connectVM-Cloud.html.md) \ No newline at end of file diff --git a/docs/windows/How-to-access-a-VM-from-Windows-PuTTY-on-3Engines-Cloud.html.md b/docs/windows/How-to-access-a-VM-from-Windows-PuTTY-on-connectVM-Cloud.html.md similarity index 90% rename from docs/windows/How-to-access-a-VM-from-Windows-PuTTY-on-3Engines-Cloud.html.md rename to docs/windows/How-to-access-a-VM-from-Windows-PuTTY-on-connectVM-Cloud.html.md index 49e087a..303bcd8 100644 --- a/docs/windows/How-to-access-a-VM-from-Windows-PuTTY-on-3Engines-Cloud.html.md +++ b/docs/windows/How-to-access-a-VM-from-Windows-PuTTY-on-connectVM-Cloud.html.md @@ -1,9 +1,9 @@ -How to access a VM from Windows PuTTY on 3Engines Cloud[🔗](#how-to-access-a-vm-from-windows-putty-on-brand-name "Permalink to this headline") +How to access a VM from Windows PuTTY on connectVM Cloud[🔗](#how-to-access-a-vm-from-windows-putty-on-brand-name "Permalink to this headline") =============================================================================================================================================== The link below shows how to generate and add rsa key pairs: -[How to connect to a virtual machine via SSH from Windows 10 Command Prompt on 3Engines Cloud](How-to-connect-to-a-virtual-machine-via-SSH-from-Windows-10-Command-Prompt-on-3Engines-Cloud.html.md) +[How to connect to a virtual machine via SSH from Windows 10 Command Prompt on connectVM Cloud](How-to-connect-to-a-virtual-machine-via-SSH-from-Windows-10-Command-Prompt-on-connectVM-Cloud.html.md) In this tutorial key.pem is equivalent to the id\_rsa file that we obtain in a zip package after the key generation process. diff --git a/docs/windows/How-to-connect-to-a-virtual-machine-via-SSH-from-Windows-10-Command-Prompt-on-3Engines-Cloud.html.md b/docs/windows/How-to-connect-to-a-virtual-machine-via-SSH-from-Windows-10-Command-Prompt-on-connectVM-Cloud.html.md similarity index 77% rename from docs/windows/How-to-connect-to-a-virtual-machine-via-SSH-from-Windows-10-Command-Prompt-on-3Engines-Cloud.html.md rename to docs/windows/How-to-connect-to-a-virtual-machine-via-SSH-from-Windows-10-Command-Prompt-on-connectVM-Cloud.html.md index b3c7233..3ac7c00 100644 --- a/docs/windows/How-to-connect-to-a-virtual-machine-via-SSH-from-Windows-10-Command-Prompt-on-3Engines-Cloud.html.md +++ b/docs/windows/How-to-connect-to-a-virtual-machine-via-SSH-from-Windows-10-Command-Prompt-on-connectVM-Cloud.html.md @@ -1,14 +1,14 @@ -How to connect to a virtual machine via SSH from Windows 10 Command Prompt on 3Engines Cloud[🔗](#how-to-connect-to-a-virtual-machine-via-ssh-from-windows-10-command-prompt-on-brand-name "Permalink to this headline") +How to connect to a virtual machine via SSH from Windows 10 Command Prompt on connectVM Cloud[🔗](#how-to-connect-to-a-virtual-machine-via-ssh-from-windows-10-command-prompt-on-brand-name "Permalink to this headline") ========================================================================================================================================================================================================================= Requirements[🔗](#requirements "Permalink to this headline") ----------------------------------------------------------- -The private and public keys were created and saved on the local disk of your computer. ([How to create key pair in 3Engines Dashboard on 3Engines Cloud](../cloud/How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md)) +The private and public keys were created and saved on the local disk of your computer. ([How to create key pair in connectVM Dashboard on connectVM Cloud](../cloud/How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md)) -During the virtual machine creation procedure, the generated key was attached. ([How to create new Linux VM in 3Engines Dashboard Horizon on 3Engines Cloud](../cloud/How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md)) +During the virtual machine creation procedure, the generated key was attached. ([How to create new Linux VM in connectVM Dashboard Horizon on connectVM Cloud](../cloud/How-to-create-new-Linux-VM-in-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md)) -A floating IP was assigned to your VM. ([How to Add or Remove Floating IP’s to your VM on 3Engines Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md)) +A floating IP was assigned to your VM. ([How to Add or Remove Floating IP’s to your VM on connectVM Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md)) Check in “Installed features” if the OpenSSH client is installed, if not click **Add a feature**, search for **OpenSSH client** and install it. diff --git a/docs/windows/windows.html.md b/docs/windows/windows.html.md index 014e7b5..cf74119 100644 --- a/docs/windows/windows.html.md +++ b/docs/windows/windows.html.md @@ -2,9 +2,9 @@ ## Available Documentation -* [How to access a VM from Windows PuTTY on 3Engines Cloud](How-to-access-a-VM-from-Windows-PuTTY-on-3Engines-Cloud.html.md) -* [Connecting to a Windows VM via RDP through a Linux bastion host port forwarding on 3Engines Cloud](Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-3Engines-Cloud.html.md) -* [How to connect to a virtual machine via SSH from Windows 10 Command Prompt on 3Engines Cloud](How-to-connect-to-a-virtual-machine-via-SSH-from-Windows-10-Command-Prompt-on-3Engines-Cloud.html.md) -* [How to Create SSH Key Pair in Windows 10 On 3Engines Cloud](How-To-Create-SSH-Key-Pair-In-Windows-On-3Engines-Cloud.html.md) -* [Can I change my password through RDP on 3Engines Cloud?](Can-I-change-my-password-through-RDP-on-3Engines-Cloud.html.md) -* [How to Create SSH Key Pair in Windows 11 On 3Engines Cloud](How-To-Create-SSH-Key-Pair-In-Windows-11-On-3Engines-Cloud.html.md) +* [How to access a VM from Windows PuTTY on connectVM Cloud](How-to-access-a-VM-from-Windows-PuTTY-on-connectVM-Cloud.html.md) +* [Connecting to a Windows VM via RDP through a Linux bastion host port forwarding on connectVM Cloud](Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-connectVM-Cloud.html.md) +* [How to connect to a virtual machine via SSH from Windows 10 Command Prompt on connectVM Cloud](How-to-connect-to-a-virtual-machine-via-SSH-from-Windows-10-Command-Prompt-on-connectVM-Cloud.html.md) +* [How to Create SSH Key Pair in Windows 10 On connectVM Cloud](How-To-Create-SSH-Key-Pair-In-Windows-On-connectVM-Cloud.html.md) +* [Can I change my password through RDP on connectVM Cloud?](Can-I-change-my-password-through-RDP-on-connectVM-Cloud.html.md) +* [How to Create SSH Key Pair in Windows 11 On connectVM Cloud](How-To-Create-SSH-Key-Pair-In-Windows-11-On-connectVM-Cloud.html.md) diff --git a/mkdocs.yml b/mkdocs.yml index 85f9fd1..d0cf80d 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -1,9 +1,9 @@ -site_name: 3Engines Documentation -site_description: Documentation for 3Engines services and products -site_author: 3Engines -site_url: https://docs.3Engines.com/ -# repo_url: https://github.com/3Engines # Adjust if you have a specific repo -repo_name: 3Engines/docs # Adjust if you have a specific repo +site_name: connectVM Documentation +site_description: Documentation for connectVM services and products +site_author: connectVM +site_url: https://docs.connectVM.com/ +# repo_url: https://github.com/connectVM # Adjust if you have a specific repo +repo_name: connectVM/docs # Adjust if you have a specific repo docs_dir: docs site_dir: site use_directory_urls: false @@ -68,174 +68,174 @@ nav: # - Account Management: # - Overview: accountmanagement/accountmanagement.html.md # - Registration and Setting up an Account: accountmanagement/Registration-And-Account.html.md - # - How to start using dashboard services on 3Engines Cloud: accountmanagement/How-to-start-using-dashboard-services-on-3Engines-Cloud.html.md - # - Two-Factor Authentication to 3Engines Cloud site using mobile application: accountmanagement/Two-Factor-Authentication-for-3Engines-Cloud-Site.html.md - # - Two-Factor Authentication to 3Engines Cloud site using KeePassXC on desktop: accountmanagement/Using-KeePassXC-for-Two-Factor-Authentication-on-3Engines-Cloud.html.md - # - How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication: accountmanagement/How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md - # - How to manage TOTP authentication on 3Engines Cloud: accountmanagement/How-to-manage-TOTP-authentication-on-3Engines-Cloud.html.md + # - How to start using dashboard services on connectVM Cloud: accountmanagement/How-to-start-using-dashboard-services-on-connectVM-Cloud.html.md + # - Two-Factor Authentication to connectVM Cloud site using mobile application: accountmanagement/Two-Factor-Authentication-for-connectVM-Cloud-Site.html.md + # - Two-Factor Authentication to connectVM Cloud site using KeePassXC on desktop: accountmanagement/Using-KeePassXC-for-Two-Factor-Authentication-on-connectVM-Cloud.html.md + # - How to activate connectVM CLI access to connectVM Cloud cloud using one- or two-factor authentication: accountmanagement/How-to-activate-connectVM-CLI-access-to-connectVM-Cloud-cloud-using-one-or-two-factor-authentication.html.md + # - How to manage TOTP authentication on connectVM Cloud: accountmanagement/How-to-manage-TOTP-authentication-on-connectVM-Cloud.html.md # - Adding and editing Organization: accountmanagement/Adding-Editing-Organizations.html.md - # - How to buy credits using Pay Per Use wallet on 3Engines Cloud: accountmanagement/How-to-buy-credits-using-pay-per-use-wallet-on-3Engines-Cloud.html.md + # - How to buy credits using Pay Per Use wallet on connectVM Cloud: accountmanagement/How-to-buy-credits-using-pay-per-use-wallet-on-connectVM-Cloud.html.md # - Forgotten Password: accountmanagement/Forgotten-Password.html.md # - Editing profile: accountmanagement/Editing-Profile.html.md # - Wallets and Contracts Management: accountmanagement/Contracts-Wallets.html.md # - Services: accountmanagement/Services.html.md # - Inviting new user to your Organization: accountmanagement/Inviting-New-User.html.md # - Removing user from Organization: accountmanagement/Removing-User-From-Organization.html.md - # - Tenant manager users and roles on 3Engines Cloud: accountmanagement/Tenant-Manager-Users-And-Roles-On-3Engines-Cloud.html.md + # - Tenant manager users and roles on connectVM Cloud: accountmanagement/Tenant-Manager-Users-And-Roles-On-connectVM-Cloud.html.md # - Helpdesk and Support: accountmanagement/Help-Desk-And-Support.html.md # - Privacy policy for clients: accountmanagement/Privacy-Policy.html.md - # - Cookie consent on 3Engines Cloud: accountmanagement/Cookie-consent-on-3Engines-Cloud.html.md + # - Cookie consent on connectVM Cloud: accountmanagement/Cookie-consent-on-connectVM-Cloud.html.md - Cloud: - Overview: cloud/cloud.html.md - - Dashboard Overview – Project Quotas And Flavors Limits on 3Engines Cloud: cloud/Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-3Engines-Cloud.html.md - - How to access the VM from 3Engines console on 3Engines Cloud: cloud/How-to-access-the-VM-from-3Engines-console-on-3Engines-Cloud.html.md - - How to clone existing and configured VMs on 3Engines Cloud: cloud/How-to-clone-existing-and-configured-VMs-on-3Engines-Cloud.html.md - - How to fix unresponsive console issue on 3Engines Cloud: cloud/How-to-fix-unresponsive-console-issue-on-3Engines-Cloud.html.md - - How to generate and manage EC2 credentials on 3Engines Cloud: cloud/How-to-generate-ec2-credentials-on-3Engines-Cloud.html.md - - How to generate or use Application Credentials via CLI on 3Engines Cloud: cloud/How-to-generate-or-use-Application-Credentials-via-CLI-on-3Engines-Cloud.html.md - - How to Use GUI in Linux VM on 3Engines Cloud and access it From Local Linux Computer: cloud/How-to-use-GUI-in-Linux-VM-on-3Engines-Cloud-and-access-it-from-local-Linux-computer.html.md - - How To Create a New Linux VM With NVIDIA Virtual GPU in the 3Engines Dashboard Horizon on 3Engines Cloud: cloud/How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md - - How to install and use Docker on Ubuntu 24.04: cloud/How-to-use-Docker-on-3Engines-Cloud.html.md - - How to use Security Groups in Horizon on 3Engines Cloud: cloud/How-to-use-Security-Groups-in-Horizon-on-3Engines-Cloud.html.md - - How to create key pair in 3Engines Dashboard on 3Engines Cloud: cloud/How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md - - How to create new Linux VM in 3Engines Dashboard Horizon on 3Engines Cloud: cloud/How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md - - How to install Python virtualenv or virtualenvwrapper on 3Engines Cloud: cloud/How-to-install-Python-virtualenv-or-virtualenvwrapper-on-3Engines-Cloud.html.md - - How to start a VM from a snapshot on 3Engines Cloud: cloud/How-to-start-a-VM-from-a-snapshot-on-3Engines-Cloud.html.md - - Status Power State and dependencies in billing of instance VMs on 3Engines Cloud: cloud/Status-Power-State-and-dependences-in-billing-of-instances-VMs-on-3Engines-Cloud.html.md - - How to upload your custom image using 3Engines CLI on 3Engines Cloud: cloud/How-to-upload-your-custom-image-using-3Engines-CLI-on-3Engines-Cloud.html.md - - VM created with option Create New Volume No on 3Engines Cloud: cloud/VM-created-with-option-Create-New-Volume-No-on-3Engines-Cloud.html.md - - VM created with option Create New Volume Yes on 3Engines Cloud: cloud/VM-created-with-option-Create-New-Volume-Yes-on-3Engines-Cloud.html.md - - What is an 3Engines domain on 3Engines Cloud: cloud/What-is-an-3Engines-domain-on-3Engines-Cloud.html.md - - What is an 3Engines project on 3Engines Cloud: cloud/What-is-an-3Engines-project-on-3Engines-Cloud.html.md - - How to create a Linux VM and access it from Windows desktop on 3Engines Cloud: cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md - - How to create a Linux VM and access it from Linux command line on 3Engines Cloud: cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md - - DNS as a Service on 3Engines Cloud Hosting: cloud/DNS-as-a-Service-on-3Engines-Cloud-Hosting.html.md - - What Image Formats are Available in 3Engines 3Engines Cloud cloud: cloud/What-Image-Formats-are-available-in-3Engines-3Engines-Cloud-Cloud.html.md - - How to upload custom image to 3Engines Cloud cloud using 3Engines Horizon dashboard: cloud/How-to-upload-custom-image-to-3Engines-Cloud-cloud-using-3Engines-Horizon-dashboard.html.md - - How to create Windows VM on 3Engines Horizon and access it via web console on 3Engines Cloud: cloud/How-to-create-Windows-VM-on-3Engines-Horizon-and-access-it-via-web-console-on-3Engines-Cloud.html.md - - How to transfer volumes between domains and projects using Horizon dashboard on 3Engines Cloud: cloud/How-to-transfer-volumes-between-domains-and-projects-using-Horizon-dashboard-on-3Engines-Cloud.html.md - - Spot instances on 3Engines Cloud: cloud/Spot-instances-on-3Engines-Cloud.html.md - - How to create instance snapshot using Horizon on 3Engines Cloud: cloud/How-to-create-instance-snapshot-using-Horizon-on-3Engines-Cloud.html.md - - How to start a VM from instance snapshot using Horizon dashboard on 3Engines Cloud: cloud/How-to-start-a-VM-from-instance-snapshot-using-Horizon-dashboard-on-3Engines-Cloud.html.md - - How to create a VM using the 3Engines CLI client on 3Engines Cloud cloud: cloud/How-to-create-a-VM-using-the-3Engines-CLI-client-on-3Engines-Cloud-cloud.html.md - - 3Engines User Roles on 3Engines Cloud: cloud/3Engines-user-roles-on-3Engines-Cloud.html.md - - Resizing a virtual machine using 3Engines Horizon on 3Engines Cloud: cloud/Resizing-a-virtual-machine-using-3Engines-Horizon-on-3Engines-Cloud.html.md - - Block storage and object storage performance limits on 3Engines Cloud: cloud/Block-storage-and-object-storage-performance-limits-on-3Engines-Cloud.html.md + - Dashboard Overview – Project Quotas And Flavors Limits on connectVM Cloud: cloud/Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-connectVM-Cloud.html.md + - How to access the VM from connectVM console on connectVM Cloud: cloud/How-to-access-the-VM-from-connectVM-console-on-connectVM-Cloud.html.md + - How to clone existing and configured VMs on connectVM Cloud: cloud/How-to-clone-existing-and-configured-VMs-on-connectVM-Cloud.html.md + - How to fix unresponsive console issue on connectVM Cloud: cloud/How-to-fix-unresponsive-console-issue-on-connectVM-Cloud.html.md + - How to generate and manage EC2 credentials on connectVM Cloud: cloud/How-to-generate-ec2-credentials-on-connectVM-Cloud.html.md + - How to generate or use Application Credentials via CLI on connectVM Cloud: cloud/How-to-generate-or-use-Application-Credentials-via-CLI-on-connectVM-Cloud.html.md + - How to Use GUI in Linux VM on connectVM Cloud and access it From Local Linux Computer: cloud/How-to-use-GUI-in-Linux-VM-on-connectVM-Cloud-and-access-it-from-local-Linux-computer.html.md + - How To Create a New Linux VM With NVIDIA Virtual GPU in the connectVM Dashboard Horizon on connectVM Cloud: cloud/How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md + - How to install and use Docker on Ubuntu 24.04: cloud/How-to-use-Docker-on-connectVM-Cloud.html.md + - How to use Security Groups in Horizon on connectVM Cloud: cloud/How-to-use-Security-Groups-in-Horizon-on-connectVM-Cloud.html.md + - How to create key pair in connectVM Dashboard on connectVM Cloud: cloud/How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md + - How to create new Linux VM in connectVM Dashboard Horizon on connectVM Cloud: cloud/How-to-create-new-Linux-VM-in-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md + - How to install Python virtualenv or virtualenvwrapper on connectVM Cloud: cloud/How-to-install-Python-virtualenv-or-virtualenvwrapper-on-connectVM-Cloud.html.md + - How to start a VM from a snapshot on connectVM Cloud: cloud/How-to-start-a-VM-from-a-snapshot-on-connectVM-Cloud.html.md + - Status Power State and dependencies in billing of instance VMs on connectVM Cloud: cloud/Status-Power-State-and-dependences-in-billing-of-instances-VMs-on-connectVM-Cloud.html.md + - How to upload your custom image using connectVM CLI on connectVM Cloud: cloud/How-to-upload-your-custom-image-using-connectVM-CLI-on-connectVM-Cloud.html.md + - VM created with option Create New Volume No on connectVM Cloud: cloud/VM-created-with-option-Create-New-Volume-No-on-connectVM-Cloud.html.md + - VM created with option Create New Volume Yes on connectVM Cloud: cloud/VM-created-with-option-Create-New-Volume-Yes-on-connectVM-Cloud.html.md + - What is an connectVM domain on connectVM Cloud: cloud/What-is-an-connectVM-domain-on-connectVM-Cloud.html.md + - What is an connectVM project on connectVM Cloud: cloud/What-is-an-connectVM-project-on-connectVM-Cloud.html.md + - How to create a Linux VM and access it from Windows desktop on connectVM Cloud: cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-connectVM-Cloud.html.md + - How to create a Linux VM and access it from Linux command line on connectVM Cloud: cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md + - DNS as a Service on connectVM Cloud Hosting: cloud/DNS-as-a-Service-on-connectVM-Cloud-Hosting.html.md + - What Image Formats are Available in connectVM connectVM Cloud cloud: cloud/What-Image-Formats-are-available-in-connectVM-connectVM-Cloud-Cloud.html.md + - How to upload custom image to connectVM Cloud cloud using connectVM Horizon dashboard: cloud/How-to-upload-custom-image-to-connectVM-Cloud-cloud-using-connectVM-Horizon-dashboard.html.md + - How to create Windows VM on connectVM Horizon and access it via web console on connectVM Cloud: cloud/How-to-create-Windows-VM-on-connectVM-Horizon-and-access-it-via-web-console-on-connectVM-Cloud.html.md + - How to transfer volumes between domains and projects using Horizon dashboard on connectVM Cloud: cloud/How-to-transfer-volumes-between-domains-and-projects-using-Horizon-dashboard-on-connectVM-Cloud.html.md + - Spot instances on connectVM Cloud: cloud/Spot-instances-on-connectVM-Cloud.html.md + - How to create instance snapshot using Horizon on connectVM Cloud: cloud/How-to-create-instance-snapshot-using-Horizon-on-connectVM-Cloud.html.md + - How to start a VM from instance snapshot using Horizon dashboard on connectVM Cloud: cloud/How-to-start-a-VM-from-instance-snapshot-using-Horizon-dashboard-on-connectVM-Cloud.html.md + - How to create a VM using the connectVM CLI client on connectVM Cloud cloud: cloud/How-to-create-a-VM-using-the-connectVM-CLI-client-on-connectVM-Cloud-cloud.html.md + - connectVM User Roles on connectVM Cloud: cloud/connectVM-user-roles-on-connectVM-Cloud.html.md + - Resizing a virtual machine using connectVM Horizon on connectVM Cloud: cloud/Resizing-a-virtual-machine-using-connectVM-Horizon-on-connectVM-Cloud.html.md + - Block storage and object storage performance limits on connectVM Cloud: cloud/Block-storage-and-object-storage-performance-limits-on-connectVM-Cloud.html.md - Data Volume: - Overview: datavolume/datavolume.html.md - - How to attach a volume to VM less than 2TB on Linux on 3Engines Cloud: datavolume/How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-3Engines-Cloud.html.md - - How to attach a volume to VM more than 2TB on Linux on 3Engines Cloud: datavolume/How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-3Engines-Cloud.html.md - - Ephemeral vs Persistent storage option Create New Volume on 3Engines Cloud: datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-3Engines-Cloud.html.md - - How to export a volume over NFS on 3Engines Cloud: datavolume/How-to-export-a-volume-over-NFS-on-3Engines-Cloud.html.md - - How to export a volume over NFS outside of a project on 3Engines Cloud: datavolume/How-to-export-a-volume-over-NFS-outside-of-a-project-on-3Engines-Cloud.html.md - - How to extend the volume in Linux on 3Engines Cloud: datavolume/How-to-extend-the-volume-in-Linux-on-3Engines-Cloud.html.md - - How to mount object storage in Linux on 3Engines Cloud: datavolume/How-to-mount-object-storage-in-Linux-on-3Engines-Cloud.html.md - - How to move data volume between two VMs using 3Engines Horizon on 3Engines Cloud: datavolume/How-to-move-data-volume-between-two-VMs-using-3Engines-Horizon-on-3Engines-Cloud.html.md - - How many objects can I put into Object Storage container bucket on 3Engines Cloud: datavolume/How-many-objects-can-I-put-into-Object-Storage-container-bucket-on-3Engines-Cloud.html.md - - How to create volume Snapshot and attach as Volume on Linux or Windows on 3Engines Cloud: datavolume/How-to-create-volume-Snapshot-and-attach-as-Volume-on-Linux-or-Windows-on-3Engines-Cloud.html.md - - Volume snapshot inheritance and its consequences on 3Engines Cloud: datavolume/Volume-snapshot-inheritance-and-its-consequences-on-3Engines-Cloud.html.md - - How to Create Backup of Your Volume From Windows Machine on 3Engines Cloud: datavolume/How-To-Create-Backup-Of-Your-Volume-From-Windows-Machine-on-3Engines-Cloud.html.md - - How To Attach Volume To Windows VM On 3Engines Cloud: datavolume/How-To-Attach-Volume-To-Windows-VM-On-3Engines-Cloud.html.md - - How to create or delete volume snapshot on 3Engines Cloud: datavolume/How-to-create-or-delete-volume-snapshot-on-3Engines-Cloud.html.md - - How to restore volume from snapshot on 3Engines Cloud: datavolume/How-to-restore-volume-from-snapshot-on-3Engines-Cloud.html.md - - Bootable versus non-bootable volumes on 3Engines Cloud: datavolume/Bootable-versus-non-bootable-volumes-on-3Engines-Cloud.html.md + - How to attach a volume to VM less than 2TB on Linux on connectVM Cloud: datavolume/How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-connectVM-Cloud.html.md + - How to attach a volume to VM more than 2TB on Linux on connectVM Cloud: datavolume/How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-connectVM-Cloud.html.md + - Ephemeral vs Persistent storage option Create New Volume on connectVM Cloud: datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-connectVM-Cloud.html.md + - How to export a volume over NFS on connectVM Cloud: datavolume/How-to-export-a-volume-over-NFS-on-connectVM-Cloud.html.md + - How to export a volume over NFS outside of a project on connectVM Cloud: datavolume/How-to-export-a-volume-over-NFS-outside-of-a-project-on-connectVM-Cloud.html.md + - How to extend the volume in Linux on connectVM Cloud: datavolume/How-to-extend-the-volume-in-Linux-on-connectVM-Cloud.html.md + - How to mount object storage in Linux on connectVM Cloud: datavolume/How-to-mount-object-storage-in-Linux-on-connectVM-Cloud.html.md + - How to move data volume between two VMs using connectVM Horizon on connectVM Cloud: datavolume/How-to-move-data-volume-between-two-VMs-using-connectVM-Horizon-on-connectVM-Cloud.html.md + - How many objects can I put into Object Storage container bucket on connectVM Cloud: datavolume/How-many-objects-can-I-put-into-Object-Storage-container-bucket-on-connectVM-Cloud.html.md + - How to create volume Snapshot and attach as Volume on Linux or Windows on connectVM Cloud: datavolume/How-to-create-volume-Snapshot-and-attach-as-Volume-on-Linux-or-Windows-on-connectVM-Cloud.html.md + - Volume snapshot inheritance and its consequences on connectVM Cloud: datavolume/Volume-snapshot-inheritance-and-its-consequences-on-connectVM-Cloud.html.md + - How to Create Backup of Your Volume From Windows Machine on connectVM Cloud: datavolume/How-To-Create-Backup-Of-Your-Volume-From-Windows-Machine-on-connectVM-Cloud.html.md + - How To Attach Volume To Windows VM On connectVM Cloud: datavolume/How-To-Attach-Volume-To-Windows-VM-On-connectVM-Cloud.html.md + - How to create or delete volume snapshot on connectVM Cloud: datavolume/How-to-create-or-delete-volume-snapshot-on-connectVM-Cloud.html.md + - How to restore volume from snapshot on connectVM Cloud: datavolume/How-to-restore-volume-from-snapshot-on-connectVM-Cloud.html.md + - Bootable versus non-bootable volumes on connectVM Cloud: datavolume/Bootable-versus-non-bootable-volumes-on-connectVM-Cloud.html.md # - Kubernetes: # - Overview: kubernetes/kubernetes.html.md - # - How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum: kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md - # - Default Kubernetes cluster templates in 3Engines Cloud Cloud: kubernetes/Default-Kubernetes-cluster-templates-in-3Engines-Cloud-Cloud.html.md - # - How To Install 3Engines and Magnum Clients for Command Line Interface to 3Engines Cloud Horizon: kubernetes/How-To-Install-3Engines-and-Magnum-Clients-for-Command-Line-Interface-to-3Engines-Cloud-Horizon.html.md - # - How To Use Command Line Interface for Kubernetes Clusters On 3Engines Cloud 3Engines Magnum: kubernetes/How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-3Engines-Cloud-3Engines-Magnum.html.md - # - How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum: kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md - # - Using Dashboard To Access Kubernetes Cluster Post Deployment On 3Engines Cloud 3Engines Magnum: kubernetes/Using-Dashboard-To-Access-Kubernetes-Cluster-Post-Deployment-On-3Engines-Cloud-3Engines-Magnum.html.md - # - How To Create API Server LoadBalancer for Kubernetes Cluster on 3Engines Cloud 3Engines Magnum: kubernetes/How-To-Create-API-Server-LoadBalancer-for-Kubernetes-Cluster-On-3Engines-Cloud-3Engines-Magnum.html.md - # - Creating Additional Nodegroups in Kubernetes Cluster on 3Engines Cloud 3Engines Magnum: kubernetes/Creating-Additional-Nodegroups-in-Kubernetes-Cluster-on-3Engines-Cloud-3Engines-Magnum.html.md - # - Autoscaling Kubernetes Cluster Resources on 3Engines Cloud 3Engines Magnum: kubernetes/Autoscaling-Kubernetes-Cluster-Resources-on-3Engines-Cloud-3Engines-Magnum.html.md - # - Volume-based vs Ephemeral-based Storage for Kubernetes Clusters on 3Engines Cloud 3Engines Magnum: kubernetes/Volume-based-vs-Ephemeral-based-Storage-for-Kubernetes-Clusters-on-3Engines-Cloud-3Engines-Magnum.html.md + # - How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum: kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md + # - Default Kubernetes cluster templates in connectVM Cloud Cloud: kubernetes/Default-Kubernetes-cluster-templates-in-connectVM-Cloud-Cloud.html.md + # - How To Install connectVM and Magnum Clients for Command Line Interface to connectVM Cloud Horizon: kubernetes/How-To-Install-connectVM-and-Magnum-Clients-for-Command-Line-Interface-to-connectVM-Cloud-Horizon.html.md + # - How To Use Command Line Interface for Kubernetes Clusters On connectVM Cloud connectVM Magnum: kubernetes/How-To-Use-Command-Line-Interface-for-Kubernetes-Clusters-On-connectVM-Cloud-connectVM-Magnum.html.md + # - How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum: kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md + # - Using Dashboard To Access Kubernetes Cluster Post Deployment On connectVM Cloud connectVM Magnum: kubernetes/Using-Dashboard-To-Access-Kubernetes-Cluster-Post-Deployment-On-connectVM-Cloud-connectVM-Magnum.html.md + # - How To Create API Server LoadBalancer for Kubernetes Cluster on connectVM Cloud connectVM Magnum: kubernetes/How-To-Create-API-Server-LoadBalancer-for-Kubernetes-Cluster-On-connectVM-Cloud-connectVM-Magnum.html.md + # - Creating Additional Nodegroups in Kubernetes Cluster on connectVM Cloud connectVM Magnum: kubernetes/Creating-Additional-Nodegroups-in-Kubernetes-Cluster-on-connectVM-Cloud-connectVM-Magnum.html.md + # - Autoscaling Kubernetes Cluster Resources on connectVM Cloud connectVM Magnum: kubernetes/Autoscaling-Kubernetes-Cluster-Resources-on-connectVM-Cloud-connectVM-Magnum.html.md + # - Volume-based vs Ephemeral-based Storage for Kubernetes Clusters on connectVM Cloud connectVM Magnum: kubernetes/Volume-based-vs-Ephemeral-based-Storage-for-Kubernetes-Clusters-on-connectVM-Cloud-connectVM-Magnum.html.md # - Backup of Kubernetes Cluster using Velero: kubernetes/Backup-of-Kubernetes-Cluster-using-Velero.html.md - # - Using Kubernetes Ingress on 3Engines Cloud 3Engines Magnum: kubernetes/Using-Kubernetes-Ingress-on-3Engines-Cloud-3Engines-Magnum.html.md - # - Deploying Helm Charts on Magnum Kubernetes Clusters on 3Engines Cloud Cloud: kubernetes/Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md - # - Deploying HTTPS Services on Magnum Kubernetes in 3Engines Cloud Cloud: kubernetes/Deploying-HTTPS-Services-on-Magnum-Kubernetes-in-3Engines-Cloud-Cloud.html.md - # - Installing JupyterHub on Magnum Kubernetes Cluster in 3Engines Cloud Cloud: kubernetes/Installing-JupyterHub-on-Magnum-Kubernetes-cluster-in-3Engines-Cloud-cloud.html.md - # - Install and run Argo Workflows on 3Engines Cloud Magnum Kubernetes: kubernetes/Install-and-run-Argo-Workflows-on-3Engines-Cloud-Magnum-Kubernetes.html.md - # - Installing HashiCorp Vault on 3Engines Cloud Magnum: kubernetes/Installing-HashiCorp-Vault-on-3Engines-Cloud-Magnum.html.md - # - HTTP Request-based Autoscaling on K8S using Prometheus and Keda on 3Engines Cloud: kubernetes/HTTP-Request-based-Autoscaling-on-K8S-using-Prometheus-and-Keda-on-3Engines-Cloud.html.md - # - Create and access NFS server from Kubernetes on 3Engines Cloud: kubernetes/Create-and-access-NFS-server-from-Kubernetes-on-3Engines-Cloud.html.md - # - Deploy Keycloak on Kubernetes with a sample app on 3Engines Cloud: kubernetes/Deploy-Keycloak-on-Kubernetes-with-a-sample-app-on-3Engines-Cloud.html.md - # - Install and run Dask on a Kubernetes cluster in 3Engines Cloud cloud: kubernetes/Install-and-run-Dask-on-a-Kubernetes-cluster-in-3Engines-Cloud-cloud.html.md - # - Install and run NooBaa on Kubernetes cluster in single- and multicloud-environment on 3Engines Cloud: kubernetes/Install-and-run-NooBaa-on-Kubernetes-cluster-in-single-and-multicloud-environment-on-3Engines-Cloud.html.md - # - Private container registries with Harbor on 3Engines Cloud Kubernetes: kubernetes/Private-container-registries-with-Harbor-on-3Engines-Cloud-Kubernetes.html.md - # - Deploying vGPU workloads on 3Engines Cloud Kubernetes: kubernetes/Deploying-vGPU-workloads-on-3Engines-Cloud-Kubernetes.html.md - # - Kubernetes cluster observability with Prometheus and Grafana on 3Engines Cloud: kubernetes/Kubernetes-cluster-observability-with-Prometheus-and-Grafana-on-3Engines-Cloud.html.md - # - Enable Kubeapps app launcher on 3Engines Cloud Magnum Kubernetes cluster: kubernetes/Enable-Kubeapps-app-launcher-on-3Engines-Cloud-Magnum-Kubernetes-cluster.html.md - # - Install GitLab on 3Engines Cloud Kubernetes: kubernetes/Install-GitLab-on-3Engines-Cloud-Kubernetes.html.md - # - Sealed Secrets on 3Engines Cloud Kubernetes: kubernetes/Sealed-Secrets-on-3Engines-Cloud-Kubernetes.html.md - # - CI/CD pipelines with GitLab on 3Engines Cloud Kubernetes - building a Docker image: kubernetes/CICD-pipelines-with-GitLab-on-3Engines-Cloud-Kubernetes-building-a-Docker-image.html.md - # - How to create Kubernetes cluster using Terraform on 3Engines Cloud: kubernetes/How-to-create-Kubernetes-cluster-using-Terraform-on-3Engines-Cloud.html.md - # - GitOps with Argo CD on 3Engines Cloud Kubernetes: kubernetes/GitOps-with-Argo-CD-on-3Engines-Cloud-Kubernetes.html.md - # - Configuring IP Whitelisting for 3Engines Load Balancer using Horizon and CLI on 3Engines Cloud: kubernetes/Configuring-IP-Whitelisting-for-3Engines-Load-Balancer-using-Horizon-and-CLI-on-3Engines-Cloud.html.md - # - Configuring IP Whitelisting for 3Engines Load Balancer using Terraform on 3Engines Cloud: kubernetes/Configuring-IP-Whitelisting-for-3Engines-Load-Balancer-using-Terraform-on-3Engines-Cloud.html.md - # - Implementing IP Whitelisting for Load Balancers with Security Groups on 3Engines Cloud: kubernetes/Implementing-IP-Whitelisting-for-Load-Balancers-with-Security-Groups-on-3Engines-Cloud.html.md - # - How to install Rancher RKE2 Kubernetes on 3Engines Cloud: kubernetes/How-to-install-Rancher-RKE2-Kubernetes-on-3Engines-Cloud-cloud.html.md - # - Automatic Kubernetes cluster upgrade on 3Engines Cloud 3Engines Magnum: kubernetes/Automatic-Kubernetes-cluster-upgrade-on-3Engines-Cloud-3Engines-Magnum.html.md + # - Using Kubernetes Ingress on connectVM Cloud connectVM Magnum: kubernetes/Using-Kubernetes-Ingress-on-connectVM-Cloud-connectVM-Magnum.html.md + # - Deploying Helm Charts on Magnum Kubernetes Clusters on connectVM Cloud Cloud: kubernetes/Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md + # - Deploying HTTPS Services on Magnum Kubernetes in connectVM Cloud Cloud: kubernetes/Deploying-HTTPS-Services-on-Magnum-Kubernetes-in-connectVM-Cloud-Cloud.html.md + # - Installing JupyterHub on Magnum Kubernetes Cluster in connectVM Cloud Cloud: kubernetes/Installing-JupyterHub-on-Magnum-Kubernetes-cluster-in-connectVM-Cloud-cloud.html.md + # - Install and run Argo Workflows on connectVM Cloud Magnum Kubernetes: kubernetes/Install-and-run-Argo-Workflows-on-connectVM-Cloud-Magnum-Kubernetes.html.md + # - Installing HashiCorp Vault on connectVM Cloud Magnum: kubernetes/Installing-HashiCorp-Vault-on-connectVM-Cloud-Magnum.html.md + # - HTTP Request-based Autoscaling on K8S using Prometheus and Keda on connectVM Cloud: kubernetes/HTTP-Request-based-Autoscaling-on-K8S-using-Prometheus-and-Keda-on-connectVM-Cloud.html.md + # - Create and access NFS server from Kubernetes on connectVM Cloud: kubernetes/Create-and-access-NFS-server-from-Kubernetes-on-connectVM-Cloud.html.md + # - Deploy Keycloak on Kubernetes with a sample app on connectVM Cloud: kubernetes/Deploy-Keycloak-on-Kubernetes-with-a-sample-app-on-connectVM-Cloud.html.md + # - Install and run Dask on a Kubernetes cluster in connectVM Cloud cloud: kubernetes/Install-and-run-Dask-on-a-Kubernetes-cluster-in-connectVM-Cloud-cloud.html.md + # - Install and run NooBaa on Kubernetes cluster in single- and multicloud-environment on connectVM Cloud: kubernetes/Install-and-run-NooBaa-on-Kubernetes-cluster-in-single-and-multicloud-environment-on-connectVM-Cloud.html.md + # - Private container registries with Harbor on connectVM Cloud Kubernetes: kubernetes/Private-container-registries-with-Harbor-on-connectVM-Cloud-Kubernetes.html.md + # - Deploying vGPU workloads on connectVM Cloud Kubernetes: kubernetes/Deploying-vGPU-workloads-on-connectVM-Cloud-Kubernetes.html.md + # - Kubernetes cluster observability with Prometheus and Grafana on connectVM Cloud: kubernetes/Kubernetes-cluster-observability-with-Prometheus-and-Grafana-on-connectVM-Cloud.html.md + # - Enable Kubeapps app launcher on connectVM Cloud Magnum Kubernetes cluster: kubernetes/Enable-Kubeapps-app-launcher-on-connectVM-Cloud-Magnum-Kubernetes-cluster.html.md + # - Install GitLab on connectVM Cloud Kubernetes: kubernetes/Install-GitLab-on-connectVM-Cloud-Kubernetes.html.md + # - Sealed Secrets on connectVM Cloud Kubernetes: kubernetes/Sealed-Secrets-on-connectVM-Cloud-Kubernetes.html.md + # - CI/CD pipelines with GitLab on connectVM Cloud Kubernetes - building a Docker image: kubernetes/CICD-pipelines-with-GitLab-on-connectVM-Cloud-Kubernetes-building-a-Docker-image.html.md + # - How to create Kubernetes cluster using Terraform on connectVM Cloud: kubernetes/How-to-create-Kubernetes-cluster-using-Terraform-on-connectVM-Cloud.html.md + # - GitOps with Argo CD on connectVM Cloud Kubernetes: kubernetes/GitOps-with-Argo-CD-on-connectVM-Cloud-Kubernetes.html.md + # - Configuring IP Whitelisting for connectVM Load Balancer using Horizon and CLI on connectVM Cloud: kubernetes/Configuring-IP-Whitelisting-for-connectVM-Load-Balancer-using-Horizon-and-CLI-on-connectVM-Cloud.html.md + # - Configuring IP Whitelisting for connectVM Load Balancer using Terraform on connectVM Cloud: kubernetes/Configuring-IP-Whitelisting-for-connectVM-Load-Balancer-using-Terraform-on-connectVM-Cloud.html.md + # - Implementing IP Whitelisting for Load Balancers with Security Groups on connectVM Cloud: kubernetes/Implementing-IP-Whitelisting-for-Load-Balancers-with-Security-Groups-on-connectVM-Cloud.html.md + # - How to install Rancher RKE2 Kubernetes on connectVM Cloud: kubernetes/How-to-install-Rancher-RKE2-Kubernetes-on-connectVM-Cloud-cloud.html.md + # - Automatic Kubernetes cluster upgrade on connectVM Cloud connectVM Magnum: kubernetes/Automatic-Kubernetes-cluster-upgrade-on-connectVM-Cloud-connectVM-Magnum.html.md - Networking: - Overview: networking/networking.html.md - - How can I access my VMs using names instead of IP addresses on 3Engines Cloud: networking/How-can-I-access-my-VMs-using-names-instead-of-IP-addresses-on-3Engines-Cloud.html.md - - How to Add or Remove Floating IP’s to your VM on 3Engines Cloud: networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md - - Cannot access VM with SSH or PING on 3Engines Cloud: networking/Cannot-access-VM-with-SSH-or-PING-on-3Engines-Cloud.html.md - - Cannot ping VM on 3Engines Cloud: networking/Cannot-ping-VM-on-3Engines-Cloud.html.md - - How to connect to your virtual machine via SSH in Linux on 3Engines Cloud: networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-3Engines-Cloud.html.md - - How to create a network with router in Horizon Dashboard on 3Engines Cloud: networking/How-to-create-a-network-with-router-in-Horizon-Dashboard-on-3Engines-Cloud.html.md - - How can I open new ports for http for my service or instance on 3Engines Cloud: networking/How-can-I-open-new-ports-port-80-for-http-for-my-service-or-instance-on-3Engines-Cloud.html.md - - Generating an SSH keypair in Linux on 3Engines Cloud: networking/Generating-a-SSH-keypair-in-Linux-on-3Engines-Cloud.html.md - - How to add SSH key from Horizon web console on 3Engines Cloud: networking/How-to-add-SSH-key-from-Horizon-web-console-on-3Engines-Cloud.html.md - - How is my VM visible in the internet with no Floating IP attached on 3Engines Cloud: networking/How-is-my-VM-visible-in-the-internet-with-no-Floating-IP-attached-on-3Engines-Cloud.html.md - - How to run and configure Firewall as a service and VPN as a service on 3Engines Cloud: networking/How-to-run-and-configure-Firewall-as-a-service-and-VPN-as-a-service-on-3Engines-Cloud.html.md - - How to import SSH public key to 3Engines Horizon on 3Engines Cloud: networking/How-to-Import-SSH-Public-Key-to-3Engines-Horizon-on-3Engines-Cloud.html.md - # - 3Engines CLI: - # - Overview: 3Enginescli/3Enginescli.html.md - # - How to Backup an Instance and Download it to the Desktop on 3Engines Cloud 3Engines Hosting: 3Enginescli/How-to-backup-an-instance-and-download-it-to-the-desktop-on-3Engines-Cloud.html.md - # - How to create a set of VMs using 3Engines Heat Orchestration on 3Engines Cloud: 3Enginescli/How-to-create-a-set-of-VMs-using-3Engines-Heat-Orchestration-on-3Engines-Cloud.html.md - # - How to Create and Configure New 3Engines Project Through Horizon on 3Engines Cloud Cloud: 3Enginescli/How-To-Create-and-Configure-New-Project-on-3Engines-Cloud-Cloud.html.md - # - How to install 3EnginesClient for Linux on 3Engines Cloud: 3Enginescli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md - # - How to install 3EnginesClient GitBash for Windows on 3Engines Cloud: 3Enginescli/How-to-install-3EnginesClient-GitBash-or-Cygwin-for-Windows-on-3Engines-Cloud.html.md - # - How to share private container from object storage to another user on 3Engines Cloud: 3Enginescli/How-to-share-private-container-from-object-storage-to-another-user-on-3Engines-Cloud.html.md - # - How to install 3EnginesClient on Windows using Windows Subsystem for Linux on 3Engines Cloud 3Engines Hosting: 3Enginescli/How-to-install-3EnginesClient-on-Windows-using-Windows-Subsystem-for-Linux-on-3Engines-Cloud-3Engines-Hosting.html.md - # - How to move data volume between VMs using 3Engines CLI on 3Engines Cloud: 3Enginescli/How-to-move-data-volume-between-two-VMs-using-3Engines-CLI-on-3Engines-Cloud.html.md - # - How to access object storage using 3Engines CLI on 3Engines Cloud: 3Enginescli/How-to-access-object-storage-using-3Engines-CLI-on-3Engines-Cloud.html.md - # - How to transfer volumes between domains and projects using 3Engines CLI client on 3Engines Cloud: 3Enginescli/How-to-transfer-volumes-between-domains-and-projects-using-3Engines-CLI-client-on-3Engines-Cloud.html.md - # - How to start a VM from instance snapshot using 3Engines CLI on 3Engines Cloud: 3Enginescli/How-to-start-a-VM-from-instance-snapshot-using-3Engines-CLI-on-3Engines-Cloud.html.md - # - How to create instance snapshot using 3Engines CLI on 3Engines Cloud: 3Enginescli/How-to-create-instance-snapshot-using-3Engines-CLI-on-3Engines-Cloud.html.md - # - Resizing a virtual machine using 3Engines CLI on 3Engines Cloud: 3Enginescli/Resizing-a-virtual-machine-using-3Engines-CLI-on-3Engines-Cloud.html.md - # - Use backup command to create rotating backups of virtual machines on 3Engines Cloud cloud: 3Enginescli/Use-backup-command-to-create-rotating-backups-of-virtual-machines-on-3Engines-Cloud.html.md - # - Use script to create daily weekly and monthly rotating backups of virtual machines on 3Engines Cloud: 3Enginescli/Use-script-to-create-daily-weekly-and-monthly-rotating-backups-of-virtual-machines-using-on-3Engines-Cloud.html.md - # - 3Engines Development: - # - Overview: 3Enginesdev/3Enginesdev.html.md - # - Authenticating with 3EnginesSDK using Keycloak Credentials on 3Engines Cloud: 3Enginesdev/Authenticating-to-3EnginesSDK-using-Keycloak-Credentials-on-3Engines-Cloud.html.md - # - Generating and authorizing Terraform using Keycloak user on 3Engines Cloud: 3Enginesdev/Generating-and-authorizing-Terraform-using-Keycloak-user-on-3Engines-Cloud.html.md + - How can I access my VMs using names instead of IP addresses on connectVM Cloud: networking/How-can-I-access-my-VMs-using-names-instead-of-IP-addresses-on-connectVM-Cloud.html.md + - How to Add or Remove Floating IP’s to your VM on connectVM Cloud: networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md + - Cannot access VM with SSH or PING on connectVM Cloud: networking/Cannot-access-VM-with-SSH-or-PING-on-connectVM-Cloud.html.md + - Cannot ping VM on connectVM Cloud: networking/Cannot-ping-VM-on-connectVM-Cloud.html.md + - How to connect to your virtual machine via SSH in Linux on connectVM Cloud: networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-connectVM-Cloud.html.md + - How to create a network with router in Horizon Dashboard on connectVM Cloud: networking/How-to-create-a-network-with-router-in-Horizon-Dashboard-on-connectVM-Cloud.html.md + - How can I open new ports for http for my service or instance on connectVM Cloud: networking/How-can-I-open-new-ports-port-80-for-http-for-my-service-or-instance-on-connectVM-Cloud.html.md + - Generating an SSH keypair in Linux on connectVM Cloud: networking/Generating-a-SSH-keypair-in-Linux-on-connectVM-Cloud.html.md + - How to add SSH key from Horizon web console on connectVM Cloud: networking/How-to-add-SSH-key-from-Horizon-web-console-on-connectVM-Cloud.html.md + - How is my VM visible in the internet with no Floating IP attached on connectVM Cloud: networking/How-is-my-VM-visible-in-the-internet-with-no-Floating-IP-attached-on-connectVM-Cloud.html.md + - How to run and configure Firewall as a service and VPN as a service on connectVM Cloud: networking/How-to-run-and-configure-Firewall-as-a-service-and-VPN-as-a-service-on-connectVM-Cloud.html.md + - How to import SSH public key to connectVM Horizon on connectVM Cloud: networking/How-to-Import-SSH-Public-Key-to-connectVM-Horizon-on-connectVM-Cloud.html.md + # - connectVM CLI: + # - Overview: connectVMcli/connectVMcli.html.md + # - How to Backup an Instance and Download it to the Desktop on connectVM Cloud connectVM Hosting: connectVMcli/How-to-backup-an-instance-and-download-it-to-the-desktop-on-connectVM-Cloud.html.md + # - How to create a set of VMs using connectVM Heat Orchestration on connectVM Cloud: connectVMcli/How-to-create-a-set-of-VMs-using-connectVM-Heat-Orchestration-on-connectVM-Cloud.html.md + # - How to Create and Configure New connectVM Project Through Horizon on connectVM Cloud Cloud: connectVMcli/How-To-Create-and-Configure-New-Project-on-connectVM-Cloud-Cloud.html.md + # - How to install connectVMClient for Linux on connectVM Cloud: connectVMcli/How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md + # - How to install connectVMClient GitBash for Windows on connectVM Cloud: connectVMcli/How-to-install-connectVMClient-GitBash-or-Cygwin-for-Windows-on-connectVM-Cloud.html.md + # - How to share private container from object storage to another user on connectVM Cloud: connectVMcli/How-to-share-private-container-from-object-storage-to-another-user-on-connectVM-Cloud.html.md + # - How to install connectVMClient on Windows using Windows Subsystem for Linux on connectVM Cloud connectVM Hosting: connectVMcli/How-to-install-connectVMClient-on-Windows-using-Windows-Subsystem-for-Linux-on-connectVM-Cloud-connectVM-Hosting.html.md + # - How to move data volume between VMs using connectVM CLI on connectVM Cloud: connectVMcli/How-to-move-data-volume-between-two-VMs-using-connectVM-CLI-on-connectVM-Cloud.html.md + # - How to access object storage using connectVM CLI on connectVM Cloud: connectVMcli/How-to-access-object-storage-using-connectVM-CLI-on-connectVM-Cloud.html.md + # - How to transfer volumes between domains and projects using connectVM CLI client on connectVM Cloud: connectVMcli/How-to-transfer-volumes-between-domains-and-projects-using-connectVM-CLI-client-on-connectVM-Cloud.html.md + # - How to start a VM from instance snapshot using connectVM CLI on connectVM Cloud: connectVMcli/How-to-start-a-VM-from-instance-snapshot-using-connectVM-CLI-on-connectVM-Cloud.html.md + # - How to create instance snapshot using connectVM CLI on connectVM Cloud: connectVMcli/How-to-create-instance-snapshot-using-connectVM-CLI-on-connectVM-Cloud.html.md + # - Resizing a virtual machine using connectVM CLI on connectVM Cloud: connectVMcli/Resizing-a-virtual-machine-using-connectVM-CLI-on-connectVM-Cloud.html.md + # - Use backup command to create rotating backups of virtual machines on connectVM Cloud cloud: connectVMcli/Use-backup-command-to-create-rotating-backups-of-virtual-machines-on-connectVM-Cloud.html.md + # - Use script to create daily weekly and monthly rotating backups of virtual machines on connectVM Cloud: connectVMcli/Use-script-to-create-daily-weekly-and-monthly-rotating-backups-of-virtual-machines-using-on-connectVM-Cloud.html.md + # - connectVM Development: + # - Overview: connectVMdev/connectVMdev.html.md + # - Authenticating with connectVMSDK using Keycloak Credentials on connectVM Cloud: connectVMdev/Authenticating-to-connectVMSDK-using-Keycloak-Credentials-on-connectVM-Cloud.html.md + # - Generating and authorizing Terraform using Keycloak user on connectVM Cloud: connectVMdev/Generating-and-authorizing-Terraform-using-Keycloak-user-on-connectVM-Cloud.html.md - S3: - Overview: s3/s3.html.md - - How to Delete Large S3 Bucket on 3Engines Cloud: s3/How-to-delete-large-S3-bucket-on-3Engines-Cloud.html.md - - How to Mount Object Storage Container as a File System in Linux Using s3fs on 3Engines Cloud: s3/How-to-mount-object-storage-container-as-a-file-system-in-Linux-using-s3fs-on-3Engines-Cloud.html.md - - Bucket sharing using s3 bucket policy on 3Engines Cloud: s3/Bucket-sharing-using-s3-bucket-policy-on-3Engines-Cloud.html.md - - How to use Object Storage on 3Engines Cloud: s3/How-to-use-Object-Storage-on-3Engines-Cloud.html.md - - How to access private object storage using S3cmd or boto3 on 3Engines Cloud: s3/How-to-access-private-object-storage-using-S3cmd-or-boto3-on-3Engines-Cloud.html.md - - How to Install Boto3 in Windows on 3Engines Cloud: s3/How-To-Install-boto3-In-Windows-on-3Engines-Cloud.html.md - - Server-Side Encryption with Customer-Managed Keys (SSE-C) on 3Engines Cloud: s3/Server-Side-Encryption-with-Customer-Managed-Keys-SSE-C-on-3Engines-Cloud.html.md - - How to mount object storage container from 3Engines Cloud as file system on local Windows computer: s3/How-to-mount-object-storage-container-from-3Engines-Cloud-as-file-system-on-local-Windows-computer.html.md - - How to install s3cmd on Linux on 3Engines Cloud: s3/How-to-install-s3cmd-on-Linux-on-3Engines-Cloud.html.md - - How to access object storage from 3Engines Cloud using boto3: s3/How-to-access-object-storage-from-3Engines-Cloud-using-boto3.html.md - - How to access object storage from 3Engines Cloud using s3cmd: s3/How-to-access-object-storage-from-3Engines-Cloud-using-s3cmd.html.md - - Configuration files for s3cmd command on 3Engines Cloud: s3/Configuration-files-for-s3cmd-command-on-3Engines-Cloud.html.md - - S3 bucket object versioning on 3Engines Cloud: s3/S3-bucket-object-versioning-on-3Engines-Cloud.html.md + - How to Delete Large S3 Bucket on connectVM Cloud: s3/How-to-delete-large-S3-bucket-on-connectVM-Cloud.html.md + - How to Mount Object Storage Container as a File System in Linux Using s3fs on connectVM Cloud: s3/How-to-mount-object-storage-container-as-a-file-system-in-Linux-using-s3fs-on-connectVM-Cloud.html.md + - Bucket sharing using s3 bucket policy on connectVM Cloud: s3/Bucket-sharing-using-s3-bucket-policy-on-connectVM-Cloud.html.md + - How to use Object Storage on connectVM Cloud: s3/How-to-use-Object-Storage-on-connectVM-Cloud.html.md + - How to access private object storage using S3cmd or boto3 on connectVM Cloud: s3/How-to-access-private-object-storage-using-S3cmd-or-boto3-on-connectVM-Cloud.html.md + - How to Install Boto3 in Windows on connectVM Cloud: s3/How-To-Install-boto3-In-Windows-on-connectVM-Cloud.html.md + - Server-Side Encryption with Customer-Managed Keys (SSE-C) on connectVM Cloud: s3/Server-Side-Encryption-with-Customer-Managed-Keys-SSE-C-on-connectVM-Cloud.html.md + - How to mount object storage container from connectVM Cloud as file system on local Windows computer: s3/How-to-mount-object-storage-container-from-connectVM-Cloud-as-file-system-on-local-Windows-computer.html.md + - How to install s3cmd on Linux on connectVM Cloud: s3/How-to-install-s3cmd-on-Linux-on-connectVM-Cloud.html.md + - How to access object storage from connectVM Cloud using boto3: s3/How-to-access-object-storage-from-connectVM-Cloud-using-boto3.html.md + - How to access object storage from connectVM Cloud using s3cmd: s3/How-to-access-object-storage-from-connectVM-Cloud-using-s3cmd.html.md + - Configuration files for s3cmd command on connectVM Cloud: s3/Configuration-files-for-s3cmd-command-on-connectVM-Cloud.html.md + - S3 bucket object versioning on connectVM Cloud: s3/S3-bucket-object-versioning-on-connectVM-Cloud.html.md - Windows: - Overview: windows/windows.html.md - - How to access a VM from Windows PuTTY on 3Engines Cloud: windows/How-to-access-a-VM-from-Windows-PuTTY-on-3Engines-Cloud.html.md - - Connecting to a Windows VM via RDP through a Linux bastion host port forwarding on 3Engines Cloud: windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-3Engines-Cloud.html.md - - How to connect to a virtual machine via SSH from Windows 10 Command Prompt on 3Engines Cloud: windows/How-to-connect-to-a-virtual-machine-via-SSH-from-Windows-10-Command-Prompt-on-3Engines-Cloud.html.md - - How to Create SSH Key Pair in Windows 10 On 3Engines Cloud: windows/How-To-Create-SSH-Key-Pair-In-Windows-On-3Engines-Cloud.html.md - - Can I change my password through RDP on 3Engines Cloud?: windows/Can-I-change-my-password-through-RDP-on-3Engines-Cloud.html.md - - How to Create SSH Key Pair in Windows 11 On 3Engines Cloud: windows/How-To-Create-SSH-Key-Pair-In-Windows-11-On-3Engines-Cloud.html.md + - How to access a VM from Windows PuTTY on connectVM Cloud: windows/How-to-access-a-VM-from-Windows-PuTTY-on-connectVM-Cloud.html.md + - Connecting to a Windows VM via RDP through a Linux bastion host port forwarding on connectVM Cloud: windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-connectVM-Cloud.html.md + - How to connect to a virtual machine via SSH from Windows 10 Command Prompt on connectVM Cloud: windows/How-to-connect-to-a-virtual-machine-via-SSH-from-Windows-10-Command-Prompt-on-connectVM-Cloud.html.md + - How to Create SSH Key Pair in Windows 10 On connectVM Cloud: windows/How-To-Create-SSH-Key-Pair-In-Windows-On-connectVM-Cloud.html.md + - Can I change my password through RDP on connectVM Cloud?: windows/Can-I-change-my-password-through-RDP-on-connectVM-Cloud.html.md + - How to Create SSH Key Pair in Windows 11 On connectVM Cloud: windows/How-To-Create-SSH-Key-Pair-In-Windows-11-On-connectVM-Cloud.html.md # - Release Notes: # - Overview: releasenotes/releasenotes.html.md # - Release Notes: releasenotes/releasenotes.html.md @@ -297,15 +297,15 @@ plugins: # extra: # social: # - icon: fontawesome/brands/github -# link: https://github.com/3Engines -# name: 3Engines on GitHub +# link: https://github.com/connectVM +# name: connectVM on GitHub # - icon: fontawesome/brands/twitter -# link: https://twitter.com/3Engines -# name: 3Engines on Twitter +# link: https://twitter.com/connectVM +# name: connectVM on Twitter # analytics: # provider: google # property: UA-XXXXXX-X # Replace with your actual Google Analytics ID # generator: false # copyright: | -# © 2025 3Engines +# © 2025 connectVM diff --git a/site/404.html b/site/404.html deleted file mode 100644 index 5308dde..0000000 --- a/site/404.html +++ /dev/null @@ -1 +0,0 @@ - 3Engines Documentation

404 - Not found

\ No newline at end of file diff --git a/site/_images/01.png b/site/_images/01.png deleted file mode 100644 index 9b88d1a..0000000 Binary files a/site/_images/01.png and /dev/null differ diff --git a/site/_images/02.png b/site/_images/02.png deleted file mode 100644 index 0717ec8..0000000 Binary files a/site/_images/02.png and /dev/null differ diff --git a/site/_images/03.png b/site/_images/03.png deleted file mode 100644 index 4197dd6..0000000 Binary files a/site/_images/03.png and /dev/null differ diff --git a/site/_images/04.png b/site/_images/04.png deleted file mode 100644 index a098e5f..0000000 Binary files a/site/_images/04.png and /dev/null differ diff --git a/site/_images/05.png b/site/_images/05.png deleted file mode 100644 index ffdf3e8..0000000 Binary files a/site/_images/05.png and /dev/null differ diff --git a/site/_images/06.png b/site/_images/06.png deleted file mode 100644 index 91d86ed..0000000 Binary files a/site/_images/06.png and /dev/null differ diff --git a/site/_images/07.png b/site/_images/07.png deleted file mode 100644 index ba069c7..0000000 Binary files a/site/_images/07.png and /dev/null differ diff --git a/site/_images/08.png b/site/_images/08.png deleted file mode 100644 index db567df..0000000 Binary files a/site/_images/08.png and /dev/null differ diff --git a/site/_images/09.png b/site/_images/09.png deleted file mode 100644 index f70c7fe..0000000 Binary files a/site/_images/09.png and /dev/null differ diff --git a/site/_images/10.png b/site/_images/10.png deleted file mode 100644 index 2586a6e..0000000 Binary files a/site/_images/10.png and /dev/null differ diff --git a/site/_images/11.png b/site/_images/11.png deleted file mode 100644 index ebc19db..0000000 Binary files a/site/_images/11.png and /dev/null differ diff --git a/site/_images/12.png b/site/_images/12.png deleted file mode 100644 index c6242ed..0000000 Binary files a/site/_images/12.png and /dev/null differ diff --git a/site/_images/13.png b/site/_images/13.png deleted file mode 100644 index 7fb0799..0000000 Binary files a/site/_images/13.png and /dev/null differ diff --git a/site/_images/14.png b/site/_images/14.png deleted file mode 100644 index 6892535..0000000 Binary files a/site/_images/14.png and /dev/null differ diff --git a/site/_images/15.png b/site/_images/15.png deleted file mode 100644 index b842d46..0000000 Binary files a/site/_images/15.png and /dev/null differ diff --git a/site/_images/3Engines-logo.png b/site/_images/3Engines-logo.png deleted file mode 100644 index 9e62d1c..0000000 Binary files a/site/_images/3Engines-logo.png and /dev/null differ diff --git a/site/_images/3Engines-user-roles-create-4.png b/site/_images/3Engines-user-roles-create-4.png deleted file mode 100644 index 5a16423..0000000 Binary files a/site/_images/3Engines-user-roles-create-4.png and /dev/null differ diff --git a/site/_images/3Engines_cli.png b/site/_images/3Engines_cli.png deleted file mode 100644 index 90ae28f..0000000 Binary files a/site/_images/3Engines_cli.png and /dev/null differ diff --git a/site/_images/3Engines_cli_install_linux_help.png b/site/_images/3Engines_cli_install_linux_help.png deleted file mode 100644 index ab01c95..0000000 Binary files a/site/_images/3Engines_cli_install_linux_help.png and /dev/null differ diff --git a/site/_images/3Engines_cloud_1.png b/site/_images/3Engines_cloud_1.png deleted file mode 100644 index 3ba756c..0000000 Binary files a/site/_images/3Engines_cloud_1.png and /dev/null differ diff --git a/site/_images/3Engines_cloud_10.png b/site/_images/3Engines_cloud_10.png deleted file mode 100644 index 675fbbf..0000000 Binary files a/site/_images/3Engines_cloud_10.png and /dev/null differ diff --git a/site/_images/3Engines_cloud_11.png b/site/_images/3Engines_cloud_11.png deleted file mode 100644 index 4197300..0000000 Binary files a/site/_images/3Engines_cloud_11.png and /dev/null differ diff --git a/site/_images/3Engines_cloud_2.png b/site/_images/3Engines_cloud_2.png deleted file mode 100644 index cf0583d..0000000 Binary files a/site/_images/3Engines_cloud_2.png and /dev/null differ diff --git a/site/_images/3Engines_cloud_3.png b/site/_images/3Engines_cloud_3.png deleted file mode 100644 index 31059f3..0000000 Binary files a/site/_images/3Engines_cloud_3.png and /dev/null differ diff --git a/site/_images/3Engines_cloud_5.png b/site/_images/3Engines_cloud_5.png deleted file mode 100644 index a0fa606..0000000 Binary files a/site/_images/3Engines_cloud_5.png and /dev/null differ diff --git a/site/_images/3Engines_cloud_6.png b/site/_images/3Engines_cloud_6.png deleted file mode 100644 index c69e2ad..0000000 Binary files a/site/_images/3Engines_cloud_6.png and /dev/null differ diff --git a/site/_images/3Engines_cloud_7.png b/site/_images/3Engines_cloud_7.png deleted file mode 100644 index d474b73..0000000 Binary files a/site/_images/3Engines_cloud_7.png and /dev/null differ diff --git a/site/_images/3Engines_cloud_8.png b/site/_images/3Engines_cloud_8.png deleted file mode 100644 index 2f9f98d..0000000 Binary files a/site/_images/3Engines_cloud_8.png and /dev/null differ diff --git a/site/_images/3Engines_cloud_9.png b/site/_images/3Engines_cloud_9.png deleted file mode 100644 index 85e79d7..0000000 Binary files a/site/_images/3Engines_cloud_9.png and /dev/null differ diff --git a/site/_images/3Engines_coe.png b/site/_images/3Engines_coe.png deleted file mode 100644 index b651cdf..0000000 Binary files a/site/_images/3Engines_coe.png and /dev/null differ diff --git a/site/_images/3Engines_coe_cluster_list.png b/site/_images/3Engines_coe_cluster_list.png deleted file mode 100644 index fb48053..0000000 Binary files a/site/_images/3Engines_coe_cluster_list.png and /dev/null differ diff --git a/site/_images/3Engines_container_create_help.png b/site/_images/3Engines_container_create_help.png deleted file mode 100644 index 91bbf0e..0000000 Binary files a/site/_images/3Engines_container_create_help.png and /dev/null differ diff --git a/site/_images/3Engines_help.png b/site/_images/3Engines_help.png deleted file mode 100644 index 1940906..0000000 Binary files a/site/_images/3Engines_help.png and /dev/null differ diff --git a/site/_images/3Engines_server_create_help.png b/site/_images/3Engines_server_create_help.png deleted file mode 100644 index 4c43a72..0000000 Binary files a/site/_images/3Engines_server_create_help.png and /dev/null differ diff --git a/site/_images/3Engines_vim.png b/site/_images/3Engines_vim.png deleted file mode 100644 index 23ea6d9..0000000 Binary files a/site/_images/3Engines_vim.png and /dev/null differ diff --git a/site/_images/3Enginescli_flavor_list.png b/site/_images/3Enginescli_flavor_list.png deleted file mode 100644 index 7489515..0000000 Binary files a/site/_images/3Enginescli_flavor_list.png and /dev/null differ diff --git a/site/_images/Screenshot_20241006_124004.png b/site/_images/Screenshot_20241006_124004.png deleted file mode 100644 index 3bab1c7..0000000 Binary files a/site/_images/Screenshot_20241006_124004.png and /dev/null differ diff --git a/site/_images/Screenshot_20241006_125234.png b/site/_images/Screenshot_20241006_125234.png deleted file mode 100644 index 8866b3f..0000000 Binary files a/site/_images/Screenshot_20241006_125234.png and /dev/null differ diff --git a/site/_images/Screenshot_20241006_125651.png b/site/_images/Screenshot_20241006_125651.png deleted file mode 100644 index 57c60ff..0000000 Binary files a/site/_images/Screenshot_20241006_125651.png and /dev/null differ diff --git a/site/_images/Screenshot_20241006_130817.png b/site/_images/Screenshot_20241006_130817.png deleted file mode 100644 index 4370c09..0000000 Binary files a/site/_images/Screenshot_20241006_130817.png and /dev/null differ diff --git a/site/_images/Screenshot_20241006_132113.png b/site/_images/Screenshot_20241006_132113.png deleted file mode 100644 index 14ee6bf..0000000 Binary files a/site/_images/Screenshot_20241006_132113.png and /dev/null differ diff --git a/site/_images/Screenshot_20241006_132619.png b/site/_images/Screenshot_20241006_132619.png deleted file mode 100644 index 1d65097..0000000 Binary files a/site/_images/Screenshot_20241006_132619.png and /dev/null differ diff --git a/site/_images/Screenshot_20241006_133524.png b/site/_images/Screenshot_20241006_133524.png deleted file mode 100644 index d574320..0000000 Binary files a/site/_images/Screenshot_20241006_133524.png and /dev/null differ diff --git a/site/_images/Screenshot_20241006_134749.png b/site/_images/Screenshot_20241006_134749.png deleted file mode 100644 index 02cbdb3..0000000 Binary files a/site/_images/Screenshot_20241006_134749.png and /dev/null differ diff --git a/site/_images/Screenshot_20241006_135229.png b/site/_images/Screenshot_20241006_135229.png deleted file mode 100644 index 42fffb9..0000000 Binary files a/site/_images/Screenshot_20241006_135229.png and /dev/null differ diff --git a/site/_images/Screenshot_20241006_143434.png b/site/_images/Screenshot_20241006_143434.png deleted file mode 100644 index 2d97523..0000000 Binary files a/site/_images/Screenshot_20241006_143434.png and /dev/null differ diff --git a/site/_images/Screenshot_20241006_145844.png b/site/_images/Screenshot_20241006_145844.png deleted file mode 100644 index ee8435f..0000000 Binary files a/site/_images/Screenshot_20241006_145844.png and /dev/null differ diff --git a/site/_images/Tenant_manager_01_3Engines.png b/site/_images/Tenant_manager_01_3Engines.png deleted file mode 100644 index 6b27b3d..0000000 Binary files a/site/_images/Tenant_manager_01_3Engines.png and /dev/null differ diff --git a/site/_images/Tenant_manager_02_3Engines.png b/site/_images/Tenant_manager_02_3Engines.png deleted file mode 100644 index d8b5dd6..0000000 Binary files a/site/_images/Tenant_manager_02_3Engines.png and /dev/null differ diff --git a/site/_images/Tenant_manager_03_3Engines.png b/site/_images/Tenant_manager_03_3Engines.png deleted file mode 100644 index 9b6b11b..0000000 Binary files a/site/_images/Tenant_manager_03_3Engines.png and /dev/null differ diff --git a/site/_images/Tenant_manager_04_3Engines.png b/site/_images/Tenant_manager_04_3Engines.png deleted file mode 100644 index 56018c8..0000000 Binary files a/site/_images/Tenant_manager_04_3Engines.png and /dev/null differ diff --git a/site/_images/Tenant_manager_05_3Engines.png b/site/_images/Tenant_manager_05_3Engines.png deleted file mode 100644 index 9dbfcfa..0000000 Binary files a/site/_images/Tenant_manager_05_3Engines.png and /dev/null differ diff --git a/site/_images/a_record_in_dns.png b/site/_images/a_record_in_dns.png deleted file mode 100644 index e09eac1..0000000 Binary files a/site/_images/a_record_in_dns.png and /dev/null differ diff --git a/site/_images/accessvm2.png b/site/_images/accessvm2.png deleted file mode 100644 index 495223f..0000000 Binary files a/site/_images/accessvm2.png and /dev/null differ diff --git a/site/_images/accessvm3.png b/site/_images/accessvm3.png deleted file mode 100644 index 6fc2eef..0000000 Binary files a/site/_images/accessvm3.png and /dev/null differ diff --git a/site/_images/accessvm4v2.png b/site/_images/accessvm4v2.png deleted file mode 100644 index 2e43afc..0000000 Binary files a/site/_images/accessvm4v2.png and /dev/null differ diff --git a/site/_images/accessvm5.png b/site/_images/accessvm5.png deleted file mode 100644 index 8daf791..0000000 Binary files a/site/_images/accessvm5.png and /dev/null differ diff --git a/site/_images/account-final.png b/site/_images/account-final.png deleted file mode 100644 index 3c8cf1f..0000000 Binary files a/site/_images/account-final.png and /dev/null differ diff --git a/site/_images/account-groups.png b/site/_images/account-groups.png deleted file mode 100644 index 557b432..0000000 Binary files a/site/_images/account-groups.png and /dev/null differ diff --git a/site/_images/account-menu.png b/site/_images/account-menu.png deleted file mode 100644 index 94d69b2..0000000 Binary files a/site/_images/account-menu.png and /dev/null differ diff --git a/site/_images/account-new.png b/site/_images/account-new.png deleted file mode 100644 index 068a710..0000000 Binary files a/site/_images/account-new.png and /dev/null differ diff --git a/site/_images/account-properties.png b/site/_images/account-properties.png deleted file mode 100644 index 8ea1b22..0000000 Binary files a/site/_images/account-properties.png and /dev/null differ diff --git a/site/_images/activate-api-2fa-01_creodias.png b/site/_images/activate-api-2fa-01_creodias.png deleted file mode 100644 index 956c527..0000000 Binary files a/site/_images/activate-api-2fa-01_creodias.png and /dev/null differ diff --git a/site/_images/activate-api-2fa-02_creodias.png b/site/_images/activate-api-2fa-02_creodias.png deleted file mode 100644 index 3e1f724..0000000 Binary files a/site/_images/activate-api-2fa-02_creodias.png and /dev/null differ diff --git a/site/_images/activate-api-2fa-03_creodias.png b/site/_images/activate-api-2fa-03_creodias.png deleted file mode 100644 index 84ac8db..0000000 Binary files a/site/_images/activate-api-2fa-03_creodias.png and /dev/null differ diff --git a/site/_images/activate_environment.png b/site/_images/activate_environment.png deleted file mode 100644 index b6191e3..0000000 Binary files a/site/_images/activate_environment.png and /dev/null differ diff --git a/site/_images/add_ticket.png b/site/_images/add_ticket.png deleted file mode 100644 index 39dc506..0000000 Binary files a/site/_images/add_ticket.png and /dev/null differ diff --git a/site/_images/add_ticket_3Enginescloud.png b/site/_images/add_ticket_3Enginescloud.png deleted file mode 100644 index e1038f9..0000000 Binary files a/site/_images/add_ticket_3Enginescloud.png and /dev/null differ diff --git a/site/_images/advanced_option.png b/site/_images/advanced_option.png deleted file mode 100644 index 1e0f00f..0000000 Binary files a/site/_images/advanced_option.png and /dev/null differ diff --git a/site/_images/after_delete_cluster.png b/site/_images/after_delete_cluster.png deleted file mode 100644 index f350cfd..0000000 Binary files a/site/_images/after_delete_cluster.png and /dev/null differ diff --git a/site/_images/all_nodes.png b/site/_images/all_nodes.png deleted file mode 100644 index b49c760..0000000 Binary files a/site/_images/all_nodes.png and /dev/null differ diff --git a/site/_images/any_other_route.png b/site/_images/any_other_route.png deleted file mode 100644 index 7832c66..0000000 Binary files a/site/_images/any_other_route.png and /dev/null differ diff --git a/site/_images/apache_bitnami.png b/site/_images/apache_bitnami.png deleted file mode 100644 index a37fcad..0000000 Binary files a/site/_images/apache_bitnami.png and /dev/null differ diff --git a/site/_images/apache_ip.png b/site/_images/apache_ip.png deleted file mode 100644 index ee26810..0000000 Binary files a/site/_images/apache_ip.png and /dev/null differ diff --git a/site/_images/apache_route.png b/site/_images/apache_route.png deleted file mode 100644 index 46ff43c..0000000 Binary files a/site/_images/apache_route.png and /dev/null differ diff --git a/site/_images/api_access.png b/site/_images/api_access.png deleted file mode 100644 index 0331557..0000000 Binary files a/site/_images/api_access.png and /dev/null differ diff --git a/site/_images/api_address.png b/site/_images/api_address.png deleted file mode 100644 index b23f069..0000000 Binary files a/site/_images/api_address.png and /dev/null differ diff --git a/site/_images/apply_yaml.png b/site/_images/apply_yaml.png deleted file mode 100644 index 62d743f..0000000 Binary files a/site/_images/apply_yaml.png and /dev/null differ diff --git a/site/_images/associate_floating_ip.png b/site/_images/associate_floating_ip.png deleted file mode 100644 index 235cc1f..0000000 Binary files a/site/_images/associate_floating_ip.png and /dev/null differ diff --git a/site/_images/auto_scaling_filled_in.png b/site/_images/auto_scaling_filled_in.png deleted file mode 100644 index 7bde4df..0000000 Binary files a/site/_images/auto_scaling_filled_in.png and /dev/null differ diff --git a/site/_images/autoscale_custom_worker.png b/site/_images/autoscale_custom_worker.png deleted file mode 100644 index dd61c45..0000000 Binary files a/site/_images/autoscale_custom_worker.png and /dev/null differ diff --git a/site/_images/autoscale_with_role.png b/site/_images/autoscale_with_role.png deleted file mode 100644 index 9076997..0000000 Binary files a/site/_images/autoscale_with_role.png and /dev/null differ diff --git a/site/_images/backup-command-rotating-backups-05_creodias.png b/site/_images/backup-command-rotating-backups-05_creodias.png deleted file mode 100644 index 871679d..0000000 Binary files a/site/_images/backup-command-rotating-backups-05_creodias.png and /dev/null differ diff --git a/site/_images/backup-command-rotating-backups-06_creodias.png b/site/_images/backup-command-rotating-backups-06_creodias.png deleted file mode 100644 index 559b28f..0000000 Binary files a/site/_images/backup-command-rotating-backups-06_creodias.png and /dev/null differ diff --git a/site/_images/backup-command-rotating-backups-08_creodias.png b/site/_images/backup-command-rotating-backups-08_creodias.png deleted file mode 100644 index 1ac3e26..0000000 Binary files a/site/_images/backup-command-rotating-backups-08_creodias.png and /dev/null differ diff --git a/site/_images/backupinst1.png b/site/_images/backupinst1.png deleted file mode 100644 index a07c70a..0000000 Binary files a/site/_images/backupinst1.png and /dev/null differ diff --git a/site/_images/backupinst2.png b/site/_images/backupinst2.png deleted file mode 100644 index fa8c02c..0000000 Binary files a/site/_images/backupinst2.png and /dev/null differ diff --git a/site/_images/backupinst3.png b/site/_images/backupinst3.png deleted file mode 100644 index 9e7e935..0000000 Binary files a/site/_images/backupinst3.png and /dev/null differ diff --git a/site/_images/backupinst4.png b/site/_images/backupinst4.png deleted file mode 100644 index bfa259f..0000000 Binary files a/site/_images/backupinst4.png and /dev/null differ diff --git a/site/_images/backupinst5.png b/site/_images/backupinst5.png deleted file mode 100644 index 345add2..0000000 Binary files a/site/_images/backupinst5.png and /dev/null differ diff --git a/site/_images/boot_source.png b/site/_images/boot_source.png deleted file mode 100644 index 61a25e5..0000000 Binary files a/site/_images/boot_source.png and /dev/null differ diff --git a/site/_images/bootable-versus-nonbootable-volume-01_creodias.png b/site/_images/bootable-versus-nonbootable-volume-01_creodias.png deleted file mode 100644 index e80bdaa..0000000 Binary files a/site/_images/bootable-versus-nonbootable-volume-01_creodias.png and /dev/null differ diff --git a/site/_images/bootable-versus-nonbootable-volume-02_creodias.png b/site/_images/bootable-versus-nonbootable-volume-02_creodias.png deleted file mode 100644 index 8eb8f98..0000000 Binary files a/site/_images/bootable-versus-nonbootable-volume-02_creodias.png and /dev/null differ diff --git a/site/_images/bootable-versus-nonbootable-volume-03_creodias.png b/site/_images/bootable-versus-nonbootable-volume-03_creodias.png deleted file mode 100644 index 11b2e30..0000000 Binary files a/site/_images/bootable-versus-nonbootable-volume-03_creodias.png and /dev/null differ diff --git a/site/_images/bootable-versus-nonbootable-volume-04_creodias.png b/site/_images/bootable-versus-nonbootable-volume-04_creodias.png deleted file mode 100644 index 3c9e4a5..0000000 Binary files a/site/_images/bootable-versus-nonbootable-volume-04_creodias.png and /dev/null differ diff --git a/site/_images/bootable-versus-nonbootable-volume-05_creodias.png b/site/_images/bootable-versus-nonbootable-volume-05_creodias.png deleted file mode 100644 index 5b27e8e..0000000 Binary files a/site/_images/bootable-versus-nonbootable-volume-05_creodias.png and /dev/null differ diff --git a/site/_images/bootable-versus-nonbootable-volume-06_creodias.png b/site/_images/bootable-versus-nonbootable-volume-06_creodias.png deleted file mode 100644 index 7bac119..0000000 Binary files a/site/_images/bootable-versus-nonbootable-volume-06_creodias.png and /dev/null differ diff --git a/site/_images/bootable-versus-nonbootable-volume-07_creodias.png b/site/_images/bootable-versus-nonbootable-volume-07_creodias.png deleted file mode 100644 index 50c2432..0000000 Binary files a/site/_images/bootable-versus-nonbootable-volume-07_creodias.png and /dev/null differ diff --git a/site/_images/bootable-versus-nonbootable-volume-08_creodias.png b/site/_images/bootable-versus-nonbootable-volume-08_creodias.png deleted file mode 100644 index 74be3c2..0000000 Binary files a/site/_images/bootable-versus-nonbootable-volume-08_creodias.png and /dev/null differ diff --git a/site/_images/bootable-versus-nonbootable-volume-09_creodias.png b/site/_images/bootable-versus-nonbootable-volume-09_creodias.png deleted file mode 100644 index 00aeca0..0000000 Binary files a/site/_images/bootable-versus-nonbootable-volume-09_creodias.png and /dev/null differ diff --git a/site/_images/bootable-versus-nonbootable-volume-10_creodias.png b/site/_images/bootable-versus-nonbootable-volume-10_creodias.png deleted file mode 100644 index 703a7c7..0000000 Binary files a/site/_images/bootable-versus-nonbootable-volume-10_creodias.png and /dev/null differ diff --git a/site/_images/bootable-versus-nonbootable-volume-11_creodias.png b/site/_images/bootable-versus-nonbootable-volume-11_creodias.png deleted file mode 100644 index 0f27030..0000000 Binary files a/site/_images/bootable-versus-nonbootable-volume-11_creodias.png and /dev/null differ diff --git a/site/_images/bootable-versus-nonbootable-volume-12_creodias.png b/site/_images/bootable-versus-nonbootable-volume-12_creodias.png deleted file mode 100644 index bfb24cd..0000000 Binary files a/site/_images/bootable-versus-nonbootable-volume-12_creodias.png and /dev/null differ diff --git a/site/_images/bootable-versus-nonbootable-volume-13_creodias.png b/site/_images/bootable-versus-nonbootable-volume-13_creodias.png deleted file mode 100644 index f3974c0..0000000 Binary files a/site/_images/bootable-versus-nonbootable-volume-13_creodias.png and /dev/null differ diff --git a/site/_images/bootable-versus-nonbootable-volume-14_creodias.png b/site/_images/bootable-versus-nonbootable-volume-14_creodias.png deleted file mode 100644 index 8228eb8..0000000 Binary files a/site/_images/bootable-versus-nonbootable-volume-14_creodias.png and /dev/null differ diff --git a/site/_images/bootable-versus-nonbootable-volume-16_creodias.png b/site/_images/bootable-versus-nonbootable-volume-16_creodias.png deleted file mode 100644 index e60072d..0000000 Binary files a/site/_images/bootable-versus-nonbootable-volume-16_creodias.png and /dev/null differ diff --git a/site/_images/bootable-versus-nonbootable-volume-21_creodias.png b/site/_images/bootable-versus-nonbootable-volume-21_creodias.png deleted file mode 100644 index b8f4f47..0000000 Binary files a/site/_images/bootable-versus-nonbootable-volume-21_creodias.png and /dev/null differ diff --git a/site/_images/bootable-versus-nonbootable-volume-22_creodias.png b/site/_images/bootable-versus-nonbootable-volume-22_creodias.png deleted file mode 100644 index e9789f2..0000000 Binary files a/site/_images/bootable-versus-nonbootable-volume-22_creodias.png and /dev/null differ diff --git a/site/_images/boto1.png b/site/_images/boto1.png deleted file mode 100644 index f239d2f..0000000 Binary files a/site/_images/boto1.png and /dev/null differ diff --git a/site/_images/boto2.png b/site/_images/boto2.png deleted file mode 100644 index f469be0..0000000 Binary files a/site/_images/boto2.png and /dev/null differ diff --git a/site/_images/boto3.png b/site/_images/boto3.png deleted file mode 100644 index ddd77a6..0000000 Binary files a/site/_images/boto3.png and /dev/null differ diff --git a/site/_images/boto4.png b/site/_images/boto4.png deleted file mode 100644 index 69d9acb..0000000 Binary files a/site/_images/boto4.png and /dev/null differ diff --git a/site/_images/bucketnew_created.png b/site/_images/bucketnew_created.png deleted file mode 100644 index 577e0bb..0000000 Binary files a/site/_images/bucketnew_created.png and /dev/null differ diff --git a/site/_images/c1.png b/site/_images/c1.png deleted file mode 100644 index 44e0c50..0000000 Binary files a/site/_images/c1.png and /dev/null differ diff --git a/site/_images/c4.png b/site/_images/c4.png deleted file mode 100644 index 0c7ca9f..0000000 Binary files a/site/_images/c4.png and /dev/null differ diff --git a/site/_images/choose_os.png b/site/_images/choose_os.png deleted file mode 100644 index 33ac6e3..0000000 Binary files a/site/_images/choose_os.png and /dev/null differ diff --git a/site/_images/cli_newcluster.png b/site/_images/cli_newcluster.png deleted file mode 100644 index 5595574..0000000 Binary files a/site/_images/cli_newcluster.png and /dev/null differ diff --git a/site/_images/cli_os_cloud.png b/site/_images/cli_os_cloud.png deleted file mode 100644 index 205173f..0000000 Binary files a/site/_images/cli_os_cloud.png and /dev/null differ diff --git a/site/_images/click_button_launch_stack.png b/site/_images/click_button_launch_stack.png deleted file mode 100644 index 9a59f5b..0000000 Binary files a/site/_images/click_button_launch_stack.png and /dev/null differ diff --git a/site/_images/click_on_email.png b/site/_images/click_on_email.png deleted file mode 100644 index fcc7f30..0000000 Binary files a/site/_images/click_on_email.png and /dev/null differ diff --git a/site/_images/clone2.png b/site/_images/clone2.png deleted file mode 100644 index 907f8a5..0000000 Binary files a/site/_images/clone2.png and /dev/null differ diff --git a/site/_images/clone3.png b/site/_images/clone3.png deleted file mode 100644 index 511cfa4..0000000 Binary files a/site/_images/clone3.png and /dev/null differ diff --git a/site/_images/cluster_config_editor.png b/site/_images/cluster_config_editor.png deleted file mode 100644 index 2a120d0..0000000 Binary files a/site/_images/cluster_config_editor.png and /dev/null differ diff --git a/site/_images/cluster_forming.png b/site/_images/cluster_forming.png deleted file mode 100644 index ee17eba..0000000 Binary files a/site/_images/cluster_forming.png and /dev/null differ diff --git a/site/_images/cluster_inside.png b/site/_images/cluster_inside.png deleted file mode 100644 index 7ca0d61..0000000 Binary files a/site/_images/cluster_inside.png and /dev/null differ diff --git a/site/_images/cluster_list_horizon.png b/site/_images/cluster_list_horizon.png deleted file mode 100644 index 5e6e6bf..0000000 Binary files a/site/_images/cluster_list_horizon.png and /dev/null differ diff --git a/site/_images/cluster_name_filled_in.png b/site/_images/cluster_name_filled_in.png deleted file mode 100644 index bcb316e..0000000 Binary files a/site/_images/cluster_name_filled_in.png and /dev/null differ diff --git a/site/_images/cluster_size_new.png b/site/_images/cluster_size_new.png deleted file mode 100644 index 4c8af94..0000000 Binary files a/site/_images/cluster_size_new.png and /dev/null differ diff --git a/site/_images/cluster_successful.png b/site/_images/cluster_successful.png deleted file mode 100644 index 77fb5fe..0000000 Binary files a/site/_images/cluster_successful.png and /dev/null differ diff --git a/site/_images/cluster_template_detail2.png b/site/_images/cluster_template_detail2.png deleted file mode 100644 index cd4568b..0000000 Binary files a/site/_images/cluster_template_detail2.png and /dev/null differ diff --git a/site/_images/clusters.png b/site/_images/clusters.png deleted file mode 100644 index e0edb15..0000000 Binary files a/site/_images/clusters.png and /dev/null differ diff --git a/site/_images/clusters_command.png b/site/_images/clusters_command.png deleted file mode 100644 index c9204d1..0000000 Binary files a/site/_images/clusters_command.png and /dev/null differ diff --git a/site/_images/code_structure.png b/site/_images/code_structure.png deleted file mode 100644 index be5fbfe..0000000 Binary files a/site/_images/code_structure.png and /dev/null differ diff --git a/site/_images/combination_swift_commands.png b/site/_images/combination_swift_commands.png deleted file mode 100644 index 8919230..0000000 Binary files a/site/_images/combination_swift_commands.png and /dev/null differ diff --git a/site/_images/complete_example.png b/site/_images/complete_example.png deleted file mode 100644 index 0a2e31c..0000000 Binary files a/site/_images/complete_example.png and /dev/null differ diff --git a/site/_images/compute_instances.png b/site/_images/compute_instances.png deleted file mode 100644 index f096700..0000000 Binary files a/site/_images/compute_instances.png and /dev/null differ diff --git a/site/_images/confi_created.png b/site/_images/confi_created.png deleted file mode 100644 index 3b4d28d..0000000 Binary files a/site/_images/confi_created.png and /dev/null differ diff --git a/site/_images/conn01.png b/site/_images/conn01.png deleted file mode 100644 index fe27d7a..0000000 Binary files a/site/_images/conn01.png and /dev/null differ diff --git a/site/_images/conn02b.png b/site/_images/conn02b.png deleted file mode 100644 index b380c2e..0000000 Binary files a/site/_images/conn02b.png and /dev/null differ diff --git a/site/_images/conn03b.png b/site/_images/conn03b.png deleted file mode 100644 index 3b80c89..0000000 Binary files a/site/_images/conn03b.png and /dev/null differ diff --git a/site/_images/conn04b.png b/site/_images/conn04b.png deleted file mode 100644 index 846396d..0000000 Binary files a/site/_images/conn04b.png and /dev/null differ diff --git a/site/_images/conn05b.png b/site/_images/conn05b.png deleted file mode 100644 index 11bef88..0000000 Binary files a/site/_images/conn05b.png and /dev/null differ diff --git a/site/_images/conn06b.png b/site/_images/conn06b.png deleted file mode 100644 index 9478481..0000000 Binary files a/site/_images/conn06b.png and /dev/null differ diff --git a/site/_images/conn07b.png b/site/_images/conn07b.png deleted file mode 100644 index 1600e0b..0000000 Binary files a/site/_images/conn07b.png and /dev/null differ diff --git a/site/_images/conn08b.png b/site/_images/conn08b.png deleted file mode 100644 index acae0db..0000000 Binary files a/site/_images/conn08b.png and /dev/null differ diff --git a/site/_images/conn09b.png b/site/_images/conn09b.png deleted file mode 100644 index d60f6a5..0000000 Binary files a/site/_images/conn09b.png and /dev/null differ diff --git a/site/_images/conn10b.png b/site/_images/conn10b.png deleted file mode 100644 index 1703388..0000000 Binary files a/site/_images/conn10b.png and /dev/null differ diff --git a/site/_images/conn11.png b/site/_images/conn11.png deleted file mode 100644 index 99b1d98..0000000 Binary files a/site/_images/conn11.png and /dev/null differ diff --git a/site/_images/conn11b.png b/site/_images/conn11b.png deleted file mode 100644 index f935fd1..0000000 Binary files a/site/_images/conn11b.png and /dev/null differ diff --git a/site/_images/cookie-consent-3Engines-cloud-1.png b/site/_images/cookie-consent-3Engines-cloud-1.png deleted file mode 100644 index 1b43c1f..0000000 Binary files a/site/_images/cookie-consent-3Engines-cloud-1.png and /dev/null differ diff --git a/site/_images/cookie-consent-3Engines-cloud-11.png b/site/_images/cookie-consent-3Engines-cloud-11.png deleted file mode 100644 index b6c3b27..0000000 Binary files a/site/_images/cookie-consent-3Engines-cloud-11.png and /dev/null differ diff --git a/site/_images/cookie-consent-3Engines-cloud-12.png b/site/_images/cookie-consent-3Engines-cloud-12.png deleted file mode 100644 index ce90d09..0000000 Binary files a/site/_images/cookie-consent-3Engines-cloud-12.png and /dev/null differ diff --git a/site/_images/cookie-consent-3Engines-cloud-13.png b/site/_images/cookie-consent-3Engines-cloud-13.png deleted file mode 100644 index 7e5f8fb..0000000 Binary files a/site/_images/cookie-consent-3Engines-cloud-13.png and /dev/null differ diff --git a/site/_images/cookie-consent-3Engines-cloud-15.png b/site/_images/cookie-consent-3Engines-cloud-15.png deleted file mode 100644 index 54f9135..0000000 Binary files a/site/_images/cookie-consent-3Engines-cloud-15.png and /dev/null differ diff --git a/site/_images/cookie-consent-3Engines-cloud-2.png b/site/_images/cookie-consent-3Engines-cloud-2.png deleted file mode 100644 index 2670a86..0000000 Binary files a/site/_images/cookie-consent-3Engines-cloud-2.png and /dev/null differ diff --git a/site/_images/cookie-consent-3Engines-cloud-4.png b/site/_images/cookie-consent-3Engines-cloud-4.png deleted file mode 100644 index 1a97e0a..0000000 Binary files a/site/_images/cookie-consent-3Engines-cloud-4.png and /dev/null differ diff --git a/site/_images/cookie-consent-3Engines-cloud-5.png b/site/_images/cookie-consent-3Engines-cloud-5.png deleted file mode 100644 index 9dc0272..0000000 Binary files a/site/_images/cookie-consent-3Engines-cloud-5.png and /dev/null differ diff --git a/site/_images/cookie-consent-3Engines-cloud-6.png b/site/_images/cookie-consent-3Engines-cloud-6.png deleted file mode 100644 index aefd922..0000000 Binary files a/site/_images/cookie-consent-3Engines-cloud-6.png and /dev/null differ diff --git a/site/_images/cookie-consent-3Engines-cloud-7.png b/site/_images/cookie-consent-3Engines-cloud-7.png deleted file mode 100644 index 997bab8..0000000 Binary files a/site/_images/cookie-consent-3Engines-cloud-7.png and /dev/null differ diff --git a/site/_images/cookie-consent-3Engines-cloud-8.png b/site/_images/cookie-consent-3Engines-cloud-8.png deleted file mode 100644 index 24b6006..0000000 Binary files a/site/_images/cookie-consent-3Engines-cloud-8.png and /dev/null differ diff --git a/site/_images/cookie-consent-3Engines-cloud-9.png b/site/_images/cookie-consent-3Engines-cloud-9.png deleted file mode 100644 index 9df7b04..0000000 Binary files a/site/_images/cookie-consent-3Engines-cloud-9.png and /dev/null differ diff --git a/site/_images/cookie-consent-for-site-1.png b/site/_images/cookie-consent-for-site-1.png deleted file mode 100644 index ad30d49..0000000 Binary files a/site/_images/cookie-consent-for-site-1.png and /dev/null differ diff --git a/site/_images/copy.png b/site/_images/copy.png deleted file mode 100644 index 4fb11bb..0000000 Binary files a/site/_images/copy.png and /dev/null differ diff --git a/site/_images/create-linux-linux-04_creodias.png b/site/_images/create-linux-linux-04_creodias.png deleted file mode 100644 index d628fbd..0000000 Binary files a/site/_images/create-linux-linux-04_creodias.png and /dev/null differ diff --git a/site/_images/create-linux-linux-05_creodias.png b/site/_images/create-linux-linux-05_creodias.png deleted file mode 100644 index 8eee648..0000000 Binary files a/site/_images/create-linux-linux-05_creodias.png and /dev/null differ diff --git a/site/_images/create-linux-linux-06_creodias.png b/site/_images/create-linux-linux-06_creodias.png deleted file mode 100644 index 0a458be..0000000 Binary files a/site/_images/create-linux-linux-06_creodias.png and /dev/null differ diff --git a/site/_images/create-linux-linux-07_creodias.png b/site/_images/create-linux-linux-07_creodias.png deleted file mode 100644 index 9e48dd4..0000000 Binary files a/site/_images/create-linux-linux-07_creodias.png and /dev/null differ diff --git a/site/_images/create-linux-linux-08_creodias.png b/site/_images/create-linux-linux-08_creodias.png deleted file mode 100644 index 8ae2d71..0000000 Binary files a/site/_images/create-linux-linux-08_creodias.png and /dev/null differ diff --git a/site/_images/create-linux-linux-09_creodias.png b/site/_images/create-linux-linux-09_creodias.png deleted file mode 100644 index 9556f7a..0000000 Binary files a/site/_images/create-linux-linux-09_creodias.png and /dev/null differ diff --git a/site/_images/create-linux-linux-10_creodias.png b/site/_images/create-linux-linux-10_creodias.png deleted file mode 100644 index c8c1cf2..0000000 Binary files a/site/_images/create-linux-linux-10_creodias.png and /dev/null differ diff --git a/site/_images/create-linux-linux-12_creodias.png b/site/_images/create-linux-linux-12_creodias.png deleted file mode 100644 index e2b060d..0000000 Binary files a/site/_images/create-linux-linux-12_creodias.png and /dev/null differ diff --git a/site/_images/create-linux-linux-13_creodias.png b/site/_images/create-linux-linux-13_creodias.png deleted file mode 100644 index 88993d9..0000000 Binary files a/site/_images/create-linux-linux-13_creodias.png and /dev/null differ diff --git a/site/_images/create-volume-windows-01_creodias.png b/site/_images/create-volume-windows-01_creodias.png deleted file mode 100644 index 3808823..0000000 Binary files a/site/_images/create-volume-windows-01_creodias.png and /dev/null differ diff --git a/site/_images/create-volume-windows-02_creodias.png b/site/_images/create-volume-windows-02_creodias.png deleted file mode 100644 index d3e4edc..0000000 Binary files a/site/_images/create-volume-windows-02_creodias.png and /dev/null differ diff --git a/site/_images/create-volume-windows-03_creodias.png b/site/_images/create-volume-windows-03_creodias.png deleted file mode 100644 index 2ef4986..0000000 Binary files a/site/_images/create-volume-windows-03_creodias.png and /dev/null differ diff --git a/site/_images/create-volume-windows-04_creodias.png b/site/_images/create-volume-windows-04_creodias.png deleted file mode 100644 index 5f09824..0000000 Binary files a/site/_images/create-volume-windows-04_creodias.png and /dev/null differ diff --git a/site/_images/create-volume-windows-05_creodias.png b/site/_images/create-volume-windows-05_creodias.png deleted file mode 100644 index c6bf35f..0000000 Binary files a/site/_images/create-volume-windows-05_creodias.png and /dev/null differ diff --git a/site/_images/create-volume-windows-06_creodias.png b/site/_images/create-volume-windows-06_creodias.png deleted file mode 100644 index 6219002..0000000 Binary files a/site/_images/create-volume-windows-06_creodias.png and /dev/null differ diff --git a/site/_images/create-volume-windows-07_creodias.png b/site/_images/create-volume-windows-07_creodias.png deleted file mode 100644 index cdfad9b..0000000 Binary files a/site/_images/create-volume-windows-07_creodias.png and /dev/null differ diff --git a/site/_images/create-volume-windows-08_creodias.png b/site/_images/create-volume-windows-08_creodias.png deleted file mode 100644 index 1ee2d3d..0000000 Binary files a/site/_images/create-volume-windows-08_creodias.png and /dev/null differ diff --git a/site/_images/create-volume-windows-09_creodias.png b/site/_images/create-volume-windows-09_creodias.png deleted file mode 100644 index 4d80ac3..0000000 Binary files a/site/_images/create-volume-windows-09_creodias.png and /dev/null differ diff --git a/site/_images/create-volume-windows-10_creodias.png b/site/_images/create-volume-windows-10_creodias.png deleted file mode 100644 index cbffeea..0000000 Binary files a/site/_images/create-volume-windows-10_creodias.png and /dev/null differ diff --git a/site/_images/create-volume-windows-11_creodias.png b/site/_images/create-volume-windows-11_creodias.png deleted file mode 100644 index 3aaa67d..0000000 Binary files a/site/_images/create-volume-windows-11_creodias.png and /dev/null differ diff --git a/site/_images/create-volume-windows-12_creodias.png b/site/_images/create-volume-windows-12_creodias.png deleted file mode 100644 index ef72bcc..0000000 Binary files a/site/_images/create-volume-windows-12_creodias.png and /dev/null differ diff --git a/site/_images/create-volume-windows-13_creodias.png b/site/_images/create-volume-windows-13_creodias.png deleted file mode 100644 index 06108c3..0000000 Binary files a/site/_images/create-volume-windows-13_creodias.png and /dev/null differ diff --git a/site/_images/create-volume-windows-14_creodias.png b/site/_images/create-volume-windows-14_creodias.png deleted file mode 100644 index 525797f..0000000 Binary files a/site/_images/create-volume-windows-14_creodias.png and /dev/null differ diff --git a/site/_images/create-volume-windows-15_creodias.png b/site/_images/create-volume-windows-15_creodias.png deleted file mode 100644 index 17456ca..0000000 Binary files a/site/_images/create-volume-windows-15_creodias.png and /dev/null differ diff --git a/site/_images/create-volume-windows-16_creodias.png b/site/_images/create-volume-windows-16_creodias.png deleted file mode 100644 index 277660b..0000000 Binary files a/site/_images/create-volume-windows-16_creodias.png and /dev/null differ diff --git a/site/_images/create-volume-windows-17_creodias.png b/site/_images/create-volume-windows-17_creodias.png deleted file mode 100644 index 155eb5f..0000000 Binary files a/site/_images/create-volume-windows-17_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-01_creodias.png b/site/_images/create-windows-vm-horizon-web-console-01_creodias.png deleted file mode 100644 index 113d0d1..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-01_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-02_creodias.png b/site/_images/create-windows-vm-horizon-web-console-02_creodias.png deleted file mode 100644 index 90da4fb..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-02_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-03_creodias.png b/site/_images/create-windows-vm-horizon-web-console-03_creodias.png deleted file mode 100644 index 11ffeb4..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-03_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-04_creodias.png b/site/_images/create-windows-vm-horizon-web-console-04_creodias.png deleted file mode 100644 index 7206371..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-04_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-05_creodias.png b/site/_images/create-windows-vm-horizon-web-console-05_creodias.png deleted file mode 100644 index aa49961..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-05_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-06_creodias.png b/site/_images/create-windows-vm-horizon-web-console-06_creodias.png deleted file mode 100644 index 8e4bf68..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-06_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-07_creodias.png b/site/_images/create-windows-vm-horizon-web-console-07_creodias.png deleted file mode 100644 index ff3296e..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-07_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-09_creodias.png b/site/_images/create-windows-vm-horizon-web-console-09_creodias.png deleted file mode 100644 index b9423b8..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-09_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-10_creodias.png b/site/_images/create-windows-vm-horizon-web-console-10_creodias.png deleted file mode 100644 index e69bd12..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-10_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-11_creodias.png b/site/_images/create-windows-vm-horizon-web-console-11_creodias.png deleted file mode 100644 index 0f3f371..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-11_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-12_creodias.png b/site/_images/create-windows-vm-horizon-web-console-12_creodias.png deleted file mode 100644 index 6b78c08..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-12_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-13_creodias.png b/site/_images/create-windows-vm-horizon-web-console-13_creodias.png deleted file mode 100644 index e3c72c4..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-13_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-14_creodias.png b/site/_images/create-windows-vm-horizon-web-console-14_creodias.png deleted file mode 100644 index 148a3e6..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-14_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-15_creodias.png b/site/_images/create-windows-vm-horizon-web-console-15_creodias.png deleted file mode 100644 index ceea4d7..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-15_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-16_creodias.png b/site/_images/create-windows-vm-horizon-web-console-16_creodias.png deleted file mode 100644 index 0fb1d29..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-16_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-17_creodias.png b/site/_images/create-windows-vm-horizon-web-console-17_creodias.png deleted file mode 100644 index 8d99f73..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-17_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-18_creodias.png b/site/_images/create-windows-vm-horizon-web-console-18_creodias.png deleted file mode 100644 index 4660663..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-18_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-19_creodias.png b/site/_images/create-windows-vm-horizon-web-console-19_creodias.png deleted file mode 100644 index 20be437..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-19_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-21_creodias.png b/site/_images/create-windows-vm-horizon-web-console-21_creodias.png deleted file mode 100644 index 7fab87c..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-21_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-23_creodias.png b/site/_images/create-windows-vm-horizon-web-console-23_creodias.png deleted file mode 100644 index 401c671..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-23_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-24_creodias.png b/site/_images/create-windows-vm-horizon-web-console-24_creodias.png deleted file mode 100644 index 9376e53..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-24_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-25_creodias.png b/site/_images/create-windows-vm-horizon-web-console-25_creodias.png deleted file mode 100644 index 6e9431e..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-25_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-26_creodias.png b/site/_images/create-windows-vm-horizon-web-console-26_creodias.png deleted file mode 100644 index c68bc71..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-26_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-27_creodias.png b/site/_images/create-windows-vm-horizon-web-console-27_creodias.png deleted file mode 100644 index 90ddec8..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-27_creodias.png and /dev/null differ diff --git a/site/_images/create-windows-vm-horizon-web-console-28_creodias.png b/site/_images/create-windows-vm-horizon-web-console-28_creodias.png deleted file mode 100644 index 353df17..0000000 Binary files a/site/_images/create-windows-vm-horizon-web-console-28_creodias.png and /dev/null differ diff --git a/site/_images/create_account_3Enginescloud.png b/site/_images/create_account_3Enginescloud.png deleted file mode 100644 index 64a2b12..0000000 Binary files a/site/_images/create_account_3Enginescloud.png and /dev/null differ diff --git a/site/_images/create_client_with_authentication.png b/site/_images/create_client_with_authentication.png deleted file mode 100644 index 6599ba1..0000000 Binary files a/site/_images/create_client_with_authentication.png and /dev/null differ diff --git a/site/_images/create_cluster_advanced.png b/site/_images/create_cluster_advanced.png deleted file mode 100644 index 790adad..0000000 Binary files a/site/_images/create_cluster_advanced.png and /dev/null differ diff --git a/site/_images/create_cluster_details.png b/site/_images/create_cluster_details.png deleted file mode 100644 index 145e275..0000000 Binary files a/site/_images/create_cluster_details.png and /dev/null differ diff --git a/site/_images/create_cluster_size.png b/site/_images/create_cluster_size.png deleted file mode 100644 index 8485f20..0000000 Binary files a/site/_images/create_cluster_size.png and /dev/null differ diff --git a/site/_images/create_cluster_working.png b/site/_images/create_cluster_working.png deleted file mode 100644 index 1283f25..0000000 Binary files a/site/_images/create_cluster_working.png and /dev/null differ diff --git a/site/_images/create_credential.png b/site/_images/create_credential.png deleted file mode 100644 index 2ffebde..0000000 Binary files a/site/_images/create_credential.png and /dev/null differ diff --git a/site/_images/create_heat_4.png b/site/_images/create_heat_4.png deleted file mode 100644 index f2b59dc..0000000 Binary files a/site/_images/create_heat_4.png and /dev/null differ diff --git a/site/_images/create_main_site_dns.png b/site/_images/create_main_site_dns.png deleted file mode 100644 index 02b72a8..0000000 Binary files a/site/_images/create_main_site_dns.png and /dev/null differ diff --git a/site/_images/create_new_cluster.png b/site/_images/create_new_cluster.png deleted file mode 100644 index e646670..0000000 Binary files a/site/_images/create_new_cluster.png and /dev/null differ diff --git a/site/_images/create_new_cluster_filled_in2.png b/site/_images/create_new_cluster_filled_in2.png deleted file mode 100644 index 7b994d6..0000000 Binary files a/site/_images/create_new_cluster_filled_in2.png and /dev/null differ diff --git a/site/_images/create_new_template.png b/site/_images/create_new_template.png deleted file mode 100644 index b3d144d..0000000 Binary files a/site/_images/create_new_template.png and /dev/null differ diff --git a/site/_images/create_new_with_name.png b/site/_images/create_new_with_name.png deleted file mode 100644 index b5a074c..0000000 Binary files a/site/_images/create_new_with_name.png and /dev/null differ diff --git a/site/_images/create_object_container.png b/site/_images/create_object_container.png deleted file mode 100644 index 4b4d75d..0000000 Binary files a/site/_images/create_object_container.png and /dev/null differ diff --git a/site/_images/create_project.png b/site/_images/create_project.png deleted file mode 100644 index 0d2341e..0000000 Binary files a/site/_images/create_project.png and /dev/null differ diff --git a/site/_images/create_ssh_key_windows_11-03_creodias.png b/site/_images/create_ssh_key_windows_11-03_creodias.png deleted file mode 100644 index 82bc103..0000000 Binary files a/site/_images/create_ssh_key_windows_11-03_creodias.png and /dev/null differ diff --git a/site/_images/create_ssh_key_windows_11-04_creodias.png b/site/_images/create_ssh_key_windows_11-04_creodias.png deleted file mode 100644 index b79d005..0000000 Binary files a/site/_images/create_ssh_key_windows_11-04_creodias.png and /dev/null differ diff --git a/site/_images/create_ssh_key_windows_11-07_creodias.png b/site/_images/create_ssh_key_windows_11-07_creodias.png deleted file mode 100644 index 60ba750..0000000 Binary files a/site/_images/create_ssh_key_windows_11-07_creodias.png and /dev/null differ diff --git a/site/_images/create_ssh_key_windows_11-08_creodias.png b/site/_images/create_ssh_key_windows_11-08_creodias.png deleted file mode 100644 index 02045e6..0000000 Binary files a/site/_images/create_ssh_key_windows_11-08_creodias.png and /dev/null differ diff --git a/site/_images/create_ssh_key_windows_11-09_creodias.png b/site/_images/create_ssh_key_windows_11-09_creodias.png deleted file mode 100644 index 79de078..0000000 Binary files a/site/_images/create_ssh_key_windows_11-09_creodias.png and /dev/null differ diff --git a/site/_images/create_ssh_key_windows_11-10_creodias.png b/site/_images/create_ssh_key_windows_11-10_creodias.png deleted file mode 100644 index 9c8f37f..0000000 Binary files a/site/_images/create_ssh_key_windows_11-10_creodias.png and /dev/null differ diff --git a/site/_images/create_ssh_key_windows_11-11_creodias.png b/site/_images/create_ssh_key_windows_11-11_creodias.png deleted file mode 100644 index 88035c7..0000000 Binary files a/site/_images/create_ssh_key_windows_11-11_creodias.png and /dev/null differ diff --git a/site/_images/create_ssh_key_windows_11-12_creodias.png b/site/_images/create_ssh_key_windows_11-12_creodias.png deleted file mode 100644 index 081c588..0000000 Binary files a/site/_images/create_ssh_key_windows_11-12_creodias.png and /dev/null differ diff --git a/site/_images/create_ssh_key_windows_11-13_creodias.png b/site/_images/create_ssh_key_windows_11-13_creodias.png deleted file mode 100644 index aa7e742..0000000 Binary files a/site/_images/create_ssh_key_windows_11-13_creodias.png and /dev/null differ diff --git a/site/_images/create_ssh_key_windows_11-14_creodias.png b/site/_images/create_ssh_key_windows_11-14_creodias.png deleted file mode 100644 index 869a4c1..0000000 Binary files a/site/_images/create_ssh_key_windows_11-14_creodias.png and /dev/null differ diff --git a/site/_images/create_ssh_key_windows_11-15_creodias.png b/site/_images/create_ssh_key_windows_11-15_creodias.png deleted file mode 100644 index 82666ed..0000000 Binary files a/site/_images/create_ssh_key_windows_11-15_creodias.png and /dev/null differ diff --git a/site/_images/create_ssh_key_windows_11-16_creodias.png b/site/_images/create_ssh_key_windows_11-16_creodias.png deleted file mode 100644 index d2be3a3..0000000 Binary files a/site/_images/create_ssh_key_windows_11-16_creodias.png and /dev/null differ diff --git a/site/_images/create_ssh_key_windows_11-19_creodias.png b/site/_images/create_ssh_key_windows_11-19_creodias.png deleted file mode 100644 index 03f9e82..0000000 Binary files a/site/_images/create_ssh_key_windows_11-19_creodias.png and /dev/null differ diff --git a/site/_images/create_ssh_key_windows_11-20_creodias.png b/site/_images/create_ssh_key_windows_11-20_creodias.png deleted file mode 100644 index 2c349c0..0000000 Binary files a/site/_images/create_ssh_key_windows_11-20_creodias.png and /dev/null differ diff --git a/site/_images/create_ssh_key_windows_11-21_creodias.png b/site/_images/create_ssh_key_windows_11-21_creodias.png deleted file mode 100644 index 882bb9a..0000000 Binary files a/site/_images/create_ssh_key_windows_11-21_creodias.png and /dev/null differ diff --git a/site/_images/create_ssh_key_windows_11-22_creodias.png b/site/_images/create_ssh_key_windows_11-22_creodias.png deleted file mode 100644 index 15805d3..0000000 Binary files a/site/_images/create_ssh_key_windows_11-22_creodias.png and /dev/null differ diff --git a/site/_images/create_vm_cli_1.png b/site/_images/create_vm_cli_1.png deleted file mode 100644 index 066a98d..0000000 Binary files a/site/_images/create_vm_cli_1.png and /dev/null differ diff --git a/site/_images/create_www_subdomain.png b/site/_images/create_www_subdomain.png deleted file mode 100644 index 33e8c5c..0000000 Binary files a/site/_images/create_www_subdomain.png and /dev/null differ diff --git a/site/_images/created_instances.png b/site/_images/created_instances.png deleted file mode 100644 index acda912..0000000 Binary files a/site/_images/created_instances.png and /dev/null differ diff --git a/site/_images/created_new_nodegroup.png b/site/_images/created_new_nodegroup.png deleted file mode 100644 index 6f9879c..0000000 Binary files a/site/_images/created_new_nodegroup.png and /dev/null differ diff --git a/site/_images/createnew10.png b/site/_images/createnew10.png deleted file mode 100644 index 19a08d7..0000000 Binary files a/site/_images/createnew10.png and /dev/null differ diff --git a/site/_images/createnew11.png b/site/_images/createnew11.png deleted file mode 100644 index 67f9a02..0000000 Binary files a/site/_images/createnew11.png and /dev/null differ diff --git a/site/_images/createnew12.png b/site/_images/createnew12.png deleted file mode 100644 index 5713889..0000000 Binary files a/site/_images/createnew12.png and /dev/null differ diff --git a/site/_images/createnew13.png b/site/_images/createnew13.png deleted file mode 100644 index 66cff3c..0000000 Binary files a/site/_images/createnew13.png and /dev/null differ diff --git a/site/_images/createnew14.png b/site/_images/createnew14.png deleted file mode 100644 index 63f80de..0000000 Binary files a/site/_images/createnew14.png and /dev/null differ diff --git a/site/_images/createnew16.png b/site/_images/createnew16.png deleted file mode 100644 index 3f0428f..0000000 Binary files a/site/_images/createnew16.png and /dev/null differ diff --git a/site/_images/createnew18.png b/site/_images/createnew18.png deleted file mode 100644 index 193cfbe..0000000 Binary files a/site/_images/createnew18.png and /dev/null differ diff --git a/site/_images/createnew19.png b/site/_images/createnew19.png deleted file mode 100644 index f13518d..0000000 Binary files a/site/_images/createnew19.png and /dev/null differ diff --git a/site/_images/createnew6.png b/site/_images/createnew6.png deleted file mode 100644 index 2a61f81..0000000 Binary files a/site/_images/createnew6.png and /dev/null differ diff --git a/site/_images/createnew7.png b/site/_images/createnew7.png deleted file mode 100644 index f4b6db2..0000000 Binary files a/site/_images/createnew7.png and /dev/null differ diff --git a/site/_images/createnew8.png b/site/_images/createnew8.png deleted file mode 100644 index 559d1e9..0000000 Binary files a/site/_images/createnew8.png and /dev/null differ diff --git a/site/_images/createnew9.png b/site/_images/createnew9.png deleted file mode 100644 index 7168fb6..0000000 Binary files a/site/_images/createnew9.png and /dev/null differ diff --git a/site/_images/creation_in_progress2.png b/site/_images/creation_in_progress2.png deleted file mode 100644 index 514883b..0000000 Binary files a/site/_images/creation_in_progress2.png and /dev/null differ diff --git a/site/_images/credential_create_help.png b/site/_images/credential_create_help.png deleted file mode 100644 index 5db56eb..0000000 Binary files a/site/_images/credential_create_help.png and /dev/null differ diff --git a/site/_images/credentials_first_time.png b/site/_images/credentials_first_time.png deleted file mode 100644 index e03ddd2..0000000 Binary files a/site/_images/credentials_first_time.png and /dev/null differ diff --git a/site/_images/customize_the_cloud.png b/site/_images/customize_the_cloud.png deleted file mode 100644 index 6fe23f8..0000000 Binary files a/site/_images/customize_the_cloud.png and /dev/null differ diff --git a/site/_images/daemonset_01.png b/site/_images/daemonset_01.png deleted file mode 100644 index 711c9a2..0000000 Binary files a/site/_images/daemonset_01.png and /dev/null differ diff --git a/site/_images/dashboard-services-10-3Engines-cloud.png b/site/_images/dashboard-services-10-3Engines-cloud.png deleted file mode 100644 index 6523bf2..0000000 Binary files a/site/_images/dashboard-services-10-3Engines-cloud.png and /dev/null differ diff --git a/site/_images/dashboard-services-2-3Engines-cloud.png b/site/_images/dashboard-services-2-3Engines-cloud.png deleted file mode 100644 index 1ac2ae8..0000000 Binary files a/site/_images/dashboard-services-2-3Engines-cloud.png and /dev/null differ diff --git a/site/_images/dashboard-services-3-3Engines-cloud.png b/site/_images/dashboard-services-3-3Engines-cloud.png deleted file mode 100644 index 11ceca0..0000000 Binary files a/site/_images/dashboard-services-3-3Engines-cloud.png and /dev/null differ diff --git a/site/_images/dashboard-services-4-3Engines-cloud.png b/site/_images/dashboard-services-4-3Engines-cloud.png deleted file mode 100644 index 9c7e49c..0000000 Binary files a/site/_images/dashboard-services-4-3Engines-cloud.png and /dev/null differ diff --git a/site/_images/dashboard-services-5-3Engines-cloud.png b/site/_images/dashboard-services-5-3Engines-cloud.png deleted file mode 100644 index 220808f..0000000 Binary files a/site/_images/dashboard-services-5-3Engines-cloud.png and /dev/null differ diff --git a/site/_images/dashboard-services-6-3Engines-cloud.png b/site/_images/dashboard-services-6-3Engines-cloud.png deleted file mode 100644 index 4747ec7..0000000 Binary files a/site/_images/dashboard-services-6-3Engines-cloud.png and /dev/null differ diff --git a/site/_images/dashboard-services-7-3Engines-cloud.png b/site/_images/dashboard-services-7-3Engines-cloud.png deleted file mode 100644 index 0e1aebe..0000000 Binary files a/site/_images/dashboard-services-7-3Engines-cloud.png and /dev/null differ diff --git a/site/_images/dashboard-services-9-3Engines-cloud.png b/site/_images/dashboard-services-9-3Engines-cloud.png deleted file mode 100644 index a3a23da..0000000 Binary files a/site/_images/dashboard-services-9-3Engines-cloud.png and /dev/null differ diff --git a/site/_images/dashboard2.png b/site/_images/dashboard2.png deleted file mode 100644 index 27f0be0..0000000 Binary files a/site/_images/dashboard2.png and /dev/null differ diff --git a/site/_images/dashboard_installed.png b/site/_images/dashboard_installed.png deleted file mode 100644 index eb2cba2..0000000 Binary files a/site/_images/dashboard_installed.png and /dev/null differ diff --git a/site/_images/dashboard_view.png b/site/_images/dashboard_view.png deleted file mode 100644 index 47c8116..0000000 Binary files a/site/_images/dashboard_view.png and /dev/null differ diff --git a/site/_images/dashboardover1-v2.png b/site/_images/dashboardover1-v2.png deleted file mode 100644 index f0e17a1..0000000 Binary files a/site/_images/dashboardover1-v2.png and /dev/null differ diff --git a/site/_images/dashboardover2-v2.png b/site/_images/dashboardover2-v2.png deleted file mode 100644 index 1a7802e..0000000 Binary files a/site/_images/dashboardover2-v2.png and /dev/null differ diff --git a/site/_images/dask_dashboard_5_workers.png b/site/_images/dask_dashboard_5_workers.png deleted file mode 100644 index d36be08..0000000 Binary files a/site/_images/dask_dashboard_5_workers.png and /dev/null differ diff --git a/site/_images/debian_test_created.png b/site/_images/debian_test_created.png deleted file mode 100644 index 8f3ddfb..0000000 Binary files a/site/_images/debian_test_created.png and /dev/null differ diff --git a/site/_images/default_security_groups.png b/site/_images/default_security_groups.png deleted file mode 100644 index 567dd02..0000000 Binary files a/site/_images/default_security_groups.png and /dev/null differ diff --git a/site/_images/devvdb.png b/site/_images/devvdb.png deleted file mode 100644 index 95762b5..0000000 Binary files a/site/_images/devvdb.png and /dev/null differ diff --git a/site/_images/dns1.png b/site/_images/dns1.png deleted file mode 100644 index 9ac83d9..0000000 Binary files a/site/_images/dns1.png and /dev/null differ diff --git a/site/_images/dockerspace_created.png b/site/_images/dockerspace_created.png deleted file mode 100644 index 1368dfc..0000000 Binary files a/site/_images/dockerspace_created.png and /dev/null differ diff --git a/site/_images/download_config_cli.png b/site/_images/download_config_cli.png deleted file mode 100644 index 91c4daf..0000000 Binary files a/site/_images/download_config_cli.png and /dev/null differ diff --git a/site/_images/download_config_horizon.png b/site/_images/download_config_horizon.png deleted file mode 100644 index cdf493a..0000000 Binary files a/site/_images/download_config_horizon.png and /dev/null differ diff --git a/site/_images/download_rc_file_2fa.png b/site/_images/download_rc_file_2fa.png deleted file mode 100644 index 3e8aac0..0000000 Binary files a/site/_images/download_rc_file_2fa.png and /dev/null differ diff --git a/site/_images/drop-down-menu.png b/site/_images/drop-down-menu.png deleted file mode 100644 index b17c1b1..0000000 Binary files a/site/_images/drop-down-menu.png and /dev/null differ diff --git a/site/_images/edit.png b/site/_images/edit.png deleted file mode 100644 index 99054e9..0000000 Binary files a/site/_images/edit.png and /dev/null differ diff --git a/site/_images/editing_profile_3Enginescloud.png b/site/_images/editing_profile_3Enginescloud.png deleted file mode 100644 index 8c4687a..0000000 Binary files a/site/_images/editing_profile_3Enginescloud.png and /dev/null differ diff --git a/site/_images/eefa_freeotp_qr_icon.png b/site/_images/eefa_freeotp_qr_icon.png deleted file mode 100644 index 1fc102d..0000000 Binary files a/site/_images/eefa_freeotp_qr_icon.png and /dev/null differ diff --git a/site/_images/eefa_logged_in_creodias.png b/site/_images/eefa_logged_in_creodias.png deleted file mode 100644 index e23291c..0000000 Binary files a/site/_images/eefa_logged_in_creodias.png and /dev/null differ diff --git a/site/_images/eefa_logged_in_creodias.png.html b/site/_images/eefa_logged_in_creodias.png.html deleted file mode 100644 index b810900..0000000 --- a/site/_images/eefa_logged_in_creodias.png.html +++ /dev/null @@ -1,12 +0,0 @@ - Eefa logged in creodias.png - 3Engines Documentation

Eefa logged in creodias.png

None

\ No newline at end of file diff --git a/site/_images/eefa_mobile_auth_setup_creodias.png b/site/_images/eefa_mobile_auth_setup_creodias.png deleted file mode 100644 index 4ea0248..0000000 Binary files a/site/_images/eefa_mobile_auth_setup_creodias.png and /dev/null differ diff --git a/site/_images/eefa_mobile_auth_setup_creodias.png.html b/site/_images/eefa_mobile_auth_setup_creodias.png.html deleted file mode 100644 index cfb563e..0000000 --- a/site/_images/eefa_mobile_auth_setup_creodias.png.html +++ /dev/null @@ -1,12 +0,0 @@ - Eefa mobile auth setup creodias.png - 3Engines Documentation

Eefa mobile auth setup creodias.png

None

\ No newline at end of file diff --git a/site/_images/eefa_qr_screen_creodias.png b/site/_images/eefa_qr_screen_creodias.png deleted file mode 100644 index 2d5eac1..0000000 Binary files a/site/_images/eefa_qr_screen_creodias.png and /dev/null differ diff --git a/site/_images/eefa_qr_screen_creodias.png.html b/site/_images/eefa_qr_screen_creodias.png.html deleted file mode 100644 index e5e0727..0000000 --- a/site/_images/eefa_qr_screen_creodias.png.html +++ /dev/null @@ -1,12 +0,0 @@ - Eefa qr screen creodias.png - 3Engines Documentation

Eefa qr screen creodias.png

None

\ No newline at end of file diff --git a/site/_images/eefa_restart_login_creodias.png b/site/_images/eefa_restart_login_creodias.png deleted file mode 100644 index 5ba7dae..0000000 Binary files a/site/_images/eefa_restart_login_creodias.png and /dev/null differ diff --git a/site/_images/eefa_restart_login_creodias.png.html b/site/_images/eefa_restart_login_creodias.png.html deleted file mode 100644 index 39c66c3..0000000 --- a/site/_images/eefa_restart_login_creodias.png.html +++ /dev/null @@ -1,12 +0,0 @@ - Eefa restart login creodias.png - 3Engines Documentation

Eefa restart login creodias.png

None

\ No newline at end of file diff --git a/site/_images/eefa_several_rows.png b/site/_images/eefa_several_rows.png deleted file mode 100644 index 57b889f..0000000 Binary files a/site/_images/eefa_several_rows.png and /dev/null differ diff --git a/site/_images/eefa_several_rows.png.html b/site/_images/eefa_several_rows.png.html deleted file mode 100644 index a95c4c1..0000000 --- a/site/_images/eefa_several_rows.png.html +++ /dev/null @@ -1,12 +0,0 @@ - Eefa several rows.png - 3Engines Documentation

Eefa several rows.png

None

\ No newline at end of file diff --git a/site/_images/eefa_sign_regular_creodias.png b/site/_images/eefa_sign_regular_creodias.png deleted file mode 100644 index 8328b00..0000000 Binary files a/site/_images/eefa_sign_regular_creodias.png and /dev/null differ diff --git a/site/_images/eefa_sign_regular_creodias.png.html b/site/_images/eefa_sign_regular_creodias.png.html deleted file mode 100644 index 76d3820..0000000 --- a/site/_images/eefa_sign_regular_creodias.png.html +++ /dev/null @@ -1,12 +0,0 @@ - Eefa sign regular creodias.png - 3Engines Documentation

Eefa sign regular creodias.png

None

\ No newline at end of file diff --git a/site/_images/eefa_start_creodias.png b/site/_images/eefa_start_creodias.png deleted file mode 100644 index a3444e1..0000000 Binary files a/site/_images/eefa_start_creodias.png and /dev/null differ diff --git a/site/_images/eefa_start_creodias.png.html b/site/_images/eefa_start_creodias.png.html deleted file mode 100644 index 5448e01..0000000 --- a/site/_images/eefa_start_creodias.png.html +++ /dev/null @@ -1,12 +0,0 @@ - Eefa start creodias.png - 3Engines Documentation

Eefa start creodias.png

None

\ No newline at end of file diff --git a/site/_images/eefa_tapped.png b/site/_images/eefa_tapped.png deleted file mode 100644 index d61c760..0000000 Binary files a/site/_images/eefa_tapped.png and /dev/null differ diff --git a/site/_images/eefa_tapped.png.html b/site/_images/eefa_tapped.png.html deleted file mode 100644 index 958940b..0000000 --- a/site/_images/eefa_tapped.png.html +++ /dev/null @@ -1,12 +0,0 @@ - Eefa tapped.png - 3Engines Documentation

Eefa tapped.png

None

\ No newline at end of file diff --git a/site/_images/enable_load_balancer_checked.png b/site/_images/enable_load_balancer_checked.png deleted file mode 100644 index 119ac36..0000000 Binary files a/site/_images/enable_load_balancer_checked.png and /dev/null differ diff --git a/site/_images/enable_load_balancer_unchecked.png b/site/_images/enable_load_balancer_unchecked.png deleted file mode 100644 index 852884e..0000000 Binary files a/site/_images/enable_load_balancer_unchecked.png and /dev/null differ diff --git a/site/_images/enabled.png b/site/_images/enabled.png deleted file mode 100644 index 7c441c4..0000000 Binary files a/site/_images/enabled.png and /dev/null differ diff --git a/site/_images/enter_new_password_3Enginescloud.png b/site/_images/enter_new_password_3Enginescloud.png deleted file mode 100644 index 8af7335..0000000 Binary files a/site/_images/enter_new_password_3Enginescloud.png and /dev/null differ diff --git a/site/_images/enter_the_six_digit_code2.png b/site/_images/enter_the_six_digit_code2.png deleted file mode 100644 index bbeecca..0000000 Binary files a/site/_images/enter_the_six_digit_code2.png and /dev/null differ diff --git a/site/_images/export_os_cloud.png b/site/_images/export_os_cloud.png deleted file mode 100644 index 89f9f5d..0000000 Binary files a/site/_images/export_os_cloud.png and /dev/null differ diff --git a/site/_images/fedora_image.png b/site/_images/fedora_image.png deleted file mode 100644 index 5f642fe..0000000 Binary files a/site/_images/fedora_image.png and /dev/null differ diff --git a/site/_images/filtered_cirros.png b/site/_images/filtered_cirros.png deleted file mode 100644 index f89ee3c..0000000 Binary files a/site/_images/filtered_cirros.png and /dev/null differ diff --git a/site/_images/final_result.png b/site/_images/final_result.png deleted file mode 100644 index b988e67..0000000 Binary files a/site/_images/final_result.png and /dev/null differ diff --git a/site/_images/fip1.png b/site/_images/fip1.png deleted file mode 100644 index 5aec841..0000000 Binary files a/site/_images/fip1.png and /dev/null differ diff --git a/site/_images/fip2.png b/site/_images/fip2.png deleted file mode 100644 index 019dd84..0000000 Binary files a/site/_images/fip2.png and /dev/null differ diff --git a/site/_images/fip3.png b/site/_images/fip3.png deleted file mode 100644 index 5add93c..0000000 Binary files a/site/_images/fip3.png and /dev/null differ diff --git a/site/_images/fip4.png b/site/_images/fip4.png deleted file mode 100644 index 5fa2556..0000000 Binary files a/site/_images/fip4.png and /dev/null differ diff --git a/site/_images/fip5.png b/site/_images/fip5.png deleted file mode 100644 index 5ad58b5..0000000 Binary files a/site/_images/fip5.png and /dev/null differ diff --git a/site/_images/fip6.png b/site/_images/fip6.png deleted file mode 100644 index 7cf1a46..0000000 Binary files a/site/_images/fip6.png and /dev/null differ diff --git a/site/_images/fip7.png b/site/_images/fip7.png deleted file mode 100644 index 2f6c9b7..0000000 Binary files a/site/_images/fip7.png and /dev/null differ diff --git a/site/_images/fip8.png b/site/_images/fip8.png deleted file mode 100644 index 1565416..0000000 Binary files a/site/_images/fip8.png and /dev/null differ diff --git a/site/_images/fip9.png b/site/_images/fip9.png deleted file mode 100644 index 33b748c..0000000 Binary files a/site/_images/fip9.png and /dev/null differ diff --git a/site/_images/first_argo_example.png b/site/_images/first_argo_example.png deleted file mode 100644 index bdfb03b..0000000 Binary files a/site/_images/first_argo_example.png and /dev/null differ diff --git a/site/_images/fixconsole.png b/site/_images/fixconsole.png deleted file mode 100644 index c92a69c..0000000 Binary files a/site/_images/fixconsole.png and /dev/null differ diff --git a/site/_images/flask_run.png b/site/_images/flask_run.png deleted file mode 100644 index 9ab38cb..0000000 Binary files a/site/_images/flask_run.png and /dev/null differ diff --git a/site/_images/flavor2_master2.png b/site/_images/flavor2_master2.png deleted file mode 100644 index 61b184f..0000000 Binary files a/site/_images/flavor2_master2.png and /dev/null differ diff --git a/site/_images/flavor_list_2fa_short.png b/site/_images/flavor_list_2fa_short.png deleted file mode 100644 index 4647f58..0000000 Binary files a/site/_images/flavor_list_2fa_short.png and /dev/null differ diff --git a/site/_images/flavors_list.png b/site/_images/flavors_list.png deleted file mode 100644 index 8160b54..0000000 Binary files a/site/_images/flavors_list.png and /dev/null differ diff --git a/site/_images/flavors_listed_spot.png b/site/_images/flavors_listed_spot.png deleted file mode 100644 index 999d9e6..0000000 Binary files a/site/_images/flavors_listed_spot.png and /dev/null differ diff --git a/site/_images/floating_ip_created.png b/site/_images/floating_ip_created.png deleted file mode 100644 index 5248c6a..0000000 Binary files a/site/_images/floating_ip_created.png and /dev/null differ diff --git a/site/_images/floating_ips.png b/site/_images/floating_ips.png deleted file mode 100644 index 99cc728..0000000 Binary files a/site/_images/floating_ips.png and /dev/null differ diff --git a/site/_images/forgot_your_password_3Enginescloud.png b/site/_images/forgot_your_password_3Enginescloud.png deleted file mode 100644 index 36c8e05..0000000 Binary files a/site/_images/forgot_your_password_3Enginescloud.png and /dev/null differ diff --git a/site/_images/format_image_upload.png b/site/_images/format_image_upload.png deleted file mode 100644 index 3101570..0000000 Binary files a/site/_images/format_image_upload.png and /dev/null differ diff --git a/site/_images/four_created.png b/site/_images/four_created.png deleted file mode 100644 index 2e64431..0000000 Binary files a/site/_images/four_created.png and /dev/null differ diff --git a/site/_images/fra1-2-default-template.png b/site/_images/fra1-2-default-template.png deleted file mode 100644 index 3499deb..0000000 Binary files a/site/_images/fra1-2-default-template.png and /dev/null differ diff --git a/site/_images/freeotp_icon_to_select.png b/site/_images/freeotp_icon_to_select.png deleted file mode 100644 index d35ebd5..0000000 Binary files a/site/_images/freeotp_icon_to_select.png and /dev/null differ diff --git a/site/_images/freeotp_icon_to_select.png.html b/site/_images/freeotp_icon_to_select.png.html deleted file mode 100644 index c278b6b..0000000 --- a/site/_images/freeotp_icon_to_select.png.html +++ /dev/null @@ -1,12 +0,0 @@ - Freeotp icon to select.png - 3Engines Documentation

Freeotp icon to select.png

None

\ No newline at end of file diff --git a/site/_images/freeotp_tapped_number.png b/site/_images/freeotp_tapped_number.png deleted file mode 100644 index f9ac40a..0000000 Binary files a/site/_images/freeotp_tapped_number.png and /dev/null differ diff --git a/site/_images/freeotp_tapped_number.png.html b/site/_images/freeotp_tapped_number.png.html deleted file mode 100644 index 1abe9b3..0000000 --- a/site/_images/freeotp_tapped_number.png.html +++ /dev/null @@ -1,12 +0,0 @@ - Freeotp tapped number.png - 3Engines Documentation

Freeotp tapped number.png

None

\ No newline at end of file diff --git a/site/_images/fwaas-openvpn-v2-34.png b/site/_images/fwaas-openvpn-v2-34.png deleted file mode 100644 index 3b8f6f1..0000000 Binary files a/site/_images/fwaas-openvpn-v2-34.png and /dev/null differ diff --git a/site/_images/generate_credentials.png b/site/_images/generate_credentials.png deleted file mode 100644 index 5609d2e..0000000 Binary files a/site/_images/generate_credentials.png and /dev/null differ diff --git a/site/_images/get_nodes_large.png b/site/_images/get_nodes_large.png deleted file mode 100644 index 52cd50c..0000000 Binary files a/site/_images/get_nodes_large.png and /dev/null differ diff --git a/site/_images/git-bash01_creodias.png b/site/_images/git-bash01_creodias.png deleted file mode 100644 index 5aa638b..0000000 Binary files a/site/_images/git-bash01_creodias.png and /dev/null differ diff --git a/site/_images/git-bash02_creodias.png b/site/_images/git-bash02_creodias.png deleted file mode 100644 index d9a2a5d..0000000 Binary files a/site/_images/git-bash02_creodias.png and /dev/null differ diff --git a/site/_images/git-bash03_creodias.png b/site/_images/git-bash03_creodias.png deleted file mode 100644 index 8743d9e..0000000 Binary files a/site/_images/git-bash03_creodias.png and /dev/null differ diff --git a/site/_images/git-bash04_creodias.png b/site/_images/git-bash04_creodias.png deleted file mode 100644 index 981aa01..0000000 Binary files a/site/_images/git-bash04_creodias.png and /dev/null differ diff --git a/site/_images/git-bash05_creodias.png b/site/_images/git-bash05_creodias.png deleted file mode 100644 index 4aaa040..0000000 Binary files a/site/_images/git-bash05_creodias.png and /dev/null differ diff --git a/site/_images/git-bash06_creodias.png b/site/_images/git-bash06_creodias.png deleted file mode 100644 index 9db0c23..0000000 Binary files a/site/_images/git-bash06_creodias.png and /dev/null differ diff --git a/site/_images/git-bash07_creodias.png b/site/_images/git-bash07_creodias.png deleted file mode 100644 index 6211334..0000000 Binary files a/site/_images/git-bash07_creodias.png and /dev/null differ diff --git a/site/_images/git-bash09_creodias.png b/site/_images/git-bash09_creodias.png deleted file mode 100644 index 0657e0b..0000000 Binary files a/site/_images/git-bash09_creodias.png and /dev/null differ diff --git a/site/_images/git-bash10_creodias.png b/site/_images/git-bash10_creodias.png deleted file mode 100644 index ba39ce7..0000000 Binary files a/site/_images/git-bash10_creodias.png and /dev/null differ diff --git a/site/_images/git-bash11_creodias.png b/site/_images/git-bash11_creodias.png deleted file mode 100644 index 81eb1b6..0000000 Binary files a/site/_images/git-bash11_creodias.png and /dev/null differ diff --git a/site/_images/git-bash12_creodias.png b/site/_images/git-bash12_creodias.png deleted file mode 100644 index cc2b691..0000000 Binary files a/site/_images/git-bash12_creodias.png and /dev/null differ diff --git a/site/_images/git-bash17_creodias.png b/site/_images/git-bash17_creodias.png deleted file mode 100644 index 061695d..0000000 Binary files a/site/_images/git-bash17_creodias.png and /dev/null differ diff --git a/site/_images/gitlab_get_pods.png b/site/_images/gitlab_get_pods.png deleted file mode 100644 index b253451..0000000 Binary files a/site/_images/gitlab_get_pods.png and /dev/null differ diff --git a/site/_images/go_template_image.png b/site/_images/go_template_image.png deleted file mode 100644 index e111194..0000000 Binary files a/site/_images/go_template_image.png and /dev/null differ diff --git a/site/_images/gpu_templates.png b/site/_images/gpu_templates.png deleted file mode 100644 index e0f74a4..0000000 Binary files a/site/_images/gpu_templates.png and /dev/null differ diff --git a/site/_images/heat-test2.png b/site/_images/heat-test2.png deleted file mode 100644 index 6cb249f..0000000 Binary files a/site/_images/heat-test2.png and /dev/null differ diff --git a/site/_images/heat_instance.png b/site/_images/heat_instance.png deleted file mode 100644 index 34b90dd..0000000 Binary files a/site/_images/heat_instance.png and /dev/null differ diff --git a/site/_images/heat_test2_instances.png b/site/_images/heat_test2_instances.png deleted file mode 100644 index dfd216c..0000000 Binary files a/site/_images/heat_test2_instances.png and /dev/null differ diff --git a/site/_images/heat_test2_stacks.png b/site/_images/heat_test2_stacks.png deleted file mode 100644 index 93a3c87..0000000 Binary files a/site/_images/heat_test2_stacks.png and /dev/null differ diff --git a/site/_images/horizon_flavors.png b/site/_images/horizon_flavors.png deleted file mode 100644 index 4e4115a..0000000 Binary files a/site/_images/horizon_flavors.png and /dev/null differ diff --git a/site/_images/how-to-create-instance-snapshot-cli-12_creodias.png b/site/_images/how-to-create-instance-snapshot-cli-12_creodias.png deleted file mode 100644 index 5b049d0..0000000 Binary files a/site/_images/how-to-create-instance-snapshot-cli-12_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-instance-snapshot-cli-13_creodias.png b/site/_images/how-to-create-instance-snapshot-cli-13_creodias.png deleted file mode 100644 index a7a0a24..0000000 Binary files a/site/_images/how-to-create-instance-snapshot-cli-13_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-instance-snapshot-cli-14_creodias.png b/site/_images/how-to-create-instance-snapshot-cli-14_creodias.png deleted file mode 100644 index cd4e7eb..0000000 Binary files a/site/_images/how-to-create-instance-snapshot-cli-14_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-instance-snapshot-cli-15_creodias.png b/site/_images/how-to-create-instance-snapshot-cli-15_creodias.png deleted file mode 100644 index de7eac4..0000000 Binary files a/site/_images/how-to-create-instance-snapshot-cli-15_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-instance-snapshot-cli-16_creodias.png b/site/_images/how-to-create-instance-snapshot-cli-16_creodias.png deleted file mode 100644 index 954fecc..0000000 Binary files a/site/_images/how-to-create-instance-snapshot-cli-16_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-instance-snapshot-cli-17_creodias.png b/site/_images/how-to-create-instance-snapshot-cli-17_creodias.png deleted file mode 100644 index 3ec6ac4..0000000 Binary files a/site/_images/how-to-create-instance-snapshot-cli-17_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-instance-snapshot-cli-18_creodias.png b/site/_images/how-to-create-instance-snapshot-cli-18_creodias.png deleted file mode 100644 index edc59ce..0000000 Binary files a/site/_images/how-to-create-instance-snapshot-cli-18_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-instance-snapshot-cli-19_creodias.png b/site/_images/how-to-create-instance-snapshot-cli-19_creodias.png deleted file mode 100644 index aa44ade..0000000 Binary files a/site/_images/how-to-create-instance-snapshot-cli-19_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-instance-snapshot-cli-20_creodias.png b/site/_images/how-to-create-instance-snapshot-cli-20_creodias.png deleted file mode 100644 index 0279381..0000000 Binary files a/site/_images/how-to-create-instance-snapshot-cli-20_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-instance-snapshot-cli-21_creodias.png b/site/_images/how-to-create-instance-snapshot-cli-21_creodias.png deleted file mode 100644 index f92dc94..0000000 Binary files a/site/_images/how-to-create-instance-snapshot-cli-21_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-instance-snapshot-cli-22_creodias.png b/site/_images/how-to-create-instance-snapshot-cli-22_creodias.png deleted file mode 100644 index 5789719..0000000 Binary files a/site/_images/how-to-create-instance-snapshot-cli-22_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-instance-snapshot-cli-23_creodias.png b/site/_images/how-to-create-instance-snapshot-cli-23_creodias.png deleted file mode 100644 index 1c67a2d..0000000 Binary files a/site/_images/how-to-create-instance-snapshot-cli-23_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-instance-snapshot-horizon-13_creodias.png b/site/_images/how-to-create-instance-snapshot-horizon-13_creodias.png deleted file mode 100644 index d661803..0000000 Binary files a/site/_images/how-to-create-instance-snapshot-horizon-13_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-rotating-backups-05_creodias.png b/site/_images/how-to-create-rotating-backups-05_creodias.png deleted file mode 100644 index e56575b..0000000 Binary files a/site/_images/how-to-create-rotating-backups-05_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-volume-snapshot-Horizon-01_creodias.png b/site/_images/how-to-create-volume-snapshot-Horizon-01_creodias.png deleted file mode 100644 index 9afb6ae..0000000 Binary files a/site/_images/how-to-create-volume-snapshot-Horizon-01_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-volume-snapshot-Horizon-02_creodias.png b/site/_images/how-to-create-volume-snapshot-Horizon-02_creodias.png deleted file mode 100644 index 9985d01..0000000 Binary files a/site/_images/how-to-create-volume-snapshot-Horizon-02_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-volume-snapshot-Horizon-03_creodias.png b/site/_images/how-to-create-volume-snapshot-Horizon-03_creodias.png deleted file mode 100644 index 1c25fd4..0000000 Binary files a/site/_images/how-to-create-volume-snapshot-Horizon-03_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-volume-snapshot-Horizon-04_creodias.png b/site/_images/how-to-create-volume-snapshot-Horizon-04_creodias.png deleted file mode 100644 index 0452673..0000000 Binary files a/site/_images/how-to-create-volume-snapshot-Horizon-04_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-volume-snapshot-Horizon-05_creodias.png b/site/_images/how-to-create-volume-snapshot-Horizon-05_creodias.png deleted file mode 100644 index 2055728..0000000 Binary files a/site/_images/how-to-create-volume-snapshot-Horizon-05_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-volume-snapshot-Horizon-06_creodias.png b/site/_images/how-to-create-volume-snapshot-Horizon-06_creodias.png deleted file mode 100644 index 9b15293..0000000 Binary files a/site/_images/how-to-create-volume-snapshot-Horizon-06_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-volume-snapshot-Horizon-07_creodias.png b/site/_images/how-to-create-volume-snapshot-Horizon-07_creodias.png deleted file mode 100644 index b7990aa..0000000 Binary files a/site/_images/how-to-create-volume-snapshot-Horizon-07_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-volume-snapshot-Horizon-08_creodias.png b/site/_images/how-to-create-volume-snapshot-Horizon-08_creodias.png deleted file mode 100644 index 56648d4..0000000 Binary files a/site/_images/how-to-create-volume-snapshot-Horizon-08_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-volume-snapshot-cli-01_creodias.png b/site/_images/how-to-create-volume-snapshot-cli-01_creodias.png deleted file mode 100644 index 1afd3f7..0000000 Binary files a/site/_images/how-to-create-volume-snapshot-cli-01_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-volume-snapshot-cli-02_creodias.png b/site/_images/how-to-create-volume-snapshot-cli-02_creodias.png deleted file mode 100644 index 8450b4f..0000000 Binary files a/site/_images/how-to-create-volume-snapshot-cli-02_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-volume-snapshot-cli-03_creodias.png b/site/_images/how-to-create-volume-snapshot-cli-03_creodias.png deleted file mode 100644 index 5915525..0000000 Binary files a/site/_images/how-to-create-volume-snapshot-cli-03_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-volume-snapshot-cli-04_creodias.png b/site/_images/how-to-create-volume-snapshot-cli-04_creodias.png deleted file mode 100644 index ed4b657..0000000 Binary files a/site/_images/how-to-create-volume-snapshot-cli-04_creodias.png and /dev/null differ diff --git a/site/_images/how-to-create-volume-snapshot-cli-05_creodias.png b/site/_images/how-to-create-volume-snapshot-cli-05_creodias.png deleted file mode 100644 index 0dc2154..0000000 Binary files a/site/_images/how-to-create-volume-snapshot-cli-05_creodias.png and /dev/null differ diff --git a/site/_images/how-to-move-data-volume-cli-12_creodias.png b/site/_images/how-to-move-data-volume-cli-12_creodias.png deleted file mode 100644 index d93be5f..0000000 Binary files a/site/_images/how-to-move-data-volume-cli-12_creodias.png and /dev/null differ diff --git a/site/_images/how-to-move-data-volume-cli-13_creodias.png b/site/_images/how-to-move-data-volume-cli-13_creodias.png deleted file mode 100644 index 5b17af9..0000000 Binary files a/site/_images/how-to-move-data-volume-cli-13_creodias.png and /dev/null differ diff --git a/site/_images/how-to-move-data-volume-cli-14_creodias.png b/site/_images/how-to-move-data-volume-cli-14_creodias.png deleted file mode 100644 index 3631f1b..0000000 Binary files a/site/_images/how-to-move-data-volume-cli-14_creodias.png and /dev/null differ diff --git a/site/_images/how-to-move-data-volume-cli-15_creodias.png b/site/_images/how-to-move-data-volume-cli-15_creodias.png deleted file mode 100644 index ee9c4f8..0000000 Binary files a/site/_images/how-to-move-data-volume-cli-15_creodias.png and /dev/null differ diff --git a/site/_images/how-to-move-data-volume-cli-31_creodias.png b/site/_images/how-to-move-data-volume-cli-31_creodias.png deleted file mode 100644 index 295e11c..0000000 Binary files a/site/_images/how-to-move-data-volume-cli-31_creodias.png and /dev/null differ diff --git a/site/_images/how-to-move-data-volume-cli-32_creodias.png b/site/_images/how-to-move-data-volume-cli-32_creodias.png deleted file mode 100644 index ab27b35..0000000 Binary files a/site/_images/how-to-move-data-volume-cli-32_creodias.png and /dev/null differ diff --git a/site/_images/how-to-move-data-volume-horizon-05_creodias.png b/site/_images/how-to-move-data-volume-horizon-05_creodias.png deleted file mode 100644 index 4d772a2..0000000 Binary files a/site/_images/how-to-move-data-volume-horizon-05_creodias.png and /dev/null differ diff --git a/site/_images/how-to-move-data-volume-horizon-06_creodias.png b/site/_images/how-to-move-data-volume-horizon-06_creodias.png deleted file mode 100644 index c059523..0000000 Binary files a/site/_images/how-to-move-data-volume-horizon-06_creodias.png and /dev/null differ diff --git a/site/_images/how-to-move-data-volume-horizon-07_creodias.png b/site/_images/how-to-move-data-volume-horizon-07_creodias.png deleted file mode 100644 index a2294ae..0000000 Binary files a/site/_images/how-to-move-data-volume-horizon-07_creodias.png and /dev/null differ diff --git a/site/_images/how-to-move-data-volume-horizon-08_creodias.png b/site/_images/how-to-move-data-volume-horizon-08_creodias.png deleted file mode 100644 index 10afe81..0000000 Binary files a/site/_images/how-to-move-data-volume-horizon-08_creodias.png and /dev/null differ diff --git a/site/_images/how-to-move-data-volume-horizon-09_creodias.png b/site/_images/how-to-move-data-volume-horizon-09_creodias.png deleted file mode 100644 index f341f07..0000000 Binary files a/site/_images/how-to-move-data-volume-horizon-09_creodias.png and /dev/null differ diff --git a/site/_images/how-to-move-data-volume-horizon-10_creodias.png b/site/_images/how-to-move-data-volume-horizon-10_creodias.png deleted file mode 100644 index 3c84141..0000000 Binary files a/site/_images/how-to-move-data-volume-horizon-10_creodias.png and /dev/null differ diff --git a/site/_images/how-to-move-data-volume-horizon-27_creodias.png b/site/_images/how-to-move-data-volume-horizon-27_creodias.png deleted file mode 100644 index c1d8c32..0000000 Binary files a/site/_images/how-to-move-data-volume-horizon-27_creodias.png and /dev/null differ diff --git a/site/_images/how-to-move-data-volume-horizon-28_creodias.png b/site/_images/how-to-move-data-volume-horizon-28_creodias.png deleted file mode 100644 index a275f4b..0000000 Binary files a/site/_images/how-to-move-data-volume-horizon-28_creodias.png and /dev/null differ diff --git a/site/_images/how-to-move-data-volume-horizon-29_creodias.png b/site/_images/how-to-move-data-volume-horizon-29_creodias.png deleted file mode 100644 index f0b6371..0000000 Binary files a/site/_images/how-to-move-data-volume-horizon-29_creodias.png and /dev/null differ diff --git a/site/_images/how-to-move-data-volume-horizon-30_creodias.png b/site/_images/how-to-move-data-volume-horizon-30_creodias.png deleted file mode 100644 index cc9237a..0000000 Binary files a/site/_images/how-to-move-data-volume-horizon-30_creodias.png and /dev/null differ diff --git a/site/_images/how-to-move-data-volume-horizon-33_creodias.png b/site/_images/how-to-move-data-volume-horizon-33_creodias.png deleted file mode 100644 index 422677f..0000000 Binary files a/site/_images/how-to-move-data-volume-horizon-33_creodias.png and /dev/null differ diff --git a/site/_images/how-to-move-data-volume-horizon-34_creodias.png b/site/_images/how-to-move-data-volume-horizon-34_creodias.png deleted file mode 100644 index 668a0d5..0000000 Binary files a/site/_images/how-to-move-data-volume-horizon-34_creodias.png and /dev/null differ diff --git a/site/_images/how-to-restore-volume-from-snapshot-Horizon-01_creodias.png b/site/_images/how-to-restore-volume-from-snapshot-Horizon-01_creodias.png deleted file mode 100644 index d7d8c62..0000000 Binary files a/site/_images/how-to-restore-volume-from-snapshot-Horizon-01_creodias.png and /dev/null differ diff --git a/site/_images/how-to-restore-volume-from-snapshot-Horizon-02_creodias.png b/site/_images/how-to-restore-volume-from-snapshot-Horizon-02_creodias.png deleted file mode 100644 index e39be29..0000000 Binary files a/site/_images/how-to-restore-volume-from-snapshot-Horizon-02_creodias.png and /dev/null differ diff --git a/site/_images/how-to-restore-volume-from-snapshot-Horizon-03_creodias.png b/site/_images/how-to-restore-volume-from-snapshot-Horizon-03_creodias.png deleted file mode 100644 index 9c5a7e1..0000000 Binary files a/site/_images/how-to-restore-volume-from-snapshot-Horizon-03_creodias.png and /dev/null differ diff --git a/site/_images/how-to-restore-volume-from-snapshot-Horizon-04_creodias.png b/site/_images/how-to-restore-volume-from-snapshot-Horizon-04_creodias.png deleted file mode 100644 index 22cead1..0000000 Binary files a/site/_images/how-to-restore-volume-from-snapshot-Horizon-04_creodias.png and /dev/null differ diff --git a/site/_images/how-to-restore-volume-from-snapshot-cli-01_creodias.png b/site/_images/how-to-restore-volume-from-snapshot-cli-01_creodias.png deleted file mode 100644 index 1320997..0000000 Binary files a/site/_images/how-to-restore-volume-from-snapshot-cli-01_creodias.png and /dev/null differ diff --git a/site/_images/how-to-restore-volume-from-snapshot-cli-02_creodias.png b/site/_images/how-to-restore-volume-from-snapshot-cli-02_creodias.png deleted file mode 100644 index 0a79a90..0000000 Binary files a/site/_images/how-to-restore-volume-from-snapshot-cli-02_creodias.png and /dev/null differ diff --git a/site/_images/how-to-restore-volume-from-snapshot-cli-03_creodias.png b/site/_images/how-to-restore-volume-from-snapshot-cli-03_creodias.png deleted file mode 100644 index e3029b1..0000000 Binary files a/site/_images/how-to-restore-volume-from-snapshot-cli-03_creodias.png and /dev/null differ diff --git a/site/_images/identity_projects.png b/site/_images/identity_projects.png deleted file mode 100644 index 6cbd497..0000000 Binary files a/site/_images/identity_projects.png and /dev/null differ diff --git a/site/_images/image-2024-2-13_13-15-17.png b/site/_images/image-2024-2-13_13-15-17.png deleted file mode 100644 index a3baee2..0000000 Binary files a/site/_images/image-2024-2-13_13-15-17.png and /dev/null differ diff --git a/site/_images/image-2024-2-13_14-44-49.png b/site/_images/image-2024-2-13_14-44-49.png deleted file mode 100644 index 9dcaa11..0000000 Binary files a/site/_images/image-2024-2-13_14-44-49.png and /dev/null differ diff --git a/site/_images/image-2024-2-13_15-39-52.png b/site/_images/image-2024-2-13_15-39-52.png deleted file mode 100644 index 6018b78..0000000 Binary files a/site/_images/image-2024-2-13_15-39-52.png and /dev/null differ diff --git a/site/_images/image-2024-2-13_15-48-38.png b/site/_images/image-2024-2-13_15-48-38.png deleted file mode 100644 index ced9ccd..0000000 Binary files a/site/_images/image-2024-2-13_15-48-38.png and /dev/null differ diff --git a/site/_images/image-2024-2-13_15-58-45.png b/site/_images/image-2024-2-13_15-58-45.png deleted file mode 100644 index 7d73096..0000000 Binary files a/site/_images/image-2024-2-13_15-58-45.png and /dev/null differ diff --git a/site/_images/image-2024-2-13_16-13-21.png b/site/_images/image-2024-2-13_16-13-21.png deleted file mode 100644 index c5859e7..0000000 Binary files a/site/_images/image-2024-2-13_16-13-21.png and /dev/null differ diff --git a/site/_images/image-2024-2-13_16-29-35.png b/site/_images/image-2024-2-13_16-29-35.png deleted file mode 100644 index f0fc7c0..0000000 Binary files a/site/_images/image-2024-2-13_16-29-35.png and /dev/null differ diff --git a/site/_images/image-2024-2-13_16-31-37.png b/site/_images/image-2024-2-13_16-31-37.png deleted file mode 100644 index 474ed07..0000000 Binary files a/site/_images/image-2024-2-13_16-31-37.png and /dev/null differ diff --git a/site/_images/image-2024-2-13_16-8-43.png b/site/_images/image-2024-2-13_16-8-43.png deleted file mode 100644 index 309e507..0000000 Binary files a/site/_images/image-2024-2-13_16-8-43.png and /dev/null differ diff --git a/site/_images/image-2024-4-26_15-4-3.png b/site/_images/image-2024-4-26_15-4-3.png deleted file mode 100644 index fd41ecc..0000000 Binary files a/site/_images/image-2024-4-26_15-4-3.png and /dev/null differ diff --git a/site/_images/image-2024-4-26_16-58-33.png b/site/_images/image-2024-4-26_16-58-33.png deleted file mode 100644 index c831584..0000000 Binary files a/site/_images/image-2024-4-26_16-58-33.png and /dev/null differ diff --git a/site/_images/image-2024-4-26_17-57-57.png b/site/_images/image-2024-4-26_17-57-57.png deleted file mode 100644 index 9ddb230..0000000 Binary files a/site/_images/image-2024-4-26_17-57-57.png and /dev/null differ diff --git a/site/_images/image-2024-4-29_12-56-40.png b/site/_images/image-2024-4-29_12-56-40.png deleted file mode 100644 index 2eaa9fa..0000000 Binary files a/site/_images/image-2024-4-29_12-56-40.png and /dev/null differ diff --git a/site/_images/image-2024-4-29_14-13-1.png b/site/_images/image-2024-4-29_14-13-1.png deleted file mode 100644 index 3e62d3e..0000000 Binary files a/site/_images/image-2024-4-29_14-13-1.png and /dev/null differ diff --git a/site/_images/image-2024-4-29_14-16-12.png b/site/_images/image-2024-4-29_14-16-12.png deleted file mode 100644 index a75c89b..0000000 Binary files a/site/_images/image-2024-4-29_14-16-12.png and /dev/null differ diff --git a/site/_images/image-2024-4-30_14-0-23.png b/site/_images/image-2024-4-30_14-0-23.png deleted file mode 100644 index 0202715..0000000 Binary files a/site/_images/image-2024-4-30_14-0-23.png and /dev/null differ diff --git a/site/_images/image-2024-5-10_16-28-4.png b/site/_images/image-2024-5-10_16-28-4.png deleted file mode 100644 index 22aac8f..0000000 Binary files a/site/_images/image-2024-5-10_16-28-4.png and /dev/null differ diff --git a/site/_images/image-2024-5-10_16-30-8.png b/site/_images/image-2024-5-10_16-30-8.png deleted file mode 100644 index 1c88f71..0000000 Binary files a/site/_images/image-2024-5-10_16-30-8.png and /dev/null differ diff --git a/site/_images/image-2024-5-14_14-54-10.png b/site/_images/image-2024-5-14_14-54-10.png deleted file mode 100644 index aef9dfb..0000000 Binary files a/site/_images/image-2024-5-14_14-54-10.png and /dev/null differ diff --git a/site/_images/image-2024-5-14_15-34-0.png b/site/_images/image-2024-5-14_15-34-0.png deleted file mode 100644 index 46e2ab0..0000000 Binary files a/site/_images/image-2024-5-14_15-34-0.png and /dev/null differ diff --git a/site/_images/image-2024-5-14_15-4-21.png b/site/_images/image-2024-5-14_15-4-21.png deleted file mode 100644 index 756a6c6..0000000 Binary files a/site/_images/image-2024-5-14_15-4-21.png and /dev/null differ diff --git a/site/_images/image-2024-5-17_11-20-27.png b/site/_images/image-2024-5-17_11-20-27.png deleted file mode 100644 index 55a6e28..0000000 Binary files a/site/_images/image-2024-5-17_11-20-27.png and /dev/null differ diff --git a/site/_images/image-2024-5-22_10-23-58.png b/site/_images/image-2024-5-22_10-23-58.png deleted file mode 100644 index f4a9fd6..0000000 Binary files a/site/_images/image-2024-5-22_10-23-58.png and /dev/null differ diff --git a/site/_images/image-2024-5-22_10-27-25.png b/site/_images/image-2024-5-22_10-27-25.png deleted file mode 100644 index 7c3c337..0000000 Binary files a/site/_images/image-2024-5-22_10-27-25.png and /dev/null differ diff --git a/site/_images/image-2024-5-22_10-38-53.png b/site/_images/image-2024-5-22_10-38-53.png deleted file mode 100644 index 73080e5..0000000 Binary files a/site/_images/image-2024-5-22_10-38-53.png and /dev/null differ diff --git a/site/_images/image-2024-5-22_11-17-12.png b/site/_images/image-2024-5-22_11-17-12.png deleted file mode 100644 index 0dacc1c..0000000 Binary files a/site/_images/image-2024-5-22_11-17-12.png and /dev/null differ diff --git a/site/_images/image-2024-5-23_17-16-2.png b/site/_images/image-2024-5-23_17-16-2.png deleted file mode 100644 index 64ccf40..0000000 Binary files a/site/_images/image-2024-5-23_17-16-2.png and /dev/null differ diff --git a/site/_images/image-2024-5-23_17-39-37.png b/site/_images/image-2024-5-23_17-39-37.png deleted file mode 100644 index 9a4d957..0000000 Binary files a/site/_images/image-2024-5-23_17-39-37.png and /dev/null differ diff --git a/site/_images/image-2024-5-6_13-48-13.png b/site/_images/image-2024-5-6_13-48-13.png deleted file mode 100644 index 225ff54..0000000 Binary files a/site/_images/image-2024-5-6_13-48-13.png and /dev/null differ diff --git a/site/_images/image-2024-5-6_14-25-36.png b/site/_images/image-2024-5-6_14-25-36.png deleted file mode 100644 index a09a3e2..0000000 Binary files a/site/_images/image-2024-5-6_14-25-36.png and /dev/null differ diff --git a/site/_images/image-2024-6-17_15-52-40.png b/site/_images/image-2024-6-17_15-52-40.png deleted file mode 100644 index 705e484..0000000 Binary files a/site/_images/image-2024-6-17_15-52-40.png and /dev/null differ diff --git a/site/_images/image-2024-6-18_17-32-8.png b/site/_images/image-2024-6-18_17-32-8.png deleted file mode 100644 index df6a1a1..0000000 Binary files a/site/_images/image-2024-6-18_17-32-8.png and /dev/null differ diff --git a/site/_images/image-2024-6-18_18-1-53.png b/site/_images/image-2024-6-18_18-1-53.png deleted file mode 100644 index 8ff89c0..0000000 Binary files a/site/_images/image-2024-6-18_18-1-53.png and /dev/null differ diff --git a/site/_images/image-2024-7-23_16-5-28.png b/site/_images/image-2024-7-23_16-5-28.png deleted file mode 100644 index fd7400a..0000000 Binary files a/site/_images/image-2024-7-23_16-5-28.png and /dev/null differ diff --git a/site/_images/image-2024-7-24_13-56-3.png b/site/_images/image-2024-7-24_13-56-3.png deleted file mode 100644 index 3daa33f..0000000 Binary files a/site/_images/image-2024-7-24_13-56-3.png and /dev/null differ diff --git a/site/_images/image-2024-7-24_14-9-18.png b/site/_images/image-2024-7-24_14-9-18.png deleted file mode 100644 index 5221fdb..0000000 Binary files a/site/_images/image-2024-7-24_14-9-18.png and /dev/null differ diff --git a/site/_images/image-2024-7-24_15-20-4.png b/site/_images/image-2024-7-24_15-20-4.png deleted file mode 100644 index aa76077..0000000 Binary files a/site/_images/image-2024-7-24_15-20-4.png and /dev/null differ diff --git a/site/_images/image-2024-7-24_15-27-55.png b/site/_images/image-2024-7-24_15-27-55.png deleted file mode 100644 index fd7400a..0000000 Binary files a/site/_images/image-2024-7-24_15-27-55.png and /dev/null differ diff --git a/site/_images/image-2024-7-24_15-29-17.png b/site/_images/image-2024-7-24_15-29-17.png deleted file mode 100644 index 7a5b400..0000000 Binary files a/site/_images/image-2024-7-24_15-29-17.png and /dev/null differ diff --git a/site/_images/image-2024-7-24_15-30-26.png b/site/_images/image-2024-7-24_15-30-26.png deleted file mode 100644 index cd83def..0000000 Binary files a/site/_images/image-2024-7-24_15-30-26.png and /dev/null differ diff --git a/site/_images/image-2024-7-26_12-36-54.png b/site/_images/image-2024-7-26_12-36-54.png deleted file mode 100644 index d52d8bc..0000000 Binary files a/site/_images/image-2024-7-26_12-36-54.png and /dev/null differ diff --git a/site/_images/image-2024-7-29_10-2-57.png b/site/_images/image-2024-7-29_10-2-57.png deleted file mode 100644 index 31174ee..0000000 Binary files a/site/_images/image-2024-7-29_10-2-57.png and /dev/null differ diff --git a/site/_images/image-2024-7-29_9-54-45.png b/site/_images/image-2024-7-29_9-54-45.png deleted file mode 100644 index 9614832..0000000 Binary files a/site/_images/image-2024-7-29_9-54-45.png and /dev/null differ diff --git a/site/_images/image-2024-7-29_9-56-44.png b/site/_images/image-2024-7-29_9-56-44.png deleted file mode 100644 index ba4f106..0000000 Binary files a/site/_images/image-2024-7-29_9-56-44.png and /dev/null differ diff --git a/site/_images/image-end-of-article.png b/site/_images/image-end-of-article.png deleted file mode 100644 index c7bbfd3..0000000 Binary files a/site/_images/image-end-of-article.png and /dev/null differ diff --git a/site/_images/image2022-12-9_10-55-8.png b/site/_images/image2022-12-9_10-55-8.png deleted file mode 100644 index 0e4e966..0000000 Binary files a/site/_images/image2022-12-9_10-55-8.png and /dev/null differ diff --git a/site/_images/image2023-1-13_13-6-5.png b/site/_images/image2023-1-13_13-6-5.png deleted file mode 100644 index edc921f..0000000 Binary files a/site/_images/image2023-1-13_13-6-5.png and /dev/null differ diff --git a/site/_images/image2023-11-7_13-17-10.png b/site/_images/image2023-11-7_13-17-10.png deleted file mode 100644 index faa5da7..0000000 Binary files a/site/_images/image2023-11-7_13-17-10.png and /dev/null differ diff --git a/site/_images/image2023-11-7_13-22-56.png b/site/_images/image2023-11-7_13-22-56.png deleted file mode 100644 index 6c10e94..0000000 Binary files a/site/_images/image2023-11-7_13-22-56.png and /dev/null differ diff --git a/site/_images/image2023-11-7_13-40-1.png b/site/_images/image2023-11-7_13-40-1.png deleted file mode 100644 index 7a42f78..0000000 Binary files a/site/_images/image2023-11-7_13-40-1.png and /dev/null differ diff --git a/site/_images/image2023-11-7_14-24-1.png b/site/_images/image2023-11-7_14-24-1.png deleted file mode 100644 index 42a78e7..0000000 Binary files a/site/_images/image2023-11-7_14-24-1.png and /dev/null differ diff --git a/site/_images/image2023-11-7_14-47-56.png b/site/_images/image2023-11-7_14-47-56.png deleted file mode 100644 index f027550..0000000 Binary files a/site/_images/image2023-11-7_14-47-56.png and /dev/null differ diff --git a/site/_images/image2023-11-7_14-54-8.png b/site/_images/image2023-11-7_14-54-8.png deleted file mode 100644 index 5d0c3ec..0000000 Binary files a/site/_images/image2023-11-7_14-54-8.png and /dev/null differ diff --git a/site/_images/image2023-11-7_15-1-59.png b/site/_images/image2023-11-7_15-1-59.png deleted file mode 100644 index 2ea94cf..0000000 Binary files a/site/_images/image2023-11-7_15-1-59.png and /dev/null differ diff --git a/site/_images/image2023-11-7_15-15-23.png b/site/_images/image2023-11-7_15-15-23.png deleted file mode 100644 index 940f653..0000000 Binary files a/site/_images/image2023-11-7_15-15-23.png and /dev/null differ diff --git a/site/_images/image2023-11-7_15-16-10.png b/site/_images/image2023-11-7_15-16-10.png deleted file mode 100644 index 948a34b..0000000 Binary files a/site/_images/image2023-11-7_15-16-10.png and /dev/null differ diff --git a/site/_images/image2023-11-7_15-38-40.png b/site/_images/image2023-11-7_15-38-40.png deleted file mode 100644 index f02f7e6..0000000 Binary files a/site/_images/image2023-11-7_15-38-40.png and /dev/null differ diff --git a/site/_images/image2023-2-15_16-41-49.png b/site/_images/image2023-2-15_16-41-49.png deleted file mode 100644 index 136503f..0000000 Binary files a/site/_images/image2023-2-15_16-41-49.png and /dev/null differ diff --git a/site/_images/image2023-2-15_17-50-44.png b/site/_images/image2023-2-15_17-50-44.png deleted file mode 100644 index d29f4c1..0000000 Binary files a/site/_images/image2023-2-15_17-50-44.png and /dev/null differ diff --git a/site/_images/image2023-2-15_18-13-51.png b/site/_images/image2023-2-15_18-13-51.png deleted file mode 100644 index 0867ce2..0000000 Binary files a/site/_images/image2023-2-15_18-13-51.png and /dev/null differ diff --git a/site/_images/image2023-2-6_15-25-4.png b/site/_images/image2023-2-6_15-25-4.png deleted file mode 100644 index 4045be3..0000000 Binary files a/site/_images/image2023-2-6_15-25-4.png and /dev/null differ diff --git a/site/_images/image2023-4-4_13-28-40.png b/site/_images/image2023-4-4_13-28-40.png deleted file mode 100644 index 5258a88..0000000 Binary files a/site/_images/image2023-4-4_13-28-40.png and /dev/null differ diff --git a/site/_images/image2023-4-4_13-37-48.png b/site/_images/image2023-4-4_13-37-48.png deleted file mode 100644 index 219f51c..0000000 Binary files a/site/_images/image2023-4-4_13-37-48.png and /dev/null differ diff --git a/site/_images/image2023-6-14_15-24-46.png b/site/_images/image2023-6-14_15-24-46.png deleted file mode 100644 index 5f57b0c..0000000 Binary files a/site/_images/image2023-6-14_15-24-46.png and /dev/null differ diff --git a/site/_images/image2023-6-14_15-26-51.png b/site/_images/image2023-6-14_15-26-51.png deleted file mode 100644 index 6358a79..0000000 Binary files a/site/_images/image2023-6-14_15-26-51.png and /dev/null differ diff --git a/site/_images/image2023-6-14_15-29-22.png b/site/_images/image2023-6-14_15-29-22.png deleted file mode 100644 index 9cf5cfb..0000000 Binary files a/site/_images/image2023-6-14_15-29-22.png and /dev/null differ diff --git a/site/_images/image2023-6-14_15-40-56.png b/site/_images/image2023-6-14_15-40-56.png deleted file mode 100644 index 8741dde..0000000 Binary files a/site/_images/image2023-6-14_15-40-56.png and /dev/null differ diff --git a/site/_images/image2023-6-14_16-41-7.png b/site/_images/image2023-6-14_16-41-7.png deleted file mode 100644 index 7973ba5..0000000 Binary files a/site/_images/image2023-6-14_16-41-7.png and /dev/null differ diff --git a/site/_images/image2023-6-14_16-8-44.png b/site/_images/image2023-6-14_16-8-44.png deleted file mode 100644 index 478dde5..0000000 Binary files a/site/_images/image2023-6-14_16-8-44.png and /dev/null differ diff --git a/site/_images/image2023-6-15_8-43-7.png b/site/_images/image2023-6-15_8-43-7.png deleted file mode 100644 index c479c01..0000000 Binary files a/site/_images/image2023-6-15_8-43-7.png and /dev/null differ diff --git a/site/_images/image2023-6-1_17-6-3.png b/site/_images/image2023-6-1_17-6-3.png deleted file mode 100644 index cb4d712..0000000 Binary files a/site/_images/image2023-6-1_17-6-3.png and /dev/null differ diff --git a/site/_images/image2023-6-1_17-8-5.png b/site/_images/image2023-6-1_17-8-5.png deleted file mode 100644 index 1073001..0000000 Binary files a/site/_images/image2023-6-1_17-8-5.png and /dev/null differ diff --git a/site/_images/image2023-6-26_11-27-0.png b/site/_images/image2023-6-26_11-27-0.png deleted file mode 100644 index cd3da9f..0000000 Binary files a/site/_images/image2023-6-26_11-27-0.png and /dev/null differ diff --git a/site/_images/image2023-6-26_11-54-29.png b/site/_images/image2023-6-26_11-54-29.png deleted file mode 100644 index 20d1e24..0000000 Binary files a/site/_images/image2023-6-26_11-54-29.png and /dev/null differ diff --git a/site/_images/image2023-6-26_12-0-35.png b/site/_images/image2023-6-26_12-0-35.png deleted file mode 100644 index f102086..0000000 Binary files a/site/_images/image2023-6-26_12-0-35.png and /dev/null differ diff --git a/site/_images/image2023-6-26_12-36-24.png b/site/_images/image2023-6-26_12-36-24.png deleted file mode 100644 index 2c81eb2..0000000 Binary files a/site/_images/image2023-6-26_12-36-24.png and /dev/null differ diff --git a/site/_images/image2023-6-26_12-42-24.png b/site/_images/image2023-6-26_12-42-24.png deleted file mode 100644 index 6685c0a..0000000 Binary files a/site/_images/image2023-6-26_12-42-24.png and /dev/null differ diff --git a/site/_images/image2023-7-20_11-58-22.png b/site/_images/image2023-7-20_11-58-22.png deleted file mode 100644 index 578b33a..0000000 Binary files a/site/_images/image2023-7-20_11-58-22.png and /dev/null differ diff --git a/site/_images/image2023-8-2_16-11-43.png b/site/_images/image2023-8-2_16-11-43.png deleted file mode 100644 index e541fb5..0000000 Binary files a/site/_images/image2023-8-2_16-11-43.png and /dev/null differ diff --git a/site/_images/image2023-8-2_16-36-11.png b/site/_images/image2023-8-2_16-36-11.png deleted file mode 100644 index 50a74dc..0000000 Binary files a/site/_images/image2023-8-2_16-36-11.png and /dev/null differ diff --git a/site/_images/image2023-8-2_16-44-28.png b/site/_images/image2023-8-2_16-44-28.png deleted file mode 100644 index 8897a6b..0000000 Binary files a/site/_images/image2023-8-2_16-44-28.png and /dev/null differ diff --git a/site/_images/image2023-8-2_16-7-51.png b/site/_images/image2023-8-2_16-7-51.png deleted file mode 100644 index 7d5865e..0000000 Binary files a/site/_images/image2023-8-2_16-7-51.png and /dev/null differ diff --git a/site/_images/image2023-8-3_14-41-56.png b/site/_images/image2023-8-3_14-41-56.png deleted file mode 100644 index 425efb7..0000000 Binary files a/site/_images/image2023-8-3_14-41-56.png and /dev/null differ diff --git a/site/_images/image2023-8-3_15-11-48.png b/site/_images/image2023-8-3_15-11-48.png deleted file mode 100644 index ee4d963..0000000 Binary files a/site/_images/image2023-8-3_15-11-48.png and /dev/null differ diff --git a/site/_images/image2023-8-8_14-2-4.png b/site/_images/image2023-8-8_14-2-4.png deleted file mode 100644 index 0254a2b..0000000 Binary files a/site/_images/image2023-8-8_14-2-4.png and /dev/null differ diff --git a/site/_images/image2023-8-8_14-4-40.png b/site/_images/image2023-8-8_14-4-40.png deleted file mode 100644 index f0d06ac..0000000 Binary files a/site/_images/image2023-8-8_14-4-40.png and /dev/null differ diff --git a/site/_images/image_options_explanation.png b/site/_images/image_options_explanation.png deleted file mode 100644 index 7bc8374..0000000 Binary files a/site/_images/image_options_explanation.png and /dev/null differ diff --git a/site/_images/importdashboard.png b/site/_images/importdashboard.png deleted file mode 100644 index 77e0bf7..0000000 Binary files a/site/_images/importdashboard.png and /dev/null differ diff --git a/site/_images/install-cron-1.png b/site/_images/install-cron-1.png deleted file mode 100644 index 4df7f88..0000000 Binary files a/site/_images/install-cron-1.png and /dev/null differ diff --git a/site/_images/install-cron-2.png b/site/_images/install-cron-2.png deleted file mode 100644 index 2e748b1..0000000 Binary files a/site/_images/install-cron-2.png and /dev/null differ diff --git a/site/_images/install-cron-mulitple-1.png b/site/_images/install-cron-mulitple-1.png deleted file mode 100644 index 058c642..0000000 Binary files a/site/_images/install-cron-mulitple-1.png and /dev/null differ diff --git a/site/_images/install-s3cmd-linux-01_creodias.png b/site/_images/install-s3cmd-linux-01_creodias.png deleted file mode 100644 index e6251ac..0000000 Binary files a/site/_images/install-s3cmd-linux-01_creodias.png and /dev/null differ diff --git a/site/_images/install-s3cmd-linux-02_creodias.png b/site/_images/install-s3cmd-linux-02_creodias.png deleted file mode 100644 index 866a0d9..0000000 Binary files a/site/_images/install-s3cmd-linux-02_creodias.png and /dev/null differ diff --git a/site/_images/install_new_pip.png b/site/_images/install_new_pip.png deleted file mode 100644 index 49e34a2..0000000 Binary files a/site/_images/install_new_pip.png and /dev/null differ diff --git a/site/_images/install_noobaa_locally.png b/site/_images/install_noobaa_locally.png deleted file mode 100644 index 9a243b8..0000000 Binary files a/site/_images/install_noobaa_locally.png and /dev/null differ diff --git a/site/_images/installation_done.png b/site/_images/installation_done.png deleted file mode 100644 index 8cb081d..0000000 Binary files a/site/_images/installation_done.png and /dev/null differ diff --git a/site/_images/installation_of_velero.png b/site/_images/installation_of_velero.png deleted file mode 100644 index a2ea8b8..0000000 Binary files a/site/_images/installation_of_velero.png and /dev/null differ diff --git a/site/_images/installed_mybackup2.png b/site/_images/installed_mybackup2.png deleted file mode 100644 index ecbae6b..0000000 Binary files a/site/_images/installed_mybackup2.png and /dev/null differ diff --git a/site/_images/instance.png b/site/_images/instance.png deleted file mode 100644 index c05eff9..0000000 Binary files a/site/_images/instance.png and /dev/null differ diff --git a/site/_images/instance_blue_green.png b/site/_images/instance_blue_green.png deleted file mode 100644 index d1cd996..0000000 Binary files a/site/_images/instance_blue_green.png and /dev/null differ diff --git a/site/_images/instance_ephemeral_create_snapshot.png b/site/_images/instance_ephemeral_create_snapshot.png deleted file mode 100644 index 0fbc2ba..0000000 Binary files a/site/_images/instance_ephemeral_create_snapshot.png and /dev/null differ diff --git a/site/_images/instance_ephemeral_shut_off.png b/site/_images/instance_ephemeral_shut_off.png deleted file mode 100644 index b4847fb..0000000 Binary files a/site/_images/instance_ephemeral_shut_off.png and /dev/null differ diff --git a/site/_images/instance_ephemeral_snapshot.png b/site/_images/instance_ephemeral_snapshot.png deleted file mode 100644 index e2b017c..0000000 Binary files a/site/_images/instance_ephemeral_snapshot.png and /dev/null differ diff --git a/site/_images/instance_persistent_active_0bytes.png b/site/_images/instance_persistent_active_0bytes.png deleted file mode 100644 index 7f98bfa..0000000 Binary files a/site/_images/instance_persistent_active_0bytes.png and /dev/null differ diff --git a/site/_images/instance_persistent_create_shanpshot_button.png b/site/_images/instance_persistent_create_shanpshot_button.png deleted file mode 100644 index aacb1d0..0000000 Binary files a/site/_images/instance_persistent_create_shanpshot_button.png and /dev/null differ diff --git a/site/_images/instance_persistent_created.png b/site/_images/instance_persistent_created.png deleted file mode 100644 index 688d9b6..0000000 Binary files a/site/_images/instance_persistent_created.png and /dev/null differ diff --git a/site/_images/instance_persistent_new_name.png b/site/_images/instance_persistent_new_name.png deleted file mode 100644 index 923959a..0000000 Binary files a/site/_images/instance_persistent_new_name.png and /dev/null differ diff --git a/site/_images/instance_persistent_show_data.png b/site/_images/instance_persistent_show_data.png deleted file mode 100644 index 0855030..0000000 Binary files a/site/_images/instance_persistent_show_data.png and /dev/null differ diff --git a/site/_images/instance_persistent_shut_down_indees.png b/site/_images/instance_persistent_shut_down_indees.png deleted file mode 100644 index 400a4c5..0000000 Binary files a/site/_images/instance_persistent_shut_down_indees.png and /dev/null differ diff --git a/site/_images/instance_persistent_volume_shapshot.png b/site/_images/instance_persistent_volume_shapshot.png deleted file mode 100644 index b7d5740..0000000 Binary files a/site/_images/instance_persistent_volume_shapshot.png and /dev/null differ diff --git a/site/_images/instance_persistent_volumes_volumes.png b/site/_images/instance_persistent_volumes_volumes.png deleted file mode 100644 index 11197f8..0000000 Binary files a/site/_images/instance_persistent_volumes_volumes.png and /dev/null differ diff --git a/site/_images/instances.png b/site/_images/instances.png deleted file mode 100644 index 76578ab..0000000 Binary files a/site/_images/instances.png and /dev/null differ diff --git a/site/_images/inv_01_3Enginescloud.png b/site/_images/inv_01_3Enginescloud.png deleted file mode 100644 index 025f90d..0000000 Binary files a/site/_images/inv_01_3Enginescloud.png and /dev/null differ diff --git a/site/_images/inv_02_3Enginescloud.png b/site/_images/inv_02_3Enginescloud.png deleted file mode 100644 index 83e2bdc..0000000 Binary files a/site/_images/inv_02_3Enginescloud.png and /dev/null differ diff --git a/site/_images/ip_address_from_article.png b/site/_images/ip_address_from_article.png deleted file mode 100644 index 8c9624d..0000000 Binary files a/site/_images/ip_address_from_article.png and /dev/null differ diff --git a/site/_images/jq_error.png b/site/_images/jq_error.png deleted file mode 100644 index 6ebf2e2..0000000 Binary files a/site/_images/jq_error.png and /dev/null differ diff --git a/site/_images/keepassxc_01_creodias.png b/site/_images/keepassxc_01_creodias.png deleted file mode 100644 index d087a48..0000000 Binary files a/site/_images/keepassxc_01_creodias.png and /dev/null differ diff --git a/site/_images/keepassxc_02_creodias.png b/site/_images/keepassxc_02_creodias.png deleted file mode 100644 index 483921d..0000000 Binary files a/site/_images/keepassxc_02_creodias.png and /dev/null differ diff --git a/site/_images/keepassxc_03_creodias.png b/site/_images/keepassxc_03_creodias.png deleted file mode 100644 index 725c644..0000000 Binary files a/site/_images/keepassxc_03_creodias.png and /dev/null differ diff --git a/site/_images/keepassxc_04_creodias.png b/site/_images/keepassxc_04_creodias.png deleted file mode 100644 index 9e999f4..0000000 Binary files a/site/_images/keepassxc_04_creodias.png and /dev/null differ diff --git a/site/_images/keepassxc_05_creodias.png b/site/_images/keepassxc_05_creodias.png deleted file mode 100644 index b9e5358..0000000 Binary files a/site/_images/keepassxc_05_creodias.png and /dev/null differ diff --git a/site/_images/keepassxc_06_creodias.png b/site/_images/keepassxc_06_creodias.png deleted file mode 100644 index 05442ce..0000000 Binary files a/site/_images/keepassxc_06_creodias.png and /dev/null differ diff --git a/site/_images/keepassxc_07_creodias.png b/site/_images/keepassxc_07_creodias.png deleted file mode 100644 index 507252e..0000000 Binary files a/site/_images/keepassxc_07_creodias.png and /dev/null differ diff --git a/site/_images/keepassxc_08_creodias.png b/site/_images/keepassxc_08_creodias.png deleted file mode 100644 index 6231c7f..0000000 Binary files a/site/_images/keepassxc_08_creodias.png and /dev/null differ diff --git a/site/_images/keepassxc_09_creodias.png b/site/_images/keepassxc_09_creodias.png deleted file mode 100644 index dcfa2db..0000000 Binary files a/site/_images/keepassxc_09_creodias.png and /dev/null differ diff --git a/site/_images/keepassxc_10_creodias.png b/site/_images/keepassxc_10_creodias.png deleted file mode 100644 index e8c6c2b..0000000 Binary files a/site/_images/keepassxc_10_creodias.png and /dev/null differ diff --git a/site/_images/keepassxc_11_creodias.png b/site/_images/keepassxc_11_creodias.png deleted file mode 100644 index 89de0de..0000000 Binary files a/site/_images/keepassxc_11_creodias.png and /dev/null differ diff --git a/site/_images/key-location-putty.png b/site/_images/key-location-putty.png deleted file mode 100644 index 3655722..0000000 Binary files a/site/_images/key-location-putty.png and /dev/null differ diff --git a/site/_images/keycloack_full_screen.png b/site/_images/keycloack_full_screen.png deleted file mode 100644 index b774125..0000000 Binary files a/site/_images/keycloack_full_screen.png and /dev/null differ diff --git a/site/_images/keypair1.png b/site/_images/keypair1.png deleted file mode 100644 index ce215a0..0000000 Binary files a/site/_images/keypair1.png and /dev/null differ diff --git a/site/_images/keypair2.png b/site/_images/keypair2.png deleted file mode 100644 index bd11136..0000000 Binary files a/site/_images/keypair2.png and /dev/null differ diff --git a/site/_images/keypair3.png b/site/_images/keypair3.png deleted file mode 100644 index d496bba..0000000 Binary files a/site/_images/keypair3.png and /dev/null differ diff --git a/site/_images/keypair4.png b/site/_images/keypair4.png deleted file mode 100644 index 8b8d517..0000000 Binary files a/site/_images/keypair4.png and /dev/null differ diff --git a/site/_images/keypair5.png b/site/_images/keypair5.png deleted file mode 100644 index 6e34679..0000000 Binary files a/site/_images/keypair5.png and /dev/null differ diff --git a/site/_images/ku_3Engines_line_entry.png b/site/_images/ku_3Engines_line_entry.png deleted file mode 100644 index c0d98a6..0000000 Binary files a/site/_images/ku_3Engines_line_entry.png and /dev/null differ diff --git a/site/_images/ku_blanks.png b/site/_images/ku_blanks.png deleted file mode 100644 index 33bb567..0000000 Binary files a/site/_images/ku_blanks.png and /dev/null differ diff --git a/site/_images/ku_blanks_ok.png b/site/_images/ku_blanks_ok.png deleted file mode 100644 index 5297ce1..0000000 Binary files a/site/_images/ku_blanks_ok.png and /dev/null differ diff --git a/site/_images/ku_labels_broken.png b/site/_images/ku_labels_broken.png deleted file mode 100644 index ef014ef..0000000 Binary files a/site/_images/ku_labels_broken.png and /dev/null differ diff --git a/site/_images/ku_long_line.png b/site/_images/ku_long_line.png deleted file mode 100644 index cc798e9..0000000 Binary files a/site/_images/ku_long_line.png and /dev/null differ diff --git a/site/_images/ku_no_blanks.png b/site/_images/ku_no_blanks.png deleted file mode 100644 index 895950d..0000000 Binary files a/site/_images/ku_no_blanks.png and /dev/null differ diff --git a/site/_images/kubectl_get_node.png b/site/_images/kubectl_get_node.png deleted file mode 100644 index 0c3a7af..0000000 Binary files a/site/_images/kubectl_get_node.png and /dev/null differ diff --git a/site/_images/kubectl_help.png b/site/_images/kubectl_help.png deleted file mode 100644 index f12dc90..0000000 Binary files a/site/_images/kubectl_help.png and /dev/null differ diff --git a/site/_images/kubectl_show_5_workers.png b/site/_images/kubectl_show_5_workers.png deleted file mode 100644 index 2358630..0000000 Binary files a/site/_images/kubectl_show_5_workers.png and /dev/null differ diff --git a/site/_images/kubectl_without_access.png b/site/_images/kubectl_without_access.png deleted file mode 100644 index 8c306a7..0000000 Binary files a/site/_images/kubectl_without_access.png and /dev/null differ diff --git a/site/_images/kubectl_working.png b/site/_images/kubectl_working.png deleted file mode 100644 index cd6965a..0000000 Binary files a/site/_images/kubectl_working.png and /dev/null differ diff --git a/site/_images/kubernetes_url.png b/site/_images/kubernetes_url.png deleted file mode 100644 index 74cb59f..0000000 Binary files a/site/_images/kubernetes_url.png and /dev/null differ diff --git a/site/_images/labels.png b/site/_images/labels.png deleted file mode 100644 index 89da2eb..0000000 Binary files a/site/_images/labels.png and /dev/null differ diff --git a/site/_images/launch_instance.png b/site/_images/launch_instance.png deleted file mode 100644 index c18545d..0000000 Binary files a/site/_images/launch_instance.png and /dev/null differ diff --git a/site/_images/launch_instance_created_instances.png b/site/_images/launch_instance_created_instances.png deleted file mode 100644 index 6a38338..0000000 Binary files a/site/_images/launch_instance_created_instances.png and /dev/null differ diff --git a/site/_images/launch_instance_details.png b/site/_images/launch_instance_details.png deleted file mode 100644 index 3fe98a9..0000000 Binary files a/site/_images/launch_instance_details.png and /dev/null differ diff --git a/site/_images/launch_instance_flavor.png b/site/_images/launch_instance_flavor.png deleted file mode 100644 index ef5b25e..0000000 Binary files a/site/_images/launch_instance_flavor.png and /dev/null differ diff --git a/site/_images/launch_instance_key_pair.png b/site/_images/launch_instance_key_pair.png deleted file mode 100644 index 11c1938..0000000 Binary files a/site/_images/launch_instance_key_pair.png and /dev/null differ diff --git a/site/_images/launch_instance_launch_instance.png b/site/_images/launch_instance_launch_instance.png deleted file mode 100644 index e62c1ec..0000000 Binary files a/site/_images/launch_instance_launch_instance.png and /dev/null differ diff --git a/site/_images/launch_instance_networks.png b/site/_images/launch_instance_networks.png deleted file mode 100644 index 6953171..0000000 Binary files a/site/_images/launch_instance_networks.png and /dev/null differ diff --git a/site/_images/launch_instance_security_groups.png b/site/_images/launch_instance_security_groups.png deleted file mode 100644 index 433faab..0000000 Binary files a/site/_images/launch_instance_security_groups.png and /dev/null differ diff --git a/site/_images/launch_instance_source.png b/site/_images/launch_instance_source.png deleted file mode 100644 index 7b5197f..0000000 Binary files a/site/_images/launch_instance_source.png and /dev/null differ diff --git a/site/_images/launch_stack.png b/site/_images/launch_stack.png deleted file mode 100644 index 6eb55d7..0000000 Binary files a/site/_images/launch_stack.png and /dev/null differ diff --git a/site/_images/linux-gui-03_creodias.png b/site/_images/linux-gui-03_creodias.png deleted file mode 100644 index 017f89e..0000000 Binary files a/site/_images/linux-gui-03_creodias.png and /dev/null differ diff --git a/site/_images/linux-gui-04_creodias.png b/site/_images/linux-gui-04_creodias.png deleted file mode 100644 index b62d99f..0000000 Binary files a/site/_images/linux-gui-04_creodias.png and /dev/null differ diff --git a/site/_images/linux-gui-05_creodias.png b/site/_images/linux-gui-05_creodias.png deleted file mode 100644 index 1b65527..0000000 Binary files a/site/_images/linux-gui-05_creodias.png and /dev/null differ diff --git a/site/_images/linux-gui-06_creodias.png b/site/_images/linux-gui-06_creodias.png deleted file mode 100644 index a7c5d86..0000000 Binary files a/site/_images/linux-gui-06_creodias.png and /dev/null differ diff --git a/site/_images/linux-gui-07_creodias.png b/site/_images/linux-gui-07_creodias.png deleted file mode 100644 index bd8cbfc..0000000 Binary files a/site/_images/linux-gui-07_creodias.png and /dev/null differ diff --git a/site/_images/linux-gui-08_creodias.png b/site/_images/linux-gui-08_creodias.png deleted file mode 100644 index 71c1d62..0000000 Binary files a/site/_images/linux-gui-08_creodias.png and /dev/null differ diff --git a/site/_images/linux-gui-09_creodias.png b/site/_images/linux-gui-09_creodias.png deleted file mode 100644 index 520a061..0000000 Binary files a/site/_images/linux-gui-09_creodias.png and /dev/null differ diff --git a/site/_images/linux-gui-11_creodias.png b/site/_images/linux-gui-11_creodias.png deleted file mode 100644 index 4076c27..0000000 Binary files a/site/_images/linux-gui-11_creodias.png and /dev/null differ diff --git a/site/_images/linux-gui-12_creodias.png b/site/_images/linux-gui-12_creodias.png deleted file mode 100644 index 4463f6a..0000000 Binary files a/site/_images/linux-gui-12_creodias.png and /dev/null differ diff --git a/site/_images/linux-gui-13_creodias.png b/site/_images/linux-gui-13_creodias.png deleted file mode 100644 index 5b3bc09..0000000 Binary files a/site/_images/linux-gui-13_creodias.png and /dev/null differ diff --git a/site/_images/linux-gui-14_creodias.png b/site/_images/linux-gui-14_creodias.png deleted file mode 100644 index 8c9000c..0000000 Binary files a/site/_images/linux-gui-14_creodias.png and /dev/null differ diff --git a/site/_images/linux-gui-15_creodias.png b/site/_images/linux-gui-15_creodias.png deleted file mode 100644 index 4d80e9e..0000000 Binary files a/site/_images/linux-gui-15_creodias.png and /dev/null differ diff --git a/site/_images/linux-gui-16_creodias.png b/site/_images/linux-gui-16_creodias.png deleted file mode 100644 index 7f85b9e..0000000 Binary files a/site/_images/linux-gui-16_creodias.png and /dev/null differ diff --git a/site/_images/linux-gui-17_creodias.png b/site/_images/linux-gui-17_creodias.png deleted file mode 100644 index 47089ae..0000000 Binary files a/site/_images/linux-gui-17_creodias.png and /dev/null differ diff --git a/site/_images/listing_nodegroups.png b/site/_images/listing_nodegroups.png deleted file mode 100644 index d7955c8..0000000 Binary files a/site/_images/listing_nodegroups.png and /dev/null differ diff --git a/site/_images/locust_test.png b/site/_images/locust_test.png deleted file mode 100644 index 4ff31ca..0000000 Binary files a/site/_images/locust_test.png and /dev/null differ diff --git a/site/_images/login_3Enginescloud.png b/site/_images/login_3Enginescloud.png deleted file mode 100644 index fac10f1..0000000 Binary files a/site/_images/login_3Enginescloud.png and /dev/null differ diff --git a/site/_images/manage-totp-01_creodias.png b/site/_images/manage-totp-01_creodias.png deleted file mode 100644 index 515d92d..0000000 Binary files a/site/_images/manage-totp-01_creodias.png and /dev/null differ diff --git a/site/_images/manage-totp-02_creodias.png b/site/_images/manage-totp-02_creodias.png deleted file mode 100644 index 369eec0..0000000 Binary files a/site/_images/manage-totp-02_creodias.png and /dev/null differ diff --git a/site/_images/manage-totp-03_creodias.png b/site/_images/manage-totp-03_creodias.png deleted file mode 100644 index 952e916..0000000 Binary files a/site/_images/manage-totp-03_creodias.png and /dev/null differ diff --git a/site/_images/manage-totp-04_creodias.png b/site/_images/manage-totp-04_creodias.png deleted file mode 100644 index 0748ebe..0000000 Binary files a/site/_images/manage-totp-04_creodias.png and /dev/null differ diff --git a/site/_images/manage-totp-05_3Enginescloud.png b/site/_images/manage-totp-05_3Enginescloud.png deleted file mode 100644 index c94fd0b..0000000 Binary files a/site/_images/manage-totp-05_3Enginescloud.png and /dev/null differ diff --git a/site/_images/management.png b/site/_images/management.png deleted file mode 100644 index 4ccb216..0000000 Binary files a/site/_images/management.png and /dev/null differ diff --git a/site/_images/master_node_addresses.png b/site/_images/master_node_addresses.png deleted file mode 100644 index a5481b4..0000000 Binary files a/site/_images/master_node_addresses.png and /dev/null differ diff --git a/site/_images/mount-eodata-windows-open-03_creodias.png b/site/_images/mount-eodata-windows-open-03_creodias.png deleted file mode 100644 index 664a0c3..0000000 Binary files a/site/_images/mount-eodata-windows-open-03_creodias.png and /dev/null differ diff --git a/site/_images/mount-eodata-windows-open-04_creodias.png b/site/_images/mount-eodata-windows-open-04_creodias.png deleted file mode 100644 index c77b904..0000000 Binary files a/site/_images/mount-eodata-windows-open-04_creodias.png and /dev/null differ diff --git a/site/_images/mount-eodata-windows-open-05_creodias.png b/site/_images/mount-eodata-windows-open-05_creodias.png deleted file mode 100644 index a6d6903..0000000 Binary files a/site/_images/mount-eodata-windows-open-05_creodias.png and /dev/null differ diff --git a/site/_images/mount-eodata-windows-open-06_creodias.png b/site/_images/mount-eodata-windows-open-06_creodias.png deleted file mode 100644 index 8590e59..0000000 Binary files a/site/_images/mount-eodata-windows-open-06_creodias.png and /dev/null differ diff --git a/site/_images/mount-eodata-windows-open-07_creodias.png b/site/_images/mount-eodata-windows-open-07_creodias.png deleted file mode 100644 index 2b35cbb..0000000 Binary files a/site/_images/mount-eodata-windows-open-07_creodias.png and /dev/null differ diff --git a/site/_images/mount-eodata-windows-open-10_creodias.png b/site/_images/mount-eodata-windows-open-10_creodias.png deleted file mode 100644 index eea5406..0000000 Binary files a/site/_images/mount-eodata-windows-open-10_creodias.png and /dev/null differ diff --git a/site/_images/mount-eodata-windows-open-11_creodias.png b/site/_images/mount-eodata-windows-open-11_creodias.png deleted file mode 100644 index fd8e970..0000000 Binary files a/site/_images/mount-eodata-windows-open-11_creodias.png and /dev/null differ diff --git a/site/_images/mount-eodata-windows-open-12_creodias.png b/site/_images/mount-eodata-windows-open-12_creodias.png deleted file mode 100644 index 18022ec..0000000 Binary files a/site/_images/mount-eodata-windows-open-12_creodias.png and /dev/null differ diff --git a/site/_images/mount-eodata-windows-open-13_creodias.png b/site/_images/mount-eodata-windows-open-13_creodias.png deleted file mode 100644 index dac4ffd..0000000 Binary files a/site/_images/mount-eodata-windows-open-13_creodias.png and /dev/null differ diff --git a/site/_images/mount-eodata-windows-open-nssm-01_creodias.png b/site/_images/mount-eodata-windows-open-nssm-01_creodias.png deleted file mode 100644 index a43bb1d..0000000 Binary files a/site/_images/mount-eodata-windows-open-nssm-01_creodias.png and /dev/null differ diff --git a/site/_images/mount-eodata-windows-open-remove-01_creodias.png b/site/_images/mount-eodata-windows-open-remove-01_creodias.png deleted file mode 100644 index b0157d7..0000000 Binary files a/site/_images/mount-eodata-windows-open-remove-01_creodias.png and /dev/null differ diff --git a/site/_images/mount-eodata-windows-open-remove-03_creodias.png b/site/_images/mount-eodata-windows-open-remove-03_creodias.png deleted file mode 100644 index 35f2b7d..0000000 Binary files a/site/_images/mount-eodata-windows-open-remove-03_creodias.png and /dev/null differ diff --git a/site/_images/mount-eodata-windows-open-remove-04_creodias.png b/site/_images/mount-eodata-windows-open-remove-04_creodias.png deleted file mode 100644 index 22e3658..0000000 Binary files a/site/_images/mount-eodata-windows-open-remove-04_creodias.png and /dev/null differ diff --git a/site/_images/mount-eodata-windows-open-remove-05_creodias.png b/site/_images/mount-eodata-windows-open-remove-05_creodias.png deleted file mode 100644 index 0c72467..0000000 Binary files a/site/_images/mount-eodata-windows-open-remove-05_creodias.png and /dev/null differ diff --git a/site/_images/mount-eodata-windows-open-remove-06_creodias.png b/site/_images/mount-eodata-windows-open-remove-06_creodias.png deleted file mode 100644 index ad1023a..0000000 Binary files a/site/_images/mount-eodata-windows-open-remove-06_creodias.png and /dev/null differ diff --git a/site/_images/mount-eodata-windows-open-remove-07_creodias.png b/site/_images/mount-eodata-windows-open-remove-07_creodias.png deleted file mode 100644 index 75e01e4..0000000 Binary files a/site/_images/mount-eodata-windows-open-remove-07_creodias.png and /dev/null differ diff --git a/site/_images/mount-eodata-windows-open-remove-08_creodias.png b/site/_images/mount-eodata-windows-open-remove-08_creodias.png deleted file mode 100644 index 4c65039..0000000 Binary files a/site/_images/mount-eodata-windows-open-remove-08_creodias.png and /dev/null differ diff --git a/site/_images/mount-eodata-windows-rclone-01_creodias.png b/site/_images/mount-eodata-windows-rclone-01_creodias.png deleted file mode 100644 index 7813cde..0000000 Binary files a/site/_images/mount-eodata-windows-rclone-01_creodias.png and /dev/null differ diff --git a/site/_images/mount-eodata-windows-rclone-02_creodias.png b/site/_images/mount-eodata-windows-rclone-02_creodias.png deleted file mode 100644 index fea2d7a..0000000 Binary files a/site/_images/mount-eodata-windows-rclone-02_creodias.png and /dev/null differ diff --git a/site/_images/mount-object-storage-s3fs-linux-03_creodias.png b/site/_images/mount-object-storage-s3fs-linux-03_creodias.png deleted file mode 100644 index 9e37bf8..0000000 Binary files a/site/_images/mount-object-storage-s3fs-linux-03_creodias.png and /dev/null differ diff --git a/site/_images/mount-object-storage-s3fs-linux-04_creodias.png b/site/_images/mount-object-storage-s3fs-linux-04_creodias.png deleted file mode 100644 index 7c88fa9..0000000 Binary files a/site/_images/mount-object-storage-s3fs-linux-04_creodias.png and /dev/null differ diff --git a/site/_images/mount-object-storage-s3fs-linux-05_creodias.png b/site/_images/mount-object-storage-s3fs-linux-05_creodias.png deleted file mode 100644 index 3e5c1fd..0000000 Binary files a/site/_images/mount-object-storage-s3fs-linux-05_creodias.png and /dev/null differ diff --git a/site/_images/mount-object-storage-s3fs-linux-06_creodias.png b/site/_images/mount-object-storage-s3fs-linux-06_creodias.png deleted file mode 100644 index 4b309e2..0000000 Binary files a/site/_images/mount-object-storage-s3fs-linux-06_creodias.png and /dev/null differ diff --git a/site/_images/mount-object-storage-windows-horizon-01_creodias.png b/site/_images/mount-object-storage-windows-horizon-01_creodias.png deleted file mode 100644 index af0a35f..0000000 Binary files a/site/_images/mount-object-storage-windows-horizon-01_creodias.png and /dev/null differ diff --git a/site/_images/nano_redis_yaml.png b/site/_images/nano_redis_yaml.png deleted file mode 100644 index e79c91a..0000000 Binary files a/site/_images/nano_redis_yaml.png and /dev/null differ diff --git a/site/_images/nano_values.png b/site/_images/nano_values.png deleted file mode 100644 index 9661207..0000000 Binary files a/site/_images/nano_values.png and /dev/null differ diff --git a/site/_images/net1.png b/site/_images/net1.png deleted file mode 100644 index 8510fc1..0000000 Binary files a/site/_images/net1.png and /dev/null differ diff --git a/site/_images/net10.png b/site/_images/net10.png deleted file mode 100644 index b306b44..0000000 Binary files a/site/_images/net10.png and /dev/null differ diff --git a/site/_images/net11.png b/site/_images/net11.png deleted file mode 100644 index cf355ac..0000000 Binary files a/site/_images/net11.png and /dev/null differ diff --git a/site/_images/net12.png b/site/_images/net12.png deleted file mode 100644 index fc00c00..0000000 Binary files a/site/_images/net12.png and /dev/null differ diff --git a/site/_images/net13.png b/site/_images/net13.png deleted file mode 100644 index ea58402..0000000 Binary files a/site/_images/net13.png and /dev/null differ diff --git a/site/_images/net2.png b/site/_images/net2.png deleted file mode 100644 index 8842249..0000000 Binary files a/site/_images/net2.png and /dev/null differ diff --git a/site/_images/net3.png b/site/_images/net3.png deleted file mode 100644 index d6c809e..0000000 Binary files a/site/_images/net3.png and /dev/null differ diff --git a/site/_images/net4.png b/site/_images/net4.png deleted file mode 100644 index d3942b5..0000000 Binary files a/site/_images/net4.png and /dev/null differ diff --git a/site/_images/net5.png b/site/_images/net5.png deleted file mode 100644 index 27cd944..0000000 Binary files a/site/_images/net5.png and /dev/null differ diff --git a/site/_images/net6.png b/site/_images/net6.png deleted file mode 100644 index 3b35540..0000000 Binary files a/site/_images/net6.png and /dev/null differ diff --git a/site/_images/net7.png b/site/_images/net7.png deleted file mode 100644 index ac82630..0000000 Binary files a/site/_images/net7.png and /dev/null differ diff --git a/site/_images/net8.png b/site/_images/net8.png deleted file mode 100644 index e0fba30..0000000 Binary files a/site/_images/net8.png and /dev/null differ diff --git a/site/_images/net9.png b/site/_images/net9.png deleted file mode 100644 index 12d990a..0000000 Binary files a/site/_images/net9.png and /dev/null differ diff --git a/site/_images/network_list.png b/site/_images/network_list.png deleted file mode 100644 index 8e264e9..0000000 Binary files a/site/_images/network_list.png and /dev/null differ diff --git a/site/_images/network_option.png b/site/_images/network_option.png deleted file mode 100644 index d4c03b1..0000000 Binary files a/site/_images/network_option.png and /dev/null differ diff --git a/site/_images/network_topology_with_labels.png b/site/_images/network_topology_with_labels.png deleted file mode 100644 index 1856baf..0000000 Binary files a/site/_images/network_topology_with_labels.png and /dev/null differ diff --git a/site/_images/networks5.png b/site/_images/networks5.png deleted file mode 100644 index ecb7064..0000000 Binary files a/site/_images/networks5.png and /dev/null differ diff --git a/site/_images/networks_list.png b/site/_images/networks_list.png deleted file mode 100644 index 72a85ee..0000000 Binary files a/site/_images/networks_list.png and /dev/null differ diff --git a/site/_images/new-s3cmd-download-69.png b/site/_images/new-s3cmd-download-69.png deleted file mode 100644 index 2bc9866..0000000 Binary files a/site/_images/new-s3cmd-download-69.png and /dev/null differ diff --git a/site/_images/new_access_token.png b/site/_images/new_access_token.png deleted file mode 100644 index e0659ca..0000000 Binary files a/site/_images/new_access_token.png and /dev/null differ diff --git a/site/_images/new_docker-1.png b/site/_images/new_docker-1.png deleted file mode 100644 index eb92fd4..0000000 Binary files a/site/_images/new_docker-1.png and /dev/null differ diff --git a/site/_images/new_docker-1.png.html b/site/_images/new_docker-1.png.html deleted file mode 100644 index 9b4931e..0000000 --- a/site/_images/new_docker-1.png.html +++ /dev/null @@ -1,12 +0,0 @@ - New docker 1.png - 3Engines Documentation

New docker 1.png

None

\ No newline at end of file diff --git a/site/_images/new_instances2.png b/site/_images/new_instances2.png deleted file mode 100644 index 1f1ea1a..0000000 Binary files a/site/_images/new_instances2.png and /dev/null differ diff --git a/site/_images/new_project.png b/site/_images/new_project.png deleted file mode 100644 index 1b262c1..0000000 Binary files a/site/_images/new_project.png and /dev/null differ diff --git a/site/_images/newvm1.png b/site/_images/newvm1.png deleted file mode 100644 index 617e854..0000000 Binary files a/site/_images/newvm1.png and /dev/null differ diff --git a/site/_images/newvm10.png b/site/_images/newvm10.png deleted file mode 100644 index 6141975..0000000 Binary files a/site/_images/newvm10.png and /dev/null differ diff --git a/site/_images/newvm11.png b/site/_images/newvm11.png deleted file mode 100644 index 0cc36de..0000000 Binary files a/site/_images/newvm11.png and /dev/null differ diff --git a/site/_images/newvm12.png b/site/_images/newvm12.png deleted file mode 100644 index 372d82b..0000000 Binary files a/site/_images/newvm12.png and /dev/null differ diff --git a/site/_images/newvm13.png b/site/_images/newvm13.png deleted file mode 100644 index ac11e96..0000000 Binary files a/site/_images/newvm13.png and /dev/null differ diff --git a/site/_images/newvm2.png b/site/_images/newvm2.png deleted file mode 100644 index 844dc13..0000000 Binary files a/site/_images/newvm2.png and /dev/null differ diff --git a/site/_images/newvm3.png b/site/_images/newvm3.png deleted file mode 100644 index 00f1245..0000000 Binary files a/site/_images/newvm3.png and /dev/null differ diff --git a/site/_images/newvm4.png b/site/_images/newvm4.png deleted file mode 100644 index efb42f0..0000000 Binary files a/site/_images/newvm4.png and /dev/null differ diff --git a/site/_images/newvm5.png b/site/_images/newvm5.png deleted file mode 100644 index cdcd817..0000000 Binary files a/site/_images/newvm5.png and /dev/null differ diff --git a/site/_images/newvm6.png b/site/_images/newvm6.png deleted file mode 100644 index 1956266..0000000 Binary files a/site/_images/newvm6.png and /dev/null differ diff --git a/site/_images/newvm7.png b/site/_images/newvm7.png deleted file mode 100644 index 07a8699..0000000 Binary files a/site/_images/newvm7.png and /dev/null differ diff --git a/site/_images/newvm8.png b/site/_images/newvm8.png deleted file mode 100644 index 8e57f0d..0000000 Binary files a/site/_images/newvm8.png and /dev/null differ diff --git a/site/_images/newvm9.png b/site/_images/newvm9.png deleted file mode 100644 index da05770..0000000 Binary files a/site/_images/newvm9.png and /dev/null differ diff --git a/site/_images/nfs_server_2049.png b/site/_images/nfs_server_2049.png deleted file mode 100644 index f082b3b..0000000 Binary files a/site/_images/nfs_server_2049.png and /dev/null differ diff --git a/site/_images/nginx-backup.png b/site/_images/nginx-backup.png deleted file mode 100644 index aad9634..0000000 Binary files a/site/_images/nginx-backup.png and /dev/null differ diff --git a/site/_images/no-ingress-controller.png b/site/_images/no-ingress-controller.png deleted file mode 100644 index a82ef50..0000000 Binary files a/site/_images/no-ingress-controller.png and /dev/null differ diff --git a/site/_images/no_networks_present.png b/site/_images/no_networks_present.png deleted file mode 100644 index 3640568..0000000 Binary files a/site/_images/no_networks_present.png and /dev/null differ diff --git a/site/_images/nodegroup_list_1.png b/site/_images/nodegroup_list_1.png deleted file mode 100644 index 696991b..0000000 Binary files a/site/_images/nodegroup_list_1.png and /dev/null differ diff --git a/site/_images/nodegroup_resized.png b/site/_images/nodegroup_resized.png deleted file mode 100644 index 7c5ce61..0000000 Binary files a/site/_images/nodegroup_resized.png and /dev/null differ diff --git a/site/_images/nodegroup_with_added_role.png b/site/_images/nodegroup_with_added_role.png deleted file mode 100644 index 123fd95..0000000 Binary files a/site/_images/nodegroup_with_added_role.png and /dev/null differ diff --git a/site/_images/nodegroups_in_cluster_id.png b/site/_images/nodegroups_in_cluster_id.png deleted file mode 100644 index 64f0bc4..0000000 Binary files a/site/_images/nodegroups_in_cluster_id.png and /dev/null differ diff --git a/site/_images/nodegroups_network_graph.png b/site/_images/nodegroups_network_graph.png deleted file mode 100644 index 243d730..0000000 Binary files a/site/_images/nodegroups_network_graph.png and /dev/null differ diff --git a/site/_images/nodes_address.png b/site/_images/nodes_address.png deleted file mode 100644 index 8b0eba3..0000000 Binary files a/site/_images/nodes_address.png and /dev/null differ diff --git a/site/_images/noloadbalancer_created.png b/site/_images/noloadbalancer_created.png deleted file mode 100644 index 4fc6e7b..0000000 Binary files a/site/_images/noloadbalancer_created.png and /dev/null differ diff --git a/site/_images/number_of_master_nodes_filled_in.png b/site/_images/number_of_master_nodes_filled_in.png deleted file mode 100644 index 1c41440..0000000 Binary files a/site/_images/number_of_master_nodes_filled_in.png and /dev/null differ diff --git a/site/_images/nvidia_chosen_3Engines_cloud.png b/site/_images/nvidia_chosen_3Engines_cloud.png deleted file mode 100644 index 4c685da..0000000 Binary files a/site/_images/nvidia_chosen_3Engines_cloud.png and /dev/null differ diff --git a/site/_images/object-storage-windows-example1_creodias.png b/site/_images/object-storage-windows-example1_creodias.png deleted file mode 100644 index c62f609..0000000 Binary files a/site/_images/object-storage-windows-example1_creodias.png and /dev/null differ diff --git a/site/_images/object_create_container_name.png b/site/_images/object_create_container_name.png deleted file mode 100644 index 0016af9..0000000 Binary files a/site/_images/object_create_container_name.png and /dev/null differ diff --git a/site/_images/object_list_backup09.png b/site/_images/object_list_backup09.png deleted file mode 100644 index 130b04c..0000000 Binary files a/site/_images/object_list_backup09.png and /dev/null differ diff --git a/site/_images/older_uuid.png b/site/_images/older_uuid.png deleted file mode 100644 index 20402d7..0000000 Binary files a/site/_images/older_uuid.png and /dev/null differ diff --git a/site/_images/orch4.png b/site/_images/orch4.png deleted file mode 100644 index 4f05245..0000000 Binary files a/site/_images/orch4.png and /dev/null differ diff --git a/site/_images/otp01.png b/site/_images/otp01.png deleted file mode 100644 index b3601f2..0000000 Binary files a/site/_images/otp01.png and /dev/null differ diff --git a/site/_images/otp01.png.html b/site/_images/otp01.png.html deleted file mode 100644 index 3cc15b6..0000000 --- a/site/_images/otp01.png.html +++ /dev/null @@ -1,12 +0,0 @@ - Otp01.png - 3Engines Documentation

Otp01.png

None

\ No newline at end of file diff --git a/site/_images/otp02.png b/site/_images/otp02.png deleted file mode 100644 index a0d3ddd..0000000 Binary files a/site/_images/otp02.png and /dev/null differ diff --git a/site/_images/otp02.png.html b/site/_images/otp02.png.html deleted file mode 100644 index 723ac30..0000000 --- a/site/_images/otp02.png.html +++ /dev/null @@ -1,12 +0,0 @@ - Otp02.png - 3Engines Documentation

Otp02.png

None

\ No newline at end of file diff --git a/site/_images/otp03.png b/site/_images/otp03.png deleted file mode 100644 index 2f36b3a..0000000 Binary files a/site/_images/otp03.png and /dev/null differ diff --git a/site/_images/otp03.png.html b/site/_images/otp03.png.html deleted file mode 100644 index a5ae98e..0000000 --- a/site/_images/otp03.png.html +++ /dev/null @@ -1,12 +0,0 @@ - Otp03.png - 3Engines Documentation

Otp03.png

None

\ No newline at end of file diff --git a/site/_images/otp04.png b/site/_images/otp04.png deleted file mode 100644 index e81e2c3..0000000 Binary files a/site/_images/otp04.png and /dev/null differ diff --git a/site/_images/otp04.png.html b/site/_images/otp04.png.html deleted file mode 100644 index 4d357e1..0000000 --- a/site/_images/otp04.png.html +++ /dev/null @@ -1,12 +0,0 @@ - Otp04.png - 3Engines Documentation

Otp04.png

None

\ No newline at end of file diff --git a/site/_images/otp05.png b/site/_images/otp05.png deleted file mode 100644 index 6268be4..0000000 Binary files a/site/_images/otp05.png and /dev/null differ diff --git a/site/_images/otp05.png.html b/site/_images/otp05.png.html deleted file mode 100644 index 12cba4a..0000000 --- a/site/_images/otp05.png.html +++ /dev/null @@ -1,12 +0,0 @@ - Otp05.png - 3Engines Documentation

Otp05.png

None

\ No newline at end of file diff --git a/site/_images/otp07.png b/site/_images/otp07.png deleted file mode 100644 index a09cf67..0000000 Binary files a/site/_images/otp07.png and /dev/null differ diff --git a/site/_images/otp07.png.html b/site/_images/otp07.png.html deleted file mode 100644 index 01e0143..0000000 --- a/site/_images/otp07.png.html +++ /dev/null @@ -1,12 +0,0 @@ - Otp07.png - 3Engines Documentation

Otp07.png

None

\ No newline at end of file diff --git a/site/_images/otp08.png b/site/_images/otp08.png deleted file mode 100644 index 93d5d21..0000000 Binary files a/site/_images/otp08.png and /dev/null differ diff --git a/site/_images/otp08.png.html b/site/_images/otp08.png.html deleted file mode 100644 index 9ddc500..0000000 --- a/site/_images/otp08.png.html +++ /dev/null @@ -1,12 +0,0 @@ - Otp08.png - 3Engines Documentation

Otp08.png

None

\ No newline at end of file diff --git a/site/_images/otp09.png b/site/_images/otp09.png deleted file mode 100644 index 18d0d6c..0000000 Binary files a/site/_images/otp09.png and /dev/null differ diff --git a/site/_images/otp09.png.html b/site/_images/otp09.png.html deleted file mode 100644 index fdd0877..0000000 --- a/site/_images/otp09.png.html +++ /dev/null @@ -1,12 +0,0 @@ - Otp09.png - 3Engines Documentation

Otp09.png

None

\ No newline at end of file diff --git a/site/_images/overview.png b/site/_images/overview.png deleted file mode 100644 index ada7de7..0000000 Binary files a/site/_images/overview.png and /dev/null differ diff --git a/site/_images/owner_con.png b/site/_images/owner_con.png deleted file mode 100644 index 1b2ec78..0000000 Binary files a/site/_images/owner_con.png and /dev/null differ diff --git a/site/_images/owner_login.png b/site/_images/owner_login.png deleted file mode 100644 index a4817dc..0000000 Binary files a/site/_images/owner_login.png and /dev/null differ diff --git a/site/_images/owner_main.png b/site/_images/owner_main.png deleted file mode 100644 index e555081..0000000 Binary files a/site/_images/owner_main.png and /dev/null differ diff --git a/site/_images/owner_rc.png b/site/_images/owner_rc.png deleted file mode 100644 index e726557..0000000 Binary files a/site/_images/owner_rc.png and /dev/null differ diff --git a/site/_images/owner_upload_0.png b/site/_images/owner_upload_0.png deleted file mode 100644 index d510c2f..0000000 Binary files a/site/_images/owner_upload_0.png and /dev/null differ diff --git a/site/_images/owner_upload_1.png b/site/_images/owner_upload_1.png deleted file mode 100644 index ff7debd..0000000 Binary files a/site/_images/owner_upload_1.png and /dev/null differ diff --git a/site/_images/parameters.png b/site/_images/parameters.png deleted file mode 100644 index ea196f6..0000000 Binary files a/site/_images/parameters.png and /dev/null differ diff --git a/site/_images/pastebin1.png b/site/_images/pastebin1.png deleted file mode 100644 index fee625e..0000000 Binary files a/site/_images/pastebin1.png and /dev/null differ diff --git a/site/_images/pastebin2.png b/site/_images/pastebin2.png deleted file mode 100644 index 329d1aa..0000000 Binary files a/site/_images/pastebin2.png and /dev/null differ diff --git a/site/_images/pastebin3.png b/site/_images/pastebin3.png deleted file mode 100644 index 3056180..0000000 Binary files a/site/_images/pastebin3.png and /dev/null differ diff --git a/site/_images/pastebin4.png b/site/_images/pastebin4.png deleted file mode 100644 index 918194b..0000000 Binary files a/site/_images/pastebin4.png and /dev/null differ diff --git a/site/_images/pastebin5.png b/site/_images/pastebin5.png deleted file mode 100644 index 69e2efe..0000000 Binary files a/site/_images/pastebin5.png and /dev/null differ diff --git a/site/_images/present_clusters.png b/site/_images/present_clusters.png deleted file mode 100644 index 507a08f..0000000 Binary files a/site/_images/present_clusters.png and /dev/null differ diff --git a/site/_images/present_networks.png b/site/_images/present_networks.png deleted file mode 100644 index ddb3015..0000000 Binary files a/site/_images/present_networks.png and /dev/null differ diff --git a/site/_images/project1.png b/site/_images/project1.png deleted file mode 100644 index b122400..0000000 Binary files a/site/_images/project1.png and /dev/null differ diff --git a/site/_images/project2.png b/site/_images/project2.png deleted file mode 100644 index 910554b..0000000 Binary files a/site/_images/project2.png and /dev/null differ diff --git a/site/_images/projects.png b/site/_images/projects.png deleted file mode 100644 index 67d44f8..0000000 Binary files a/site/_images/projects.png and /dev/null differ diff --git a/site/_images/projects_present.png b/site/_images/projects_present.png deleted file mode 100644 index c67bcc0..0000000 Binary files a/site/_images/projects_present.png and /dev/null differ diff --git a/site/_images/prometheus-dashboard_9090.png b/site/_images/prometheus-dashboard_9090.png deleted file mode 100644 index f90c367..0000000 Binary files a/site/_images/prometheus-dashboard_9090.png and /dev/null differ diff --git a/site/_images/putty-02.png b/site/_images/putty-02.png deleted file mode 100644 index 7f4e059..0000000 Binary files a/site/_images/putty-02.png and /dev/null differ diff --git a/site/_images/putty-03.png b/site/_images/putty-03.png deleted file mode 100644 index 37c307c..0000000 Binary files a/site/_images/putty-03.png and /dev/null differ diff --git a/site/_images/putty-04.png b/site/_images/putty-04.png deleted file mode 100644 index c819283..0000000 Binary files a/site/_images/putty-04.png and /dev/null differ diff --git a/site/_images/putty-05.png b/site/_images/putty-05.png deleted file mode 100644 index 3e619ed..0000000 Binary files a/site/_images/putty-05.png and /dev/null differ diff --git a/site/_images/putty-06.png b/site/_images/putty-06.png deleted file mode 100644 index 55969a6..0000000 Binary files a/site/_images/putty-06.png and /dev/null differ diff --git a/site/_images/putty-07.png b/site/_images/putty-07.png deleted file mode 100644 index 9bb8398..0000000 Binary files a/site/_images/putty-07.png and /dev/null differ diff --git a/site/_images/putty-08.png b/site/_images/putty-08.png deleted file mode 100644 index 6273035..0000000 Binary files a/site/_images/putty-08.png and /dev/null differ diff --git a/site/_images/putty-09.png b/site/_images/putty-09.png deleted file mode 100644 index 71bc3ef..0000000 Binary files a/site/_images/putty-09.png and /dev/null differ diff --git a/site/_images/putty-10.png b/site/_images/putty-10.png deleted file mode 100644 index 8186f4d..0000000 Binary files a/site/_images/putty-10.png and /dev/null differ diff --git a/site/_images/putty-11.png b/site/_images/putty-11.png deleted file mode 100644 index a7cf0d9..0000000 Binary files a/site/_images/putty-11.png and /dev/null differ diff --git a/site/_images/putty-12.png b/site/_images/putty-12.png deleted file mode 100644 index 2bbdbe2..0000000 Binary files a/site/_images/putty-12.png and /dev/null differ diff --git a/site/_images/putty-13.png b/site/_images/putty-13.png deleted file mode 100644 index b0089d9..0000000 Binary files a/site/_images/putty-13.png and /dev/null differ diff --git a/site/_images/putty-14.png b/site/_images/putty-14.png deleted file mode 100644 index f8cc63c..0000000 Binary files a/site/_images/putty-14.png and /dev/null differ diff --git a/site/_images/putty-15.png b/site/_images/putty-15.png deleted file mode 100644 index ecd07d7..0000000 Binary files a/site/_images/putty-15.png and /dev/null differ diff --git a/site/_images/putty-16.png b/site/_images/putty-16.png deleted file mode 100644 index 2579abd..0000000 Binary files a/site/_images/putty-16.png and /dev/null differ diff --git a/site/_images/rc_file_content.png b/site/_images/rc_file_content.png deleted file mode 100644 index 463a42a..0000000 Binary files a/site/_images/rc_file_content.png and /dev/null differ diff --git a/site/_images/redis-data.png b/site/_images/redis-data.png deleted file mode 100644 index c993c8b..0000000 Binary files a/site/_images/redis-data.png and /dev/null differ diff --git a/site/_images/redis_kill.png b/site/_images/redis_kill.png deleted file mode 100644 index 56f826c..0000000 Binary files a/site/_images/redis_kill.png and /dev/null differ diff --git a/site/_images/register_3Enginescloud.png b/site/_images/register_3Enginescloud.png deleted file mode 100644 index 9c1f815..0000000 Binary files a/site/_images/register_3Enginescloud.png and /dev/null differ diff --git a/site/_images/register_3Enginescloud1.png b/site/_images/register_3Enginescloud1.png deleted file mode 100644 index 9c1f815..0000000 Binary files a/site/_images/register_3Enginescloud1.png and /dev/null differ diff --git a/site/_images/register_3Enginescloud1.png.html b/site/_images/register_3Enginescloud1.png.html deleted file mode 100644 index bb7f399..0000000 --- a/site/_images/register_3Enginescloud1.png.html +++ /dev/null @@ -1,12 +0,0 @@ - register 3Enginescloud1.png - 3Engines Documentation

register 3Enginescloud1.png

None

\ No newline at end of file diff --git a/site/_images/register_organization_3Enginescloud.png b/site/_images/register_organization_3Enginescloud.png deleted file mode 100644 index a902746..0000000 Binary files a/site/_images/register_organization_3Enginescloud.png and /dev/null differ diff --git a/site/_images/registration_successful_3Enginescloud.png b/site/_images/registration_successful_3Enginescloud.png deleted file mode 100644 index 8226029..0000000 Binary files a/site/_images/registration_successful_3Enginescloud.png and /dev/null differ diff --git a/site/_images/removed_ec2_empty.png b/site/_images/removed_ec2_empty.png deleted file mode 100644 index ef71535..0000000 Binary files a/site/_images/removed_ec2_empty.png and /dev/null differ diff --git a/site/_images/request_for_nodegroup.png b/site/_images/request_for_nodegroup.png deleted file mode 100644 index fd97e77..0000000 Binary files a/site/_images/request_for_nodegroup.png and /dev/null differ diff --git a/site/_images/resize-vm-horizon-1.png b/site/_images/resize-vm-horizon-1.png deleted file mode 100644 index 2248e84..0000000 Binary files a/site/_images/resize-vm-horizon-1.png and /dev/null differ diff --git a/site/_images/resize-vm-horizon-10.png b/site/_images/resize-vm-horizon-10.png deleted file mode 100644 index 98e6d86..0000000 Binary files a/site/_images/resize-vm-horizon-10.png and /dev/null differ diff --git a/site/_images/resize-vm-horizon-11.png b/site/_images/resize-vm-horizon-11.png deleted file mode 100644 index af93eb6..0000000 Binary files a/site/_images/resize-vm-horizon-11.png and /dev/null differ diff --git a/site/_images/resize-vm-horizon-2.png b/site/_images/resize-vm-horizon-2.png deleted file mode 100644 index ed9525d..0000000 Binary files a/site/_images/resize-vm-horizon-2.png and /dev/null differ diff --git a/site/_images/resize-vm-horizon-3.png b/site/_images/resize-vm-horizon-3.png deleted file mode 100644 index 0cd93a8..0000000 Binary files a/site/_images/resize-vm-horizon-3.png and /dev/null differ diff --git a/site/_images/resize-vm-horizon-4.png b/site/_images/resize-vm-horizon-4.png deleted file mode 100644 index 8386b1e..0000000 Binary files a/site/_images/resize-vm-horizon-4.png and /dev/null differ diff --git a/site/_images/resize-vm-horizon-5.png b/site/_images/resize-vm-horizon-5.png deleted file mode 100644 index f50afd2..0000000 Binary files a/site/_images/resize-vm-horizon-5.png and /dev/null differ diff --git a/site/_images/resize-vm-horizon-7.png b/site/_images/resize-vm-horizon-7.png deleted file mode 100644 index 2ed428b..0000000 Binary files a/site/_images/resize-vm-horizon-7.png and /dev/null differ diff --git a/site/_images/resize-vm-horizon-8.png b/site/_images/resize-vm-horizon-8.png deleted file mode 100644 index 2584334..0000000 Binary files a/site/_images/resize-vm-horizon-8.png and /dev/null differ diff --git a/site/_images/resize-vm-horizon-cli-2.png b/site/_images/resize-vm-horizon-cli-2.png deleted file mode 100644 index e1880e3..0000000 Binary files a/site/_images/resize-vm-horizon-cli-2.png and /dev/null differ diff --git a/site/_images/resize-vm-horizon-cli-3.png b/site/_images/resize-vm-horizon-cli-3.png deleted file mode 100644 index 14e07f1..0000000 Binary files a/site/_images/resize-vm-horizon-cli-3.png and /dev/null differ diff --git a/site/_images/resize-vm-horizon-cli-4.png b/site/_images/resize-vm-horizon-cli-4.png deleted file mode 100644 index aa48517..0000000 Binary files a/site/_images/resize-vm-horizon-cli-4.png and /dev/null differ diff --git a/site/_images/resize_instance.png b/site/_images/resize_instance.png deleted file mode 100644 index 35ecbf0..0000000 Binary files a/site/_images/resize_instance.png and /dev/null differ diff --git a/site/_images/result_of_creating_nodegroup.png b/site/_images/result_of_creating_nodegroup.png deleted file mode 100644 index 24479a2..0000000 Binary files a/site/_images/result_of_creating_nodegroup.png and /dev/null differ diff --git a/site/_images/role_test.png b/site/_images/role_test.png deleted file mode 100644 index cf139d4..0000000 Binary files a/site/_images/role_test.png and /dev/null differ diff --git a/site/_images/run-mmc.png b/site/_images/run-mmc.png deleted file mode 100644 index cffcaf7..0000000 Binary files a/site/_images/run-mmc.png and /dev/null differ diff --git a/site/_images/s3-bucket-versioning-01_creodias.png b/site/_images/s3-bucket-versioning-01_creodias.png deleted file mode 100644 index 4e7581a..0000000 Binary files a/site/_images/s3-bucket-versioning-01_creodias.png and /dev/null differ diff --git a/site/_images/s3-bucket-versioning-02_creodias.png b/site/_images/s3-bucket-versioning-02_creodias.png deleted file mode 100644 index 5305489..0000000 Binary files a/site/_images/s3-bucket-versioning-02_creodias.png and /dev/null differ diff --git a/site/_images/s3-bucket-versioning-03_creodias.png b/site/_images/s3-bucket-versioning-03_creodias.png deleted file mode 100644 index 7cbb78a..0000000 Binary files a/site/_images/s3-bucket-versioning-03_creodias.png and /dev/null differ diff --git a/site/_images/s3-bucket-versioning-04_creodias.png b/site/_images/s3-bucket-versioning-04_creodias.png deleted file mode 100644 index 672a054..0000000 Binary files a/site/_images/s3-bucket-versioning-04_creodias.png and /dev/null differ diff --git a/site/_images/s3-bucket-versioning-05_creodias.png b/site/_images/s3-bucket-versioning-05_creodias.png deleted file mode 100644 index 37bc0bd..0000000 Binary files a/site/_images/s3-bucket-versioning-05_creodias.png and /dev/null differ diff --git a/site/_images/s3-bucket-versioning-06_creodias.png b/site/_images/s3-bucket-versioning-06_creodias.png deleted file mode 100644 index b1b9ef7..0000000 Binary files a/site/_images/s3-bucket-versioning-06_creodias.png and /dev/null differ diff --git a/site/_images/s3-bucket-versioning-07_creodias.png b/site/_images/s3-bucket-versioning-07_creodias.png deleted file mode 100644 index 5daf979..0000000 Binary files a/site/_images/s3-bucket-versioning-07_creodias.png and /dev/null differ diff --git a/site/_images/s3-bucket-versioning-08_creodias.png b/site/_images/s3-bucket-versioning-08_creodias.png deleted file mode 100644 index dfce4a0..0000000 Binary files a/site/_images/s3-bucket-versioning-08_creodias.png and /dev/null differ diff --git a/site/_images/s3-bucket-versioning-09_creodias.png b/site/_images/s3-bucket-versioning-09_creodias.png deleted file mode 100644 index fd7671c..0000000 Binary files a/site/_images/s3-bucket-versioning-09_creodias.png and /dev/null differ diff --git a/site/_images/saml_3Engines_cloud.png b/site/_images/saml_3Engines_cloud.png deleted file mode 100644 index dad2d8b..0000000 Binary files a/site/_images/saml_3Engines_cloud.png and /dev/null differ diff --git a/site/_images/screen03.png b/site/_images/screen03.png deleted file mode 100644 index 10c6310..0000000 Binary files a/site/_images/screen03.png and /dev/null differ diff --git a/site/_images/screen03a.png b/site/_images/screen03a.png deleted file mode 100644 index 0e4ab5b..0000000 Binary files a/site/_images/screen03a.png and /dev/null differ diff --git a/site/_images/screen07.png b/site/_images/screen07.png deleted file mode 100644 index 9720655..0000000 Binary files a/site/_images/screen07.png and /dev/null differ diff --git a/site/_images/screen1.png b/site/_images/screen1.png deleted file mode 100644 index 1ee046d..0000000 Binary files a/site/_images/screen1.png and /dev/null differ diff --git a/site/_images/screen11.png b/site/_images/screen11.png deleted file mode 100644 index 7508435..0000000 Binary files a/site/_images/screen11.png and /dev/null differ diff --git a/site/_images/screen12.png b/site/_images/screen12.png deleted file mode 100644 index 1bb22f4..0000000 Binary files a/site/_images/screen12.png and /dev/null differ diff --git a/site/_images/screen13.png b/site/_images/screen13.png deleted file mode 100644 index a8d0672..0000000 Binary files a/site/_images/screen13.png and /dev/null differ diff --git a/site/_images/screen14.png b/site/_images/screen14.png deleted file mode 100644 index 4965cca..0000000 Binary files a/site/_images/screen14.png and /dev/null differ diff --git a/site/_images/screen15.png b/site/_images/screen15.png deleted file mode 100644 index 5895d05..0000000 Binary files a/site/_images/screen15.png and /dev/null differ diff --git a/site/_images/screen16.png b/site/_images/screen16.png deleted file mode 100644 index fc56e34..0000000 Binary files a/site/_images/screen16.png and /dev/null differ diff --git a/site/_images/screen17b.png b/site/_images/screen17b.png deleted file mode 100644 index 7961f77..0000000 Binary files a/site/_images/screen17b.png and /dev/null differ diff --git a/site/_images/screen18.png b/site/_images/screen18.png deleted file mode 100644 index b56b79f..0000000 Binary files a/site/_images/screen18.png and /dev/null differ diff --git a/site/_images/screen19.png b/site/_images/screen19.png deleted file mode 100644 index e1f0d4e..0000000 Binary files a/site/_images/screen19.png and /dev/null differ diff --git a/site/_images/screen2.png b/site/_images/screen2.png deleted file mode 100644 index 48f9ca8..0000000 Binary files a/site/_images/screen2.png and /dev/null differ diff --git a/site/_images/screen20.png b/site/_images/screen20.png deleted file mode 100644 index 95b4355..0000000 Binary files a/site/_images/screen20.png and /dev/null differ diff --git a/site/_images/screen21.png b/site/_images/screen21.png deleted file mode 100644 index d4e4646..0000000 Binary files a/site/_images/screen21.png and /dev/null differ diff --git a/site/_images/screen22.png b/site/_images/screen22.png deleted file mode 100644 index 191778a..0000000 Binary files a/site/_images/screen22.png and /dev/null differ diff --git a/site/_images/screen23.png b/site/_images/screen23.png deleted file mode 100644 index 1dab999..0000000 Binary files a/site/_images/screen23.png and /dev/null differ diff --git a/site/_images/screen23a.png b/site/_images/screen23a.png deleted file mode 100644 index 3cc198c..0000000 Binary files a/site/_images/screen23a.png and /dev/null differ diff --git a/site/_images/screen24a.png b/site/_images/screen24a.png deleted file mode 100644 index d2cb81f..0000000 Binary files a/site/_images/screen24a.png and /dev/null differ diff --git a/site/_images/screen25a.png b/site/_images/screen25a.png deleted file mode 100644 index 764d973..0000000 Binary files a/site/_images/screen25a.png and /dev/null differ diff --git a/site/_images/screen26a.png b/site/_images/screen26a.png deleted file mode 100644 index 883a4ac..0000000 Binary files a/site/_images/screen26a.png and /dev/null differ diff --git a/site/_images/screen27a.png b/site/_images/screen27a.png deleted file mode 100644 index bfc3b25..0000000 Binary files a/site/_images/screen27a.png and /dev/null differ diff --git a/site/_images/screen28a.png b/site/_images/screen28a.png deleted file mode 100644 index fd4d32e..0000000 Binary files a/site/_images/screen28a.png and /dev/null differ diff --git a/site/_images/screen29b.png b/site/_images/screen29b.png deleted file mode 100644 index 997caea..0000000 Binary files a/site/_images/screen29b.png and /dev/null differ diff --git a/site/_images/screen3.png b/site/_images/screen3.png deleted file mode 100644 index 392159f..0000000 Binary files a/site/_images/screen3.png and /dev/null differ diff --git a/site/_images/screen30b.png b/site/_images/screen30b.png deleted file mode 100644 index d202452..0000000 Binary files a/site/_images/screen30b.png and /dev/null differ diff --git a/site/_images/screen31a.png b/site/_images/screen31a.png deleted file mode 100644 index 0a59f5e..0000000 Binary files a/site/_images/screen31a.png and /dev/null differ diff --git a/site/_images/screen32a.png b/site/_images/screen32a.png deleted file mode 100644 index 1614b1b..0000000 Binary files a/site/_images/screen32a.png and /dev/null differ diff --git a/site/_images/screen33a.png b/site/_images/screen33a.png deleted file mode 100644 index dec6b2d..0000000 Binary files a/site/_images/screen33a.png and /dev/null differ diff --git a/site/_images/screen34a.png b/site/_images/screen34a.png deleted file mode 100644 index 3c08033..0000000 Binary files a/site/_images/screen34a.png and /dev/null differ diff --git a/site/_images/screen35a.png b/site/_images/screen35a.png deleted file mode 100644 index a43eed9..0000000 Binary files a/site/_images/screen35a.png and /dev/null differ diff --git a/site/_images/screen36.png b/site/_images/screen36.png deleted file mode 100644 index ca8fb87..0000000 Binary files a/site/_images/screen36.png and /dev/null differ diff --git a/site/_images/screen4.png b/site/_images/screen4.png deleted file mode 100644 index a691dee..0000000 Binary files a/site/_images/screen4.png and /dev/null differ diff --git a/site/_images/screen5.png b/site/_images/screen5.png deleted file mode 100644 index 67bfc4c..0000000 Binary files a/site/_images/screen5.png and /dev/null differ diff --git a/site/_images/screen6.png b/site/_images/screen6.png deleted file mode 100644 index 460bb26..0000000 Binary files a/site/_images/screen6.png and /dev/null differ diff --git a/site/_images/screen7.png b/site/_images/screen7.png deleted file mode 100644 index 8d6a388..0000000 Binary files a/site/_images/screen7.png and /dev/null differ diff --git a/site/_images/screen8.png b/site/_images/screen8.png deleted file mode 100644 index 514fed1..0000000 Binary files a/site/_images/screen8.png and /dev/null differ diff --git a/site/_images/screen9.png b/site/_images/screen9.png deleted file mode 100644 index a0d1393..0000000 Binary files a/site/_images/screen9.png and /dev/null differ diff --git a/site/_images/scrn10.png b/site/_images/scrn10.png deleted file mode 100644 index 77b4dfa..0000000 Binary files a/site/_images/scrn10.png and /dev/null differ diff --git a/site/_images/scrn28.png b/site/_images/scrn28.png deleted file mode 100644 index 1550ec0..0000000 Binary files a/site/_images/scrn28.png and /dev/null differ diff --git a/site/_images/scrn30.png b/site/_images/scrn30.png deleted file mode 100644 index 0c2ace1..0000000 Binary files a/site/_images/scrn30.png and /dev/null differ diff --git a/site/_images/search_repo.png b/site/_images/search_repo.png deleted file mode 100644 index a8a84d0..0000000 Binary files a/site/_images/search_repo.png and /dev/null differ diff --git a/site/_images/select_ci_cd_option.png b/site/_images/select_ci_cd_option.png deleted file mode 100644 index 1b39513..0000000 Binary files a/site/_images/select_ci_cd_option.png and /dev/null differ diff --git a/site/_images/select_role.png b/site/_images/select_role.png deleted file mode 100644 index edb1fb2..0000000 Binary files a/site/_images/select_role.png and /dev/null differ diff --git a/site/_images/select_template_yaml.png b/site/_images/select_template_yaml.png deleted file mode 100644 index 82a631e..0000000 Binary files a/site/_images/select_template_yaml.png and /dev/null differ diff --git a/site/_images/services_3Enginescloud.png b/site/_images/services_3Enginescloud.png deleted file mode 100644 index 5db0891..0000000 Binary files a/site/_images/services_3Enginescloud.png and /dev/null differ diff --git a/site/_images/several_ec2_pairs.png b/site/_images/several_ec2_pairs.png deleted file mode 100644 index e37abf2..0000000 Binary files a/site/_images/several_ec2_pairs.png and /dev/null differ diff --git a/site/_images/show_example_domain_record_sets.png b/site/_images/show_example_domain_record_sets.png deleted file mode 100644 index bf71045..0000000 Binary files a/site/_images/show_example_domain_record_sets.png and /dev/null differ diff --git a/site/_images/shut_off_instance.png b/site/_images/shut_off_instance.png deleted file mode 100644 index d413646..0000000 Binary files a/site/_images/shut_off_instance.png and /dev/null differ diff --git a/site/_images/size_screen_filled.png b/site/_images/size_screen_filled.png deleted file mode 100644 index 7d96da5..0000000 Binary files a/site/_images/size_screen_filled.png and /dev/null differ diff --git a/site/_images/snap-in.png b/site/_images/snap-in.png deleted file mode 100644 index 792c34b..0000000 Binary files a/site/_images/snap-in.png and /dev/null differ diff --git a/site/_images/snap00.png b/site/_images/snap00.png deleted file mode 100644 index a61326f..0000000 Binary files a/site/_images/snap00.png and /dev/null differ diff --git a/site/_images/snap01.png b/site/_images/snap01.png deleted file mode 100644 index 711d837..0000000 Binary files a/site/_images/snap01.png and /dev/null differ diff --git a/site/_images/snap1.png b/site/_images/snap1.png deleted file mode 100644 index 93bb720..0000000 Binary files a/site/_images/snap1.png and /dev/null differ diff --git a/site/_images/snap2.png b/site/_images/snap2.png deleted file mode 100644 index 1d807d3..0000000 Binary files a/site/_images/snap2.png and /dev/null differ diff --git a/site/_images/snap3.png b/site/_images/snap3.png deleted file mode 100644 index 05e5685..0000000 Binary files a/site/_images/snap3.png and /dev/null differ diff --git a/site/_images/snap4.png b/site/_images/snap4.png deleted file mode 100644 index 06a0446..0000000 Binary files a/site/_images/snap4.png and /dev/null differ diff --git a/site/_images/snap5.png b/site/_images/snap5.png deleted file mode 100644 index c7ec975..0000000 Binary files a/site/_images/snap5.png and /dev/null differ diff --git a/site/_images/snap6.png b/site/_images/snap6.png deleted file mode 100644 index 349f6fa..0000000 Binary files a/site/_images/snap6.png and /dev/null differ diff --git a/site/_images/snap7.png b/site/_images/snap7.png deleted file mode 100644 index 30c0c8d..0000000 Binary files a/site/_images/snap7.png and /dev/null differ diff --git a/site/_images/snap8.png b/site/_images/snap8.png deleted file mode 100644 index f5e3311..0000000 Binary files a/site/_images/snap8.png and /dev/null differ diff --git a/site/_images/some_nodes.png b/site/_images/some_nodes.png deleted file mode 100644 index ff1fd3f..0000000 Binary files a/site/_images/some_nodes.png and /dev/null differ diff --git a/site/_images/spot_flavors_when_creating.png b/site/_images/spot_flavors_when_creating.png deleted file mode 100644 index 477e204..0000000 Binary files a/site/_images/spot_flavors_when_creating.png and /dev/null differ diff --git a/site/_images/spot_hma_created.png b/site/_images/spot_hma_created.png deleted file mode 100644 index 506b300..0000000 Binary files a/site/_images/spot_hma_created.png and /dev/null differ diff --git a/site/_images/ssh-import-01_creodias.png b/site/_images/ssh-import-01_creodias.png deleted file mode 100644 index 14c9b10..0000000 Binary files a/site/_images/ssh-import-01_creodias.png and /dev/null differ diff --git a/site/_images/ssh-import-02_creodias.png b/site/_images/ssh-import-02_creodias.png deleted file mode 100644 index d296c2f..0000000 Binary files a/site/_images/ssh-import-02_creodias.png and /dev/null differ diff --git a/site/_images/ssh-import-03_creodias.png b/site/_images/ssh-import-03_creodias.png deleted file mode 100644 index deb5261..0000000 Binary files a/site/_images/ssh-import-03_creodias.png and /dev/null differ diff --git a/site/_images/ssh-import-04_creodias.png b/site/_images/ssh-import-04_creodias.png deleted file mode 100644 index f481563..0000000 Binary files a/site/_images/ssh-import-04_creodias.png and /dev/null differ diff --git a/site/_images/ssh1.png b/site/_images/ssh1.png deleted file mode 100644 index c6ec3ae..0000000 Binary files a/site/_images/ssh1.png and /dev/null differ diff --git a/site/_images/ssh2.png b/site/_images/ssh2.png deleted file mode 100644 index 50a25aa..0000000 Binary files a/site/_images/ssh2.png and /dev/null differ diff --git a/site/_images/ssh3.png b/site/_images/ssh3.png deleted file mode 100644 index 78a3092..0000000 Binary files a/site/_images/ssh3.png and /dev/null differ diff --git a/site/_images/ssh_linux1.png b/site/_images/ssh_linux1.png deleted file mode 100644 index a1726dd..0000000 Binary files a/site/_images/ssh_linux1.png and /dev/null differ diff --git a/site/_images/ssh_linux2.png b/site/_images/ssh_linux2.png deleted file mode 100644 index 5343275..0000000 Binary files a/site/_images/ssh_linux2.png and /dev/null differ diff --git a/site/_images/ssh_windows_1.png b/site/_images/ssh_windows_1.png deleted file mode 100644 index b2fa4ef..0000000 Binary files a/site/_images/ssh_windows_1.png and /dev/null differ diff --git a/site/_images/ssh_windows_2.png b/site/_images/ssh_windows_2.png deleted file mode 100644 index f09cbb9..0000000 Binary files a/site/_images/ssh_windows_2.png and /dev/null differ diff --git a/site/_images/ssh_windows_3.png b/site/_images/ssh_windows_3.png deleted file mode 100644 index e57b1bd..0000000 Binary files a/site/_images/ssh_windows_3.png and /dev/null differ diff --git a/site/_images/ssh_windows_4.png b/site/_images/ssh_windows_4.png deleted file mode 100644 index a0dd222..0000000 Binary files a/site/_images/ssh_windows_4.png and /dev/null differ diff --git a/site/_images/ssh_windows_5.png b/site/_images/ssh_windows_5.png deleted file mode 100644 index 3aaafdb..0000000 Binary files a/site/_images/ssh_windows_5.png and /dev/null differ diff --git a/site/_images/ssh_windows_6.png b/site/_images/ssh_windows_6.png deleted file mode 100644 index 03464d1..0000000 Binary files a/site/_images/ssh_windows_6.png and /dev/null differ diff --git a/site/_images/stacks_creations.png b/site/_images/stacks_creations.png deleted file mode 100644 index e0b7e32..0000000 Binary files a/site/_images/stacks_creations.png and /dev/null differ diff --git a/site/_images/stacks_menu.png b/site/_images/stacks_menu.png deleted file mode 100644 index a06fc32..0000000 Binary files a/site/_images/stacks_menu.png and /dev/null differ diff --git a/site/_images/start_using_vault.png b/site/_images/start_using_vault.png deleted file mode 100644 index 00f7fb0..0000000 Binary files a/site/_images/start_using_vault.png and /dev/null differ diff --git a/site/_images/start_vm_instance_snapshot_cli-01_creodias.png b/site/_images/start_vm_instance_snapshot_cli-01_creodias.png deleted file mode 100644 index c1ecf4c..0000000 Binary files a/site/_images/start_vm_instance_snapshot_cli-01_creodias.png and /dev/null differ diff --git a/site/_images/start_vm_instance_snapshot_cli-02_creodias.png b/site/_images/start_vm_instance_snapshot_cli-02_creodias.png deleted file mode 100644 index eda43c4..0000000 Binary files a/site/_images/start_vm_instance_snapshot_cli-02_creodias.png and /dev/null differ diff --git a/site/_images/start_vm_instance_snapshot_cli-03_creodias.png b/site/_images/start_vm_instance_snapshot_cli-03_creodias.png deleted file mode 100644 index 5fae858..0000000 Binary files a/site/_images/start_vm_instance_snapshot_cli-03_creodias.png and /dev/null differ diff --git a/site/_images/start_vm_instance_snapshot_cli-04_creodias.png b/site/_images/start_vm_instance_snapshot_cli-04_creodias.png deleted file mode 100644 index 3a027ca..0000000 Binary files a/site/_images/start_vm_instance_snapshot_cli-04_creodias.png and /dev/null differ diff --git a/site/_images/start_vm_instance_snapshot_cli-05_creodias.png b/site/_images/start_vm_instance_snapshot_cli-05_creodias.png deleted file mode 100644 index d722bfc..0000000 Binary files a/site/_images/start_vm_instance_snapshot_cli-05_creodias.png and /dev/null differ diff --git a/site/_images/start_vm_instance_snapshot_horizon-01_creodias.png b/site/_images/start_vm_instance_snapshot_horizon-01_creodias.png deleted file mode 100644 index 3968ab1..0000000 Binary files a/site/_images/start_vm_instance_snapshot_horizon-01_creodias.png and /dev/null differ diff --git a/site/_images/start_vm_instance_snapshot_horizon-02_creodias.png b/site/_images/start_vm_instance_snapshot_horizon-02_creodias.png deleted file mode 100644 index 733fb9a..0000000 Binary files a/site/_images/start_vm_instance_snapshot_horizon-02_creodias.png and /dev/null differ diff --git a/site/_images/start_vm_instance_snapshot_horizon-03_creodias.png b/site/_images/start_vm_instance_snapshot_horizon-03_creodias.png deleted file mode 100644 index e56d43b..0000000 Binary files a/site/_images/start_vm_instance_snapshot_horizon-03_creodias.png and /dev/null differ diff --git a/site/_images/start_vm_instance_snapshot_horizon-04_creodias.png b/site/_images/start_vm_instance_snapshot_horizon-04_creodias.png deleted file mode 100644 index c6fc165..0000000 Binary files a/site/_images/start_vm_instance_snapshot_horizon-04_creodias.png and /dev/null differ diff --git a/site/_images/start_vm_instance_snapshot_horizon-05_creodias.png b/site/_images/start_vm_instance_snapshot_horizon-05_creodias.png deleted file mode 100644 index 1558b43..0000000 Binary files a/site/_images/start_vm_instance_snapshot_horizon-05_creodias.png and /dev/null differ diff --git a/site/_images/start_vm_instance_snapshot_horizon-06_creodias.png b/site/_images/start_vm_instance_snapshot_horizon-06_creodias.png deleted file mode 100644 index 17a2e08..0000000 Binary files a/site/_images/start_vm_instance_snapshot_horizon-06_creodias.png and /dev/null differ diff --git a/site/_images/start_vm_instance_snapshot_horizon-07_creodias.png b/site/_images/start_vm_instance_snapshot_horizon-07_creodias.png deleted file mode 100644 index eb58bad..0000000 Binary files a/site/_images/start_vm_instance_snapshot_horizon-07_creodias.png and /dev/null differ diff --git a/site/_images/start_vm_instance_snapshot_horizon-08_creodias.png b/site/_images/start_vm_instance_snapshot_horizon-08_creodias.png deleted file mode 100644 index 775b6ec..0000000 Binary files a/site/_images/start_vm_instance_snapshot_horizon-08_creodias.png and /dev/null differ diff --git a/site/_images/start_vm_instance_snapshot_horizon-09_creodias.png b/site/_images/start_vm_instance_snapshot_horizon-09_creodias.png deleted file mode 100644 index 17f193d..0000000 Binary files a/site/_images/start_vm_instance_snapshot_horizon-09_creodias.png and /dev/null differ diff --git a/site/_images/starting_to_server.png b/site/_images/starting_to_server.png deleted file mode 100644 index fe77104..0000000 Binary files a/site/_images/starting_to_server.png and /dev/null differ diff --git a/site/_images/state_again.png b/site/_images/state_again.png deleted file mode 100644 index b10f1e9..0000000 Binary files a/site/_images/state_again.png and /dev/null differ diff --git a/site/_images/statuspower.png b/site/_images/statuspower.png deleted file mode 100644 index fbc676a..0000000 Binary files a/site/_images/statuspower.png and /dev/null differ diff --git a/site/_images/step-create-an-image.png b/site/_images/step-create-an-image.png deleted file mode 100644 index 82d996e..0000000 Binary files a/site/_images/step-create-an-image.png and /dev/null differ diff --git a/site/_images/successful_installation_of_gitlab.png b/site/_images/successful_installation_of_gitlab.png deleted file mode 100644 index deaa5f6..0000000 Binary files a/site/_images/successful_installation_of_gitlab.png and /dev/null differ diff --git a/site/_images/sudo_su_eouser.png b/site/_images/sudo_su_eouser.png deleted file mode 100644 index 358254f..0000000 Binary files a/site/_images/sudo_su_eouser.png and /dev/null differ diff --git a/site/_images/swapped_address.png b/site/_images/swapped_address.png deleted file mode 100644 index d1c26b7..0000000 Binary files a/site/_images/swapped_address.png and /dev/null differ diff --git a/site/_images/table_testing.png b/site/_images/table_testing.png deleted file mode 100644 index 5fac4cb..0000000 Binary files a/site/_images/table_testing.png and /dev/null differ diff --git a/site/_images/template_generator.png b/site/_images/template_generator.png deleted file mode 100644 index 6557ace..0000000 Binary files a/site/_images/template_generator.png and /dev/null differ diff --git a/site/_images/template_show_non_gpu.png b/site/_images/template_show_non_gpu.png deleted file mode 100644 index 3e1dffe..0000000 Binary files a/site/_images/template_show_non_gpu.png and /dev/null differ diff --git a/site/_images/terraform_adding_repository.png b/site/_images/terraform_adding_repository.png deleted file mode 100644 index 2f18fbd..0000000 Binary files a/site/_images/terraform_adding_repository.png and /dev/null differ diff --git a/site/_images/terraform_apply.png b/site/_images/terraform_apply.png deleted file mode 100644 index 5a46fde..0000000 Binary files a/site/_images/terraform_apply.png and /dev/null differ diff --git a/site/_images/terraform_flavor_list_short.png b/site/_images/terraform_flavor_list_short.png deleted file mode 100644 index 87f7146..0000000 Binary files a/site/_images/terraform_flavor_list_short.png and /dev/null differ diff --git a/site/_images/terraform_horizon.png b/site/_images/terraform_horizon.png deleted file mode 100644 index b14ee32..0000000 Binary files a/site/_images/terraform_horizon.png and /dev/null differ diff --git a/site/_images/terraform_init.png b/site/_images/terraform_init.png deleted file mode 100644 index e7d2095..0000000 Binary files a/site/_images/terraform_init.png and /dev/null differ diff --git a/site/_images/terraform_yes.png b/site/_images/terraform_yes.png deleted file mode 100644 index 7d7e2cb..0000000 Binary files a/site/_images/terraform_yes.png and /dev/null differ diff --git a/site/_images/testproject.png b/site/_images/testproject.png deleted file mode 100644 index 303d480..0000000 Binary files a/site/_images/testproject.png and /dev/null differ diff --git a/site/_images/three_backups_mybackup.png b/site/_images/three_backups_mybackup.png deleted file mode 100644 index 55580fc..0000000 Binary files a/site/_images/three_backups_mybackup.png and /dev/null differ diff --git a/site/_images/tickets_3Enginescloud.png b/site/_images/tickets_3Enginescloud.png deleted file mode 100644 index bb69592..0000000 Binary files a/site/_images/tickets_3Enginescloud.png and /dev/null differ diff --git a/site/_images/trag_8080.png b/site/_images/trag_8080.png deleted file mode 100644 index 5f93cf5..0000000 Binary files a/site/_images/trag_8080.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-cli-14_creodias.png b/site/_images/transfer-volume-between-projects-cli-14_creodias.png deleted file mode 100644 index c8b3e97..0000000 Binary files a/site/_images/transfer-volume-between-projects-cli-14_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-cli-25_creodias.png b/site/_images/transfer-volume-between-projects-cli-25_creodias.png deleted file mode 100644 index f4bd0fa..0000000 Binary files a/site/_images/transfer-volume-between-projects-cli-25_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-cli-26_creodias.png b/site/_images/transfer-volume-between-projects-cli-26_creodias.png deleted file mode 100644 index 9018dce..0000000 Binary files a/site/_images/transfer-volume-between-projects-cli-26_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-cli-27_creodias.png b/site/_images/transfer-volume-between-projects-cli-27_creodias.png deleted file mode 100644 index 21babce..0000000 Binary files a/site/_images/transfer-volume-between-projects-cli-27_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-cli-32_creodias.png b/site/_images/transfer-volume-between-projects-cli-32_creodias.png deleted file mode 100644 index 486ba8c..0000000 Binary files a/site/_images/transfer-volume-between-projects-cli-32_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-cli-33_creodias.png b/site/_images/transfer-volume-between-projects-cli-33_creodias.png deleted file mode 100644 index 1f9b5d7..0000000 Binary files a/site/_images/transfer-volume-between-projects-cli-33_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-cli-34_creodias.png b/site/_images/transfer-volume-between-projects-cli-34_creodias.png deleted file mode 100644 index 65b1ec5..0000000 Binary files a/site/_images/transfer-volume-between-projects-cli-34_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-horizon-11_creodias.png b/site/_images/transfer-volume-between-projects-horizon-11_creodias.png deleted file mode 100644 index 274382d..0000000 Binary files a/site/_images/transfer-volume-between-projects-horizon-11_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-horizon-15_creodias.png b/site/_images/transfer-volume-between-projects-horizon-15_creodias.png deleted file mode 100644 index 17e44fd..0000000 Binary files a/site/_images/transfer-volume-between-projects-horizon-15_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-horizon-16_creodias.png b/site/_images/transfer-volume-between-projects-horizon-16_creodias.png deleted file mode 100644 index 541d27d..0000000 Binary files a/site/_images/transfer-volume-between-projects-horizon-16_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-horizon-17_creodias.png b/site/_images/transfer-volume-between-projects-horizon-17_creodias.png deleted file mode 100644 index b421263..0000000 Binary files a/site/_images/transfer-volume-between-projects-horizon-17_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-horizon-18_creodias.png b/site/_images/transfer-volume-between-projects-horizon-18_creodias.png deleted file mode 100644 index cb7ff31..0000000 Binary files a/site/_images/transfer-volume-between-projects-horizon-18_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-horizon-19_creodias.png b/site/_images/transfer-volume-between-projects-horizon-19_creodias.png deleted file mode 100644 index 762cdac..0000000 Binary files a/site/_images/transfer-volume-between-projects-horizon-19_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-horizon-20_creodias.png b/site/_images/transfer-volume-between-projects-horizon-20_creodias.png deleted file mode 100644 index 251e58c..0000000 Binary files a/site/_images/transfer-volume-between-projects-horizon-20_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-horizon-21_creodias.png b/site/_images/transfer-volume-between-projects-horizon-21_creodias.png deleted file mode 100644 index f0be344..0000000 Binary files a/site/_images/transfer-volume-between-projects-horizon-21_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-horizon-32_creodias.png b/site/_images/transfer-volume-between-projects-horizon-32_creodias.png deleted file mode 100644 index 9ea84c8..0000000 Binary files a/site/_images/transfer-volume-between-projects-horizon-32_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-horizon-33_creodias.png b/site/_images/transfer-volume-between-projects-horizon-33_creodias.png deleted file mode 100644 index 67da5cc..0000000 Binary files a/site/_images/transfer-volume-between-projects-horizon-33_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-horizon-35_creodias.png b/site/_images/transfer-volume-between-projects-horizon-35_creodias.png deleted file mode 100644 index c0e8be8..0000000 Binary files a/site/_images/transfer-volume-between-projects-horizon-35_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-horizon-36_creodias.png b/site/_images/transfer-volume-between-projects-horizon-36_creodias.png deleted file mode 100644 index 4754b6d..0000000 Binary files a/site/_images/transfer-volume-between-projects-horizon-36_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-horizon-37_creodias.png b/site/_images/transfer-volume-between-projects-horizon-37_creodias.png deleted file mode 100644 index 118546c..0000000 Binary files a/site/_images/transfer-volume-between-projects-horizon-37_creodias.png and /dev/null differ diff --git a/site/_images/transfer-volume-between-projects-horizon-38_creodias.png b/site/_images/transfer-volume-between-projects-horizon-38_creodias.png deleted file mode 100644 index 3dfcd45..0000000 Binary files a/site/_images/transfer-volume-between-projects-horizon-38_creodias.png and /dev/null differ diff --git a/site/_images/unable_to_create_a_cluster.png b/site/_images/unable_to_create_a_cluster.png deleted file mode 100644 index 0ba9ed5..0000000 Binary files a/site/_images/unable_to_create_a_cluster.png and /dev/null differ diff --git a/site/_images/unavailable_network.png b/site/_images/unavailable_network.png deleted file mode 100644 index 1b037c9..0000000 Binary files a/site/_images/unavailable_network.png and /dev/null differ diff --git a/site/_images/unsealing_the_pod.png b/site/_images/unsealing_the_pod.png deleted file mode 100644 index b8654de..0000000 Binary files a/site/_images/unsealing_the_pod.png and /dev/null differ diff --git a/site/_images/upgrade-kubernetes-1.png b/site/_images/upgrade-kubernetes-1.png deleted file mode 100644 index b0bcb98..0000000 Binary files a/site/_images/upgrade-kubernetes-1.png and /dev/null differ diff --git a/site/_images/upgrade-kubernetes-10.png b/site/_images/upgrade-kubernetes-10.png deleted file mode 100644 index 3b272d8..0000000 Binary files a/site/_images/upgrade-kubernetes-10.png and /dev/null differ diff --git a/site/_images/upgrade-kubernetes-11.png b/site/_images/upgrade-kubernetes-11.png deleted file mode 100644 index 1322fa6..0000000 Binary files a/site/_images/upgrade-kubernetes-11.png and /dev/null differ diff --git a/site/_images/upgrade-kubernetes-15.png b/site/_images/upgrade-kubernetes-15.png deleted file mode 100644 index 48133fa..0000000 Binary files a/site/_images/upgrade-kubernetes-15.png and /dev/null differ diff --git a/site/_images/upgrade-kubernetes-17.png b/site/_images/upgrade-kubernetes-17.png deleted file mode 100644 index d657285..0000000 Binary files a/site/_images/upgrade-kubernetes-17.png and /dev/null differ diff --git a/site/_images/upload-image-cli-01_creodias.png b/site/_images/upload-image-cli-01_creodias.png deleted file mode 100644 index 7429cf7..0000000 Binary files a/site/_images/upload-image-cli-01_creodias.png and /dev/null differ diff --git a/site/_images/upload-image-cli-02_creodias.png b/site/_images/upload-image-cli-02_creodias.png deleted file mode 100644 index ac628e6..0000000 Binary files a/site/_images/upload-image-cli-02_creodias.png and /dev/null differ diff --git a/site/_images/upload-image-cli-03_creodias.png b/site/_images/upload-image-cli-03_creodias.png deleted file mode 100644 index 3a744e9..0000000 Binary files a/site/_images/upload-image-cli-03_creodias.png and /dev/null differ diff --git a/site/_images/upload-image-cli-10_creodias.png b/site/_images/upload-image-cli-10_creodias.png deleted file mode 100644 index 77f53d7..0000000 Binary files a/site/_images/upload-image-cli-10_creodias.png and /dev/null differ diff --git a/site/_images/upload-image-cli-11_creodias.png b/site/_images/upload-image-cli-11_creodias.png deleted file mode 100644 index 24770ad..0000000 Binary files a/site/_images/upload-image-cli-11_creodias.png and /dev/null differ diff --git a/site/_images/upload-image-cli-12_creodias.png b/site/_images/upload-image-cli-12_creodias.png deleted file mode 100644 index 174d448..0000000 Binary files a/site/_images/upload-image-cli-12_creodias.png and /dev/null differ diff --git a/site/_images/upload-image-horizon-01_creodias.png b/site/_images/upload-image-horizon-01_creodias.png deleted file mode 100644 index 5f7b902..0000000 Binary files a/site/_images/upload-image-horizon-01_creodias.png and /dev/null differ diff --git a/site/_images/upload-image-horizon-02_creodias.png b/site/_images/upload-image-horizon-02_creodias.png deleted file mode 100644 index fdbda22..0000000 Binary files a/site/_images/upload-image-horizon-02_creodias.png and /dev/null differ diff --git a/site/_images/upload-image-horizon-03_creodias.png b/site/_images/upload-image-horizon-03_creodias.png deleted file mode 100644 index ab30afb..0000000 Binary files a/site/_images/upload-image-horizon-03_creodias.png and /dev/null differ diff --git a/site/_images/upload-image-horizon-04_creodias.png b/site/_images/upload-image-horizon-04_creodias.png deleted file mode 100644 index 9d77303..0000000 Binary files a/site/_images/upload-image-horizon-04_creodias.png and /dev/null differ diff --git a/site/_images/upload-image-horizon-07_creodias.png b/site/_images/upload-image-horizon-07_creodias.png deleted file mode 100644 index d55fa2a..0000000 Binary files a/site/_images/upload-image-horizon-07_creodias.png and /dev/null differ diff --git a/site/_images/upload-image-horizon-08_creodias.png b/site/_images/upload-image-horizon-08_creodias.png deleted file mode 100644 index 645a0b8..0000000 Binary files a/site/_images/upload-image-horizon-08_creodias.png and /dev/null differ diff --git a/site/_images/upload-image-horizon-10_creodias.png b/site/_images/upload-image-horizon-10_creodias.png deleted file mode 100644 index 174d448..0000000 Binary files a/site/_images/upload-image-horizon-10_creodias.png and /dev/null differ diff --git a/site/_images/use-docker-4.png b/site/_images/use-docker-4.png deleted file mode 100644 index 23be291..0000000 Binary files a/site/_images/use-docker-4.png and /dev/null differ diff --git a/site/_images/use-docker-5.png b/site/_images/use-docker-5.png deleted file mode 100644 index ff770fc..0000000 Binary files a/site/_images/use-docker-5.png and /dev/null differ diff --git a/site/_images/use-docker-6.png b/site/_images/use-docker-6.png deleted file mode 100644 index 72e1d7f..0000000 Binary files a/site/_images/use-docker-6.png and /dev/null differ diff --git a/site/_images/use-docker-7.png b/site/_images/use-docker-7.png deleted file mode 100644 index e911205..0000000 Binary files a/site/_images/use-docker-7.png and /dev/null differ diff --git a/site/_images/use-docker-9.png b/site/_images/use-docker-9.png deleted file mode 100644 index a71e66c..0000000 Binary files a/site/_images/use-docker-9.png and /dev/null differ diff --git a/site/_images/use-object-storage-01_creodias.png b/site/_images/use-object-storage-01_creodias.png deleted file mode 100644 index 2de1eb1..0000000 Binary files a/site/_images/use-object-storage-01_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-02_creodias.png b/site/_images/use-object-storage-02_creodias.png deleted file mode 100644 index ecbfd1d..0000000 Binary files a/site/_images/use-object-storage-02_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-03_creodias.png b/site/_images/use-object-storage-03_creodias.png deleted file mode 100644 index be49d5d..0000000 Binary files a/site/_images/use-object-storage-03_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-04_creodias.png b/site/_images/use-object-storage-04_creodias.png deleted file mode 100644 index 174e290..0000000 Binary files a/site/_images/use-object-storage-04_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-05_creodias.png b/site/_images/use-object-storage-05_creodias.png deleted file mode 100644 index 5ed131a..0000000 Binary files a/site/_images/use-object-storage-05_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-06_creodias.png b/site/_images/use-object-storage-06_creodias.png deleted file mode 100644 index cf0ce12..0000000 Binary files a/site/_images/use-object-storage-06_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-07_creodias.png b/site/_images/use-object-storage-07_creodias.png deleted file mode 100644 index 880ab2f..0000000 Binary files a/site/_images/use-object-storage-07_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-08_creodias.png b/site/_images/use-object-storage-08_creodias.png deleted file mode 100644 index 7751ab5..0000000 Binary files a/site/_images/use-object-storage-08_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-09_creodias.png b/site/_images/use-object-storage-09_creodias.png deleted file mode 100644 index 64f32dd..0000000 Binary files a/site/_images/use-object-storage-09_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-10_creodias.png b/site/_images/use-object-storage-10_creodias.png deleted file mode 100644 index 1556e27..0000000 Binary files a/site/_images/use-object-storage-10_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-11_creodias.png b/site/_images/use-object-storage-11_creodias.png deleted file mode 100644 index 0141daf..0000000 Binary files a/site/_images/use-object-storage-11_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-13_creodias.png b/site/_images/use-object-storage-13_creodias.png deleted file mode 100644 index 37e406a..0000000 Binary files a/site/_images/use-object-storage-13_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-14_creodias.png b/site/_images/use-object-storage-14_creodias.png deleted file mode 100644 index fd371a1..0000000 Binary files a/site/_images/use-object-storage-14_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-15_creodias.png b/site/_images/use-object-storage-15_creodias.png deleted file mode 100644 index 97e049b..0000000 Binary files a/site/_images/use-object-storage-15_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-16_creodias.png b/site/_images/use-object-storage-16_creodias.png deleted file mode 100644 index e96978c..0000000 Binary files a/site/_images/use-object-storage-16_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-17_creodias.png b/site/_images/use-object-storage-17_creodias.png deleted file mode 100644 index 9ab6b2a..0000000 Binary files a/site/_images/use-object-storage-17_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-18_creodias.png b/site/_images/use-object-storage-18_creodias.png deleted file mode 100644 index 53dc40b..0000000 Binary files a/site/_images/use-object-storage-18_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-19_creodias.png b/site/_images/use-object-storage-19_creodias.png deleted file mode 100644 index 055fd24..0000000 Binary files a/site/_images/use-object-storage-19_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-delete-delete-selected_creodias.png b/site/_images/use-object-storage-delete-delete-selected_creodias.png deleted file mode 100644 index 6d9f44d..0000000 Binary files a/site/_images/use-object-storage-delete-delete-selected_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-delete-folder_creodias.png b/site/_images/use-object-storage-delete-folder_creodias.png deleted file mode 100644 index 5ad8e14..0000000 Binary files a/site/_images/use-object-storage-delete-folder_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-new-container_creodias.png b/site/_images/use-object-storage-new-container_creodias.png deleted file mode 100644 index 1593074..0000000 Binary files a/site/_images/use-object-storage-new-container_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-new-folder_creodias.png b/site/_images/use-object-storage-new-folder_creodias.png deleted file mode 100644 index d2623b6..0000000 Binary files a/site/_images/use-object-storage-new-folder_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-success_creodias.png b/site/_images/use-object-storage-success_creodias.png deleted file mode 100644 index dcfe31d..0000000 Binary files a/site/_images/use-object-storage-success_creodias.png and /dev/null differ diff --git a/site/_images/use-object-storage-upload_creodias.png b/site/_images/use-object-storage-upload_creodias.png deleted file mode 100644 index 5f97371..0000000 Binary files a/site/_images/use-object-storage-upload_creodias.png and /dev/null differ diff --git a/site/_images/use-script-rotating-backups-01_creodias.png b/site/_images/use-script-rotating-backups-01_creodias.png deleted file mode 100644 index 67f5240..0000000 Binary files a/site/_images/use-script-rotating-backups-01_creodias.png and /dev/null differ diff --git a/site/_images/use-script-rotating-backups-02_creodias.png b/site/_images/use-script-rotating-backups-02_creodias.png deleted file mode 100644 index 34d2201..0000000 Binary files a/site/_images/use-script-rotating-backups-02_creodias.png and /dev/null differ diff --git a/site/_images/use-script-rotating-backups-03_creodias.png b/site/_images/use-script-rotating-backups-03_creodias.png deleted file mode 100644 index 686090a..0000000 Binary files a/site/_images/use-script-rotating-backups-03_creodias.png and /dev/null differ diff --git a/site/_images/use-script-rotating-backups-04_creodias.png b/site/_images/use-script-rotating-backups-04_creodias.png deleted file mode 100644 index bd0138b..0000000 Binary files a/site/_images/use-script-rotating-backups-04_creodias.png and /dev/null differ diff --git a/site/_images/use-script-rotating-backups-05_creodias.png b/site/_images/use-script-rotating-backups-05_creodias.png deleted file mode 100644 index 5928bf4..0000000 Binary files a/site/_images/use-script-rotating-backups-05_creodias.png and /dev/null differ diff --git a/site/_images/use-security-groups-1_creodias.png b/site/_images/use-security-groups-1_creodias.png deleted file mode 100644 index 83b2bcf..0000000 Binary files a/site/_images/use-security-groups-1_creodias.png and /dev/null differ diff --git a/site/_images/use-security-groups-2_creodias.png b/site/_images/use-security-groups-2_creodias.png deleted file mode 100644 index e21a31b..0000000 Binary files a/site/_images/use-security-groups-2_creodias.png and /dev/null differ diff --git a/site/_images/use-security-groups-3_creodias.png b/site/_images/use-security-groups-3_creodias.png deleted file mode 100644 index 53ae139..0000000 Binary files a/site/_images/use-security-groups-3_creodias.png and /dev/null differ diff --git a/site/_images/use-security-groups-4_creodias.png b/site/_images/use-security-groups-4_creodias.png deleted file mode 100644 index 706d3d9..0000000 Binary files a/site/_images/use-security-groups-4_creodias.png and /dev/null differ diff --git a/site/_images/use-security-groups-5_creodias.png b/site/_images/use-security-groups-5_creodias.png deleted file mode 100644 index 4fa1db6..0000000 Binary files a/site/_images/use-security-groups-5_creodias.png and /dev/null differ diff --git a/site/_images/use-security-groups-6_creodias.png b/site/_images/use-security-groups-6_creodias.png deleted file mode 100644 index 6b9f68f..0000000 Binary files a/site/_images/use-security-groups-6_creodias.png and /dev/null differ diff --git a/site/_images/use-security-groups-7_creodias.png b/site/_images/use-security-groups-7_creodias.png deleted file mode 100644 index 2267221..0000000 Binary files a/site/_images/use-security-groups-7_creodias.png and /dev/null differ diff --git a/site/_images/use_125_version.png b/site/_images/use_125_version.png deleted file mode 100644 index 9fd49a7..0000000 Binary files a/site/_images/use_125_version.png and /dev/null differ diff --git a/site/_images/use_an_existing_network.png b/site/_images/use_an_existing_network.png deleted file mode 100644 index dfb1414..0000000 Binary files a/site/_images/use_an_existing_network.png and /dev/null differ diff --git a/site/_images/user-roles-list-1.png b/site/_images/user-roles-list-1.png deleted file mode 100644 index 997f259..0000000 Binary files a/site/_images/user-roles-list-1.png and /dev/null differ diff --git a/site/_images/user-roles-list-2.png b/site/_images/user-roles-list-2.png deleted file mode 100644 index 9c95382..0000000 Binary files a/site/_images/user-roles-list-2.png and /dev/null differ diff --git a/site/_images/user-roles-list-create-1.png b/site/_images/user-roles-list-create-1.png deleted file mode 100644 index cc7930b..0000000 Binary files a/site/_images/user-roles-list-create-1.png and /dev/null differ diff --git a/site/_images/user-roles-list-create-2.png b/site/_images/user-roles-list-create-2.png deleted file mode 100644 index e7c07a2..0000000 Binary files a/site/_images/user-roles-list-create-2.png and /dev/null differ diff --git a/site/_images/user-roles-list-create-3.png b/site/_images/user-roles-list-create-3.png deleted file mode 100644 index c93d43c..0000000 Binary files a/site/_images/user-roles-list-create-3.png and /dev/null differ diff --git a/site/_images/user-roles-list-create-4.png b/site/_images/user-roles-list-create-4.png deleted file mode 100644 index 07f16d9..0000000 Binary files a/site/_images/user-roles-list-create-4.png and /dev/null differ diff --git a/site/_images/user-roles-list-create-5.png b/site/_images/user-roles-list-create-5.png deleted file mode 100644 index 313a684..0000000 Binary files a/site/_images/user-roles-list-create-5.png and /dev/null differ diff --git a/site/_images/user-roles-list-create-6.png b/site/_images/user-roles-list-create-6.png deleted file mode 100644 index d904438..0000000 Binary files a/site/_images/user-roles-list-create-6.png and /dev/null differ diff --git a/site/_images/user_credentials.png b/site/_images/user_credentials.png deleted file mode 100644 index 0c799c3..0000000 Binary files a/site/_images/user_credentials.png and /dev/null differ diff --git a/site/_images/users.png b/site/_images/users.png deleted file mode 100644 index 14ae430..0000000 Binary files a/site/_images/users.png and /dev/null differ diff --git a/site/_images/users_roles_01_3Enginescloud.png b/site/_images/users_roles_01_3Enginescloud.png deleted file mode 100644 index a18f57e..0000000 Binary files a/site/_images/users_roles_01_3Enginescloud.png and /dev/null differ diff --git a/site/_images/uses_ephemeral.png b/site/_images/uses_ephemeral.png deleted file mode 100644 index f437821..0000000 Binary files a/site/_images/uses_ephemeral.png and /dev/null differ diff --git a/site/_images/value_of_spot.png b/site/_images/value_of_spot.png deleted file mode 100644 index 646d717..0000000 Binary files a/site/_images/value_of_spot.png and /dev/null differ diff --git a/site/_images/vault_created.png b/site/_images/vault_created.png deleted file mode 100644 index 8e62af7..0000000 Binary files a/site/_images/vault_created.png and /dev/null differ diff --git a/site/_images/velero_version_working.png b/site/_images/velero_version_working.png deleted file mode 100644 index 7952c5b..0000000 Binary files a/site/_images/velero_version_working.png and /dev/null differ diff --git a/site/_images/vim_editor_change.png b/site/_images/vim_editor_change.png deleted file mode 100644 index 8a2c820..0000000 Binary files a/site/_images/vim_editor_change.png and /dev/null differ diff --git a/site/_images/vol1.png b/site/_images/vol1.png deleted file mode 100644 index 05a054c..0000000 Binary files a/site/_images/vol1.png and /dev/null differ diff --git a/site/_images/vol2.png b/site/_images/vol2.png deleted file mode 100644 index e2c48e1..0000000 Binary files a/site/_images/vol2.png and /dev/null differ diff --git a/site/_images/vol3.png b/site/_images/vol3.png deleted file mode 100644 index 5f8df2c..0000000 Binary files a/site/_images/vol3.png and /dev/null differ diff --git a/site/_images/vol4.png b/site/_images/vol4.png deleted file mode 100644 index 9ad72b9..0000000 Binary files a/site/_images/vol4.png and /dev/null differ diff --git a/site/_images/vol5.png b/site/_images/vol5.png deleted file mode 100644 index f1e717a..0000000 Binary files a/site/_images/vol5.png and /dev/null differ diff --git a/site/_images/vol6.png b/site/_images/vol6.png deleted file mode 100644 index da65997..0000000 Binary files a/site/_images/vol6.png and /dev/null differ diff --git a/site/_images/volno1.png b/site/_images/volno1.png deleted file mode 100644 index bcea58c..0000000 Binary files a/site/_images/volno1.png and /dev/null differ diff --git a/site/_images/volno2.png b/site/_images/volno2.png deleted file mode 100644 index c3688b5..0000000 Binary files a/site/_images/volno2.png and /dev/null differ diff --git a/site/_images/volno3.png b/site/_images/volno3.png deleted file mode 100644 index 1c7a2c4..0000000 Binary files a/site/_images/volno3.png and /dev/null differ diff --git a/site/_images/volno4.png b/site/_images/volno4.png deleted file mode 100644 index c413573..0000000 Binary files a/site/_images/volno4.png and /dev/null differ diff --git a/site/_images/volno5.png b/site/_images/volno5.png deleted file mode 100644 index f197cd9..0000000 Binary files a/site/_images/volno5.png and /dev/null differ diff --git a/site/_images/volsnap1.png b/site/_images/volsnap1.png deleted file mode 100644 index 644f5e5..0000000 Binary files a/site/_images/volsnap1.png and /dev/null differ diff --git a/site/_images/volsnap2.png b/site/_images/volsnap2.png deleted file mode 100644 index db1db53..0000000 Binary files a/site/_images/volsnap2.png and /dev/null differ diff --git a/site/_images/volsnap3.png b/site/_images/volsnap3.png deleted file mode 100644 index f034ed2..0000000 Binary files a/site/_images/volsnap3.png and /dev/null differ diff --git a/site/_images/volsnap4.png b/site/_images/volsnap4.png deleted file mode 100644 index d193b91..0000000 Binary files a/site/_images/volsnap4.png and /dev/null differ diff --git a/site/_images/volsnap5.png b/site/_images/volsnap5.png deleted file mode 100644 index cb95f98..0000000 Binary files a/site/_images/volsnap5.png and /dev/null differ diff --git a/site/_images/volume-backup-01_creodias.png b/site/_images/volume-backup-01_creodias.png deleted file mode 100644 index e7c6f95..0000000 Binary files a/site/_images/volume-backup-01_creodias.png and /dev/null differ diff --git a/site/_images/volume-backup-02_creodias.png b/site/_images/volume-backup-02_creodias.png deleted file mode 100644 index fea00c3..0000000 Binary files a/site/_images/volume-backup-02_creodias.png and /dev/null differ diff --git a/site/_images/volume-backup-03_creodias.png b/site/_images/volume-backup-03_creodias.png deleted file mode 100644 index 394d592..0000000 Binary files a/site/_images/volume-backup-03_creodias.png and /dev/null differ diff --git a/site/_images/volume-backup-04_creodias.png b/site/_images/volume-backup-04_creodias.png deleted file mode 100644 index e9194fc..0000000 Binary files a/site/_images/volume-backup-04_creodias.png and /dev/null differ diff --git a/site/_images/volume-backup-05_creodias.png b/site/_images/volume-backup-05_creodias.png deleted file mode 100644 index ae24070..0000000 Binary files a/site/_images/volume-backup-05_creodias.png and /dev/null differ diff --git a/site/_images/volume-backup-06_creodias.png b/site/_images/volume-backup-06_creodias.png deleted file mode 100644 index 6989185..0000000 Binary files a/site/_images/volume-backup-06_creodias.png and /dev/null differ diff --git a/site/_images/volume-backup-07_creodias.png b/site/_images/volume-backup-07_creodias.png deleted file mode 100644 index 7fc3c83..0000000 Binary files a/site/_images/volume-backup-07_creodias.png and /dev/null differ diff --git a/site/_images/volume-backup-08_creodias.png b/site/_images/volume-backup-08_creodias.png deleted file mode 100644 index d12a340..0000000 Binary files a/site/_images/volume-backup-08_creodias.png and /dev/null differ diff --git a/site/_images/volume-backup-09_creodias.png b/site/_images/volume-backup-09_creodias.png deleted file mode 100644 index 1d9f8cf..0000000 Binary files a/site/_images/volume-backup-09_creodias.png and /dev/null differ diff --git a/site/_images/volume-backup-10_creodias.png b/site/_images/volume-backup-10_creodias.png deleted file mode 100644 index dddde0f..0000000 Binary files a/site/_images/volume-backup-10_creodias.png and /dev/null differ diff --git a/site/_images/volume-backup-11_creodias.png b/site/_images/volume-backup-11_creodias.png deleted file mode 100644 index bdcd749..0000000 Binary files a/site/_images/volume-backup-11_creodias.png and /dev/null differ diff --git a/site/_images/volume-backup-12_creodias.png b/site/_images/volume-backup-12_creodias.png deleted file mode 100644 index 815e66e..0000000 Binary files a/site/_images/volume-backup-12_creodias.png and /dev/null differ diff --git a/site/_images/volume-backup-13_creodias.png b/site/_images/volume-backup-13_creodias.png deleted file mode 100644 index 550f973..0000000 Binary files a/site/_images/volume-backup-13_creodias.png and /dev/null differ diff --git a/site/_images/volume-backup-14_creodias.png b/site/_images/volume-backup-14_creodias.png deleted file mode 100644 index 8933017..0000000 Binary files a/site/_images/volume-backup-14_creodias.png and /dev/null differ diff --git a/site/_images/volume-backup-15_creodias.png b/site/_images/volume-backup-15_creodias.png deleted file mode 100644 index 3c0ad1d..0000000 Binary files a/site/_images/volume-backup-15_creodias.png and /dev/null differ diff --git a/site/_images/volume-backup-16_creodias.png b/site/_images/volume-backup-16_creodias.png deleted file mode 100644 index 03b8b37..0000000 Binary files a/site/_images/volume-backup-16_creodias.png and /dev/null differ diff --git a/site/_images/volume-backup-17_creodias.png b/site/_images/volume-backup-17_creodias.png deleted file mode 100644 index a75c949..0000000 Binary files a/site/_images/volume-backup-17_creodias.png and /dev/null differ diff --git a/site/_images/volume-backup-18_creodias.png b/site/_images/volume-backup-18_creodias.png deleted file mode 100644 index b2b6a07..0000000 Binary files a/site/_images/volume-backup-18_creodias.png and /dev/null differ diff --git a/site/_images/volume-less-01_creodias.png b/site/_images/volume-less-01_creodias.png deleted file mode 100644 index dd356d3..0000000 Binary files a/site/_images/volume-less-01_creodias.png and /dev/null differ diff --git a/site/_images/volume-less-02_creodias.png b/site/_images/volume-less-02_creodias.png deleted file mode 100644 index e4bfe53..0000000 Binary files a/site/_images/volume-less-02_creodias.png and /dev/null differ diff --git a/site/_images/volume-less-03_creodias.png b/site/_images/volume-less-03_creodias.png deleted file mode 100644 index e912c37..0000000 Binary files a/site/_images/volume-less-03_creodias.png and /dev/null differ diff --git a/site/_images/volume-less-04_creodias.png b/site/_images/volume-less-04_creodias.png deleted file mode 100644 index 84ea25f..0000000 Binary files a/site/_images/volume-less-04_creodias.png and /dev/null differ diff --git a/site/_images/volume-less-05_creodias.png b/site/_images/volume-less-05_creodias.png deleted file mode 100644 index 5a5824a..0000000 Binary files a/site/_images/volume-less-05_creodias.png and /dev/null differ diff --git a/site/_images/volume-less-06_creodias.png b/site/_images/volume-less-06_creodias.png deleted file mode 100644 index 223486b..0000000 Binary files a/site/_images/volume-less-06_creodias.png and /dev/null differ diff --git a/site/_images/volume-less-07_creodias.png b/site/_images/volume-less-07_creodias.png deleted file mode 100644 index d8f6456..0000000 Binary files a/site/_images/volume-less-07_creodias.png and /dev/null differ diff --git a/site/_images/volume-less-08_creodias.png b/site/_images/volume-less-08_creodias.png deleted file mode 100644 index e2fba3c..0000000 Binary files a/site/_images/volume-less-08_creodias.png and /dev/null differ diff --git a/site/_images/volume-less-09_creodias.png b/site/_images/volume-less-09_creodias.png deleted file mode 100644 index b1ed092..0000000 Binary files a/site/_images/volume-less-09_creodias.png and /dev/null differ diff --git a/site/_images/volume-less-10_creodias.png b/site/_images/volume-less-10_creodias.png deleted file mode 100644 index 188912d..0000000 Binary files a/site/_images/volume-less-10_creodias.png and /dev/null differ diff --git a/site/_images/volume-less-11_creodias.png b/site/_images/volume-less-11_creodias.png deleted file mode 100644 index 88316d3..0000000 Binary files a/site/_images/volume-less-11_creodias.png and /dev/null differ diff --git a/site/_images/volume-more-01_creodias.png b/site/_images/volume-more-01_creodias.png deleted file mode 100644 index dd356d3..0000000 Binary files a/site/_images/volume-more-01_creodias.png and /dev/null differ diff --git a/site/_images/volume-more-02_creodias.png b/site/_images/volume-more-02_creodias.png deleted file mode 100644 index e4bfe53..0000000 Binary files a/site/_images/volume-more-02_creodias.png and /dev/null differ diff --git a/site/_images/volume-more-03_creodias.png b/site/_images/volume-more-03_creodias.png deleted file mode 100644 index d8bf2ec..0000000 Binary files a/site/_images/volume-more-03_creodias.png and /dev/null differ diff --git a/site/_images/volume-more-04_creodias.png b/site/_images/volume-more-04_creodias.png deleted file mode 100644 index 57b8932..0000000 Binary files a/site/_images/volume-more-04_creodias.png and /dev/null differ diff --git a/site/_images/volume-more-05_creodias.png b/site/_images/volume-more-05_creodias.png deleted file mode 100644 index a6adaf9..0000000 Binary files a/site/_images/volume-more-05_creodias.png and /dev/null differ diff --git a/site/_images/volume-more-06_creodias.png b/site/_images/volume-more-06_creodias.png deleted file mode 100644 index 4e6bf5a..0000000 Binary files a/site/_images/volume-more-06_creodias.png and /dev/null differ diff --git a/site/_images/volume-more-07_creodias.png b/site/_images/volume-more-07_creodias.png deleted file mode 100644 index 930a9cc..0000000 Binary files a/site/_images/volume-more-07_creodias.png and /dev/null differ diff --git a/site/_images/volume-more-08_creodias.png b/site/_images/volume-more-08_creodias.png deleted file mode 100644 index 084fdf0..0000000 Binary files a/site/_images/volume-more-08_creodias.png and /dev/null differ diff --git a/site/_images/volume-more-09_creodias.png b/site/_images/volume-more-09_creodias.png deleted file mode 100644 index 3cedbfc..0000000 Binary files a/site/_images/volume-more-09_creodias.png and /dev/null differ diff --git a/site/_images/volume-more-10_creodias.png b/site/_images/volume-more-10_creodias.png deleted file mode 100644 index 188912d..0000000 Binary files a/site/_images/volume-more-10_creodias.png and /dev/null differ diff --git a/site/_images/volume-more-11_creodias.png b/site/_images/volume-more-11_creodias.png deleted file mode 100644 index f5fb763..0000000 Binary files a/site/_images/volume-more-11_creodias.png and /dev/null differ diff --git a/site/_images/volumes.png b/site/_images/volumes.png deleted file mode 100644 index cc419c5..0000000 Binary files a/site/_images/volumes.png and /dev/null differ diff --git a/site/_images/volyes1.png b/site/_images/volyes1.png deleted file mode 100644 index ba8f2bc..0000000 Binary files a/site/_images/volyes1.png and /dev/null differ diff --git a/site/_images/volyes10.png b/site/_images/volyes10.png deleted file mode 100644 index 6eaf4c7..0000000 Binary files a/site/_images/volyes10.png and /dev/null differ diff --git a/site/_images/volyes11.png b/site/_images/volyes11.png deleted file mode 100644 index 0f6f3f9..0000000 Binary files a/site/_images/volyes11.png and /dev/null differ diff --git a/site/_images/volyes12.png b/site/_images/volyes12.png deleted file mode 100644 index b6cf398..0000000 Binary files a/site/_images/volyes12.png and /dev/null differ diff --git a/site/_images/volyes13.png b/site/_images/volyes13.png deleted file mode 100644 index f31874b..0000000 Binary files a/site/_images/volyes13.png and /dev/null differ diff --git a/site/_images/volyes14.png b/site/_images/volyes14.png deleted file mode 100644 index 273c0c3..0000000 Binary files a/site/_images/volyes14.png and /dev/null differ diff --git a/site/_images/volyes15.png b/site/_images/volyes15.png deleted file mode 100644 index 1b49e3d..0000000 Binary files a/site/_images/volyes15.png and /dev/null differ diff --git a/site/_images/volyes16.png b/site/_images/volyes16.png deleted file mode 100644 index 5bed0ad..0000000 Binary files a/site/_images/volyes16.png and /dev/null differ diff --git a/site/_images/volyes2.png b/site/_images/volyes2.png deleted file mode 100644 index 16c986d..0000000 Binary files a/site/_images/volyes2.png and /dev/null differ diff --git a/site/_images/volyes3.png b/site/_images/volyes3.png deleted file mode 100644 index 67ff79a..0000000 Binary files a/site/_images/volyes3.png and /dev/null differ diff --git a/site/_images/volyes4.png b/site/_images/volyes4.png deleted file mode 100644 index 1ee177d..0000000 Binary files a/site/_images/volyes4.png and /dev/null differ diff --git a/site/_images/volyes5.png b/site/_images/volyes5.png deleted file mode 100644 index f72a94d..0000000 Binary files a/site/_images/volyes5.png and /dev/null differ diff --git a/site/_images/volyes6.png b/site/_images/volyes6.png deleted file mode 100644 index bb29abd..0000000 Binary files a/site/_images/volyes6.png and /dev/null differ diff --git a/site/_images/volyes7.png b/site/_images/volyes7.png deleted file mode 100644 index d24915d..0000000 Binary files a/site/_images/volyes7.png and /dev/null differ diff --git a/site/_images/volyes8.png b/site/_images/volyes8.png deleted file mode 100644 index 622f4fc..0000000 Binary files a/site/_images/volyes8.png and /dev/null differ diff --git a/site/_images/volyes9.png b/site/_images/volyes9.png deleted file mode 100644 index c496173..0000000 Binary files a/site/_images/volyes9.png and /dev/null differ diff --git a/site/_images/wallets_contracts_3Enginescloud.png b/site/_images/wallets_contracts_3Enginescloud.png deleted file mode 100644 index ed5adb9..0000000 Binary files a/site/_images/wallets_contracts_3Enginescloud.png and /dev/null differ diff --git a/site/_images/waw3-1-default.png b/site/_images/waw3-1-default.png deleted file mode 100644 index 65b144e..0000000 Binary files a/site/_images/waw3-1-default.png and /dev/null differ diff --git a/site/_images/waw3-2-cloud-activated.png b/site/_images/waw3-2-cloud-activated.png deleted file mode 100644 index 5333b57..0000000 Binary files a/site/_images/waw3-2-cloud-activated.png and /dev/null differ diff --git a/site/_images/waw3-2-default_templates.png b/site/_images/waw3-2-default_templates.png deleted file mode 100644 index a34fc4a..0000000 Binary files a/site/_images/waw3-2-default_templates.png and /dev/null differ diff --git a/site/_images/waw4-1-cluster-templates-2.png b/site/_images/waw4-1-cluster-templates-2.png deleted file mode 100644 index 66b4ca1..0000000 Binary files a/site/_images/waw4-1-cluster-templates-2.png and /dev/null differ diff --git a/site/_images/welcome_nginx.png b/site/_images/welcome_nginx.png deleted file mode 100644 index b8bc482..0000000 Binary files a/site/_images/welcome_nginx.png and /dev/null differ diff --git a/site/_images/white_keypair_select.png b/site/_images/white_keypair_select.png deleted file mode 100644 index 8063e0b..0000000 Binary files a/site/_images/white_keypair_select.png and /dev/null differ diff --git a/site/_images/whitelisting-loadbalancer-1.png b/site/_images/whitelisting-loadbalancer-1.png deleted file mode 100644 index b95fd36..0000000 Binary files a/site/_images/whitelisting-loadbalancer-1.png and /dev/null differ diff --git a/site/_images/whitelisting-loadbalancer-4.png b/site/_images/whitelisting-loadbalancer-4.png deleted file mode 100644 index 7dc495d..0000000 Binary files a/site/_images/whitelisting-loadbalancer-4.png and /dev/null differ diff --git a/site/_images/whitelisting-loadbalancer-5.png b/site/_images/whitelisting-loadbalancer-5.png deleted file mode 100644 index 998bb31..0000000 Binary files a/site/_images/whitelisting-loadbalancer-5.png and /dev/null differ diff --git a/site/_images/whitelisting_again-1.png b/site/_images/whitelisting_again-1.png deleted file mode 100644 index 6cf313b..0000000 Binary files a/site/_images/whitelisting_again-1.png and /dev/null differ diff --git a/site/_images/whitelisting_again-2.png b/site/_images/whitelisting_again-2.png deleted file mode 100644 index c788a67..0000000 Binary files a/site/_images/whitelisting_again-2.png and /dev/null differ diff --git a/site/_images/whitelisting_again-3.png b/site/_images/whitelisting_again-3.png deleted file mode 100644 index 3f9f46d..0000000 Binary files a/site/_images/whitelisting_again-3.png and /dev/null differ diff --git a/site/_images/whitelisting_again-4v2.png b/site/_images/whitelisting_again-4v2.png deleted file mode 100644 index c157ae0..0000000 Binary files a/site/_images/whitelisting_again-4v2.png and /dev/null differ diff --git a/site/_images/whitelisting_again-5v2.png b/site/_images/whitelisting_again-5v2.png deleted file mode 100644 index 8465ee0..0000000 Binary files a/site/_images/whitelisting_again-5v2.png and /dev/null differ diff --git a/site/_images/whitelisting_again-7v2.png b/site/_images/whitelisting_again-7v2.png deleted file mode 100644 index 67f1e1d..0000000 Binary files a/site/_images/whitelisting_again-7v2.png and /dev/null differ diff --git a/site/_images/whitelisting_again-8v2.png b/site/_images/whitelisting_again-8v2.png deleted file mode 100644 index c9bd508..0000000 Binary files a/site/_images/whitelisting_again-8v2.png and /dev/null differ diff --git a/site/_images/whitelisting_again-9v2.png b/site/_images/whitelisting_again-9v2.png deleted file mode 100644 index 701d580..0000000 Binary files a/site/_images/whitelisting_again-9v2.png and /dev/null differ diff --git a/site/_images/worker_nodes_number.png b/site/_images/worker_nodes_number.png deleted file mode 100644 index a856162..0000000 Binary files a/site/_images/worker_nodes_number.png and /dev/null differ diff --git a/site/_images/wsl01_creodias.png b/site/_images/wsl01_creodias.png deleted file mode 100644 index dc82f72..0000000 Binary files a/site/_images/wsl01_creodias.png and /dev/null differ diff --git a/site/_images/wsl02_creodias.png b/site/_images/wsl02_creodias.png deleted file mode 100644 index c9d4788..0000000 Binary files a/site/_images/wsl02_creodias.png and /dev/null differ diff --git a/site/_images/wsl03_creodias.png b/site/_images/wsl03_creodias.png deleted file mode 100644 index 21682ab..0000000 Binary files a/site/_images/wsl03_creodias.png and /dev/null differ diff --git a/site/_images/wsl04_creodias.png b/site/_images/wsl04_creodias.png deleted file mode 100644 index 26a881d..0000000 Binary files a/site/_images/wsl04_creodias.png and /dev/null differ diff --git a/site/_images/wsl05_creodias.png b/site/_images/wsl05_creodias.png deleted file mode 100644 index 91e209e..0000000 Binary files a/site/_images/wsl05_creodias.png and /dev/null differ diff --git a/site/_images/wsl06_creodias.png b/site/_images/wsl06_creodias.png deleted file mode 100644 index 3d6bc91..0000000 Binary files a/site/_images/wsl06_creodias.png and /dev/null differ diff --git a/site/_images/wsl07_creodias.png b/site/_images/wsl07_creodias.png deleted file mode 100644 index 9086259..0000000 Binary files a/site/_images/wsl07_creodias.png and /dev/null differ diff --git a/site/_images/wsl08_creodias.png b/site/_images/wsl08_creodias.png deleted file mode 100644 index 2a7daf4..0000000 Binary files a/site/_images/wsl08_creodias.png and /dev/null differ diff --git a/site/_images/wsl09_creodias.png b/site/_images/wsl09_creodias.png deleted file mode 100644 index 230aa83..0000000 Binary files a/site/_images/wsl09_creodias.png and /dev/null differ diff --git a/site/_images/wsl10_creodias.png b/site/_images/wsl10_creodias.png deleted file mode 100644 index b837d7c..0000000 Binary files a/site/_images/wsl10_creodias.png and /dev/null differ diff --git a/site/_images/wsl11_creodias.png b/site/_images/wsl11_creodias.png deleted file mode 100644 index ddf3a63..0000000 Binary files a/site/_images/wsl11_creodias.png and /dev/null differ diff --git a/site/_images/wsl12_creodias.png b/site/_images/wsl12_creodias.png deleted file mode 100644 index e781eec..0000000 Binary files a/site/_images/wsl12_creodias.png and /dev/null differ diff --git a/site/_images/wsl13_creodias.png b/site/_images/wsl13_creodias.png deleted file mode 100644 index 96364d9..0000000 Binary files a/site/_images/wsl13_creodias.png and /dev/null differ diff --git a/site/_images/wsl14_creodias.png b/site/_images/wsl14_creodias.png deleted file mode 100644 index 2645266..0000000 Binary files a/site/_images/wsl14_creodias.png and /dev/null differ diff --git a/site/_images/wsl15_creodias.png b/site/_images/wsl15_creodias.png deleted file mode 100644 index 20f41c9..0000000 Binary files a/site/_images/wsl15_creodias.png and /dev/null differ diff --git a/site/_images/wsl16_creodias.png b/site/_images/wsl16_creodias.png deleted file mode 100644 index 54f958e..0000000 Binary files a/site/_images/wsl16_creodias.png and /dev/null differ diff --git a/site/_images/wsl17_creodias.png b/site/_images/wsl17_creodias.png deleted file mode 100644 index 7c32a23..0000000 Binary files a/site/_images/wsl17_creodias.png and /dev/null differ diff --git a/site/_images/wsl18_creodias.png b/site/_images/wsl18_creodias.png deleted file mode 100644 index 53615a2..0000000 Binary files a/site/_images/wsl18_creodias.png and /dev/null differ diff --git a/site/_images/wsl19_creodias.png b/site/_images/wsl19_creodias.png deleted file mode 100644 index 9b60c76..0000000 Binary files a/site/_images/wsl19_creodias.png and /dev/null differ diff --git a/site/_images/wsl20_creodias.png b/site/_images/wsl20_creodias.png deleted file mode 100644 index 7f9792f..0000000 Binary files a/site/_images/wsl20_creodias.png and /dev/null differ diff --git a/site/_images/wsl_v1_error_message.png b/site/_images/wsl_v1_error_message.png deleted file mode 100644 index 7c381e8..0000000 Binary files a/site/_images/wsl_v1_error_message.png and /dev/null differ diff --git a/site/_images/yellow_triangles.png b/site/_images/yellow_triangles.png deleted file mode 100644 index 71f17fe..0000000 Binary files a/site/_images/yellow_triangles.png and /dev/null differ diff --git a/site/accountmanagement/Adding-Editing-Organizations.html.html b/site/accountmanagement/Adding-Editing-Organizations.html.html deleted file mode 100644 index 19924ed..0000000 --- a/site/accountmanagement/Adding-Editing-Organizations.html.html +++ /dev/null @@ -1,12 +0,0 @@ - Adding and editing Organization🔗 - 3Engines Documentation

Adding and editing Organization🔗

After logging into https://portal.3Engines.com/ press Organization button on the left bar menu.

register_organization_3Enginescloud.png

In My Organization tab you can register an organization and become its administrator or join an organization if you have invitation code provided by it’s administrator.

To register new organization please fill up all fields marked with * and press Register Organization button. Once you register your organization you will be able to view and edit details.

TAX ID / VAT field is not required but without providing the data you wont be able to complete automatic order or start new contract. VAT field is required if you need to receive invoice with correct tax rate.

After registration, please go back to the left bar menu and select Organization.

In My Organization tab you will be able to:

  • check organization registration date
  • view and edit organization name, address and TAX ID / VAT number
  • manage assignments
\ No newline at end of file diff --git a/site/accountmanagement/Contracts-Wallets.html.html b/site/accountmanagement/Contracts-Wallets.html.html deleted file mode 100644 index 9df7e4b..0000000 --- a/site/accountmanagement/Contracts-Wallets.html.html +++ /dev/null @@ -1,12 +0,0 @@ - Wallets and Contracts Management🔗 - 3Engines Documentation

Wallets and Contracts Management🔗

After logging into https://portal.3Engines.com/ press Wallets/Contracts button on the left menu bar:

wallets_contracts_3Enginescloud.png

you will see the following 3 billing modes:

PPUSE (Pay Per Use Wallet)

This is a prepaid billing mode where services are billed according to usage. Tenant purchases a credit in a form of Billing Units (BU) with are added to his system wallet and are used to provision and keep resources and services. Billing Units (BU) are evaluated to 1 Euro for the sake of Price List. Billing Units (BU) are purchased through e-commerce or written contracts. Every 2 h tenant credit is decreased with the cost of used resources billed with an accuracy of up to 2 seconds. This is a very flexible mode that allows to create and remove resources at will and pay only for the used resources. This is a mode useful for experimental and development work or for environments with very variable resources.

To add an additional wallet please click Add wallet button on the top. To add funds to your already created wallet you need to use Transfer funds option. Please note that a wallet can be deleted once all funds are transferred to another wallet. You can check your billing by clicking Billing report button.

PAYG (Pay As You Go Contract)

This is a postpaid billing mode where Tenants are invoiced periodically based on actual usage. In this mode, a Tenant signs a written contract and is billed usually on monthly bases for actual usage of services and resources. PAYG contracts are purchased only through our sales department in a form of written contracts. With the exception of FIXED-TERM orders all services and resources ordered under Accounts/Projects that are attached to the PAYG contract will be added to the invoice issued at the end of agreed period. Billing is done every 2 hours. Tenants sees the increase in usage with the cost of used resources billed with an accuracy of up to 2 seconds.

To add PAYG wallet you need to raise a ticket first (please check Helpdesk and Support).

FIXED-TERM (Fixed Term Contract)

This is a billing mode where services are bought for longer periods. In this mode, Tenant purchases defined services for defined periods. FIXED-TERM contracts are purchased through e-commerce or written agreements. The long-term resources are paid directly according to price and currency stated. One cannot then change these resources but on the other hand obtains much cheaper offering. This mode is preferable for long-term usage of well-defined environments with well understood needs.

In order to successfully apply FIXED-TERM billing mode to given service in particular billing session, the contract is required to fulfill the following conditions:

  • Be active at the beginning of the session or at the moment when resource is launched;
  • Be active till the end of the 2 hours billing session.

If any of the conditions listed above is not met, service is to be billed in PPU/PAYG mode.

As a result of described billing system behavior, if contract is activated after launching services, FIXED-TERM billing mode is to be applied to them at the beginning of next billing session and not immediately.

To check how to add wallet to specific project please visit /accountmanagement/Accounts-and-Projects-Management.

\ No newline at end of file diff --git a/site/accountmanagement/Cookie-consent-on-3Engines-Cloud.html.html b/site/accountmanagement/Cookie-consent-on-3Engines-Cloud.html.html deleted file mode 100644 index 0ff42cc..0000000 --- a/site/accountmanagement/Cookie-consent-on-3Engines-Cloud.html.html +++ /dev/null @@ -1,12 +0,0 @@ - Cookie consent on 3Engines Cloud🔗 - 3Engines Documentation

Cookie consent on 3Engines Cloud🔗

A cookie is a small text file that your browser stores in local environment and later uses to track or recognize your activities on the site.

Cookies are an essential tool for the remote site to deliver the best possible user experience. The downside for the user is the potential loss of online privacy which may, among other reasons, be caused by

  • the site itself (if it uses its own cookies in a way that is detrimental to the user),
  • by many other sites that see available cookies and decide to gather reconnaissance about your surfing activities.

Introducing Cookiebot site🔗

3Engines Cloud is using Cookiebot software to manage cookies consent from the user. It will show you all of the cookies that your browser is storing and you will be able to choose which types of cookies should 3Engines Cloud take into account. Both Cookiebot and 3Engines Cloud site are GDPR compliant, however, 3Engines Cloud also has its own Privacy Policy in effect.

Of particular relevance is Cookiebot page Logging and demonstration of user consents.

Note

You can directly interfere with cookies from your browser, operating system, network or VPN access software. This boils down to detecting, showing, hiding, tracking or removing access to certain types of cookies and so on. These methods are, however, out of scope of this article.

Cookiebot window🔗

This is the Cookiebot window on 3Engines Cloud:

cookie-consent-3Engines-cloud-1.png

You will see it when visiting one of these sites for the first time:

Cookiebot is interactive and you can change your cookies preferences while using the site. If the consent for using cookies was withdrawn, you are also going to see the same starting Cookiebot window when visiting these sites after the change.

Option Allow all🔗

Click on button Allow all will do what it says – the site will record all types of cookies and, consequently, to track your behaviour completely. This option will unleash the full power of the site and you will always be able to use all of its capabilities. For you as the user, it is also the easiest and fastest way of dealing with cookies on the site.

Details view of available cookies🔗

To see the cookies that you can give your consent to, click on Details.

cookie-consent-3Engines-cloud-2.png

There are five types of cookies and you may need to scroll down to see them all.

When shown for the first time, the left button will contain label Deny. Choosing it will turn off all of the cookies apart from the Necessary cookie type, which by default cannot be turned off. If you do not like the fact that that is the default, refrain from using the site.

Necessary cookies🔗

This is the most basic type of cookie and the site presumes you have already given consent to it. That is why the check button to the right of the row, COOKIE-BUTTON, is already set to “ON”. Technically, you can try to remove the consent by clicking on that button, but you will be met with a message like this:

cookie-consent-3Engines-cloud-13.png

You can also see additional details about that cookie type and the cookies it contains. By clicking on the name of the cookie, you will be able to see from which company it is, what it looks like and so on.

cookie-consent-3Engines-cloud-15.png

The number of cookies shown per category🔗

The number of cookies that Cookiebot is showing may vary wildly and will be increased if the sites you visit are using:

  • interactive elements, such as chat widgets, embedded maps, videos etc.
  • advertising networks,
  • analytics tools,
  • CDN (Content Delivery Network),
  • recommendations,
  • affiliate marketing,
  • testing procedures

and so on.

Some large content sites may use up to 30-40 cookies per visitor – that alone will increase the general number of cookies you see through Cookiebot.

If you delete some or all cookies, perhaps using the browser of your choice, the numbers the Cookiebot will show will be almost zero (but with each visit to another site or sites, that number is almost sure to grow).

Enabling this cookie permits the site to store the preferences such as preferred language or region you are in.

For storing anonymized statistics. In spite of your data being stored in the background of the site, these cookies will not be revealed to third parties (unless forced by law).

Used to create user profiles to send advertising. If you opt out of this cookie type, you may miss some new features of the site or, eventually, miss on promotional campaigns, sales offers and so on.

All other types of cookies, if any, that have not been classified as yet.

Click on toggle button on the right side of the form window and when you finish selecting, click on Allow selection to confirm, or again, click on Allow all to activate all of them.

This option explains what cookies are and also provides links to Privacy Policy and, more specifically, to Cookie Policy.

cookie-consent-3Engines-cloud-4.png

You can still change cookie consent by clicking on Customize, which will lead you back to Details tab (already explained above).

Selecting the cookies preferences🔗

Once you click either Allow selection or Allow all buttons, the form will disappear and your selection will be fixed. To change it, click on icon COORANGE in the lower left browser window corner.

cookie-consent-3Engines-cloud-5.png

A smaller window will appear:

cookie-consent-3Engines-cloud-6.png

Clicking on Withdraw your consent, all types of cookies will be annulled except the necessary one.

Button Change your consent will lead to the Details tab we already discussed, where you will be able to edit your cookies preferences.

To see what your consent data look like, click on Show details:

cookie-consent-3Engines-cloud-7.png

Each consent you give to the site, generates a unique consent ID, which, together with the time and date, you can see in the image above. Consent ID is random, anonymous, encrypted and unique. In that way, user anonymity is preserved while the site is still in a position to conclude whether the consent was actually provided or not.

The cookie is saved on backend servers for 12 months. It is also saved in your browser so that the website can automatically read and respect the user’s consent on all subsequent page requests.

Troubleshooting🔗

You can see the contents of the cookie file through various browser options and also through a file viewer on your desktop computer. It is quite possible (but not at all advisable) to delete the cookie file outside of the browser. In particular, deleting the entire cookie by force will also delete the necessary part of the cookie. You may, then, lose access to the site, be forced to contact Helpdesk and Support and so on.

Setting up cookies on 3Engines Cloud subdomains🔗

Cookiebot procedures are exactly the same on subdomains or the dashboard.

Here is what cookie consent window will look like, for example, on https://ecommerce.3Engines.com/:

cookie-consent-3Engines-cloud-8.png

Set the cookies up by clicking on CO icon in the lover left part of the browser window.

cookie-consent-3Engines-cloud-9.png

\ No newline at end of file diff --git a/site/accountmanagement/Editing-Profile.html.html b/site/accountmanagement/Editing-Profile.html.html deleted file mode 100644 index 9d13e98..0000000 --- a/site/accountmanagement/Editing-Profile.html.html +++ /dev/null @@ -1,12 +0,0 @@ - Editing profile🔗 - 3Engines Documentation

Editing profile🔗

After logging into https://portal.3Engines.com/ press My Profile button on the left bar menu.

editing_profile_3Enginescloud.png

In My Profile tab you will be able to:

  • check your email address and registration date
  • view and edit your name and country
  • change your password
  • view and edit accepted agreements
\ No newline at end of file diff --git a/site/accountmanagement/Forgotten-Password.html.html b/site/accountmanagement/Forgotten-Password.html.html deleted file mode 100644 index 8ae9776..0000000 --- a/site/accountmanagement/Forgotten-Password.html.html +++ /dev/null @@ -1,12 +0,0 @@ - Forgotten Password🔗 - 3Engines Documentation

Forgotten Password🔗

Go to the login page and click on Forgot Password button.

forgot_your_password_3Enginescloud.png

Enter your email address into the field and press Submit button. Check your mailbox for further steps.

Open the link from email and set up a new password.

After that, click Submit button.

enter_new_password_3Enginescloud.png

If you haven’t received a message, check your SPAM folder. If you forgot the email address or the message can’t be delivered successfully, please contact our Support Team.

\ No newline at end of file diff --git a/site/accountmanagement/Help-Desk-And-Support.html.html b/site/accountmanagement/Help-Desk-And-Support.html.html deleted file mode 100644 index ac72336..0000000 --- a/site/accountmanagement/Help-Desk-And-Support.html.html +++ /dev/null @@ -1,12 +0,0 @@ - Helpdesk and Support🔗 - 3Engines Documentation

Helpdesk and Support🔗

After logging into https://portal.3Engines.com/ press the Tickets button on the left menu bar to create or manage your tickets.

tickets_3Enginescloud.png

There are few tabs available in Tickets menu:

  • ALL - allows you to view all your tickets
  • OPEN - shows your open tickets
  • CLOSED - contains list of closed tickets

As it is shown on the above picture, all tickets are categorized by Key, Topic, Status, Type, Created date and Last update date. You can sort your tickets by Type. For this purpose choose Support, Problems, Sales, Billing and Accounting, from the top drop down list. To check details or add a comment to existing tickets, please use Show details option on the right side of the window.

If you want to create a new ticket, press Add ticket button on the top of the side.

add_ticket_3Enginescloud.png

Choose proper category, add Summary, describe the issue and press Create request button. Once you press the button ticket will be visible in the OPEN tab.

\ No newline at end of file diff --git a/site/accountmanagement/How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.html b/site/accountmanagement/How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.html deleted file mode 100644 index da7d3f4..0000000 --- a/site/accountmanagement/How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.html +++ /dev/null @@ -1,23 +0,0 @@ - How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication🔗 - 3Engines Documentation

How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication🔗

One-factor and two-factor authentication for activating command line access to the cloud🔗

To log into a site, you usually provide user name and email address during the creation of the account and then you use those same data to enter the site. You provide that data once and that is why it is called “one-factor” authentication. Two-factor authentication requires the same but considers it to be only the first step; on 3Engines Cloud cloud, the second step is

  • to generate six-digit code using the appropriate software and then to
  • send it to the cloud as a means of additional certification.

Cloud parameters for authentication and, later, 3Engines CLI access, are found in a so-called RC file. This article will help you download and use it to first authenticate and then access the cloud using 3Engines CLI commands.

What We Are Going To Cover🔗

  • How to download the RC file
  • Adjusting the name of the downloaded RC file
  • The contents of the downloaded RC file
  • How to activate the downloaded RC file
  • One factor authentication
  • Two factor authentication
  • Testing the connection
  • Resolving errors

Prerequisites🔗

No. 1 Account

You need a 3Engines Cloud hosting account with access to the Horizon interface: https://horizon.3Engines.com.

No. 2 2FA

If your account has 2FA enabled (which you will recognize from the respective prompt when authenticating), you need to install and configure a piece of software which generates six-digit codes used for 2FA. To set that up, follow one of these articles, depending on the type of device you are using:

No. 3 3EnginesClient installed and available

Installing 3EnginesClient on various platforms will also install the ability to run the .sh files. Since 3Engines is written in Python, it is recommended to use a dedicated virtual environment for the rest of this article.

Install GitBash on Windows
Run .sh files and install 3EnginesClient from a GitBash window under Windows. How to install 3EnginesClient GitBash for Windows on 3Engines Cloud.
Install and run WSL (Linux under Windows)
Run .sh files and install 3EnginesClient from a Ubuntu window under Windows. How to install 3EnginesClient on Windows using Windows Subsystem for Linux on 3Engines Cloud 3Engines Hosting.
Install 3EnginesClient on Linux
How to install 3EnginesClient for Linux on 3Engines Cloud.

How to download the RC file🔗

Click on account name

Top right corner of the Horizon screen contains the account name. Depending on the cloud you are using, you will see a menu like this:
WAW3-1, WAW3-2, FRA1-1
../_images/click_on_email.png

Click on API Access

Navigate to API Access -> Download 3Engines RC File. Depending on the cloud you are using, you will see a menu like this:
WAW3-1, WAW3-2, FRA1-1
../_images/download_rc_file_2fa.png

Option 3Engines clouds.yaml File is out of scope of this article.

Which 3Engines RC file to download🔗

Choose the appropriate option, depending on the type of account:

2FA not active on the account
For clouds WAW3-1, WAW3-2, FRA1-1, select option 3Engines RC File.
2FA active on the account
Download file 3Engines RC File (2FA).

You only need one copy of the RC file at any time. If you downloaded more than one copy of the file to the same folder without moving or renaming them, your operating system may differentiate amongst the downloaded files by adding additional characters at the end of the file name.

By way of example, let the downloaded RC file name be cloud_00734_1-openrc-2fa.sh. For your convenience, you may want to

  • rename it and
  • move to the folder in which you are going to activate it.

The contents of the downloaded RC file🔗

RC file sets up environment variables which are used by the 3Engines CLI client to authenticate to the cloud. By convention, these variables are in upper case and start with OS_: OS_TENANT_ID, OS_PROJECT_NAME etc. For example, in case of one-factor authentication, the RC file will ask for password and store it into a variable called OS_PASSWORD.

Below is an example content of an RC file which does not use 2FA:

rc_file_content.png

File which supports 2FA will have additional pieces of code for providing the second factor of authentication.

How to activate the downloaded RC file🔗

The activation procedure will depend on the operating system you are working with:

Ubuntu

Assuming you are in the same folder in which the RC file is present, use the source command:

source ./cloud_00734_1-openrc-2fa.sh
-
macOS

The same source command should work on macOS. In some versions of macOS though, an alternative command zsh could serve as well:

zsh ./cloud_00734_1-openrc-2fa.sh
-

Note that in both cases ./ means “use the file in this very folder you already are in”.

Windows

On Windows, to execute file with .sh extension, you must have an installed application that can run Bash files.

See Prerequisite No. 3, which describes in more detail how to run .sh files using various scenarios on Windows.

Running with one-factor authentication🔗

The activated .sh file will run in a Terminal window (user name is grayed out for privacy reasons):

activate-api-2fa-01_creodias.png

Enter the password, either by typing it in or by pasting it in the way your terminal supports it, and press Enter on the keyboard. The password will not be visible on the screen.

If your account has only one-factor authentication, this is all you need to do to start running commands from command line.

Two-factor authentication🔗

If your file supports two-factor authentication, the terminal will first require the password, exactly the same as in case of one-factor authentication. Then you will get a prompt for the second factor, which usually comes in shape of a six-digit one-time password:

activate-api-2fa-02_creodias.png

To get the six digit code, run the app that you are using for authentication. As recommended in Prerequisite No. 2, it may be

  • FreeOTP on mobile,
  • KeePassXC on desktop, or you may run
  • other software of your choice, or you can even write
  • your own Python or Bash code to generate the six digit code.

Let’s say that, for example, you are using FreeOTP on mobile device and that this is the icon you assigned to your account:

freeotp_icon_to_select.png

Tap on it and the six-digit number will appear:

freeotp_tapped_number.png

This six-digit number will be regenerated every thirty seconds. Enter the latest number into the Terminal window and press Enter on the keyboard. If everything worked correctly, after a few seconds you should return to your normal command prompt with no additional output:

activate-api-2fa-03_creodias.png

Duration of life for environment variables set by sourcing the RC file🔗

When you source the file, environment variables are set for your current shell. To prove it, open two terminal windows, source the RC file in one of them but not in the other and you won’t be able to authenticate from that second terminal window.

That is why you will need to activate your RC file each time you start a new terminal session. Once authenticated and while that terminal window is open, you can use it to issue 3Engines CLI commands at will.

Testing the connection🔗

If not already, install 3Engines client using one of the links in Prerequisite No 3. To verify access, execute the following command which lists flavors available in 3Engines Cloud cloud:

3Engines flavor list
-

You should get output similar to this:

flavor_list_2fa_short.png

Resolving errors🔗

jq not installed🔗

jq is an app to parse JSON input. In this context, it serves to process the output from the server. It will be installed on most Linux distros. If you do not have it installed on your computer, you may get a message like this:

jq_error.png

To resolve, download from the official support page and follow the directions to install on your operating system.

If you are using Git Bash on Windows and running into this error, Step 6 of article on GitBash from Prerequisite 3, has proper instructions for installing jq.

2FA accounts: entering a wrong password and/or six-digit code🔗

If you enter a wrong six-digit code, you will get the following error:

Call to Keycloak failed with code 401 and message
- {
-  "error": "invalid_grant",
-  "error_description": "Invalid user credentials"
-}
-

If that is the case, simply activate the RC file again as previously and type the correct credentials.

2FA accounts: lost Internet connection🔗

Activating a 2FA RC file requires access to 3Engines Cloud account service because it involves not only setting variables, but also obtaining an appropriate token.

If you do not have an Internet connection, you will receive the following output after having entered a six-digit code:

Call to Keycloak failed with code 000 and message
-

It will be followed by an empty line and you will be returned to your command prompt.

To resolve this issue, please connect to the Internet and try to activate the RC file again. If you are certain that you have Internet connection, it could mean that 3Engines Cloud account service is down. If no downtime was announced for it, please contact 3Engines Cloud customer support: Helpdesk and Support

Non-2FA accounts: entering a wrong password🔗

If your account does not have two-factor authentication and you entered a wrong password, you will not get an error. However, if you try to execute a command like 3Engines flavor list, you will get the error similar to this:

The request you have made requires authentication. (HTTP 401) (Request-ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)
-

Instead of x characters, you will see a string of characters.

To resolve, activate your file again and enter the correct password.

Using the wrong file🔗

If you have a 2FA authentication enabled for your account but have tried to activate the non-2FA version of the RC file, executing, say, command 3Engines flavor list, will give you the following error:

Unrecognized schema in response body. (HTTP 401)
-

If that is the case, download the correct file if needed and use it.

What To Do Next🔗

With the appropriate version of RC file activated, you should be able to create and use

  • instances,
  • volumes,
  • networks,
  • Kubernetes clusters

and, in general, use all 3Engines CLI commands.

For example, if you want to create a new virtual machine, you can follow this article:

How to create a VM using the 3Engines CLI client on 3Engines Cloud cloud

If you want your new virtual machine to be based on an image which is not available on 3Engines Cloud cloud, you will need to upload it. The following article contains instructions how to do it:

How to upload your custom image using 3Engines CLI on 3Engines Cloud

\ No newline at end of file diff --git a/site/accountmanagement/How-to-buy-credits-using-pay-per-use-wallet-on-3Engines-Cloud.html.html b/site/accountmanagement/How-to-buy-credits-using-pay-per-use-wallet-on-3Engines-Cloud.html.html deleted file mode 100644 index 0c341ea..0000000 --- a/site/accountmanagement/How-to-buy-credits-using-pay-per-use-wallet-on-3Engines-Cloud.html.html +++ /dev/null @@ -1,12 +0,0 @@ - How to buy credits using Pay Per Use wallet on 3Engines Cloud🔗 - 3Engines Documentation

How to buy credits using Pay Per Use wallet on 3Engines Cloud🔗

In this article you will learn how to use PPU (Pay Per Use) wallet in order to cover expenses of your account at 3Engines Cloud.

What Are We Going To Cover🔗

  • Check for the correct tax ID or VAT number
  • Select PPU as your way of payment
  • Define how many credits for PPU service
  • Choose payment method
  • Check payment reports

Prerequisites🔗

No. 1 Account

You need a 3Engines Cloud hosting account with access to the Horizon interface: https://portal.3Engines.com/.

No. 2 Have payment details ready

You can pay either through bank transfer or through Stripe, in which case you can use your credit cards and other means of online payment. Be sure to have the payment information ready before you start the payment process.

Transactions over 10,000 Euros must be made using a bank transfer.

You are going to pay with the data you enter for the organization. Be sure that you have the correct tax ID or VAT number and ready to enter, if needed.

No. 3 Useful articles

As explained in Wallets and Contracts Management, there are three ways of paying for the services on 3Engines Cloud platform:

PPUSE (Pay Per Use Wallet)
Billing according to the usage.
PAYG (Pay As You Go Contract)
Tenants are invoiced periodically based on actual usage.
FIXED-TERM (Fixed Term Contract)
Billing mode where services are bought for longer periods

In case you have not entered organization data yet, see article Adding and editing Organization

Step 1 Check for the correct tax ID or VAT number🔗

Field Company tax ID / VAT number must be filled in with correct data.

3Engines_cloud_1.png

You can check it by going to: https://portal.3Engines.com/panel/profile/organization

Without it, you won’t be able to make an order. An error like this one will appear:

3Engines_cloud_11.png

Step 2 Select PPU as your way of payment🔗

On this link, you choose the actual contract type: https://ecommerce.3Engines.com/

3Engines_cloud_2.png

Click on Buy now (assuming you will choose Pay Per Use), otherwise, click on Choose Fixed term to opt for Fixed term payments.

Step 3 Define how many credits for PPU service🔗

Either by clicking button Buy now or by visiting the following link directly: https://ecommerce.3Engines.com/checkout/pay-per-use/, you will start the process of paying for PPU.

3Engines_cloud_3.png

Let’s say that you want to buy for 250 units, where each unit costs 1 Euro.

3Engines_cloud_5.png

If you have only one wallet, the default wallet will be automatically offered. If you, however, have several wallets, choose the proper one for this order.

Step 4 Choose payment method🔗

Check whether the information about your organization is correct and proceed to payment.

3Engines_cloud_6.png

There are two different ways of payment:

Direct Bank Transfer
This method is not instant and will take some time to fund your account.
Stripe
Stripe is a well established payment processor. It is completely secure and gives you the possibility to fund your account with a variety of payment methods, including credit cards.

Again, transactions over 10,000 Euros must be made using a bank transfer.

You will see a summary with a new invoice on the bottom of the page.

If you chose direct bank transfer, scroll down to the payment section and click Pay:

3Engines_cloud_7.png

Step 5 Check payment reports🔗

Check whether the invoice amount matches the actual balance. The invoice in the upper right corner next to the eye icon marked with red line.

3Engines_cloud_9.png

Check on status of the invoice by going to this link: https://ecommerce.3Engines.com/transaction-list/

3Engines_cloud_8.png

Check your wallet as well: https://portal.3Engines.com/panel/orders/pay-per-use

3Engines_cloud_10.png

What To Do Next🔗

There are two ways of reaching to us in case of any problems:

Dashboard ticket
From the browser, use link https://portal.3Engines.com/panel/profile/tickets or click on option Support –> Tickets in the Dashboard.
Standard 3Engines Cloud support
The link is https://3Engines.com/contact/
\ No newline at end of file diff --git a/site/accountmanagement/How-to-manage-TOTP-authentication-on-3Engines-Cloud.html.html b/site/accountmanagement/How-to-manage-TOTP-authentication-on-3Engines-Cloud.html.html deleted file mode 100644 index d90bcdc..0000000 --- a/site/accountmanagement/How-to-manage-TOTP-authentication-on-3Engines-Cloud.html.html +++ /dev/null @@ -1,12 +0,0 @@ - How to manage TOTP authentication on 3Engines Cloud🔗 - 3Engines Documentation

How to manage TOTP authentication on 3Engines Cloud🔗

In order to use your 3Engines Cloud account, you need to set a password, and an additional factor of authentication. For the latter, the TOTP algorithm is being used. In this article you will learn how to manage your TOTP configuration.

What Are We Going To Cover🔗

  • Important information about TOTP
  • Entering the TOTP management console
  • Removing the TOTP secret key
  • Adding a new TOTP secret key
  • Contacting customer support

Prerequisites🔗

No. 1 Account

You need a 3Engines Cloud account: https://horizon.3Engines.com

No. 2 2FA set on your account

During account initialization, you will be prompted to configure 2FA TOTP software. You can, for instance, use one of the following articles for that purpose:

\ No newline at end of file diff --git a/site/accountmanagement/How-to-start-using-dashboard-services-on-3Engines-Cloud.html.html b/site/accountmanagement/How-to-start-using-dashboard-services-on-3Engines-Cloud.html.html deleted file mode 100644 index 1d474bf..0000000 --- a/site/accountmanagement/How-to-start-using-dashboard-services-on-3Engines-Cloud.html.html +++ /dev/null @@ -1,12 +0,0 @@ - How to start using dashboard services on 3Engines Cloud🔗 - 3Engines Documentation

How to start using dashboard services on 3Engines Cloud🔗

When you try to use 3Engines Cloud dashboard at https://portal.3Engines.com/, you will see an advice on the order of operations to start using the dashboard properly.

dashboard-services-2-3Engines-cloud.png

Step 1 Set up the organization🔗

  1. Go to the organization, add it by providing the name, details and a valid EU VAT number/TAX ID assigned to your country.

The option to use is Configuration -> Organization.

dashboard-services-4-3Engines-cloud.png

See article Adding and editing Organization.

Step 2 Enable payment options🔗

Go to the eCommerce site and top up your wallet with the required funds.

dashboard-services-3-3Engines-cloud.png

See article How to buy credits using Pay Per Use wallet on 3Engines Cloud.

Step 3 Activate the project🔗

Go to “Cloud projects” and activate the project in the cloud/region you are interested in. The options to choose are Billing and Reporting -> Cloud projects/Wallets.

dashboard-services-5-3Engines-cloud.png

At the moment of this writing, there were four different regions to choose from: WAW3-1, WAW3-2, WAW4-1, FRA1-2. These regions are actually clouds running under 3Engines and in each you can have your own virtual machines, access to EO data, create Kubernetes clusters and so on. Although all clouds are running under 3Engines, there are differences in available software, hardware, resources and so on, so it pays to learn which cloud is best for you.

You may want to work with all these clouds at the same time, maybe with different groups of people working on different projects and so on.

It is up to you to activate all these clouds at once… or just one… or anything in between. The regions/clouds you activate in the dashboard can be seen in the Horizon dashboard, in the menu.

Step 4 Start using the chosen cloud in Horizon🔗

To start using the services, choose proper Cloud Panel from the Management Interfaces.

dashboard-services-6-3Engines-cloud.png

It will lead you to page https://horizon.3Engines.com:

dashboard-services-7-3Engines-cloud.png

Let’s say we want to work with cloud WAW3-1.

dashboard-services-10-3Engines-cloud.png

Click on Sign In and the Horizon will show up. Horizon will remember which project and cloud were active previously and will return to them automatically. If you want to work with another cloud, select it manually.

dashboard-services-9-3Engines-cloud.png

\ No newline at end of file diff --git a/site/accountmanagement/Inviting-New-User.html.html b/site/accountmanagement/Inviting-New-User.html.html deleted file mode 100644 index a8762d4..0000000 --- a/site/accountmanagement/Inviting-New-User.html.html +++ /dev/null @@ -1,12 +0,0 @@ - Inviting new user to your Organization🔗 - 3Engines Documentation

Inviting new user to your Organization🔗

Important

One user can only be assigned to one organization at a time.

To invite a new user to your organization you need to share an invitation code.

After logging into https://portal.3Engines.com/ press Invitations button on the left bar menu.

inv_01_3Enginescloud.png

Now you can copy an invitation code by clicking on Copy to clipboard button and send it to a new user by email.

After receiving the code, the user will join the organization by

  • clicking Join an Organization in Organization tab and
  • pasting the invitation code.

As an organization admin, you need to accept the invitation first.

Go to the Invitations tab and choose an invitation that you want to accept or – in other case – reject.

inv_02_3Enginescloud.png

After accepting the invitation you will be able to add/edit roles. For more details please check Tenant manager users and roles on 3Engines Cloud.

\ No newline at end of file diff --git a/site/accountmanagement/Privacy-Policy.html.html b/site/accountmanagement/Privacy-Policy.html.html deleted file mode 100644 index dc7e6d7..0000000 --- a/site/accountmanagement/Privacy-Policy.html.html +++ /dev/null @@ -1,12 +0,0 @@ - Privacy policy for clients🔗 - 3Engines Documentation
\ No newline at end of file diff --git a/site/accountmanagement/Registration-And-Account.html.html b/site/accountmanagement/Registration-And-Account.html.html deleted file mode 100644 index 2ae9bad..0000000 --- a/site/accountmanagement/Registration-And-Account.html.html +++ /dev/null @@ -1,12 +0,0 @@ - Registration and Setting up an Account🔗 - 3Engines Documentation

Registration and Setting up an Account🔗

Go to the https://portal.3Engines.com/ site and press CREATE ACCOUNT button.

register_3Enginescloud.png

Fill up all fields marked with * including accepting mandatory terms and conditions and press Create Account button.

Please note that marketing consents are not mandatory and can be changed at any time.

create_account_3Enginescloud.png

Once you create account below screen will appear. Please check your mail box and verify mail. After that you will be able to log in.

registration_successful_3Enginescloud.png

For general information about types of account and user roles you may have in Dashboard, see Tenant manager users and roles on 3Engines Cloud

After creating personal account you can either create new company account or join an existing account. See articles:

Adding and editing Organization

Inviting new user to your Organization

If you are a single user you can only access a limited number of services.

See article How to start using dashboard services on 3Engines Cloud

\ No newline at end of file diff --git a/site/accountmanagement/Removing-User-From-Organization.html.html b/site/accountmanagement/Removing-User-From-Organization.html.html deleted file mode 100644 index f1375f8..0000000 --- a/site/accountmanagement/Removing-User-From-Organization.html.html +++ /dev/null @@ -1,12 +0,0 @@ - Removing user from Organization🔗 - 3Engines Documentation

Removing user from Organization🔗

After logging into https://portal.3Engines.com/ press Sub-accounts button on the left bar menu to check the list of members of your Organization.

users_roles_01_3Enginescloud.png

Select user that you want to be removed and press Unassign button on the right side and after that press Confirm button.

User will have received notification about removing from your Organization.

\ No newline at end of file diff --git a/site/accountmanagement/Services.html.html b/site/accountmanagement/Services.html.html deleted file mode 100644 index f2571c9..0000000 --- a/site/accountmanagement/Services.html.html +++ /dev/null @@ -1,12 +0,0 @@ - Services🔗 - 3Engines Documentation

Services🔗

After logging into https://portal.3Engines.com/ press Active services button on the left bar menu.

services_3Enginescloud.png

In this tab you are able to filter your services by Project or by Product.

You can also check what type of contract or billing mode is assigned to your services. For more details please visit /accountmanagement/Accounts-and-Projects-Management.

How to change assigned contract🔗

PAY PER USE - user can assign wallet to specific project in the Accounts tab

PAY AS YOU GO - user can assign wallet to specific project in the Accounts tab

FIXED TERM - is assigned by 3Engines Support Team during the contract creation

Please note that PPU/PAYG assignment status is visible in the Accounts tab.

\ No newline at end of file diff --git a/site/accountmanagement/Tenant-Manager-Users-And-Roles-On-3Engines-Cloud.html.html b/site/accountmanagement/Tenant-Manager-Users-And-Roles-On-3Engines-Cloud.html.html deleted file mode 100644 index a79117a..0000000 --- a/site/accountmanagement/Tenant-Manager-Users-And-Roles-On-3Engines-Cloud.html.html +++ /dev/null @@ -1,12 +0,0 @@ - Tenant manager users and roles on 3Engines Cloudenant manager users and roles on 3Engines Cloud🔗 - 3Engines Documentation

Tenant manager users and roles on 3Engines Cloudenant manager users and roles on 3Engines Cloud🔗

Differences between 3Engines User Roles and Tenant Manager’s Roles🔗

An 3Engines role is a personality that a user assumes to perform a specific set of operations. A role includes a set of rights and privileges. A user assuming that role inherits those rights and privileges. 3Engines roles are defined for each user and each project independently.

A Tenant Manager role, on the other hand, defines whether a user should have the ability to manage an organization via the Tenant Manager or have access to 3Engines.

What Are We Going To Cover🔗

  • The difference between User Roles and Tenant Manager Role
  • List three basic roles an organization administrator you can assign
  • Show how to add a member+ role, which can have access to 3Engines and be used for managing projects

Users and Roles in the Tenant Manager🔗

After logging into https://portal.3Engines.com/ click on the Sub-accounts button on the left bar menu.

Tenant_manager_01_3Engines.png

Here you are able to:

  • Check your organizations’ list of users and their roles
  • Remove users from or add them to your organization (admin role)

As an organization administrator you can assign one of the following roles to a user:

  • admin - user with highest privileges, can manage whole organizations and has access to 3Engines.
  • member - default user with basic privileges.
  • member+ - the same as member but has 3Engines access and can manage projects.

Adding member+ user to your project in 3Engines using Horizon interface🔗

Users with the role of member+ have access to 3Engines and can be enabled to manage your organization projects. They cannot however, manage the organization itself.

To add a member+ user to the project, follow these steps:

1. Check if your user has a member+ role in Tenant Manager.

2. Log into https://horizon.3Engines.com as an admin.

3. Select Identity → Projects

Tenant_manager_02_3Engines.png

4. Select the project you want to add a user to and select Manage members

Tenant_manager_03_3Engines.png

5. Add the desired user(s) to the project by clicking on the “+” button next to them.

Tenant_manager_04_3Engines.png

6. Choose a suitable project role for the user and confirm by clicking Save in the lower-right corner.

Tenant_manager_05_3Engines.png

7. Next time the user will log into https://horizon.3Engines.com 3Engines Horizon, the suitable access to the project will be granted.

What To Do Next🔗

The article Inviting new user to your Organization shows how to invite a new user.

To the contrary, article Removing user from Organization shows how to remove a user from the organization.

The article /accountmanagement/Accounts-and-Projects-Management is a general guidance to creating and managing accounts and projects on 3Engines Cloud.

\ No newline at end of file diff --git a/site/accountmanagement/Two-Factor-Authentication-for-3Engines-Cloud-Site.html.html b/site/accountmanagement/Two-Factor-Authentication-for-3Engines-Cloud-Site.html.html deleted file mode 100644 index 0ad97be..0000000 --- a/site/accountmanagement/Two-Factor-Authentication-for-3Engines-Cloud-Site.html.html +++ /dev/null @@ -1,12 +0,0 @@ - Two-Factor Authentication to 3Engines Cloud site using mobile application🔗 - 3Engines Documentation

Two-Factor Authentication to 3Engines Cloud site using mobile application🔗

Warning

Two-Factor Authentication is required for all 3Engines Cloud users. The only exception are accounts which log in using Keystone credentials.

Traditionally, the most basic way to implement security online was to authenticate users and companies with a pair of usernames/passwords. Most usernames are email addresses and if email address is breached, the bad actor can probably learn your password too. What once used to be secure enough is not secure now because of easy access to refined brute force methods, availability of computing power at scale, social engineering methods, identity theft and so on.

The way to overcome this limitation is to introduce two or more factors or types of user authentication. These could be

  • something the user knows (email address, the name of their first pet etc.)
  • something the user has (token generator, smartphone, credit card etc.) or
  • biometric information such as fingerprint, iris, retina, voice, face and so on.

Logging into the 3Engines Cloud site uses two-factor authentication, meaning you will have to supply two independent types of data:

  • the “classical” username and password, as well as
  • the numeric code supplied by a concrete mobile app.

This article is about using mobile devices to authenticate to the cloud. If you want to use your computer to do that, see Two-Factor Authentication to 3Engines Cloud site using KeePassXC on desktop.

You will first have to install one of the following two mobile applications, for Android or iOS mobile operating systems:

We can use “mobile authenticator” as a generic term for a mobile app that can help authenticate with the account.

Which One to Use – FreeOTP or Google Authenticator?🔗

You can use FreeOTP with Google accounts instead of Google Authenticator app.

If you already use Google Authenticator app for other accounts, you may prefer it over FreeOTP.

Warning

If your accounts are protected by Google Authenticator and it stops working, then you risk losing all the data that were behind those protected accounts. The most common scenario is to switch to a new phone number and then not be able to verify the accounts via a text message to the previous phone number.

In this tutorial, you are going to use the FreeOTP app.

Warning

If you lose access to QR codes and cannot log into the Horizon site for 3Engines Cloud, ask Support service to help you by sending email to the following address support@3Engines.com.

What We Are Going To Cover🔗

  • How to start using the mobile authenticator
  • How to locate, download and install FreeOTP app on your mobile device
  • How to set up FreeOTP app and connect it to your 3Engines Cloud account
  • How to get new code each time you want to enter the site

Prerequisites🔗

Use only one of the four possible combinations for two apps and two app stores.

No. 1 FreeOTP app in Google Play Store

Download FreeOTP app in Google Play Store using this link.

No. 2 FreeOTP app in iOS App Store

Download FreeOTP app in iOS App Store using this link.

No. 3 Google Authenticator in Google Play Store

Download Google Authenticator in Google Play Store using this link.

No. 4 Google Authenticator in iOS App Store

Download Google Authenticator in iOS App Store using this link.

Warning

You should install the authenticator app before trying to log into the 3Engines Cloud site.

You are now going to download, install and use the FreeOTP app to authenticate to 3Engines Cloud site.

Step 1 Download and Install FreeOTP from the App Store🔗

Using the App Store icon from the desktop of your iOS device, locate app called freeotp. A screen like this will appear:

otp01.png

Tap on GET and the app will start downloading to your device.

otp02.png

It may take a minute or so and then install it by tapping on button Install.

otp03.png

Once installed, type on Open and the app will run. At first, there will be no tokens to work with:

otp04.png

Note

FreeOTP can also use tokens to secure access to the remote site. The 3Engines Cloud site uses QR code, so that is what you will use in this tutorial. (Both “token” and “QR scan” denote a secure connection to the site, but use different techniques in the process.)

Step 2 Scan QR and Create Brand🔗

Select a brand, which means select an icon that will make your tokens stand out graphically. If you will employ this app only to get access to 3Engines Cloud, you may select whichever icon you want.

otp05.png

In the next step, you may require that the phone is unlocked when the token is to be activated. Choose that if you are afraid someone might steal your phone and get access to your 3Engines Cloud data that way.

otp07.png

Clicking on information icon will show you legal details about this app.

otp08.png

To scan the QR code, use a QR like icon in the upper part of the screen, like this:

eefa_freeotp_qr_icon.png

Click on it to get to the scanner part of the application and read the QR code from the login screen.

Note

The QR code will appear on screen when you first try to log into the 3Engines Cloud site (see below).

eefa_qr_screen_creodias.png

Step 3 Create a Six-digit Code to Enter Into the Login Screen🔗

Finally, you will see a row within the FreeOTP app, with the icon you chose and with the code that will appear automatically. For instance, the code is 289582 and that is the code that you need to enter when the site asks you for One-time code.

otp09.png

If you created several tokens or repeatedly scanned QR code from the screen, you may see the appropriate number of rows on the mobile screen:

eefa_several_rows.png

Tapping on any of these will produce the six-digit code that you have to type into the entry form to get logged in. Only one of these will be the right one, in this case, the first row produces the correct six-digits code for 3Engines Cloud site.

eefa_tapped.png

You are now ready to log into the 3Engines Cloud site using the two-factor authentication.

How to Start Using the Mobile Authenticator With Your Account🔗

Use the usual link https://horizon.3Engines.com to log into your 3Engines Cloud account and choose 3Engines Cloud in the input menu.

eefa_start_creodias.png

Click on blue button Sign In and enter your username / email and password:

eefa_sign_regular_creodias.png

If the data you entered has not already been linked to two-factor authentication, the next screen will be Mobile Authenticator Setup:

eefa_mobile_auth_setup_creodias.png

This screen will contain the QR code that you have to read from using the mobile authenticator app, in this case, the FreeOTP app.

At this moment, start using the mobile device – activate the FreeOTP first if not already active, scan the QR code with the QR icon and, as explained above, get the six-digit code on the mobile device screen.

Retype that six-digit code into the One-time code field on computer screen. It is denoted by an asterisk, meaning that it is mandatory to enter a value into this field.

You can use the field Device Name to remind yourself on which device was the mobile authenticator app installed on.

Click on Submit and you will be brought back to the Sign in screen from the beginning:

Logging Into the Site Once the Two-Factor Authentication is Installed🔗

Here is the workflow in one place, with all of the screens repeated for easy reference.

Use the usual link https://horizon.3Engines.com to log into your 3Engines Cloud account and choose 3Engines Cloud in the input menu.

eefa_start_creodias.png

Click on blue button Sign In and enter your username / email and password:

eefa_sign_regular_creodias.png

Since the two-factor authentication is already installed, you will only see the window to enter the six-digit code.

eefa_restart_login_creodias.png

Now activate the mobile authenticator app and get the code on the device screen, for instance, like this:

eefa_tapped.png

In this case, the code is 828966. Enter it into the form, Submit and you will be logged in.

eefa_logged_in_creodias.png

Note

If the FreeOTP app is in the foreground on the mobile device while you are submitting the username and password, the app will react automatically and the proper six-digit code will appear on its own on the authenticator device.

What To Do Next🔗

As mentioned in the beginning, you can use your computer for two-factor authentication – see article Two-Factor Authentication to 3Engines Cloud site using KeePassXC on desktop.

Either using mobile device or computer to authenticate, you will be logged into Horizon. You will then need to activate access to 3Engines Cloud cloud API functions and be able to run 3Engines command. Please see article How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication.

To learn how to manage your TOTP secret key, visit the following article: How to manage TOTP authentication on 3Engines Cloud - it can be useful if you, for instance, want to use a different method of authentication, are unable to extract your secret key from currently used piece of software such as FreeOTP and do not have your secret key backed up in a readable way.

\ No newline at end of file diff --git a/site/accountmanagement/Using-KeePassXC-for-Two-Factor-Authentication-on-3Engines-Cloud.html.html b/site/accountmanagement/Using-KeePassXC-for-Two-Factor-Authentication-on-3Engines-Cloud.html.html deleted file mode 100644 index d5f8b88..0000000 --- a/site/accountmanagement/Using-KeePassXC-for-Two-Factor-Authentication-on-3Engines-Cloud.html.html +++ /dev/null @@ -1,13 +0,0 @@ - Two-Factor Authentication to 3Engines Cloud site using KeePassXC on desktop🔗 - 3Engines Documentation

Two-Factor Authentication to 3Engines Cloud site using KeePassXC on desktop🔗

Please see article Two-Factor Authentication to 3Engines Cloud site using mobile application if you want to use a smartphone app for the TOTP two-factor authentication.

If you, however, want to use your desktop or laptop computer instead, KeePassXC is probably a good choice for you. It is a free and open source graphical password manager. It stores passwords, TOTP keys and other secrets in a file on your computer. You can later, for example, move that file manually to a different computer to use that device instead of the current one.

Contrary to software such as BitWarden, 1Password or LastPass, KeePassXC does not have any cloud sync features.

Attention

Since KeePassXC does not provide any cloud storage, you need to make sure that you do not lose your file and whatever is required to decrypt it. You will lose all the content of the file if you lose any of these objects. The backup of this file should be performed.

If you already have KeePassXC installed and configured, skip to Step 3 Adding Entry or 4 Configuring the TOTP.

The following instructions are for Ubuntu. If you use a different operating system, please refer to the appropriate documentation.

Step 1 Install KeePassXC🔗

Install KeePassXC before logging in to the 3Engines Cloud website. Open the terminal, type the following command and press Enter:

sudo apt update && sudo apt upgrade -y && sudo apt install -y keepassxc
-

Step 2 Configure KeePassXC🔗

Launch KeePassXC. During its first run, you will see the following window:

keepassxc_01_creodias.png

Click the button Create new database it in order to create a file in which you can store your passwords, TOTP keys and other secrets. Now you will see the following window:

keepassxc_02_creodias.png

In the first step of database creation you may provide its name and discription. The name provided here will not be the name of your file, so you may leave it as it is. Click Continue. The following window will appear:

keepassxc_03_creodias.png

Next, you may choose how long should the decryption of your database take. However, please keep in mind that, as it is written in that window, Higher values offer more protection, but opening the database will take longer. Leave the default database format and click Continue. You will now see the following window:

keepassxc_04_creodias.png

Now you need to provide the password for decrypting your database. Enter it again in the second text field. You can also add additional security measures using the button Add additional protection…, but if you are just getting started in might not be needed.

Attention

If at any point in the future you are unable to provide your password (for example, because you have forgotten it) and any additional protection measures you configured, you will be locked out of your database and potentially lose all of its content.

Click Done.

Choose the name for the file containing your secrets and its location. Click Save.

Step 3 Add the entry for your account🔗

Your database should now be operational. Let’s create the entry containing your username, password and TOTP for the 3Engines Cloud cloud. Click Add a new entry (the fourth button on the toolbar, marked with the red rectangle on the screenshot below.

keepassxc_05_creodias.png

The following window will appear:

keepassxc_06_creodias.png

In the Title field enter the name under which your entry should be identified in your database, for example 3Engines Cloud. Then, type your username and password.

Click OK to save the entry.

If the option Automatically save after every change in the General section of the application settings is enabled, you do not have to save. If not, press CTRL+S to save the database.

Step 4 Configure TOTP🔗

Now we need to obtain your TOTP key.

Method 1: During account creation🔗

After having created an account on https://horizon.3Engines.com but before first login, you will receive the Mobile Authenticator Setup prompt, as in the following image:

keepassxc_07_creodias.png

Since you are using a computer which cannot act as a mobile device, click Unable to scan?. The QR code will now be replaced with your key:

keepassxc_08_creodias.png

Copy the code with which the QR code has just been replaced.

Once you have your TOTP key,

  • return to KeePassXC,
  • right-click the entry for your account and
  • choose the TOTP… -> Setup TOTP… option.

You will see the following window:

keepassxc_09_creodias.png

Paste your key there into the text field Key: and keep the checkbox Default RFC 6238 token settings checked. Click OK.

In order to view your code, right-click the entry and select TOTP… > Show TOTP…. It is easier, however, to simply

  • left-click that entry and
  • press CTRL+Shift+T.

You can also press CTRL+T while your entry is highlighted to copy your TOTP code to your clipboard (remember that depending on settings it will disappear from your clipboard, so make sure that you paste it in time).

The window with the code will look like this:

keepassxc_10_creodias.png

Type your 6-digit code from the above window to the text field One-time-code on the 3Engines Cloud website and choose how you would like to call your device containing the TOTP key. Please make sure that you do it before that key expires. If the key expires, you will get another one and you should type it instead. Click Submit. You should now be able to proceed with your login process.

Method 2: After another method of TOTP has already been configured🔗

If the method of TOTP authentication you are currently using allows you to extract the secret key(or you have it backed up somewhere), you should be able to use that same secret key which you are currently using for KeePassXC as well.

If no other options remain, contact 3Engines Cloud customer support for assistance.

Either way, eventually you should get your secret key. Enter it in KeePassXC the same way as explained in Method 1 above - to the Key: text field. If that secret key is already added and configured for your account, no further action should be necessary. If not and you are in the process of configuring it, paste the 6-digit TOTP code from KeePassXC in the same way as you entered the code from your other device during account setup.

Step 5 Login using TOTP🔗

Each time you login, type your credentials normally. After that you will see the following text field:

keepassxc_11_creodias.png

Generate your TOTP code as explained before (left-click the appropriate entry in KeePassXC and press CTRL+Shift+T) and type that code in the text field One-time code in your browser. If you want to simply copy your code to your clipboard, press CTRL+T while your entry is highlighted (remember that depending on settings it will disappear from your clipboard, so make sure that you paste it in time). Each code lasts only 30 seconds, so if you only have a few seconds remaining on your current code, you might want to wait until the new one is generated. Now you should be signed in.

Additional information🔗

You can find additional information about using KeePassXC in its official documentation.

\ No newline at end of file diff --git a/site/accountmanagement/accountmanagement.html.html b/site/accountmanagement/accountmanagement.html.html deleted file mode 100644 index d139468..0000000 --- a/site/accountmanagement/accountmanagement.html.html +++ /dev/null @@ -1,12 +0,0 @@ - ACCOUNT MANAGEMENT - 3Engines Documentation

ACCOUNT MANAGEMENT

\ No newline at end of file diff --git a/site/assets/images/favicon.png b/site/assets/images/favicon.png deleted file mode 100644 index 1cf13b9..0000000 Binary files a/site/assets/images/favicon.png and /dev/null differ diff --git a/site/assets/javascripts/bundle.13a4f30d.min.js b/site/assets/javascripts/bundle.13a4f30d.min.js deleted file mode 100644 index c31fa1a..0000000 --- a/site/assets/javascripts/bundle.13a4f30d.min.js +++ /dev/null @@ -1,16 +0,0 @@ -"use strict";(()=>{var Wi=Object.create;var gr=Object.defineProperty;var Vi=Object.getOwnPropertyDescriptor;var Di=Object.getOwnPropertyNames,Vt=Object.getOwnPropertySymbols,zi=Object.getPrototypeOf,yr=Object.prototype.hasOwnProperty,ao=Object.prototype.propertyIsEnumerable;var io=(e,t,r)=>t in e?gr(e,t,{enumerable:!0,configurable:!0,writable:!0,value:r}):e[t]=r,$=(e,t)=>{for(var r in t||(t={}))yr.call(t,r)&&io(e,r,t[r]);if(Vt)for(var r of Vt(t))ao.call(t,r)&&io(e,r,t[r]);return e};var so=(e,t)=>{var r={};for(var o in e)yr.call(e,o)&&t.indexOf(o)<0&&(r[o]=e[o]);if(e!=null&&Vt)for(var o of Vt(e))t.indexOf(o)<0&&ao.call(e,o)&&(r[o]=e[o]);return r};var xr=(e,t)=>()=>(t||e((t={exports:{}}).exports,t),t.exports);var Ni=(e,t,r,o)=>{if(t&&typeof t=="object"||typeof t=="function")for(let n of Di(t))!yr.call(e,n)&&n!==r&&gr(e,n,{get:()=>t[n],enumerable:!(o=Vi(t,n))||o.enumerable});return e};var Lt=(e,t,r)=>(r=e!=null?Wi(zi(e)):{},Ni(t||!e||!e.__esModule?gr(r,"default",{value:e,enumerable:!0}):r,e));var co=(e,t,r)=>new Promise((o,n)=>{var i=p=>{try{s(r.next(p))}catch(c){n(c)}},a=p=>{try{s(r.throw(p))}catch(c){n(c)}},s=p=>p.done?o(p.value):Promise.resolve(p.value).then(i,a);s((r=r.apply(e,t)).next())});var lo=xr((Er,po)=>{(function(e,t){typeof Er=="object"&&typeof po!="undefined"?t():typeof define=="function"&&define.amd?define(t):t()})(Er,function(){"use strict";function e(r){var o=!0,n=!1,i=null,a={text:!0,search:!0,url:!0,tel:!0,email:!0,password:!0,number:!0,date:!0,month:!0,week:!0,time:!0,datetime:!0,"datetime-local":!0};function s(k){return!!(k&&k!==document&&k.nodeName!=="HTML"&&k.nodeName!=="BODY"&&"classList"in k&&"contains"in k.classList)}function p(k){var ft=k.type,qe=k.tagName;return!!(qe==="INPUT"&&a[ft]&&!k.readOnly||qe==="TEXTAREA"&&!k.readOnly||k.isContentEditable)}function c(k){k.classList.contains("focus-visible")||(k.classList.add("focus-visible"),k.setAttribute("data-focus-visible-added",""))}function l(k){k.hasAttribute("data-focus-visible-added")&&(k.classList.remove("focus-visible"),k.removeAttribute("data-focus-visible-added"))}function f(k){k.metaKey||k.altKey||k.ctrlKey||(s(r.activeElement)&&c(r.activeElement),o=!0)}function u(k){o=!1}function d(k){s(k.target)&&(o||p(k.target))&&c(k.target)}function y(k){s(k.target)&&(k.target.classList.contains("focus-visible")||k.target.hasAttribute("data-focus-visible-added"))&&(n=!0,window.clearTimeout(i),i=window.setTimeout(function(){n=!1},100),l(k.target))}function L(k){document.visibilityState==="hidden"&&(n&&(o=!0),X())}function X(){document.addEventListener("mousemove",J),document.addEventListener("mousedown",J),document.addEventListener("mouseup",J),document.addEventListener("pointermove",J),document.addEventListener("pointerdown",J),document.addEventListener("pointerup",J),document.addEventListener("touchmove",J),document.addEventListener("touchstart",J),document.addEventListener("touchend",J)}function ee(){document.removeEventListener("mousemove",J),document.removeEventListener("mousedown",J),document.removeEventListener("mouseup",J),document.removeEventListener("pointermove",J),document.removeEventListener("pointerdown",J),document.removeEventListener("pointerup",J),document.removeEventListener("touchmove",J),document.removeEventListener("touchstart",J),document.removeEventListener("touchend",J)}function J(k){k.target.nodeName&&k.target.nodeName.toLowerCase()==="html"||(o=!1,ee())}document.addEventListener("keydown",f,!0),document.addEventListener("mousedown",u,!0),document.addEventListener("pointerdown",u,!0),document.addEventListener("touchstart",u,!0),document.addEventListener("visibilitychange",L,!0),X(),r.addEventListener("focus",d,!0),r.addEventListener("blur",y,!0),r.nodeType===Node.DOCUMENT_FRAGMENT_NODE&&r.host?r.host.setAttribute("data-js-focus-visible",""):r.nodeType===Node.DOCUMENT_NODE&&(document.documentElement.classList.add("js-focus-visible"),document.documentElement.setAttribute("data-js-focus-visible",""))}if(typeof window!="undefined"&&typeof document!="undefined"){window.applyFocusVisiblePolyfill=e;var t;try{t=new CustomEvent("focus-visible-polyfill-ready")}catch(r){t=document.createEvent("CustomEvent"),t.initCustomEvent("focus-visible-polyfill-ready",!1,!1,{})}window.dispatchEvent(t)}typeof document!="undefined"&&e(document)})});var qr=xr((dy,On)=>{"use strict";/*! - * escape-html - * Copyright(c) 2012-2013 TJ Holowaychuk - * Copyright(c) 2015 Andreas Lubbe - * Copyright(c) 2015 Tiancheng "Timothy" Gu - * MIT Licensed - */var $a=/["'&<>]/;On.exports=Pa;function Pa(e){var t=""+e,r=$a.exec(t);if(!r)return t;var o,n="",i=0,a=0;for(i=r.index;i{/*! - * clipboard.js v2.0.11 - * https://clipboardjs.com/ - * - * Licensed MIT © Zeno Rocha - */(function(t,r){typeof Rt=="object"&&typeof Yr=="object"?Yr.exports=r():typeof define=="function"&&define.amd?define([],r):typeof Rt=="object"?Rt.ClipboardJS=r():t.ClipboardJS=r()})(Rt,function(){return function(){var e={686:function(o,n,i){"use strict";i.d(n,{default:function(){return Ui}});var a=i(279),s=i.n(a),p=i(370),c=i.n(p),l=i(817),f=i.n(l);function u(D){try{return document.execCommand(D)}catch(A){return!1}}var d=function(A){var M=f()(A);return u("cut"),M},y=d;function L(D){var A=document.documentElement.getAttribute("dir")==="rtl",M=document.createElement("textarea");M.style.fontSize="12pt",M.style.border="0",M.style.padding="0",M.style.margin="0",M.style.position="absolute",M.style[A?"right":"left"]="-9999px";var F=window.pageYOffset||document.documentElement.scrollTop;return M.style.top="".concat(F,"px"),M.setAttribute("readonly",""),M.value=D,M}var X=function(A,M){var F=L(A);M.container.appendChild(F);var V=f()(F);return u("copy"),F.remove(),V},ee=function(A){var M=arguments.length>1&&arguments[1]!==void 0?arguments[1]:{container:document.body},F="";return typeof A=="string"?F=X(A,M):A instanceof HTMLInputElement&&!["text","search","url","tel","password"].includes(A==null?void 0:A.type)?F=X(A.value,M):(F=f()(A),u("copy")),F},J=ee;function k(D){"@babel/helpers - typeof";return typeof Symbol=="function"&&typeof Symbol.iterator=="symbol"?k=function(M){return typeof M}:k=function(M){return M&&typeof Symbol=="function"&&M.constructor===Symbol&&M!==Symbol.prototype?"symbol":typeof M},k(D)}var ft=function(){var A=arguments.length>0&&arguments[0]!==void 0?arguments[0]:{},M=A.action,F=M===void 0?"copy":M,V=A.container,Y=A.target,$e=A.text;if(F!=="copy"&&F!=="cut")throw new Error('Invalid "action" value, use either "copy" or "cut"');if(Y!==void 0)if(Y&&k(Y)==="object"&&Y.nodeType===1){if(F==="copy"&&Y.hasAttribute("disabled"))throw new Error('Invalid "target" attribute. Please use "readonly" instead of "disabled" attribute');if(F==="cut"&&(Y.hasAttribute("readonly")||Y.hasAttribute("disabled")))throw new Error(`Invalid "target" attribute. You can't cut text from elements with "readonly" or "disabled" attributes`)}else throw new Error('Invalid "target" value, use a valid Element');if($e)return J($e,{container:V});if(Y)return F==="cut"?y(Y):J(Y,{container:V})},qe=ft;function Fe(D){"@babel/helpers - typeof";return typeof Symbol=="function"&&typeof Symbol.iterator=="symbol"?Fe=function(M){return typeof M}:Fe=function(M){return M&&typeof Symbol=="function"&&M.constructor===Symbol&&M!==Symbol.prototype?"symbol":typeof M},Fe(D)}function ki(D,A){if(!(D instanceof A))throw new TypeError("Cannot call a class as a function")}function no(D,A){for(var M=0;M0&&arguments[0]!==void 0?arguments[0]:{};this.action=typeof V.action=="function"?V.action:this.defaultAction,this.target=typeof V.target=="function"?V.target:this.defaultTarget,this.text=typeof V.text=="function"?V.text:this.defaultText,this.container=Fe(V.container)==="object"?V.container:document.body}},{key:"listenClick",value:function(V){var Y=this;this.listener=c()(V,"click",function($e){return Y.onClick($e)})}},{key:"onClick",value:function(V){var Y=V.delegateTarget||V.currentTarget,$e=this.action(Y)||"copy",Wt=qe({action:$e,container:this.container,target:this.target(Y),text:this.text(Y)});this.emit(Wt?"success":"error",{action:$e,text:Wt,trigger:Y,clearSelection:function(){Y&&Y.focus(),window.getSelection().removeAllRanges()}})}},{key:"defaultAction",value:function(V){return vr("action",V)}},{key:"defaultTarget",value:function(V){var Y=vr("target",V);if(Y)return document.querySelector(Y)}},{key:"defaultText",value:function(V){return vr("text",V)}},{key:"destroy",value:function(){this.listener.destroy()}}],[{key:"copy",value:function(V){var Y=arguments.length>1&&arguments[1]!==void 0?arguments[1]:{container:document.body};return J(V,Y)}},{key:"cut",value:function(V){return y(V)}},{key:"isSupported",value:function(){var V=arguments.length>0&&arguments[0]!==void 0?arguments[0]:["copy","cut"],Y=typeof V=="string"?[V]:V,$e=!!document.queryCommandSupported;return Y.forEach(function(Wt){$e=$e&&!!document.queryCommandSupported(Wt)}),$e}}]),M}(s()),Ui=Fi},828:function(o){var n=9;if(typeof Element!="undefined"&&!Element.prototype.matches){var i=Element.prototype;i.matches=i.matchesSelector||i.mozMatchesSelector||i.msMatchesSelector||i.oMatchesSelector||i.webkitMatchesSelector}function a(s,p){for(;s&&s.nodeType!==n;){if(typeof s.matches=="function"&&s.matches(p))return s;s=s.parentNode}}o.exports=a},438:function(o,n,i){var a=i(828);function s(l,f,u,d,y){var L=c.apply(this,arguments);return l.addEventListener(u,L,y),{destroy:function(){l.removeEventListener(u,L,y)}}}function p(l,f,u,d,y){return typeof l.addEventListener=="function"?s.apply(null,arguments):typeof u=="function"?s.bind(null,document).apply(null,arguments):(typeof l=="string"&&(l=document.querySelectorAll(l)),Array.prototype.map.call(l,function(L){return s(L,f,u,d,y)}))}function c(l,f,u,d){return function(y){y.delegateTarget=a(y.target,f),y.delegateTarget&&d.call(l,y)}}o.exports=p},879:function(o,n){n.node=function(i){return i!==void 0&&i instanceof HTMLElement&&i.nodeType===1},n.nodeList=function(i){var a=Object.prototype.toString.call(i);return i!==void 0&&(a==="[object NodeList]"||a==="[object HTMLCollection]")&&"length"in i&&(i.length===0||n.node(i[0]))},n.string=function(i){return typeof i=="string"||i instanceof String},n.fn=function(i){var a=Object.prototype.toString.call(i);return a==="[object Function]"}},370:function(o,n,i){var a=i(879),s=i(438);function p(u,d,y){if(!u&&!d&&!y)throw new Error("Missing required arguments");if(!a.string(d))throw new TypeError("Second argument must be a String");if(!a.fn(y))throw new TypeError("Third argument must be a Function");if(a.node(u))return c(u,d,y);if(a.nodeList(u))return l(u,d,y);if(a.string(u))return f(u,d,y);throw new TypeError("First argument must be a String, HTMLElement, HTMLCollection, or NodeList")}function c(u,d,y){return u.addEventListener(d,y),{destroy:function(){u.removeEventListener(d,y)}}}function l(u,d,y){return Array.prototype.forEach.call(u,function(L){L.addEventListener(d,y)}),{destroy:function(){Array.prototype.forEach.call(u,function(L){L.removeEventListener(d,y)})}}}function f(u,d,y){return s(document.body,u,d,y)}o.exports=p},817:function(o){function n(i){var a;if(i.nodeName==="SELECT")i.focus(),a=i.value;else if(i.nodeName==="INPUT"||i.nodeName==="TEXTAREA"){var s=i.hasAttribute("readonly");s||i.setAttribute("readonly",""),i.select(),i.setSelectionRange(0,i.value.length),s||i.removeAttribute("readonly"),a=i.value}else{i.hasAttribute("contenteditable")&&i.focus();var p=window.getSelection(),c=document.createRange();c.selectNodeContents(i),p.removeAllRanges(),p.addRange(c),a=p.toString()}return a}o.exports=n},279:function(o){function n(){}n.prototype={on:function(i,a,s){var p=this.e||(this.e={});return(p[i]||(p[i]=[])).push({fn:a,ctx:s}),this},once:function(i,a,s){var p=this;function c(){p.off(i,c),a.apply(s,arguments)}return c._=a,this.on(i,c,s)},emit:function(i){var a=[].slice.call(arguments,1),s=((this.e||(this.e={}))[i]||[]).slice(),p=0,c=s.length;for(p;p0&&i[i.length-1])&&(c[0]===6||c[0]===2)){r=0;continue}if(c[0]===3&&(!i||c[1]>i[0]&&c[1]=e.length&&(e=void 0),{value:e&&e[o++],done:!e}}};throw new TypeError(t?"Object is not iterable.":"Symbol.iterator is not defined.")}function z(e,t){var r=typeof Symbol=="function"&&e[Symbol.iterator];if(!r)return e;var o=r.call(e),n,i=[],a;try{for(;(t===void 0||t-- >0)&&!(n=o.next()).done;)i.push(n.value)}catch(s){a={error:s}}finally{try{n&&!n.done&&(r=o.return)&&r.call(o)}finally{if(a)throw a.error}}return i}function q(e,t,r){if(r||arguments.length===2)for(var o=0,n=t.length,i;o1||p(d,L)})},y&&(n[d]=y(n[d])))}function p(d,y){try{c(o[d](y))}catch(L){u(i[0][3],L)}}function c(d){d.value instanceof nt?Promise.resolve(d.value.v).then(l,f):u(i[0][2],d)}function l(d){p("next",d)}function f(d){p("throw",d)}function u(d,y){d(y),i.shift(),i.length&&p(i[0][0],i[0][1])}}function uo(e){if(!Symbol.asyncIterator)throw new TypeError("Symbol.asyncIterator is not defined.");var t=e[Symbol.asyncIterator],r;return t?t.call(e):(e=typeof he=="function"?he(e):e[Symbol.iterator](),r={},o("next"),o("throw"),o("return"),r[Symbol.asyncIterator]=function(){return this},r);function o(i){r[i]=e[i]&&function(a){return new Promise(function(s,p){a=e[i](a),n(s,p,a.done,a.value)})}}function n(i,a,s,p){Promise.resolve(p).then(function(c){i({value:c,done:s})},a)}}function H(e){return typeof e=="function"}function ut(e){var t=function(o){Error.call(o),o.stack=new Error().stack},r=e(t);return r.prototype=Object.create(Error.prototype),r.prototype.constructor=r,r}var zt=ut(function(e){return function(r){e(this),this.message=r?r.length+` errors occurred during unsubscription: -`+r.map(function(o,n){return n+1+") "+o.toString()}).join(` - `):"",this.name="UnsubscriptionError",this.errors=r}});function Qe(e,t){if(e){var r=e.indexOf(t);0<=r&&e.splice(r,1)}}var Ue=function(){function e(t){this.initialTeardown=t,this.closed=!1,this._parentage=null,this._finalizers=null}return e.prototype.unsubscribe=function(){var t,r,o,n,i;if(!this.closed){this.closed=!0;var a=this._parentage;if(a)if(this._parentage=null,Array.isArray(a))try{for(var s=he(a),p=s.next();!p.done;p=s.next()){var c=p.value;c.remove(this)}}catch(L){t={error:L}}finally{try{p&&!p.done&&(r=s.return)&&r.call(s)}finally{if(t)throw t.error}}else a.remove(this);var l=this.initialTeardown;if(H(l))try{l()}catch(L){i=L instanceof zt?L.errors:[L]}var f=this._finalizers;if(f){this._finalizers=null;try{for(var u=he(f),d=u.next();!d.done;d=u.next()){var y=d.value;try{ho(y)}catch(L){i=i!=null?i:[],L instanceof zt?i=q(q([],z(i)),z(L.errors)):i.push(L)}}}catch(L){o={error:L}}finally{try{d&&!d.done&&(n=u.return)&&n.call(u)}finally{if(o)throw o.error}}}if(i)throw new zt(i)}},e.prototype.add=function(t){var r;if(t&&t!==this)if(this.closed)ho(t);else{if(t instanceof e){if(t.closed||t._hasParent(this))return;t._addParent(this)}(this._finalizers=(r=this._finalizers)!==null&&r!==void 0?r:[]).push(t)}},e.prototype._hasParent=function(t){var r=this._parentage;return r===t||Array.isArray(r)&&r.includes(t)},e.prototype._addParent=function(t){var r=this._parentage;this._parentage=Array.isArray(r)?(r.push(t),r):r?[r,t]:t},e.prototype._removeParent=function(t){var r=this._parentage;r===t?this._parentage=null:Array.isArray(r)&&Qe(r,t)},e.prototype.remove=function(t){var r=this._finalizers;r&&Qe(r,t),t instanceof e&&t._removeParent(this)},e.EMPTY=function(){var t=new e;return t.closed=!0,t}(),e}();var Tr=Ue.EMPTY;function Nt(e){return e instanceof Ue||e&&"closed"in e&&H(e.remove)&&H(e.add)&&H(e.unsubscribe)}function ho(e){H(e)?e():e.unsubscribe()}var Pe={onUnhandledError:null,onStoppedNotification:null,Promise:void 0,useDeprecatedSynchronousErrorHandling:!1,useDeprecatedNextContext:!1};var dt={setTimeout:function(e,t){for(var r=[],o=2;o0},enumerable:!1,configurable:!0}),t.prototype._trySubscribe=function(r){return this._throwIfClosed(),e.prototype._trySubscribe.call(this,r)},t.prototype._subscribe=function(r){return this._throwIfClosed(),this._checkFinalizedStatuses(r),this._innerSubscribe(r)},t.prototype._innerSubscribe=function(r){var o=this,n=this,i=n.hasError,a=n.isStopped,s=n.observers;return i||a?Tr:(this.currentObservers=null,s.push(r),new Ue(function(){o.currentObservers=null,Qe(s,r)}))},t.prototype._checkFinalizedStatuses=function(r){var o=this,n=o.hasError,i=o.thrownError,a=o.isStopped;n?r.error(i):a&&r.complete()},t.prototype.asObservable=function(){var r=new j;return r.source=this,r},t.create=function(r,o){return new To(r,o)},t}(j);var To=function(e){oe(t,e);function t(r,o){var n=e.call(this)||this;return n.destination=r,n.source=o,n}return t.prototype.next=function(r){var o,n;(n=(o=this.destination)===null||o===void 0?void 0:o.next)===null||n===void 0||n.call(o,r)},t.prototype.error=function(r){var o,n;(n=(o=this.destination)===null||o===void 0?void 0:o.error)===null||n===void 0||n.call(o,r)},t.prototype.complete=function(){var r,o;(o=(r=this.destination)===null||r===void 0?void 0:r.complete)===null||o===void 0||o.call(r)},t.prototype._subscribe=function(r){var o,n;return(n=(o=this.source)===null||o===void 0?void 0:o.subscribe(r))!==null&&n!==void 0?n:Tr},t}(g);var _r=function(e){oe(t,e);function t(r){var o=e.call(this)||this;return o._value=r,o}return Object.defineProperty(t.prototype,"value",{get:function(){return this.getValue()},enumerable:!1,configurable:!0}),t.prototype._subscribe=function(r){var o=e.prototype._subscribe.call(this,r);return!o.closed&&r.next(this._value),o},t.prototype.getValue=function(){var r=this,o=r.hasError,n=r.thrownError,i=r._value;if(o)throw n;return this._throwIfClosed(),i},t.prototype.next=function(r){e.prototype.next.call(this,this._value=r)},t}(g);var _t={now:function(){return(_t.delegate||Date).now()},delegate:void 0};var At=function(e){oe(t,e);function t(r,o,n){r===void 0&&(r=1/0),o===void 0&&(o=1/0),n===void 0&&(n=_t);var i=e.call(this)||this;return i._bufferSize=r,i._windowTime=o,i._timestampProvider=n,i._buffer=[],i._infiniteTimeWindow=!0,i._infiniteTimeWindow=o===1/0,i._bufferSize=Math.max(1,r),i._windowTime=Math.max(1,o),i}return t.prototype.next=function(r){var o=this,n=o.isStopped,i=o._buffer,a=o._infiniteTimeWindow,s=o._timestampProvider,p=o._windowTime;n||(i.push(r),!a&&i.push(s.now()+p)),this._trimBuffer(),e.prototype.next.call(this,r)},t.prototype._subscribe=function(r){this._throwIfClosed(),this._trimBuffer();for(var o=this._innerSubscribe(r),n=this,i=n._infiniteTimeWindow,a=n._buffer,s=a.slice(),p=0;p0?e.prototype.schedule.call(this,r,o):(this.delay=o,this.state=r,this.scheduler.flush(this),this)},t.prototype.execute=function(r,o){return o>0||this.closed?e.prototype.execute.call(this,r,o):this._execute(r,o)},t.prototype.requestAsyncId=function(r,o,n){return n===void 0&&(n=0),n!=null&&n>0||n==null&&this.delay>0?e.prototype.requestAsyncId.call(this,r,o,n):(r.flush(this),0)},t}(gt);var Lo=function(e){oe(t,e);function t(){return e!==null&&e.apply(this,arguments)||this}return t}(yt);var kr=new Lo(Oo);var Mo=function(e){oe(t,e);function t(r,o){var n=e.call(this,r,o)||this;return n.scheduler=r,n.work=o,n}return t.prototype.requestAsyncId=function(r,o,n){return n===void 0&&(n=0),n!==null&&n>0?e.prototype.requestAsyncId.call(this,r,o,n):(r.actions.push(this),r._scheduled||(r._scheduled=vt.requestAnimationFrame(function(){return r.flush(void 0)})))},t.prototype.recycleAsyncId=function(r,o,n){var i;if(n===void 0&&(n=0),n!=null?n>0:this.delay>0)return e.prototype.recycleAsyncId.call(this,r,o,n);var a=r.actions;o!=null&&o===r._scheduled&&((i=a[a.length-1])===null||i===void 0?void 0:i.id)!==o&&(vt.cancelAnimationFrame(o),r._scheduled=void 0)},t}(gt);var _o=function(e){oe(t,e);function t(){return e!==null&&e.apply(this,arguments)||this}return t.prototype.flush=function(r){this._active=!0;var o;r?o=r.id:(o=this._scheduled,this._scheduled=void 0);var n=this.actions,i;r=r||n.shift();do if(i=r.execute(r.state,r.delay))break;while((r=n[0])&&r.id===o&&n.shift());if(this._active=!1,i){for(;(r=n[0])&&r.id===o&&n.shift();)r.unsubscribe();throw i}},t}(yt);var me=new _o(Mo);var S=new j(function(e){return e.complete()});function Kt(e){return e&&H(e.schedule)}function Hr(e){return e[e.length-1]}function Xe(e){return H(Hr(e))?e.pop():void 0}function ke(e){return Kt(Hr(e))?e.pop():void 0}function Yt(e,t){return typeof Hr(e)=="number"?e.pop():t}var xt=function(e){return e&&typeof e.length=="number"&&typeof e!="function"};function Bt(e){return H(e==null?void 0:e.then)}function Gt(e){return H(e[bt])}function Jt(e){return Symbol.asyncIterator&&H(e==null?void 0:e[Symbol.asyncIterator])}function Xt(e){return new TypeError("You provided "+(e!==null&&typeof e=="object"?"an invalid object":"'"+e+"'")+" where a stream was expected. You can provide an Observable, Promise, ReadableStream, Array, AsyncIterable, or Iterable.")}function Zi(){return typeof Symbol!="function"||!Symbol.iterator?"@@iterator":Symbol.iterator}var Zt=Zi();function er(e){return H(e==null?void 0:e[Zt])}function tr(e){return fo(this,arguments,function(){var r,o,n,i;return Dt(this,function(a){switch(a.label){case 0:r=e.getReader(),a.label=1;case 1:a.trys.push([1,,9,10]),a.label=2;case 2:return[4,nt(r.read())];case 3:return o=a.sent(),n=o.value,i=o.done,i?[4,nt(void 0)]:[3,5];case 4:return[2,a.sent()];case 5:return[4,nt(n)];case 6:return[4,a.sent()];case 7:return a.sent(),[3,2];case 8:return[3,10];case 9:return r.releaseLock(),[7];case 10:return[2]}})})}function rr(e){return H(e==null?void 0:e.getReader)}function U(e){if(e instanceof j)return e;if(e!=null){if(Gt(e))return ea(e);if(xt(e))return ta(e);if(Bt(e))return ra(e);if(Jt(e))return Ao(e);if(er(e))return oa(e);if(rr(e))return na(e)}throw Xt(e)}function ea(e){return new j(function(t){var r=e[bt]();if(H(r.subscribe))return r.subscribe(t);throw new TypeError("Provided object does not correctly implement Symbol.observable")})}function ta(e){return new j(function(t){for(var r=0;r=2;return function(o){return o.pipe(e?b(function(n,i){return e(n,i,o)}):le,Te(1),r?Ve(t):Qo(function(){return new nr}))}}function jr(e){return e<=0?function(){return S}:E(function(t,r){var o=[];t.subscribe(T(r,function(n){o.push(n),e=2,!0))}function pe(e){e===void 0&&(e={});var t=e.connector,r=t===void 0?function(){return new g}:t,o=e.resetOnError,n=o===void 0?!0:o,i=e.resetOnComplete,a=i===void 0?!0:i,s=e.resetOnRefCountZero,p=s===void 0?!0:s;return function(c){var l,f,u,d=0,y=!1,L=!1,X=function(){f==null||f.unsubscribe(),f=void 0},ee=function(){X(),l=u=void 0,y=L=!1},J=function(){var k=l;ee(),k==null||k.unsubscribe()};return E(function(k,ft){d++,!L&&!y&&X();var qe=u=u!=null?u:r();ft.add(function(){d--,d===0&&!L&&!y&&(f=Ur(J,p))}),qe.subscribe(ft),!l&&d>0&&(l=new at({next:function(Fe){return qe.next(Fe)},error:function(Fe){L=!0,X(),f=Ur(ee,n,Fe),qe.error(Fe)},complete:function(){y=!0,X(),f=Ur(ee,a),qe.complete()}}),U(k).subscribe(l))})(c)}}function Ur(e,t){for(var r=[],o=2;oe.next(document)),e}function P(e,t=document){return Array.from(t.querySelectorAll(e))}function R(e,t=document){let r=fe(e,t);if(typeof r=="undefined")throw new ReferenceError(`Missing element: expected "${e}" to be present`);return r}function fe(e,t=document){return t.querySelector(e)||void 0}function Ie(){var e,t,r,o;return(o=(r=(t=(e=document.activeElement)==null?void 0:e.shadowRoot)==null?void 0:t.activeElement)!=null?r:document.activeElement)!=null?o:void 0}var wa=O(h(document.body,"focusin"),h(document.body,"focusout")).pipe(_e(1),Q(void 0),m(()=>Ie()||document.body),G(1));function et(e){return wa.pipe(m(t=>e.contains(t)),K())}function Ht(e,t){return C(()=>O(h(e,"mouseenter").pipe(m(()=>!0)),h(e,"mouseleave").pipe(m(()=>!1))).pipe(t?kt(r=>Le(+!r*t)):le,Q(e.matches(":hover"))))}function Jo(e,t){if(typeof t=="string"||typeof t=="number")e.innerHTML+=t.toString();else if(t instanceof Node)e.appendChild(t);else if(Array.isArray(t))for(let r of t)Jo(e,r)}function x(e,t,...r){let o=document.createElement(e);if(t)for(let n of Object.keys(t))typeof t[n]!="undefined"&&(typeof t[n]!="boolean"?o.setAttribute(n,t[n]):o.setAttribute(n,""));for(let n of r)Jo(o,n);return o}function sr(e){if(e>999){let t=+((e-950)%1e3>99);return`${((e+1e-6)/1e3).toFixed(t)}k`}else return e.toString()}function wt(e){let t=x("script",{src:e});return C(()=>(document.head.appendChild(t),O(h(t,"load"),h(t,"error").pipe(v(()=>$r(()=>new ReferenceError(`Invalid script: ${e}`))))).pipe(m(()=>{}),_(()=>document.head.removeChild(t)),Te(1))))}var Xo=new g,Ta=C(()=>typeof ResizeObserver=="undefined"?wt("https://unpkg.com/resize-observer-polyfill"):I(void 0)).pipe(m(()=>new ResizeObserver(e=>e.forEach(t=>Xo.next(t)))),v(e=>O(Ye,I(e)).pipe(_(()=>e.disconnect()))),G(1));function ce(e){return{width:e.offsetWidth,height:e.offsetHeight}}function ge(e){let t=e;for(;t.clientWidth===0&&t.parentElement;)t=t.parentElement;return Ta.pipe(w(r=>r.observe(t)),v(r=>Xo.pipe(b(o=>o.target===t),_(()=>r.unobserve(t)))),m(()=>ce(e)),Q(ce(e)))}function Tt(e){return{width:e.scrollWidth,height:e.scrollHeight}}function cr(e){let t=e.parentElement;for(;t&&(e.scrollWidth<=t.scrollWidth&&e.scrollHeight<=t.scrollHeight);)t=(e=t).parentElement;return t?e:void 0}function Zo(e){let t=[],r=e.parentElement;for(;r;)(e.clientWidth>r.clientWidth||e.clientHeight>r.clientHeight)&&t.push(r),r=(e=r).parentElement;return t.length===0&&t.push(document.documentElement),t}function De(e){return{x:e.offsetLeft,y:e.offsetTop}}function en(e){let t=e.getBoundingClientRect();return{x:t.x+window.scrollX,y:t.y+window.scrollY}}function tn(e){return O(h(window,"load"),h(window,"resize")).pipe(Me(0,me),m(()=>De(e)),Q(De(e)))}function pr(e){return{x:e.scrollLeft,y:e.scrollTop}}function ze(e){return O(h(e,"scroll"),h(window,"scroll"),h(window,"resize")).pipe(Me(0,me),m(()=>pr(e)),Q(pr(e)))}var rn=new g,Sa=C(()=>I(new IntersectionObserver(e=>{for(let t of e)rn.next(t)},{threshold:0}))).pipe(v(e=>O(Ye,I(e)).pipe(_(()=>e.disconnect()))),G(1));function tt(e){return Sa.pipe(w(t=>t.observe(e)),v(t=>rn.pipe(b(({target:r})=>r===e),_(()=>t.unobserve(e)),m(({isIntersecting:r})=>r))))}function on(e,t=16){return ze(e).pipe(m(({y:r})=>{let o=ce(e),n=Tt(e);return r>=n.height-o.height-t}),K())}var lr={drawer:R("[data-md-toggle=drawer]"),search:R("[data-md-toggle=search]")};function nn(e){return lr[e].checked}function Je(e,t){lr[e].checked!==t&&lr[e].click()}function Ne(e){let t=lr[e];return h(t,"change").pipe(m(()=>t.checked),Q(t.checked))}function Oa(e,t){switch(e.constructor){case HTMLInputElement:return e.type==="radio"?/^Arrow/.test(t):!0;case HTMLSelectElement:case HTMLTextAreaElement:return!0;default:return e.isContentEditable}}function La(){return O(h(window,"compositionstart").pipe(m(()=>!0)),h(window,"compositionend").pipe(m(()=>!1))).pipe(Q(!1))}function an(){let e=h(window,"keydown").pipe(b(t=>!(t.metaKey||t.ctrlKey)),m(t=>({mode:nn("search")?"search":"global",type:t.key,claim(){t.preventDefault(),t.stopPropagation()}})),b(({mode:t,type:r})=>{if(t==="global"){let o=Ie();if(typeof o!="undefined")return!Oa(o,r)}return!0}),pe());return La().pipe(v(t=>t?S:e))}function ye(){return new URL(location.href)}function lt(e,t=!1){if(B("navigation.instant")&&!t){let r=x("a",{href:e.href});document.body.appendChild(r),r.click(),r.remove()}else location.href=e.href}function sn(){return new g}function cn(){return location.hash.slice(1)}function pn(e){let t=x("a",{href:e});t.addEventListener("click",r=>r.stopPropagation()),t.click()}function Ma(e){return O(h(window,"hashchange"),e).pipe(m(cn),Q(cn()),b(t=>t.length>0),G(1))}function ln(e){return Ma(e).pipe(m(t=>fe(`[id="${t}"]`)),b(t=>typeof t!="undefined"))}function $t(e){let t=matchMedia(e);return ir(r=>t.addListener(()=>r(t.matches))).pipe(Q(t.matches))}function mn(){let e=matchMedia("print");return O(h(window,"beforeprint").pipe(m(()=>!0)),h(window,"afterprint").pipe(m(()=>!1))).pipe(Q(e.matches))}function zr(e,t){return e.pipe(v(r=>r?t():S))}function Nr(e,t){return new j(r=>{let o=new XMLHttpRequest;return o.open("GET",`${e}`),o.responseType="blob",o.addEventListener("load",()=>{o.status>=200&&o.status<300?(r.next(o.response),r.complete()):r.error(new Error(o.statusText))}),o.addEventListener("error",()=>{r.error(new Error("Network error"))}),o.addEventListener("abort",()=>{r.complete()}),typeof(t==null?void 0:t.progress$)!="undefined"&&(o.addEventListener("progress",n=>{var i;if(n.lengthComputable)t.progress$.next(n.loaded/n.total*100);else{let a=(i=o.getResponseHeader("Content-Length"))!=null?i:0;t.progress$.next(n.loaded/+a*100)}}),t.progress$.next(5)),o.send(),()=>o.abort()})}function je(e,t){return Nr(e,t).pipe(v(r=>r.text()),m(r=>JSON.parse(r)),G(1))}function fn(e,t){let r=new DOMParser;return Nr(e,t).pipe(v(o=>o.text()),m(o=>r.parseFromString(o,"text/html")),G(1))}function un(e,t){let r=new DOMParser;return Nr(e,t).pipe(v(o=>o.text()),m(o=>r.parseFromString(o,"text/xml")),G(1))}function dn(){return{x:Math.max(0,scrollX),y:Math.max(0,scrollY)}}function hn(){return O(h(window,"scroll",{passive:!0}),h(window,"resize",{passive:!0})).pipe(m(dn),Q(dn()))}function bn(){return{width:innerWidth,height:innerHeight}}function vn(){return h(window,"resize",{passive:!0}).pipe(m(bn),Q(bn()))}function gn(){return N([hn(),vn()]).pipe(m(([e,t])=>({offset:e,size:t})),G(1))}function mr(e,{viewport$:t,header$:r}){let o=t.pipe(te("size")),n=N([o,r]).pipe(m(()=>De(e)));return N([r,t,n]).pipe(m(([{height:i},{offset:a,size:s},{x:p,y:c}])=>({offset:{x:a.x-p,y:a.y-c+i},size:s})))}function _a(e){return h(e,"message",t=>t.data)}function Aa(e){let t=new g;return t.subscribe(r=>e.postMessage(r)),t}function yn(e,t=new Worker(e)){let r=_a(t),o=Aa(t),n=new g;n.subscribe(o);let i=o.pipe(Z(),ie(!0));return n.pipe(Z(),Re(r.pipe(W(i))),pe())}var Ca=R("#__config"),St=JSON.parse(Ca.textContent);St.base=`${new URL(St.base,ye())}`;function xe(){return St}function B(e){return St.features.includes(e)}function Ee(e,t){return typeof t!="undefined"?St.translations[e].replace("#",t.toString()):St.translations[e]}function Se(e,t=document){return R(`[data-md-component=${e}]`,t)}function ae(e,t=document){return P(`[data-md-component=${e}]`,t)}function ka(e){let t=R(".md-typeset > :first-child",e);return h(t,"click",{once:!0}).pipe(m(()=>R(".md-typeset",e)),m(r=>({hash:__md_hash(r.innerHTML)})))}function xn(e){if(!B("announce.dismiss")||!e.childElementCount)return S;if(!e.hidden){let t=R(".md-typeset",e);__md_hash(t.innerHTML)===__md_get("__announce")&&(e.hidden=!0)}return C(()=>{let t=new g;return t.subscribe(({hash:r})=>{e.hidden=!0,__md_set("__announce",r)}),ka(e).pipe(w(r=>t.next(r)),_(()=>t.complete()),m(r=>$({ref:e},r)))})}function Ha(e,{target$:t}){return t.pipe(m(r=>({hidden:r!==e})))}function En(e,t){let r=new g;return r.subscribe(({hidden:o})=>{e.hidden=o}),Ha(e,t).pipe(w(o=>r.next(o)),_(()=>r.complete()),m(o=>$({ref:e},o)))}function Pt(e,t){return t==="inline"?x("div",{class:"md-tooltip md-tooltip--inline",id:e,role:"tooltip"},x("div",{class:"md-tooltip__inner md-typeset"})):x("div",{class:"md-tooltip",id:e,role:"tooltip"},x("div",{class:"md-tooltip__inner md-typeset"}))}function wn(...e){return x("div",{class:"md-tooltip2",role:"tooltip"},x("div",{class:"md-tooltip2__inner md-typeset"},e))}function Tn(e,t){if(t=t?`${t}_annotation_${e}`:void 0,t){let r=t?`#${t}`:void 0;return x("aside",{class:"md-annotation",tabIndex:0},Pt(t),x("a",{href:r,class:"md-annotation__index",tabIndex:-1},x("span",{"data-md-annotation-id":e})))}else return x("aside",{class:"md-annotation",tabIndex:0},Pt(t),x("span",{class:"md-annotation__index",tabIndex:-1},x("span",{"data-md-annotation-id":e})))}function Sn(e){return x("button",{class:"md-clipboard md-icon",title:Ee("clipboard.copy"),"data-clipboard-target":`#${e} > code`})}var Ln=Lt(qr());function Qr(e,t){let r=t&2,o=t&1,n=Object.keys(e.terms).filter(p=>!e.terms[p]).reduce((p,c)=>[...p,x("del",null,(0,Ln.default)(c))," "],[]).slice(0,-1),i=xe(),a=new URL(e.location,i.base);B("search.highlight")&&a.searchParams.set("h",Object.entries(e.terms).filter(([,p])=>p).reduce((p,[c])=>`${p} ${c}`.trim(),""));let{tags:s}=xe();return x("a",{href:`${a}`,class:"md-search-result__link",tabIndex:-1},x("article",{class:"md-search-result__article md-typeset","data-md-score":e.score.toFixed(2)},r>0&&x("div",{class:"md-search-result__icon md-icon"}),r>0&&x("h1",null,e.title),r<=0&&x("h2",null,e.title),o>0&&e.text.length>0&&e.text,e.tags&&x("nav",{class:"md-tags"},e.tags.map(p=>{let c=s?p in s?`md-tag-icon md-tag--${s[p]}`:"md-tag-icon":"";return x("span",{class:`md-tag ${c}`},p)})),o>0&&n.length>0&&x("p",{class:"md-search-result__terms"},Ee("search.result.term.missing"),": ",...n)))}function Mn(e){let t=e[0].score,r=[...e],o=xe(),n=r.findIndex(l=>!`${new URL(l.location,o.base)}`.includes("#")),[i]=r.splice(n,1),a=r.findIndex(l=>l.scoreQr(l,1)),...p.length?[x("details",{class:"md-search-result__more"},x("summary",{tabIndex:-1},x("div",null,p.length>0&&p.length===1?Ee("search.result.more.one"):Ee("search.result.more.other",p.length))),...p.map(l=>Qr(l,1)))]:[]];return x("li",{class:"md-search-result__item"},c)}function _n(e){return x("ul",{class:"md-source__facts"},Object.entries(e).map(([t,r])=>x("li",{class:`md-source__fact md-source__fact--${t}`},typeof r=="number"?sr(r):r)))}function Kr(e){let t=`tabbed-control tabbed-control--${e}`;return x("div",{class:t,hidden:!0},x("button",{class:"tabbed-button",tabIndex:-1,"aria-hidden":"true"}))}function An(e){return x("div",{class:"md-typeset__scrollwrap"},x("div",{class:"md-typeset__table"},e))}function Ra(e){var o;let t=xe(),r=new URL(`../${e.version}/`,t.base);return x("li",{class:"md-version__item"},x("a",{href:`${r}`,class:"md-version__link"},e.title,((o=t.version)==null?void 0:o.alias)&&e.aliases.length>0&&x("span",{class:"md-version__alias"},e.aliases[0])))}function Cn(e,t){var o;let r=xe();return e=e.filter(n=>{var i;return!((i=n.properties)!=null&&i.hidden)}),x("div",{class:"md-version"},x("button",{class:"md-version__current","aria-label":Ee("select.version")},t.title,((o=r.version)==null?void 0:o.alias)&&t.aliases.length>0&&x("span",{class:"md-version__alias"},t.aliases[0])),x("ul",{class:"md-version__list"},e.map(Ra)))}var Ia=0;function ja(e){let t=N([et(e),Ht(e)]).pipe(m(([o,n])=>o||n),K()),r=C(()=>Zo(e)).pipe(ne(ze),pt(1),He(t),m(()=>en(e)));return t.pipe(Ae(o=>o),v(()=>N([t,r])),m(([o,n])=>({active:o,offset:n})),pe())}function Fa(e,t){let{content$:r,viewport$:o}=t,n=`__tooltip2_${Ia++}`;return C(()=>{let i=new g,a=new _r(!1);i.pipe(Z(),ie(!1)).subscribe(a);let s=a.pipe(kt(c=>Le(+!c*250,kr)),K(),v(c=>c?r:S),w(c=>c.id=n),pe());N([i.pipe(m(({active:c})=>c)),s.pipe(v(c=>Ht(c,250)),Q(!1))]).pipe(m(c=>c.some(l=>l))).subscribe(a);let p=a.pipe(b(c=>c),re(s,o),m(([c,l,{size:f}])=>{let u=e.getBoundingClientRect(),d=u.width/2;if(l.role==="tooltip")return{x:d,y:8+u.height};if(u.y>=f.height/2){let{height:y}=ce(l);return{x:d,y:-16-y}}else return{x:d,y:16+u.height}}));return N([s,i,p]).subscribe(([c,{offset:l},f])=>{c.style.setProperty("--md-tooltip-host-x",`${l.x}px`),c.style.setProperty("--md-tooltip-host-y",`${l.y}px`),c.style.setProperty("--md-tooltip-x",`${f.x}px`),c.style.setProperty("--md-tooltip-y",`${f.y}px`),c.classList.toggle("md-tooltip2--top",f.y<0),c.classList.toggle("md-tooltip2--bottom",f.y>=0)}),a.pipe(b(c=>c),re(s,(c,l)=>l),b(c=>c.role==="tooltip")).subscribe(c=>{let l=ce(R(":scope > *",c));c.style.setProperty("--md-tooltip-width",`${l.width}px`),c.style.setProperty("--md-tooltip-tail","0px")}),a.pipe(K(),ve(me),re(s)).subscribe(([c,l])=>{l.classList.toggle("md-tooltip2--active",c)}),N([a.pipe(b(c=>c)),s]).subscribe(([c,l])=>{l.role==="dialog"?(e.setAttribute("aria-controls",n),e.setAttribute("aria-haspopup","dialog")):e.setAttribute("aria-describedby",n)}),a.pipe(b(c=>!c)).subscribe(()=>{e.removeAttribute("aria-controls"),e.removeAttribute("aria-describedby"),e.removeAttribute("aria-haspopup")}),ja(e).pipe(w(c=>i.next(c)),_(()=>i.complete()),m(c=>$({ref:e},c)))})}function mt(e,{viewport$:t},r=document.body){return Fa(e,{content$:new j(o=>{let n=e.title,i=wn(n);return o.next(i),e.removeAttribute("title"),r.append(i),()=>{i.remove(),e.setAttribute("title",n)}}),viewport$:t})}function Ua(e,t){let r=C(()=>N([tn(e),ze(t)])).pipe(m(([{x:o,y:n},i])=>{let{width:a,height:s}=ce(e);return{x:o-i.x+a/2,y:n-i.y+s/2}}));return et(e).pipe(v(o=>r.pipe(m(n=>({active:o,offset:n})),Te(+!o||1/0))))}function kn(e,t,{target$:r}){let[o,n]=Array.from(e.children);return C(()=>{let i=new g,a=i.pipe(Z(),ie(!0));return i.subscribe({next({offset:s}){e.style.setProperty("--md-tooltip-x",`${s.x}px`),e.style.setProperty("--md-tooltip-y",`${s.y}px`)},complete(){e.style.removeProperty("--md-tooltip-x"),e.style.removeProperty("--md-tooltip-y")}}),tt(e).pipe(W(a)).subscribe(s=>{e.toggleAttribute("data-md-visible",s)}),O(i.pipe(b(({active:s})=>s)),i.pipe(_e(250),b(({active:s})=>!s))).subscribe({next({active:s}){s?e.prepend(o):o.remove()},complete(){e.prepend(o)}}),i.pipe(Me(16,me)).subscribe(({active:s})=>{o.classList.toggle("md-tooltip--active",s)}),i.pipe(pt(125,me),b(()=>!!e.offsetParent),m(()=>e.offsetParent.getBoundingClientRect()),m(({x:s})=>s)).subscribe({next(s){s?e.style.setProperty("--md-tooltip-0",`${-s}px`):e.style.removeProperty("--md-tooltip-0")},complete(){e.style.removeProperty("--md-tooltip-0")}}),h(n,"click").pipe(W(a),b(s=>!(s.metaKey||s.ctrlKey))).subscribe(s=>{s.stopPropagation(),s.preventDefault()}),h(n,"mousedown").pipe(W(a),re(i)).subscribe(([s,{active:p}])=>{var c;if(s.button!==0||s.metaKey||s.ctrlKey)s.preventDefault();else if(p){s.preventDefault();let l=e.parentElement.closest(".md-annotation");l instanceof HTMLElement?l.focus():(c=Ie())==null||c.blur()}}),r.pipe(W(a),b(s=>s===o),Ge(125)).subscribe(()=>e.focus()),Ua(e,t).pipe(w(s=>i.next(s)),_(()=>i.complete()),m(s=>$({ref:e},s)))})}function Wa(e){return e.tagName==="CODE"?P(".c, .c1, .cm",e):[e]}function Va(e){let t=[];for(let r of Wa(e)){let o=[],n=document.createNodeIterator(r,NodeFilter.SHOW_TEXT);for(let i=n.nextNode();i;i=n.nextNode())o.push(i);for(let i of o){let a;for(;a=/(\(\d+\))(!)?/.exec(i.textContent);){let[,s,p]=a;if(typeof p=="undefined"){let c=i.splitText(a.index);i=c.splitText(s.length),t.push(c)}else{i.textContent=s,t.push(i);break}}}}return t}function Hn(e,t){t.append(...Array.from(e.childNodes))}function fr(e,t,{target$:r,print$:o}){let n=t.closest("[id]"),i=n==null?void 0:n.id,a=new Map;for(let s of Va(t)){let[,p]=s.textContent.match(/\((\d+)\)/);fe(`:scope > li:nth-child(${p})`,e)&&(a.set(p,Tn(p,i)),s.replaceWith(a.get(p)))}return a.size===0?S:C(()=>{let s=new g,p=s.pipe(Z(),ie(!0)),c=[];for(let[l,f]of a)c.push([R(".md-typeset",f),R(`:scope > li:nth-child(${l})`,e)]);return o.pipe(W(p)).subscribe(l=>{e.hidden=!l,e.classList.toggle("md-annotation-list",l);for(let[f,u]of c)l?Hn(f,u):Hn(u,f)}),O(...[...a].map(([,l])=>kn(l,t,{target$:r}))).pipe(_(()=>s.complete()),pe())})}function $n(e){if(e.nextElementSibling){let t=e.nextElementSibling;if(t.tagName==="OL")return t;if(t.tagName==="P"&&!t.children.length)return $n(t)}}function Pn(e,t){return C(()=>{let r=$n(e);return typeof r!="undefined"?fr(r,e,t):S})}var Rn=Lt(Br());var Da=0;function In(e){if(e.nextElementSibling){let t=e.nextElementSibling;if(t.tagName==="OL")return t;if(t.tagName==="P"&&!t.children.length)return In(t)}}function za(e){return ge(e).pipe(m(({width:t})=>({scrollable:Tt(e).width>t})),te("scrollable"))}function jn(e,t){let{matches:r}=matchMedia("(hover)"),o=C(()=>{let n=new g,i=n.pipe(jr(1));n.subscribe(({scrollable:c})=>{c&&r?e.setAttribute("tabindex","0"):e.removeAttribute("tabindex")});let a=[];if(Rn.default.isSupported()&&(e.closest(".copy")||B("content.code.copy")&&!e.closest(".no-copy"))){let c=e.closest("pre");c.id=`__code_${Da++}`;let l=Sn(c.id);c.insertBefore(l,e),B("content.tooltips")&&a.push(mt(l,{viewport$}))}let s=e.closest(".highlight");if(s instanceof HTMLElement){let c=In(s);if(typeof c!="undefined"&&(s.classList.contains("annotate")||B("content.code.annotate"))){let l=fr(c,e,t);a.push(ge(s).pipe(W(i),m(({width:f,height:u})=>f&&u),K(),v(f=>f?l:S)))}}return P(":scope > span[id]",e).length&&e.classList.add("md-code__content"),za(e).pipe(w(c=>n.next(c)),_(()=>n.complete()),m(c=>$({ref:e},c)),Re(...a))});return B("content.lazy")?tt(e).pipe(b(n=>n),Te(1),v(()=>o)):o}function Na(e,{target$:t,print$:r}){let o=!0;return O(t.pipe(m(n=>n.closest("details:not([open])")),b(n=>e===n),m(()=>({action:"open",reveal:!0}))),r.pipe(b(n=>n||!o),w(()=>o=e.open),m(n=>({action:n?"open":"close"}))))}function Fn(e,t){return C(()=>{let r=new g;return r.subscribe(({action:o,reveal:n})=>{e.toggleAttribute("open",o==="open"),n&&e.scrollIntoView()}),Na(e,t).pipe(w(o=>r.next(o)),_(()=>r.complete()),m(o=>$({ref:e},o)))})}var Un=".node circle,.node ellipse,.node path,.node polygon,.node rect{fill:var(--md-mermaid-node-bg-color);stroke:var(--md-mermaid-node-fg-color)}marker{fill:var(--md-mermaid-edge-color)!important}.edgeLabel .label rect{fill:#0000}.flowchartTitleText{fill:var(--md-mermaid-label-fg-color)}.label{color:var(--md-mermaid-label-fg-color);font-family:var(--md-mermaid-font-family)}.label foreignObject{line-height:normal;overflow:visible}.label div .edgeLabel{color:var(--md-mermaid-label-fg-color)}.edgeLabel,.edgeLabel p,.label div .edgeLabel{background-color:var(--md-mermaid-label-bg-color)}.edgeLabel,.edgeLabel p{fill:var(--md-mermaid-label-bg-color);color:var(--md-mermaid-edge-color)}.edgePath .path,.flowchart-link{stroke:var(--md-mermaid-edge-color);stroke-width:.05rem}.edgePath .arrowheadPath{fill:var(--md-mermaid-edge-color);stroke:none}.cluster rect{fill:var(--md-default-fg-color--lightest);stroke:var(--md-default-fg-color--lighter)}.cluster span{color:var(--md-mermaid-label-fg-color);font-family:var(--md-mermaid-font-family)}g #flowchart-circleEnd,g #flowchart-circleStart,g #flowchart-crossEnd,g #flowchart-crossStart,g #flowchart-pointEnd,g #flowchart-pointStart{stroke:none}.classDiagramTitleText{fill:var(--md-mermaid-label-fg-color)}g.classGroup line,g.classGroup rect{fill:var(--md-mermaid-node-bg-color);stroke:var(--md-mermaid-node-fg-color)}g.classGroup text{fill:var(--md-mermaid-label-fg-color);font-family:var(--md-mermaid-font-family)}.classLabel .box{fill:var(--md-mermaid-label-bg-color);background-color:var(--md-mermaid-label-bg-color);opacity:1}.classLabel .label{fill:var(--md-mermaid-label-fg-color);font-family:var(--md-mermaid-font-family)}.node .divider{stroke:var(--md-mermaid-node-fg-color)}.relation{stroke:var(--md-mermaid-edge-color)}.cardinality{fill:var(--md-mermaid-label-fg-color);font-family:var(--md-mermaid-font-family)}.cardinality text{fill:inherit!important}defs marker.marker.composition.class path,defs marker.marker.dependency.class path,defs marker.marker.extension.class path{fill:var(--md-mermaid-edge-color)!important;stroke:var(--md-mermaid-edge-color)!important}defs marker.marker.aggregation.class path{fill:var(--md-mermaid-label-bg-color)!important;stroke:var(--md-mermaid-edge-color)!important}.statediagramTitleText{fill:var(--md-mermaid-label-fg-color)}g.stateGroup rect{fill:var(--md-mermaid-node-bg-color);stroke:var(--md-mermaid-node-fg-color)}g.stateGroup .state-title{fill:var(--md-mermaid-label-fg-color)!important;font-family:var(--md-mermaid-font-family)}g.stateGroup .composit{fill:var(--md-mermaid-label-bg-color)}.nodeLabel,.nodeLabel p{color:var(--md-mermaid-label-fg-color);font-family:var(--md-mermaid-font-family)}a .nodeLabel{text-decoration:underline}.node circle.state-end,.node circle.state-start,.start-state{fill:var(--md-mermaid-edge-color);stroke:none}.end-state-inner,.end-state-outer{fill:var(--md-mermaid-edge-color)}.end-state-inner,.node circle.state-end{stroke:var(--md-mermaid-label-bg-color)}.transition{stroke:var(--md-mermaid-edge-color)}[id^=state-fork] rect,[id^=state-join] rect{fill:var(--md-mermaid-edge-color)!important;stroke:none!important}.statediagram-cluster.statediagram-cluster .inner{fill:var(--md-default-bg-color)}.statediagram-cluster rect{fill:var(--md-mermaid-node-bg-color);stroke:var(--md-mermaid-node-fg-color)}.statediagram-state rect.divider{fill:var(--md-default-fg-color--lightest);stroke:var(--md-default-fg-color--lighter)}defs #statediagram-barbEnd{stroke:var(--md-mermaid-edge-color)}[id^=entity] path,[id^=entity] rect{fill:var(--md-default-bg-color)}.relationshipLine{stroke:var(--md-mermaid-edge-color)}defs .marker.oneOrMore.er *,defs .marker.onlyOne.er *,defs .marker.zeroOrMore.er *,defs .marker.zeroOrOne.er *{stroke:var(--md-mermaid-edge-color)!important}text:not([class]):last-child{fill:var(--md-mermaid-label-fg-color)}.actor{fill:var(--md-mermaid-sequence-actor-bg-color);stroke:var(--md-mermaid-sequence-actor-border-color)}text.actor>tspan{fill:var(--md-mermaid-sequence-actor-fg-color);font-family:var(--md-mermaid-font-family)}line{stroke:var(--md-mermaid-sequence-actor-line-color)}.actor-man circle,.actor-man line{fill:var(--md-mermaid-sequence-actorman-bg-color);stroke:var(--md-mermaid-sequence-actorman-line-color)}.messageLine0,.messageLine1{stroke:var(--md-mermaid-sequence-message-line-color)}.note{fill:var(--md-mermaid-sequence-note-bg-color);stroke:var(--md-mermaid-sequence-note-border-color)}.loopText,.loopText>tspan,.messageText,.noteText>tspan{stroke:none;font-family:var(--md-mermaid-font-family)!important}.messageText{fill:var(--md-mermaid-sequence-message-fg-color)}.loopText,.loopText>tspan{fill:var(--md-mermaid-sequence-loop-fg-color)}.noteText>tspan{fill:var(--md-mermaid-sequence-note-fg-color)}#arrowhead path{fill:var(--md-mermaid-sequence-message-line-color);stroke:none}.loopLine{fill:var(--md-mermaid-sequence-loop-bg-color);stroke:var(--md-mermaid-sequence-loop-border-color)}.labelBox{fill:var(--md-mermaid-sequence-label-bg-color);stroke:none}.labelText,.labelText>span{fill:var(--md-mermaid-sequence-label-fg-color);font-family:var(--md-mermaid-font-family)}.sequenceNumber{fill:var(--md-mermaid-sequence-number-fg-color)}rect.rect{fill:var(--md-mermaid-sequence-box-bg-color);stroke:none}rect.rect+text.text{fill:var(--md-mermaid-sequence-box-fg-color)}defs #sequencenumber{fill:var(--md-mermaid-sequence-number-bg-color)!important}";var Gr,Qa=0;function Ka(){return typeof mermaid=="undefined"||mermaid instanceof Element?wt("https://unpkg.com/mermaid@11/dist/mermaid.min.js"):I(void 0)}function Wn(e){return e.classList.remove("mermaid"),Gr||(Gr=Ka().pipe(w(()=>mermaid.initialize({startOnLoad:!1,themeCSS:Un,sequence:{actorFontSize:"16px",messageFontSize:"16px",noteFontSize:"16px"}})),m(()=>{}),G(1))),Gr.subscribe(()=>co(null,null,function*(){e.classList.add("mermaid");let t=`__mermaid_${Qa++}`,r=x("div",{class:"mermaid"}),o=e.textContent,{svg:n,fn:i}=yield mermaid.render(t,o),a=r.attachShadow({mode:"closed"});a.innerHTML=n,e.replaceWith(r),i==null||i(a)})),Gr.pipe(m(()=>({ref:e})))}var Vn=x("table");function Dn(e){return e.replaceWith(Vn),Vn.replaceWith(An(e)),I({ref:e})}function Ya(e){let t=e.find(r=>r.checked)||e[0];return O(...e.map(r=>h(r,"change").pipe(m(()=>R(`label[for="${r.id}"]`))))).pipe(Q(R(`label[for="${t.id}"]`)),m(r=>({active:r})))}function zn(e,{viewport$:t,target$:r}){let o=R(".tabbed-labels",e),n=P(":scope > input",e),i=Kr("prev");e.append(i);let a=Kr("next");return e.append(a),C(()=>{let s=new g,p=s.pipe(Z(),ie(!0));N([s,ge(e),tt(e)]).pipe(W(p),Me(1,me)).subscribe({next([{active:c},l]){let f=De(c),{width:u}=ce(c);e.style.setProperty("--md-indicator-x",`${f.x}px`),e.style.setProperty("--md-indicator-width",`${u}px`);let d=pr(o);(f.xd.x+l.width)&&o.scrollTo({left:Math.max(0,f.x-16),behavior:"smooth"})},complete(){e.style.removeProperty("--md-indicator-x"),e.style.removeProperty("--md-indicator-width")}}),N([ze(o),ge(o)]).pipe(W(p)).subscribe(([c,l])=>{let f=Tt(o);i.hidden=c.x<16,a.hidden=c.x>f.width-l.width-16}),O(h(i,"click").pipe(m(()=>-1)),h(a,"click").pipe(m(()=>1))).pipe(W(p)).subscribe(c=>{let{width:l}=ce(o);o.scrollBy({left:l*c,behavior:"smooth"})}),r.pipe(W(p),b(c=>n.includes(c))).subscribe(c=>c.click()),o.classList.add("tabbed-labels--linked");for(let c of n){let l=R(`label[for="${c.id}"]`);l.replaceChildren(x("a",{href:`#${l.htmlFor}`,tabIndex:-1},...Array.from(l.childNodes))),h(l.firstElementChild,"click").pipe(W(p),b(f=>!(f.metaKey||f.ctrlKey)),w(f=>{f.preventDefault(),f.stopPropagation()})).subscribe(()=>{history.replaceState({},"",`#${l.htmlFor}`),l.click()})}return B("content.tabs.link")&&s.pipe(Ce(1),re(t)).subscribe(([{active:c},{offset:l}])=>{let f=c.innerText.trim();if(c.hasAttribute("data-md-switching"))c.removeAttribute("data-md-switching");else{let u=e.offsetTop-l.y;for(let y of P("[data-tabs]"))for(let L of P(":scope > input",y)){let X=R(`label[for="${L.id}"]`);if(X!==c&&X.innerText.trim()===f){X.setAttribute("data-md-switching",""),L.click();break}}window.scrollTo({top:e.offsetTop-u});let d=__md_get("__tabs")||[];__md_set("__tabs",[...new Set([f,...d])])}}),s.pipe(W(p)).subscribe(()=>{for(let c of P("audio, video",e))c.pause()}),Ya(n).pipe(w(c=>s.next(c)),_(()=>s.complete()),m(c=>$({ref:e},c)))}).pipe(Ke(se))}function Nn(e,{viewport$:t,target$:r,print$:o}){return O(...P(".annotate:not(.highlight)",e).map(n=>Pn(n,{target$:r,print$:o})),...P("pre:not(.mermaid) > code",e).map(n=>jn(n,{target$:r,print$:o})),...P("pre.mermaid",e).map(n=>Wn(n)),...P("table:not([class])",e).map(n=>Dn(n)),...P("details",e).map(n=>Fn(n,{target$:r,print$:o})),...P("[data-tabs]",e).map(n=>zn(n,{viewport$:t,target$:r})),...P("[title]",e).filter(()=>B("content.tooltips")).map(n=>mt(n,{viewport$:t})))}function Ba(e,{alert$:t}){return t.pipe(v(r=>O(I(!0),I(!1).pipe(Ge(2e3))).pipe(m(o=>({message:r,active:o})))))}function qn(e,t){let r=R(".md-typeset",e);return C(()=>{let o=new g;return o.subscribe(({message:n,active:i})=>{e.classList.toggle("md-dialog--active",i),r.textContent=n}),Ba(e,t).pipe(w(n=>o.next(n)),_(()=>o.complete()),m(n=>$({ref:e},n)))})}var Ga=0;function Ja(e,t){document.body.append(e);let{width:r}=ce(e);e.style.setProperty("--md-tooltip-width",`${r}px`),e.remove();let o=cr(t),n=typeof o!="undefined"?ze(o):I({x:0,y:0}),i=O(et(t),Ht(t)).pipe(K());return N([i,n]).pipe(m(([a,s])=>{let{x:p,y:c}=De(t),l=ce(t),f=t.closest("table");return f&&t.parentElement&&(p+=f.offsetLeft+t.parentElement.offsetLeft,c+=f.offsetTop+t.parentElement.offsetTop),{active:a,offset:{x:p-s.x+l.width/2-r/2,y:c-s.y+l.height+8}}}))}function Qn(e){let t=e.title;if(!t.length)return S;let r=`__tooltip_${Ga++}`,o=Pt(r,"inline"),n=R(".md-typeset",o);return n.innerHTML=t,C(()=>{let i=new g;return i.subscribe({next({offset:a}){o.style.setProperty("--md-tooltip-x",`${a.x}px`),o.style.setProperty("--md-tooltip-y",`${a.y}px`)},complete(){o.style.removeProperty("--md-tooltip-x"),o.style.removeProperty("--md-tooltip-y")}}),O(i.pipe(b(({active:a})=>a)),i.pipe(_e(250),b(({active:a})=>!a))).subscribe({next({active:a}){a?(e.insertAdjacentElement("afterend",o),e.setAttribute("aria-describedby",r),e.removeAttribute("title")):(o.remove(),e.removeAttribute("aria-describedby"),e.setAttribute("title",t))},complete(){o.remove(),e.removeAttribute("aria-describedby"),e.setAttribute("title",t)}}),i.pipe(Me(16,me)).subscribe(({active:a})=>{o.classList.toggle("md-tooltip--active",a)}),i.pipe(pt(125,me),b(()=>!!e.offsetParent),m(()=>e.offsetParent.getBoundingClientRect()),m(({x:a})=>a)).subscribe({next(a){a?o.style.setProperty("--md-tooltip-0",`${-a}px`):o.style.removeProperty("--md-tooltip-0")},complete(){o.style.removeProperty("--md-tooltip-0")}}),Ja(o,e).pipe(w(a=>i.next(a)),_(()=>i.complete()),m(a=>$({ref:e},a)))}).pipe(Ke(se))}function Xa({viewport$:e}){if(!B("header.autohide"))return I(!1);let t=e.pipe(m(({offset:{y:n}})=>n),Be(2,1),m(([n,i])=>[nMath.abs(i-n.y)>100),m(([,[n]])=>n),K()),o=Ne("search");return N([e,o]).pipe(m(([{offset:n},i])=>n.y>400&&!i),K(),v(n=>n?r:I(!1)),Q(!1))}function Kn(e,t){return C(()=>N([ge(e),Xa(t)])).pipe(m(([{height:r},o])=>({height:r,hidden:o})),K((r,o)=>r.height===o.height&&r.hidden===o.hidden),G(1))}function Yn(e,{header$:t,main$:r}){return C(()=>{let o=new g,n=o.pipe(Z(),ie(!0));o.pipe(te("active"),He(t)).subscribe(([{active:a},{hidden:s}])=>{e.classList.toggle("md-header--shadow",a&&!s),e.hidden=s});let i=ue(P("[title]",e)).pipe(b(()=>B("content.tooltips")),ne(a=>Qn(a)));return r.subscribe(o),t.pipe(W(n),m(a=>$({ref:e},a)),Re(i.pipe(W(n))))})}function Za(e,{viewport$:t,header$:r}){return mr(e,{viewport$:t,header$:r}).pipe(m(({offset:{y:o}})=>{let{height:n}=ce(e);return{active:o>=n}}),te("active"))}function Bn(e,t){return C(()=>{let r=new g;r.subscribe({next({active:n}){e.classList.toggle("md-header__title--active",n)},complete(){e.classList.remove("md-header__title--active")}});let o=fe(".md-content h1");return typeof o=="undefined"?S:Za(o,t).pipe(w(n=>r.next(n)),_(()=>r.complete()),m(n=>$({ref:e},n)))})}function Gn(e,{viewport$:t,header$:r}){let o=r.pipe(m(({height:i})=>i),K()),n=o.pipe(v(()=>ge(e).pipe(m(({height:i})=>({top:e.offsetTop,bottom:e.offsetTop+i})),te("bottom"))));return N([o,n,t]).pipe(m(([i,{top:a,bottom:s},{offset:{y:p},size:{height:c}}])=>(c=Math.max(0,c-Math.max(0,a-p,i)-Math.max(0,c+p-s)),{offset:a-i,height:c,active:a-i<=p})),K((i,a)=>i.offset===a.offset&&i.height===a.height&&i.active===a.active))}function es(e){let t=__md_get("__palette")||{index:e.findIndex(o=>matchMedia(o.getAttribute("data-md-color-media")).matches)},r=Math.max(0,Math.min(t.index,e.length-1));return I(...e).pipe(ne(o=>h(o,"change").pipe(m(()=>o))),Q(e[r]),m(o=>({index:e.indexOf(o),color:{media:o.getAttribute("data-md-color-media"),scheme:o.getAttribute("data-md-color-scheme"),primary:o.getAttribute("data-md-color-primary"),accent:o.getAttribute("data-md-color-accent")}})),G(1))}function Jn(e){let t=P("input",e),r=x("meta",{name:"theme-color"});document.head.appendChild(r);let o=x("meta",{name:"color-scheme"});document.head.appendChild(o);let n=$t("(prefers-color-scheme: light)");return C(()=>{let i=new g;return i.subscribe(a=>{if(document.body.setAttribute("data-md-color-switching",""),a.color.media==="(prefers-color-scheme)"){let s=matchMedia("(prefers-color-scheme: light)"),p=document.querySelector(s.matches?"[data-md-color-media='(prefers-color-scheme: light)']":"[data-md-color-media='(prefers-color-scheme: dark)']");a.color.scheme=p.getAttribute("data-md-color-scheme"),a.color.primary=p.getAttribute("data-md-color-primary"),a.color.accent=p.getAttribute("data-md-color-accent")}for(let[s,p]of Object.entries(a.color))document.body.setAttribute(`data-md-color-${s}`,p);for(let s=0;sa.key==="Enter"),re(i,(a,s)=>s)).subscribe(({index:a})=>{a=(a+1)%t.length,t[a].click(),t[a].focus()}),i.pipe(m(()=>{let a=Se("header"),s=window.getComputedStyle(a);return o.content=s.colorScheme,s.backgroundColor.match(/\d+/g).map(p=>(+p).toString(16).padStart(2,"0")).join("")})).subscribe(a=>r.content=`#${a}`),i.pipe(ve(se)).subscribe(()=>{document.body.removeAttribute("data-md-color-switching")}),es(t).pipe(W(n.pipe(Ce(1))),ct(),w(a=>i.next(a)),_(()=>i.complete()),m(a=>$({ref:e},a)))})}function Xn(e,{progress$:t}){return C(()=>{let r=new g;return r.subscribe(({value:o})=>{e.style.setProperty("--md-progress-value",`${o}`)}),t.pipe(w(o=>r.next({value:o})),_(()=>r.complete()),m(o=>({ref:e,value:o})))})}var Jr=Lt(Br());function ts(e){e.setAttribute("data-md-copying","");let t=e.closest("[data-copy]"),r=t?t.getAttribute("data-copy"):e.innerText;return e.removeAttribute("data-md-copying"),r.trimEnd()}function Zn({alert$:e}){Jr.default.isSupported()&&new j(t=>{new Jr.default("[data-clipboard-target], [data-clipboard-text]",{text:r=>r.getAttribute("data-clipboard-text")||ts(R(r.getAttribute("data-clipboard-target")))}).on("success",r=>t.next(r))}).pipe(w(t=>{t.trigger.focus()}),m(()=>Ee("clipboard.copied"))).subscribe(e)}function ei(e,t){return e.protocol=t.protocol,e.hostname=t.hostname,e}function rs(e,t){let r=new Map;for(let o of P("url",e)){let n=R("loc",o),i=[ei(new URL(n.textContent),t)];r.set(`${i[0]}`,i);for(let a of P("[rel=alternate]",o)){let s=a.getAttribute("href");s!=null&&i.push(ei(new URL(s),t))}}return r}function ur(e){return un(new URL("sitemap.xml",e)).pipe(m(t=>rs(t,new URL(e))),de(()=>I(new Map)))}function os(e,t){if(!(e.target instanceof Element))return S;let r=e.target.closest("a");if(r===null)return S;if(r.target||e.metaKey||e.ctrlKey)return S;let o=new URL(r.href);return o.search=o.hash="",t.has(`${o}`)?(e.preventDefault(),I(new URL(r.href))):S}function ti(e){let t=new Map;for(let r of P(":scope > *",e.head))t.set(r.outerHTML,r);return t}function ri(e){for(let t of P("[href], [src]",e))for(let r of["href","src"]){let o=t.getAttribute(r);if(o&&!/^(?:[a-z]+:)?\/\//i.test(o)){t[r]=t[r];break}}return I(e)}function ns(e){for(let o of["[data-md-component=announce]","[data-md-component=container]","[data-md-component=header-topic]","[data-md-component=outdated]","[data-md-component=logo]","[data-md-component=skip]",...B("navigation.tabs.sticky")?["[data-md-component=tabs]"]:[]]){let n=fe(o),i=fe(o,e);typeof n!="undefined"&&typeof i!="undefined"&&n.replaceWith(i)}let t=ti(document);for(let[o,n]of ti(e))t.has(o)?t.delete(o):document.head.appendChild(n);for(let o of t.values()){let n=o.getAttribute("name");n!=="theme-color"&&n!=="color-scheme"&&o.remove()}let r=Se("container");return We(P("script",r)).pipe(v(o=>{let n=e.createElement("script");if(o.src){for(let i of o.getAttributeNames())n.setAttribute(i,o.getAttribute(i));return o.replaceWith(n),new j(i=>{n.onload=()=>i.complete()})}else return n.textContent=o.textContent,o.replaceWith(n),S}),Z(),ie(document))}function oi({location$:e,viewport$:t,progress$:r}){let o=xe();if(location.protocol==="file:")return S;let n=ur(o.base);I(document).subscribe(ri);let i=h(document.body,"click").pipe(He(n),v(([p,c])=>os(p,c)),pe()),a=h(window,"popstate").pipe(m(ye),pe());i.pipe(re(t)).subscribe(([p,{offset:c}])=>{history.replaceState(c,""),history.pushState(null,"",p)}),O(i,a).subscribe(e);let s=e.pipe(te("pathname"),v(p=>fn(p,{progress$:r}).pipe(de(()=>(lt(p,!0),S)))),v(ri),v(ns),pe());return O(s.pipe(re(e,(p,c)=>c)),s.pipe(v(()=>e),te("hash")),e.pipe(K((p,c)=>p.pathname===c.pathname&&p.hash===c.hash),v(()=>i),w(()=>history.back()))).subscribe(p=>{var c,l;history.state!==null||!p.hash?window.scrollTo(0,(l=(c=history.state)==null?void 0:c.y)!=null?l:0):(history.scrollRestoration="auto",pn(p.hash),history.scrollRestoration="manual")}),e.subscribe(()=>{history.scrollRestoration="manual"}),h(window,"beforeunload").subscribe(()=>{history.scrollRestoration="auto"}),t.pipe(te("offset"),_e(100)).subscribe(({offset:p})=>{history.replaceState(p,"")}),s}var ni=Lt(qr());function ii(e){let t=e.separator.split("|").map(n=>n.replace(/(\(\?[!=<][^)]+\))/g,"").length===0?"\uFFFD":n).join("|"),r=new RegExp(t,"img"),o=(n,i,a)=>`${i}${a}`;return n=>{n=n.replace(/[\s*+\-:~^]+/g," ").trim();let i=new RegExp(`(^|${e.separator}|)(${n.replace(/[|\\{}()[\]^$+*?.-]/g,"\\$&").replace(r,"|")})`,"img");return a=>(0,ni.default)(a).replace(i,o).replace(/<\/mark>(\s+)]*>/img,"$1")}}function It(e){return e.type===1}function dr(e){return e.type===3}function ai(e,t){let r=yn(e);return O(I(location.protocol!=="file:"),Ne("search")).pipe(Ae(o=>o),v(()=>t)).subscribe(({config:o,docs:n})=>r.next({type:0,data:{config:o,docs:n,options:{suggest:B("search.suggest")}}})),r}function si(e){var l;let{selectedVersionSitemap:t,selectedVersionBaseURL:r,currentLocation:o,currentBaseURL:n}=e,i=(l=Xr(n))==null?void 0:l.pathname;if(i===void 0)return;let a=ss(o.pathname,i);if(a===void 0)return;let s=ps(t.keys());if(!t.has(s))return;let p=Xr(a,s);if(!p||!t.has(p.href))return;let c=Xr(a,r);if(c)return c.hash=o.hash,c.search=o.search,c}function Xr(e,t){try{return new URL(e,t)}catch(r){return}}function ss(e,t){if(e.startsWith(t))return e.slice(t.length)}function cs(e,t){let r=Math.min(e.length,t.length),o;for(o=0;oS)),o=r.pipe(m(n=>{let[,i]=t.base.match(/([^/]+)\/?$/);return n.find(({version:a,aliases:s})=>a===i||s.includes(i))||n[0]}));r.pipe(m(n=>new Map(n.map(i=>[`${new URL(`../${i.version}/`,t.base)}`,i]))),v(n=>h(document.body,"click").pipe(b(i=>!i.metaKey&&!i.ctrlKey),re(o),v(([i,a])=>{if(i.target instanceof Element){let s=i.target.closest("a");if(s&&!s.target&&n.has(s.href)){let p=s.href;return!i.target.closest(".md-version")&&n.get(p)===a?S:(i.preventDefault(),I(new URL(p)))}}return S}),v(i=>ur(i).pipe(m(a=>{var s;return(s=si({selectedVersionSitemap:a,selectedVersionBaseURL:i,currentLocation:ye(),currentBaseURL:t.base}))!=null?s:i})))))).subscribe(n=>lt(n,!0)),N([r,o]).subscribe(([n,i])=>{R(".md-header__topic").appendChild(Cn(n,i))}),e.pipe(v(()=>o)).subscribe(n=>{var s;let i=new URL(t.base),a=__md_get("__outdated",sessionStorage,i);if(a===null){a=!0;let p=((s=t.version)==null?void 0:s.default)||"latest";Array.isArray(p)||(p=[p]);e:for(let c of p)for(let l of n.aliases.concat(n.version))if(new RegExp(c,"i").test(l)){a=!1;break e}__md_set("__outdated",a,sessionStorage,i)}if(a)for(let p of ae("outdated"))p.hidden=!1})}function ls(e,{worker$:t}){let{searchParams:r}=ye();r.has("q")&&(Je("search",!0),e.value=r.get("q"),e.focus(),Ne("search").pipe(Ae(i=>!i)).subscribe(()=>{let i=ye();i.searchParams.delete("q"),history.replaceState({},"",`${i}`)}));let o=et(e),n=O(t.pipe(Ae(It)),h(e,"keyup"),o).pipe(m(()=>e.value),K());return N([n,o]).pipe(m(([i,a])=>({value:i,focus:a})),G(1))}function pi(e,{worker$:t}){let r=new g,o=r.pipe(Z(),ie(!0));N([t.pipe(Ae(It)),r],(i,a)=>a).pipe(te("value")).subscribe(({value:i})=>t.next({type:2,data:i})),r.pipe(te("focus")).subscribe(({focus:i})=>{i&&Je("search",i)}),h(e.form,"reset").pipe(W(o)).subscribe(()=>e.focus());let n=R("header [for=__search]");return h(n,"click").subscribe(()=>e.focus()),ls(e,{worker$:t}).pipe(w(i=>r.next(i)),_(()=>r.complete()),m(i=>$({ref:e},i)),G(1))}function li(e,{worker$:t,query$:r}){let o=new g,n=on(e.parentElement).pipe(b(Boolean)),i=e.parentElement,a=R(":scope > :first-child",e),s=R(":scope > :last-child",e);Ne("search").subscribe(l=>s.setAttribute("role",l?"list":"presentation")),o.pipe(re(r),Wr(t.pipe(Ae(It)))).subscribe(([{items:l},{value:f}])=>{switch(l.length){case 0:a.textContent=f.length?Ee("search.result.none"):Ee("search.result.placeholder");break;case 1:a.textContent=Ee("search.result.one");break;default:let u=sr(l.length);a.textContent=Ee("search.result.other",u)}});let p=o.pipe(w(()=>s.innerHTML=""),v(({items:l})=>O(I(...l.slice(0,10)),I(...l.slice(10)).pipe(Be(4),Dr(n),v(([f])=>f)))),m(Mn),pe());return p.subscribe(l=>s.appendChild(l)),p.pipe(ne(l=>{let f=fe("details",l);return typeof f=="undefined"?S:h(f,"toggle").pipe(W(o),m(()=>f))})).subscribe(l=>{l.open===!1&&l.offsetTop<=i.scrollTop&&i.scrollTo({top:l.offsetTop})}),t.pipe(b(dr),m(({data:l})=>l)).pipe(w(l=>o.next(l)),_(()=>o.complete()),m(l=>$({ref:e},l)))}function ms(e,{query$:t}){return t.pipe(m(({value:r})=>{let o=ye();return o.hash="",r=r.replace(/\s+/g,"+").replace(/&/g,"%26").replace(/=/g,"%3D"),o.search=`q=${r}`,{url:o}}))}function mi(e,t){let r=new g,o=r.pipe(Z(),ie(!0));return r.subscribe(({url:n})=>{e.setAttribute("data-clipboard-text",e.href),e.href=`${n}`}),h(e,"click").pipe(W(o)).subscribe(n=>n.preventDefault()),ms(e,t).pipe(w(n=>r.next(n)),_(()=>r.complete()),m(n=>$({ref:e},n)))}function fi(e,{worker$:t,keyboard$:r}){let o=new g,n=Se("search-query"),i=O(h(n,"keydown"),h(n,"focus")).pipe(ve(se),m(()=>n.value),K());return o.pipe(He(i),m(([{suggest:s},p])=>{let c=p.split(/([\s-]+)/);if(s!=null&&s.length&&c[c.length-1]){let l=s[s.length-1];l.startsWith(c[c.length-1])&&(c[c.length-1]=l)}else c.length=0;return c})).subscribe(s=>e.innerHTML=s.join("").replace(/\s/g," ")),r.pipe(b(({mode:s})=>s==="search")).subscribe(s=>{switch(s.type){case"ArrowRight":e.innerText.length&&n.selectionStart===n.value.length&&(n.value=e.innerText);break}}),t.pipe(b(dr),m(({data:s})=>s)).pipe(w(s=>o.next(s)),_(()=>o.complete()),m(()=>({ref:e})))}function ui(e,{index$:t,keyboard$:r}){let o=xe();try{let n=ai(o.search,t),i=Se("search-query",e),a=Se("search-result",e);h(e,"click").pipe(b(({target:p})=>p instanceof Element&&!!p.closest("a"))).subscribe(()=>Je("search",!1)),r.pipe(b(({mode:p})=>p==="search")).subscribe(p=>{let c=Ie();switch(p.type){case"Enter":if(c===i){let l=new Map;for(let f of P(":first-child [href]",a)){let u=f.firstElementChild;l.set(f,parseFloat(u.getAttribute("data-md-score")))}if(l.size){let[[f]]=[...l].sort(([,u],[,d])=>d-u);f.click()}p.claim()}break;case"Escape":case"Tab":Je("search",!1),i.blur();break;case"ArrowUp":case"ArrowDown":if(typeof c=="undefined")i.focus();else{let l=[i,...P(":not(details) > [href], summary, details[open] [href]",a)],f=Math.max(0,(Math.max(0,l.indexOf(c))+l.length+(p.type==="ArrowUp"?-1:1))%l.length);l[f].focus()}p.claim();break;default:i!==Ie()&&i.focus()}}),r.pipe(b(({mode:p})=>p==="global")).subscribe(p=>{switch(p.type){case"f":case"s":case"/":i.focus(),i.select(),p.claim();break}});let s=pi(i,{worker$:n});return O(s,li(a,{worker$:n,query$:s})).pipe(Re(...ae("search-share",e).map(p=>mi(p,{query$:s})),...ae("search-suggest",e).map(p=>fi(p,{worker$:n,keyboard$:r}))))}catch(n){return e.hidden=!0,Ye}}function di(e,{index$:t,location$:r}){return N([t,r.pipe(Q(ye()),b(o=>!!o.searchParams.get("h")))]).pipe(m(([o,n])=>ii(o.config)(n.searchParams.get("h"))),m(o=>{var a;let n=new Map,i=document.createNodeIterator(e,NodeFilter.SHOW_TEXT);for(let s=i.nextNode();s;s=i.nextNode())if((a=s.parentElement)!=null&&a.offsetHeight){let p=s.textContent,c=o(p);c.length>p.length&&n.set(s,c)}for(let[s,p]of n){let{childNodes:c}=x("span",null,p);s.replaceWith(...Array.from(c))}return{ref:e,nodes:n}}))}function fs(e,{viewport$:t,main$:r}){let o=e.closest(".md-grid"),n=o.offsetTop-o.parentElement.offsetTop;return N([r,t]).pipe(m(([{offset:i,height:a},{offset:{y:s}}])=>(a=a+Math.min(n,Math.max(0,s-i))-n,{height:a,locked:s>=i+n})),K((i,a)=>i.height===a.height&&i.locked===a.locked))}function Zr(e,o){var n=o,{header$:t}=n,r=so(n,["header$"]);let i=R(".md-sidebar__scrollwrap",e),{y:a}=De(i);return C(()=>{let s=new g,p=s.pipe(Z(),ie(!0)),c=s.pipe(Me(0,me));return c.pipe(re(t)).subscribe({next([{height:l},{height:f}]){i.style.height=`${l-2*a}px`,e.style.top=`${f}px`},complete(){i.style.height="",e.style.top=""}}),c.pipe(Ae()).subscribe(()=>{for(let l of P(".md-nav__link--active[href]",e)){if(!l.clientHeight)continue;let f=l.closest(".md-sidebar__scrollwrap");if(typeof f!="undefined"){let u=l.offsetTop-f.offsetTop,{height:d}=ce(f);f.scrollTo({top:u-d/2})}}}),ue(P("label[tabindex]",e)).pipe(ne(l=>h(l,"click").pipe(ve(se),m(()=>l),W(p)))).subscribe(l=>{let f=R(`[id="${l.htmlFor}"]`);R(`[aria-labelledby="${l.id}"]`).setAttribute("aria-expanded",`${f.checked}`)}),fs(e,r).pipe(w(l=>s.next(l)),_(()=>s.complete()),m(l=>$({ref:e},l)))})}function hi(e,t){if(typeof t!="undefined"){let r=`https://api.github.com/repos/${e}/${t}`;return st(je(`${r}/releases/latest`).pipe(de(()=>S),m(o=>({version:o.tag_name})),Ve({})),je(r).pipe(de(()=>S),m(o=>({stars:o.stargazers_count,forks:o.forks_count})),Ve({}))).pipe(m(([o,n])=>$($({},o),n)))}else{let r=`https://api.github.com/users/${e}`;return je(r).pipe(m(o=>({repositories:o.public_repos})),Ve({}))}}function bi(e,t){let r=`https://${e}/api/v4/projects/${encodeURIComponent(t)}`;return st(je(`${r}/releases/permalink/latest`).pipe(de(()=>S),m(({tag_name:o})=>({version:o})),Ve({})),je(r).pipe(de(()=>S),m(({star_count:o,forks_count:n})=>({stars:o,forks:n})),Ve({}))).pipe(m(([o,n])=>$($({},o),n)))}function vi(e){let t=e.match(/^.+github\.com\/([^/]+)\/?([^/]+)?/i);if(t){let[,r,o]=t;return hi(r,o)}if(t=e.match(/^.+?([^/]*gitlab[^/]+)\/(.+?)\/?$/i),t){let[,r,o]=t;return bi(r,o)}return S}var us;function ds(e){return us||(us=C(()=>{let t=__md_get("__source",sessionStorage);if(t)return I(t);if(ae("consent").length){let o=__md_get("__consent");if(!(o&&o.github))return S}return vi(e.href).pipe(w(o=>__md_set("__source",o,sessionStorage)))}).pipe(de(()=>S),b(t=>Object.keys(t).length>0),m(t=>({facts:t})),G(1)))}function gi(e){let t=R(":scope > :last-child",e);return C(()=>{let r=new g;return r.subscribe(({facts:o})=>{t.appendChild(_n(o)),t.classList.add("md-source__repository--active")}),ds(e).pipe(w(o=>r.next(o)),_(()=>r.complete()),m(o=>$({ref:e},o)))})}function hs(e,{viewport$:t,header$:r}){return ge(document.body).pipe(v(()=>mr(e,{header$:r,viewport$:t})),m(({offset:{y:o}})=>({hidden:o>=10})),te("hidden"))}function yi(e,t){return C(()=>{let r=new g;return r.subscribe({next({hidden:o}){e.hidden=o},complete(){e.hidden=!1}}),(B("navigation.tabs.sticky")?I({hidden:!1}):hs(e,t)).pipe(w(o=>r.next(o)),_(()=>r.complete()),m(o=>$({ref:e},o)))})}function bs(e,{viewport$:t,header$:r}){let o=new Map,n=P(".md-nav__link",e);for(let s of n){let p=decodeURIComponent(s.hash.substring(1)),c=fe(`[id="${p}"]`);typeof c!="undefined"&&o.set(s,c)}let i=r.pipe(te("height"),m(({height:s})=>{let p=Se("main"),c=R(":scope > :first-child",p);return s+.8*(c.offsetTop-p.offsetTop)}),pe());return ge(document.body).pipe(te("height"),v(s=>C(()=>{let p=[];return I([...o].reduce((c,[l,f])=>{for(;p.length&&o.get(p[p.length-1]).tagName>=f.tagName;)p.pop();let u=f.offsetTop;for(;!u&&f.parentElement;)f=f.parentElement,u=f.offsetTop;let d=f.offsetParent;for(;d;d=d.offsetParent)u+=d.offsetTop;return c.set([...p=[...p,l]].reverse(),u)},new Map))}).pipe(m(p=>new Map([...p].sort(([,c],[,l])=>c-l))),He(i),v(([p,c])=>t.pipe(Fr(([l,f],{offset:{y:u},size:d})=>{let y=u+d.height>=Math.floor(s.height);for(;f.length;){let[,L]=f[0];if(L-c=u&&!y)f=[l.pop(),...f];else break}return[l,f]},[[],[...p]]),K((l,f)=>l[0]===f[0]&&l[1]===f[1])))))).pipe(m(([s,p])=>({prev:s.map(([c])=>c),next:p.map(([c])=>c)})),Q({prev:[],next:[]}),Be(2,1),m(([s,p])=>s.prev.length{let i=new g,a=i.pipe(Z(),ie(!0));if(i.subscribe(({prev:s,next:p})=>{for(let[c]of p)c.classList.remove("md-nav__link--passed"),c.classList.remove("md-nav__link--active");for(let[c,[l]]of s.entries())l.classList.add("md-nav__link--passed"),l.classList.toggle("md-nav__link--active",c===s.length-1)}),B("toc.follow")){let s=O(t.pipe(_e(1),m(()=>{})),t.pipe(_e(250),m(()=>"smooth")));i.pipe(b(({prev:p})=>p.length>0),He(o.pipe(ve(se))),re(s)).subscribe(([[{prev:p}],c])=>{let[l]=p[p.length-1];if(l.offsetHeight){let f=cr(l);if(typeof f!="undefined"){let u=l.offsetTop-f.offsetTop,{height:d}=ce(f);f.scrollTo({top:u-d/2,behavior:c})}}})}return B("navigation.tracking")&&t.pipe(W(a),te("offset"),_e(250),Ce(1),W(n.pipe(Ce(1))),ct({delay:250}),re(i)).subscribe(([,{prev:s}])=>{let p=ye(),c=s[s.length-1];if(c&&c.length){let[l]=c,{hash:f}=new URL(l.href);p.hash!==f&&(p.hash=f,history.replaceState({},"",`${p}`))}else p.hash="",history.replaceState({},"",`${p}`)}),bs(e,{viewport$:t,header$:r}).pipe(w(s=>i.next(s)),_(()=>i.complete()),m(s=>$({ref:e},s)))})}function vs(e,{viewport$:t,main$:r,target$:o}){let n=t.pipe(m(({offset:{y:a}})=>a),Be(2,1),m(([a,s])=>a>s&&s>0),K()),i=r.pipe(m(({active:a})=>a));return N([i,n]).pipe(m(([a,s])=>!(a&&s)),K(),W(o.pipe(Ce(1))),ie(!0),ct({delay:250}),m(a=>({hidden:a})))}function Ei(e,{viewport$:t,header$:r,main$:o,target$:n}){let i=new g,a=i.pipe(Z(),ie(!0));return i.subscribe({next({hidden:s}){e.hidden=s,s?(e.setAttribute("tabindex","-1"),e.blur()):e.removeAttribute("tabindex")},complete(){e.style.top="",e.hidden=!0,e.removeAttribute("tabindex")}}),r.pipe(W(a),te("height")).subscribe(({height:s})=>{e.style.top=`${s+16}px`}),h(e,"click").subscribe(s=>{s.preventDefault(),window.scrollTo({top:0})}),vs(e,{viewport$:t,main$:o,target$:n}).pipe(w(s=>i.next(s)),_(()=>i.complete()),m(s=>$({ref:e},s)))}function wi({document$:e,viewport$:t}){e.pipe(v(()=>P(".md-ellipsis")),ne(r=>tt(r).pipe(W(e.pipe(Ce(1))),b(o=>o),m(()=>r),Te(1))),b(r=>r.offsetWidth{let o=r.innerText,n=r.closest("a")||r;return n.title=o,B("content.tooltips")?mt(n,{viewport$:t}).pipe(W(e.pipe(Ce(1))),_(()=>n.removeAttribute("title"))):S})).subscribe(),B("content.tooltips")&&e.pipe(v(()=>P(".md-status")),ne(r=>mt(r,{viewport$:t}))).subscribe()}function Ti({document$:e,tablet$:t}){e.pipe(v(()=>P(".md-toggle--indeterminate")),w(r=>{r.indeterminate=!0,r.checked=!1}),ne(r=>h(r,"change").pipe(Vr(()=>r.classList.contains("md-toggle--indeterminate")),m(()=>r))),re(t)).subscribe(([r,o])=>{r.classList.remove("md-toggle--indeterminate"),o&&(r.checked=!1)})}function gs(){return/(iPad|iPhone|iPod)/.test(navigator.userAgent)}function Si({document$:e}){e.pipe(v(()=>P("[data-md-scrollfix]")),w(t=>t.removeAttribute("data-md-scrollfix")),b(gs),ne(t=>h(t,"touchstart").pipe(m(()=>t)))).subscribe(t=>{let r=t.scrollTop;r===0?t.scrollTop=1:r+t.offsetHeight===t.scrollHeight&&(t.scrollTop=r-1)})}function Oi({viewport$:e,tablet$:t}){N([Ne("search"),t]).pipe(m(([r,o])=>r&&!o),v(r=>I(r).pipe(Ge(r?400:100))),re(e)).subscribe(([r,{offset:{y:o}}])=>{if(r)document.body.setAttribute("data-md-scrolllock",""),document.body.style.top=`-${o}px`;else{let n=-1*parseInt(document.body.style.top,10);document.body.removeAttribute("data-md-scrolllock"),document.body.style.top="",n&&window.scrollTo(0,n)}})}Object.entries||(Object.entries=function(e){let t=[];for(let r of Object.keys(e))t.push([r,e[r]]);return t});Object.values||(Object.values=function(e){let t=[];for(let r of Object.keys(e))t.push(e[r]);return t});typeof Element!="undefined"&&(Element.prototype.scrollTo||(Element.prototype.scrollTo=function(e,t){typeof e=="object"?(this.scrollLeft=e.left,this.scrollTop=e.top):(this.scrollLeft=e,this.scrollTop=t)}),Element.prototype.replaceWith||(Element.prototype.replaceWith=function(...e){let t=this.parentNode;if(t){e.length===0&&t.removeChild(this);for(let r=e.length-1;r>=0;r--){let o=e[r];typeof o=="string"?o=document.createTextNode(o):o.parentNode&&o.parentNode.removeChild(o),r?t.insertBefore(this.previousSibling,o):t.replaceChild(o,this)}}}));function ys(){return location.protocol==="file:"?wt(`${new URL("search/search_index.js",eo.base)}`).pipe(m(()=>__index),G(1)):je(new URL("search/search_index.json",eo.base))}document.documentElement.classList.remove("no-js");document.documentElement.classList.add("js");var ot=Go(),Ft=sn(),Ot=ln(Ft),to=an(),Oe=gn(),hr=$t("(min-width: 960px)"),Mi=$t("(min-width: 1220px)"),_i=mn(),eo=xe(),Ai=document.forms.namedItem("search")?ys():Ye,ro=new g;Zn({alert$:ro});var oo=new g;B("navigation.instant")&&oi({location$:Ft,viewport$:Oe,progress$:oo}).subscribe(ot);var Li;((Li=eo.version)==null?void 0:Li.provider)==="mike"&&ci({document$:ot});O(Ft,Ot).pipe(Ge(125)).subscribe(()=>{Je("drawer",!1),Je("search",!1)});to.pipe(b(({mode:e})=>e==="global")).subscribe(e=>{switch(e.type){case"p":case",":let t=fe("link[rel=prev]");typeof t!="undefined"&<(t);break;case"n":case".":let r=fe("link[rel=next]");typeof r!="undefined"&<(r);break;case"Enter":let o=Ie();o instanceof HTMLLabelElement&&o.click()}});wi({viewport$:Oe,document$:ot});Ti({document$:ot,tablet$:hr});Si({document$:ot});Oi({viewport$:Oe,tablet$:hr});var rt=Kn(Se("header"),{viewport$:Oe}),jt=ot.pipe(m(()=>Se("main")),v(e=>Gn(e,{viewport$:Oe,header$:rt})),G(1)),xs=O(...ae("consent").map(e=>En(e,{target$:Ot})),...ae("dialog").map(e=>qn(e,{alert$:ro})),...ae("palette").map(e=>Jn(e)),...ae("progress").map(e=>Xn(e,{progress$:oo})),...ae("search").map(e=>ui(e,{index$:Ai,keyboard$:to})),...ae("source").map(e=>gi(e))),Es=C(()=>O(...ae("announce").map(e=>xn(e)),...ae("content").map(e=>Nn(e,{viewport$:Oe,target$:Ot,print$:_i})),...ae("content").map(e=>B("search.highlight")?di(e,{index$:Ai,location$:Ft}):S),...ae("header").map(e=>Yn(e,{viewport$:Oe,header$:rt,main$:jt})),...ae("header-title").map(e=>Bn(e,{viewport$:Oe,header$:rt})),...ae("sidebar").map(e=>e.getAttribute("data-md-type")==="navigation"?zr(Mi,()=>Zr(e,{viewport$:Oe,header$:rt,main$:jt})):zr(hr,()=>Zr(e,{viewport$:Oe,header$:rt,main$:jt}))),...ae("tabs").map(e=>yi(e,{viewport$:Oe,header$:rt})),...ae("toc").map(e=>xi(e,{viewport$:Oe,header$:rt,main$:jt,target$:Ot})),...ae("top").map(e=>Ei(e,{viewport$:Oe,header$:rt,main$:jt,target$:Ot})))),Ci=ot.pipe(v(()=>Es),Re(xs),G(1));Ci.subscribe();window.document$=ot;window.location$=Ft;window.target$=Ot;window.keyboard$=to;window.viewport$=Oe;window.tablet$=hr;window.screen$=Mi;window.print$=_i;window.alert$=ro;window.progress$=oo;window.component$=Ci;})(); -//# sourceMappingURL=bundle.13a4f30d.min.js.map - diff --git a/site/assets/javascripts/bundle.13a4f30d.min.js.map b/site/assets/javascripts/bundle.13a4f30d.min.js.map deleted file mode 100644 index 8941cb8..0000000 --- a/site/assets/javascripts/bundle.13a4f30d.min.js.map +++ /dev/null @@ -1,7 +0,0 @@ -{ - "version": 3, - "sources": ["node_modules/focus-visible/dist/focus-visible.js", "node_modules/escape-html/index.js", "node_modules/clipboard/dist/clipboard.js", "src/templates/assets/javascripts/bundle.ts", "node_modules/tslib/tslib.es6.mjs", "node_modules/rxjs/src/internal/util/isFunction.ts", "node_modules/rxjs/src/internal/util/createErrorClass.ts", "node_modules/rxjs/src/internal/util/UnsubscriptionError.ts", "node_modules/rxjs/src/internal/util/arrRemove.ts", "node_modules/rxjs/src/internal/Subscription.ts", "node_modules/rxjs/src/internal/config.ts", "node_modules/rxjs/src/internal/scheduler/timeoutProvider.ts", "node_modules/rxjs/src/internal/util/reportUnhandledError.ts", "node_modules/rxjs/src/internal/util/noop.ts", "node_modules/rxjs/src/internal/NotificationFactories.ts", "node_modules/rxjs/src/internal/util/errorContext.ts", "node_modules/rxjs/src/internal/Subscriber.ts", "node_modules/rxjs/src/internal/symbol/observable.ts", "node_modules/rxjs/src/internal/util/identity.ts", "node_modules/rxjs/src/internal/util/pipe.ts", "node_modules/rxjs/src/internal/Observable.ts", "node_modules/rxjs/src/internal/util/lift.ts", "node_modules/rxjs/src/internal/operators/OperatorSubscriber.ts", "node_modules/rxjs/src/internal/scheduler/animationFrameProvider.ts", "node_modules/rxjs/src/internal/util/ObjectUnsubscribedError.ts", "node_modules/rxjs/src/internal/Subject.ts", "node_modules/rxjs/src/internal/BehaviorSubject.ts", "node_modules/rxjs/src/internal/scheduler/dateTimestampProvider.ts", "node_modules/rxjs/src/internal/ReplaySubject.ts", "node_modules/rxjs/src/internal/scheduler/Action.ts", "node_modules/rxjs/src/internal/scheduler/intervalProvider.ts", "node_modules/rxjs/src/internal/scheduler/AsyncAction.ts", "node_modules/rxjs/src/internal/Scheduler.ts", "node_modules/rxjs/src/internal/scheduler/AsyncScheduler.ts", "node_modules/rxjs/src/internal/scheduler/async.ts", "node_modules/rxjs/src/internal/scheduler/QueueAction.ts", "node_modules/rxjs/src/internal/scheduler/QueueScheduler.ts", "node_modules/rxjs/src/internal/scheduler/queue.ts", "node_modules/rxjs/src/internal/scheduler/AnimationFrameAction.ts", "node_modules/rxjs/src/internal/scheduler/AnimationFrameScheduler.ts", "node_modules/rxjs/src/internal/scheduler/animationFrame.ts", "node_modules/rxjs/src/internal/observable/empty.ts", "node_modules/rxjs/src/internal/util/isScheduler.ts", "node_modules/rxjs/src/internal/util/args.ts", "node_modules/rxjs/src/internal/util/isArrayLike.ts", "node_modules/rxjs/src/internal/util/isPromise.ts", "node_modules/rxjs/src/internal/util/isInteropObservable.ts", "node_modules/rxjs/src/internal/util/isAsyncIterable.ts", "node_modules/rxjs/src/internal/util/throwUnobservableError.ts", "node_modules/rxjs/src/internal/symbol/iterator.ts", "node_modules/rxjs/src/internal/util/isIterable.ts", "node_modules/rxjs/src/internal/util/isReadableStreamLike.ts", "node_modules/rxjs/src/internal/observable/innerFrom.ts", "node_modules/rxjs/src/internal/util/executeSchedule.ts", "node_modules/rxjs/src/internal/operators/observeOn.ts", "node_modules/rxjs/src/internal/operators/subscribeOn.ts", "node_modules/rxjs/src/internal/scheduled/scheduleObservable.ts", "node_modules/rxjs/src/internal/scheduled/schedulePromise.ts", "node_modules/rxjs/src/internal/scheduled/scheduleArray.ts", "node_modules/rxjs/src/internal/scheduled/scheduleIterable.ts", "node_modules/rxjs/src/internal/scheduled/scheduleAsyncIterable.ts", "node_modules/rxjs/src/internal/scheduled/scheduleReadableStreamLike.ts", "node_modules/rxjs/src/internal/scheduled/scheduled.ts", "node_modules/rxjs/src/internal/observable/from.ts", "node_modules/rxjs/src/internal/observable/of.ts", "node_modules/rxjs/src/internal/observable/throwError.ts", "node_modules/rxjs/src/internal/util/EmptyError.ts", "node_modules/rxjs/src/internal/util/isDate.ts", "node_modules/rxjs/src/internal/operators/map.ts", "node_modules/rxjs/src/internal/util/mapOneOrManyArgs.ts", "node_modules/rxjs/src/internal/util/argsArgArrayOrObject.ts", "node_modules/rxjs/src/internal/util/createObject.ts", "node_modules/rxjs/src/internal/observable/combineLatest.ts", "node_modules/rxjs/src/internal/operators/mergeInternals.ts", "node_modules/rxjs/src/internal/operators/mergeMap.ts", "node_modules/rxjs/src/internal/operators/mergeAll.ts", "node_modules/rxjs/src/internal/operators/concatAll.ts", "node_modules/rxjs/src/internal/observable/concat.ts", "node_modules/rxjs/src/internal/observable/defer.ts", "node_modules/rxjs/src/internal/observable/fromEvent.ts", "node_modules/rxjs/src/internal/observable/fromEventPattern.ts", "node_modules/rxjs/src/internal/observable/timer.ts", "node_modules/rxjs/src/internal/observable/merge.ts", "node_modules/rxjs/src/internal/observable/never.ts", "node_modules/rxjs/src/internal/util/argsOrArgArray.ts", "node_modules/rxjs/src/internal/operators/filter.ts", "node_modules/rxjs/src/internal/observable/zip.ts", "node_modules/rxjs/src/internal/operators/audit.ts", "node_modules/rxjs/src/internal/operators/auditTime.ts", "node_modules/rxjs/src/internal/operators/bufferCount.ts", "node_modules/rxjs/src/internal/operators/catchError.ts", "node_modules/rxjs/src/internal/operators/scanInternals.ts", "node_modules/rxjs/src/internal/operators/combineLatest.ts", "node_modules/rxjs/src/internal/operators/combineLatestWith.ts", "node_modules/rxjs/src/internal/operators/debounce.ts", "node_modules/rxjs/src/internal/operators/debounceTime.ts", "node_modules/rxjs/src/internal/operators/defaultIfEmpty.ts", "node_modules/rxjs/src/internal/operators/take.ts", "node_modules/rxjs/src/internal/operators/ignoreElements.ts", "node_modules/rxjs/src/internal/operators/mapTo.ts", "node_modules/rxjs/src/internal/operators/delayWhen.ts", "node_modules/rxjs/src/internal/operators/delay.ts", "node_modules/rxjs/src/internal/operators/distinctUntilChanged.ts", "node_modules/rxjs/src/internal/operators/distinctUntilKeyChanged.ts", "node_modules/rxjs/src/internal/operators/throwIfEmpty.ts", "node_modules/rxjs/src/internal/operators/endWith.ts", "node_modules/rxjs/src/internal/operators/finalize.ts", "node_modules/rxjs/src/internal/operators/first.ts", "node_modules/rxjs/src/internal/operators/takeLast.ts", "node_modules/rxjs/src/internal/operators/merge.ts", "node_modules/rxjs/src/internal/operators/mergeWith.ts", "node_modules/rxjs/src/internal/operators/repeat.ts", "node_modules/rxjs/src/internal/operators/scan.ts", "node_modules/rxjs/src/internal/operators/share.ts", "node_modules/rxjs/src/internal/operators/shareReplay.ts", "node_modules/rxjs/src/internal/operators/skip.ts", "node_modules/rxjs/src/internal/operators/skipUntil.ts", "node_modules/rxjs/src/internal/operators/startWith.ts", "node_modules/rxjs/src/internal/operators/switchMap.ts", "node_modules/rxjs/src/internal/operators/takeUntil.ts", "node_modules/rxjs/src/internal/operators/takeWhile.ts", "node_modules/rxjs/src/internal/operators/tap.ts", "node_modules/rxjs/src/internal/operators/throttle.ts", "node_modules/rxjs/src/internal/operators/throttleTime.ts", "node_modules/rxjs/src/internal/operators/withLatestFrom.ts", "node_modules/rxjs/src/internal/operators/zip.ts", "node_modules/rxjs/src/internal/operators/zipWith.ts", "src/templates/assets/javascripts/browser/document/index.ts", "src/templates/assets/javascripts/browser/element/_/index.ts", "src/templates/assets/javascripts/browser/element/focus/index.ts", "src/templates/assets/javascripts/browser/element/hover/index.ts", "src/templates/assets/javascripts/utilities/h/index.ts", "src/templates/assets/javascripts/utilities/round/index.ts", "src/templates/assets/javascripts/browser/script/index.ts", "src/templates/assets/javascripts/browser/element/size/_/index.ts", "src/templates/assets/javascripts/browser/element/size/content/index.ts", "src/templates/assets/javascripts/browser/element/offset/_/index.ts", "src/templates/assets/javascripts/browser/element/offset/content/index.ts", "src/templates/assets/javascripts/browser/element/visibility/index.ts", "src/templates/assets/javascripts/browser/toggle/index.ts", "src/templates/assets/javascripts/browser/keyboard/index.ts", "src/templates/assets/javascripts/browser/location/_/index.ts", "src/templates/assets/javascripts/browser/location/hash/index.ts", "src/templates/assets/javascripts/browser/media/index.ts", "src/templates/assets/javascripts/browser/request/index.ts", "src/templates/assets/javascripts/browser/viewport/offset/index.ts", "src/templates/assets/javascripts/browser/viewport/size/index.ts", "src/templates/assets/javascripts/browser/viewport/_/index.ts", "src/templates/assets/javascripts/browser/viewport/at/index.ts", "src/templates/assets/javascripts/browser/worker/index.ts", "src/templates/assets/javascripts/_/index.ts", "src/templates/assets/javascripts/components/_/index.ts", "src/templates/assets/javascripts/components/announce/index.ts", "src/templates/assets/javascripts/components/consent/index.ts", "src/templates/assets/javascripts/templates/tooltip/index.tsx", "src/templates/assets/javascripts/templates/annotation/index.tsx", "src/templates/assets/javascripts/templates/clipboard/index.tsx", "src/templates/assets/javascripts/templates/search/index.tsx", "src/templates/assets/javascripts/templates/source/index.tsx", "src/templates/assets/javascripts/templates/tabbed/index.tsx", "src/templates/assets/javascripts/templates/table/index.tsx", "src/templates/assets/javascripts/templates/version/index.tsx", "src/templates/assets/javascripts/components/tooltip2/index.ts", "src/templates/assets/javascripts/components/content/annotation/_/index.ts", "src/templates/assets/javascripts/components/content/annotation/list/index.ts", "src/templates/assets/javascripts/components/content/annotation/block/index.ts", "src/templates/assets/javascripts/components/content/code/_/index.ts", "src/templates/assets/javascripts/components/content/details/index.ts", "src/templates/assets/javascripts/components/content/mermaid/index.css", "src/templates/assets/javascripts/components/content/mermaid/index.ts", "src/templates/assets/javascripts/components/content/table/index.ts", "src/templates/assets/javascripts/components/content/tabs/index.ts", "src/templates/assets/javascripts/components/content/_/index.ts", "src/templates/assets/javascripts/components/dialog/index.ts", "src/templates/assets/javascripts/components/tooltip/index.ts", "src/templates/assets/javascripts/components/header/_/index.ts", "src/templates/assets/javascripts/components/header/title/index.ts", "src/templates/assets/javascripts/components/main/index.ts", "src/templates/assets/javascripts/components/palette/index.ts", "src/templates/assets/javascripts/components/progress/index.ts", "src/templates/assets/javascripts/integrations/clipboard/index.ts", "src/templates/assets/javascripts/integrations/sitemap/index.ts", "src/templates/assets/javascripts/integrations/instant/index.ts", "src/templates/assets/javascripts/integrations/search/highlighter/index.ts", "src/templates/assets/javascripts/integrations/search/worker/message/index.ts", "src/templates/assets/javascripts/integrations/search/worker/_/index.ts", "src/templates/assets/javascripts/integrations/version/findurl/index.ts", "src/templates/assets/javascripts/integrations/version/index.ts", "src/templates/assets/javascripts/components/search/query/index.ts", "src/templates/assets/javascripts/components/search/result/index.ts", "src/templates/assets/javascripts/components/search/share/index.ts", "src/templates/assets/javascripts/components/search/suggest/index.ts", "src/templates/assets/javascripts/components/search/_/index.ts", "src/templates/assets/javascripts/components/search/highlight/index.ts", "src/templates/assets/javascripts/components/sidebar/index.ts", "src/templates/assets/javascripts/components/source/facts/github/index.ts", "src/templates/assets/javascripts/components/source/facts/gitlab/index.ts", "src/templates/assets/javascripts/components/source/facts/_/index.ts", "src/templates/assets/javascripts/components/source/_/index.ts", "src/templates/assets/javascripts/components/tabs/index.ts", "src/templates/assets/javascripts/components/toc/index.ts", "src/templates/assets/javascripts/components/top/index.ts", "src/templates/assets/javascripts/patches/ellipsis/index.ts", "src/templates/assets/javascripts/patches/indeterminate/index.ts", "src/templates/assets/javascripts/patches/scrollfix/index.ts", "src/templates/assets/javascripts/patches/scrolllock/index.ts", "src/templates/assets/javascripts/polyfills/index.ts"], - "sourcesContent": ["(function (global, factory) {\n typeof exports === 'object' && typeof module !== 'undefined' ? factory() :\n typeof define === 'function' && define.amd ? define(factory) :\n (factory());\n}(this, (function () { 'use strict';\n\n /**\n * Applies the :focus-visible polyfill at the given scope.\n * A scope in this case is either the top-level Document or a Shadow Root.\n *\n * @param {(Document|ShadowRoot)} scope\n * @see https://github.com/WICG/focus-visible\n */\n function applyFocusVisiblePolyfill(scope) {\n var hadKeyboardEvent = true;\n var hadFocusVisibleRecently = false;\n var hadFocusVisibleRecentlyTimeout = null;\n\n var inputTypesAllowlist = {\n text: true,\n search: true,\n url: true,\n tel: true,\n email: true,\n password: true,\n number: true,\n date: true,\n month: true,\n week: true,\n time: true,\n datetime: true,\n 'datetime-local': true\n };\n\n /**\n * Helper function for legacy browsers and iframes which sometimes focus\n * elements like document, body, and non-interactive SVG.\n * @param {Element} el\n */\n function isValidFocusTarget(el) {\n if (\n el &&\n el !== document &&\n el.nodeName !== 'HTML' &&\n el.nodeName !== 'BODY' &&\n 'classList' in el &&\n 'contains' in el.classList\n ) {\n return true;\n }\n return false;\n }\n\n /**\n * Computes whether the given element should automatically trigger the\n * `focus-visible` class being added, i.e. whether it should always match\n * `:focus-visible` when focused.\n * @param {Element} el\n * @return {boolean}\n */\n function focusTriggersKeyboardModality(el) {\n var type = el.type;\n var tagName = el.tagName;\n\n if (tagName === 'INPUT' && inputTypesAllowlist[type] && !el.readOnly) {\n return true;\n }\n\n if (tagName === 'TEXTAREA' && !el.readOnly) {\n return true;\n }\n\n if (el.isContentEditable) {\n return true;\n }\n\n return false;\n }\n\n /**\n * Add the `focus-visible` class to the given element if it was not added by\n * the author.\n * @param {Element} el\n */\n function addFocusVisibleClass(el) {\n if (el.classList.contains('focus-visible')) {\n return;\n }\n el.classList.add('focus-visible');\n el.setAttribute('data-focus-visible-added', '');\n }\n\n /**\n * Remove the `focus-visible` class from the given element if it was not\n * originally added by the author.\n * @param {Element} el\n */\n function removeFocusVisibleClass(el) {\n if (!el.hasAttribute('data-focus-visible-added')) {\n return;\n }\n el.classList.remove('focus-visible');\n el.removeAttribute('data-focus-visible-added');\n }\n\n /**\n * If the most recent user interaction was via the keyboard;\n * and the key press did not include a meta, alt/option, or control key;\n * then the modality is keyboard. Otherwise, the modality is not keyboard.\n * Apply `focus-visible` to any current active element and keep track\n * of our keyboard modality state with `hadKeyboardEvent`.\n * @param {KeyboardEvent} e\n */\n function onKeyDown(e) {\n if (e.metaKey || e.altKey || e.ctrlKey) {\n return;\n }\n\n if (isValidFocusTarget(scope.activeElement)) {\n addFocusVisibleClass(scope.activeElement);\n }\n\n hadKeyboardEvent = true;\n }\n\n /**\n * If at any point a user clicks with a pointing device, ensure that we change\n * the modality away from keyboard.\n * This avoids the situation where a user presses a key on an already focused\n * element, and then clicks on a different element, focusing it with a\n * pointing device, while we still think we're in keyboard modality.\n * @param {Event} e\n */\n function onPointerDown(e) {\n hadKeyboardEvent = false;\n }\n\n /**\n * On `focus`, add the `focus-visible` class to the target if:\n * - the target received focus as a result of keyboard navigation, or\n * - the event target is an element that will likely require interaction\n * via the keyboard (e.g. a text box)\n * @param {Event} e\n */\n function onFocus(e) {\n // Prevent IE from focusing the document or HTML element.\n if (!isValidFocusTarget(e.target)) {\n return;\n }\n\n if (hadKeyboardEvent || focusTriggersKeyboardModality(e.target)) {\n addFocusVisibleClass(e.target);\n }\n }\n\n /**\n * On `blur`, remove the `focus-visible` class from the target.\n * @param {Event} e\n */\n function onBlur(e) {\n if (!isValidFocusTarget(e.target)) {\n return;\n }\n\n if (\n e.target.classList.contains('focus-visible') ||\n e.target.hasAttribute('data-focus-visible-added')\n ) {\n // To detect a tab/window switch, we look for a blur event followed\n // rapidly by a visibility change.\n // If we don't see a visibility change within 100ms, it's probably a\n // regular focus change.\n hadFocusVisibleRecently = true;\n window.clearTimeout(hadFocusVisibleRecentlyTimeout);\n hadFocusVisibleRecentlyTimeout = window.setTimeout(function() {\n hadFocusVisibleRecently = false;\n }, 100);\n removeFocusVisibleClass(e.target);\n }\n }\n\n /**\n * If the user changes tabs, keep track of whether or not the previously\n * focused element had .focus-visible.\n * @param {Event} e\n */\n function onVisibilityChange(e) {\n if (document.visibilityState === 'hidden') {\n // If the tab becomes active again, the browser will handle calling focus\n // on the element (Safari actually calls it twice).\n // If this tab change caused a blur on an element with focus-visible,\n // re-apply the class when the user switches back to the tab.\n if (hadFocusVisibleRecently) {\n hadKeyboardEvent = true;\n }\n addInitialPointerMoveListeners();\n }\n }\n\n /**\n * Add a group of listeners to detect usage of any pointing devices.\n * These listeners will be added when the polyfill first loads, and anytime\n * the window is blurred, so that they are active when the window regains\n * focus.\n */\n function addInitialPointerMoveListeners() {\n document.addEventListener('mousemove', onInitialPointerMove);\n document.addEventListener('mousedown', onInitialPointerMove);\n document.addEventListener('mouseup', onInitialPointerMove);\n document.addEventListener('pointermove', onInitialPointerMove);\n document.addEventListener('pointerdown', onInitialPointerMove);\n document.addEventListener('pointerup', onInitialPointerMove);\n document.addEventListener('touchmove', onInitialPointerMove);\n document.addEventListener('touchstart', onInitialPointerMove);\n document.addEventListener('touchend', onInitialPointerMove);\n }\n\n function removeInitialPointerMoveListeners() {\n document.removeEventListener('mousemove', onInitialPointerMove);\n document.removeEventListener('mousedown', onInitialPointerMove);\n document.removeEventListener('mouseup', onInitialPointerMove);\n document.removeEventListener('pointermove', onInitialPointerMove);\n document.removeEventListener('pointerdown', onInitialPointerMove);\n document.removeEventListener('pointerup', onInitialPointerMove);\n document.removeEventListener('touchmove', onInitialPointerMove);\n document.removeEventListener('touchstart', onInitialPointerMove);\n document.removeEventListener('touchend', onInitialPointerMove);\n }\n\n /**\n * When the polfyill first loads, assume the user is in keyboard modality.\n * If any event is received from a pointing device (e.g. mouse, pointer,\n * touch), turn off keyboard modality.\n * This accounts for situations where focus enters the page from the URL bar.\n * @param {Event} e\n */\n function onInitialPointerMove(e) {\n // Work around a Safari quirk that fires a mousemove on whenever the\n // window blurs, even if you're tabbing out of the page. \u00AF\\_(\u30C4)_/\u00AF\n if (e.target.nodeName && e.target.nodeName.toLowerCase() === 'html') {\n return;\n }\n\n hadKeyboardEvent = false;\n removeInitialPointerMoveListeners();\n }\n\n // For some kinds of state, we are interested in changes at the global scope\n // only. For example, global pointer input, global key presses and global\n // visibility change should affect the state at every scope:\n document.addEventListener('keydown', onKeyDown, true);\n document.addEventListener('mousedown', onPointerDown, true);\n document.addEventListener('pointerdown', onPointerDown, true);\n document.addEventListener('touchstart', onPointerDown, true);\n document.addEventListener('visibilitychange', onVisibilityChange, true);\n\n addInitialPointerMoveListeners();\n\n // For focus and blur, we specifically care about state changes in the local\n // scope. This is because focus / blur events that originate from within a\n // shadow root are not re-dispatched from the host element if it was already\n // the active element in its own scope:\n scope.addEventListener('focus', onFocus, true);\n scope.addEventListener('blur', onBlur, true);\n\n // We detect that a node is a ShadowRoot by ensuring that it is a\n // DocumentFragment and also has a host property. This check covers native\n // implementation and polyfill implementation transparently. If we only cared\n // about the native implementation, we could just check if the scope was\n // an instance of a ShadowRoot.\n if (scope.nodeType === Node.DOCUMENT_FRAGMENT_NODE && scope.host) {\n // Since a ShadowRoot is a special kind of DocumentFragment, it does not\n // have a root element to add a class to. So, we add this attribute to the\n // host element instead:\n scope.host.setAttribute('data-js-focus-visible', '');\n } else if (scope.nodeType === Node.DOCUMENT_NODE) {\n document.documentElement.classList.add('js-focus-visible');\n document.documentElement.setAttribute('data-js-focus-visible', '');\n }\n }\n\n // It is important to wrap all references to global window and document in\n // these checks to support server-side rendering use cases\n // @see https://github.com/WICG/focus-visible/issues/199\n if (typeof window !== 'undefined' && typeof document !== 'undefined') {\n // Make the polyfill helper globally available. This can be used as a signal\n // to interested libraries that wish to coordinate with the polyfill for e.g.,\n // applying the polyfill to a shadow root:\n window.applyFocusVisiblePolyfill = applyFocusVisiblePolyfill;\n\n // Notify interested libraries of the polyfill's presence, in case the\n // polyfill was loaded lazily:\n var event;\n\n try {\n event = new CustomEvent('focus-visible-polyfill-ready');\n } catch (error) {\n // IE11 does not support using CustomEvent as a constructor directly:\n event = document.createEvent('CustomEvent');\n event.initCustomEvent('focus-visible-polyfill-ready', false, false, {});\n }\n\n window.dispatchEvent(event);\n }\n\n if (typeof document !== 'undefined') {\n // Apply the polyfill to the global document, so that no JavaScript\n // coordination is required to use the polyfill in the top-level document:\n applyFocusVisiblePolyfill(document);\n }\n\n})));\n", "/*!\n * escape-html\n * Copyright(c) 2012-2013 TJ Holowaychuk\n * Copyright(c) 2015 Andreas Lubbe\n * Copyright(c) 2015 Tiancheng \"Timothy\" Gu\n * MIT Licensed\n */\n\n'use strict';\n\n/**\n * Module variables.\n * @private\n */\n\nvar matchHtmlRegExp = /[\"'&<>]/;\n\n/**\n * Module exports.\n * @public\n */\n\nmodule.exports = escapeHtml;\n\n/**\n * Escape special characters in the given string of html.\n *\n * @param {string} string The string to escape for inserting into HTML\n * @return {string}\n * @public\n */\n\nfunction escapeHtml(string) {\n var str = '' + string;\n var match = matchHtmlRegExp.exec(str);\n\n if (!match) {\n return str;\n }\n\n var escape;\n var html = '';\n var index = 0;\n var lastIndex = 0;\n\n for (index = match.index; index < str.length; index++) {\n switch (str.charCodeAt(index)) {\n case 34: // \"\n escape = '"';\n break;\n case 38: // &\n escape = '&';\n break;\n case 39: // '\n escape = ''';\n break;\n case 60: // <\n escape = '<';\n break;\n case 62: // >\n escape = '>';\n break;\n default:\n continue;\n }\n\n if (lastIndex !== index) {\n html += str.substring(lastIndex, index);\n }\n\n lastIndex = index + 1;\n html += escape;\n }\n\n return lastIndex !== index\n ? html + str.substring(lastIndex, index)\n : html;\n}\n", "/*!\n * clipboard.js v2.0.11\n * https://clipboardjs.com/\n *\n * Licensed MIT \u00A9 Zeno Rocha\n */\n(function webpackUniversalModuleDefinition(root, factory) {\n\tif(typeof exports === 'object' && typeof module === 'object')\n\t\tmodule.exports = factory();\n\telse if(typeof define === 'function' && define.amd)\n\t\tdefine([], factory);\n\telse if(typeof exports === 'object')\n\t\texports[\"ClipboardJS\"] = factory();\n\telse\n\t\troot[\"ClipboardJS\"] = factory();\n})(this, function() {\nreturn /******/ (function() { // webpackBootstrap\n/******/ \tvar __webpack_modules__ = ({\n\n/***/ 686:\n/***/ (function(__unused_webpack_module, __webpack_exports__, __webpack_require__) {\n\n\"use strict\";\n\n// EXPORTS\n__webpack_require__.d(__webpack_exports__, {\n \"default\": function() { return /* binding */ clipboard; }\n});\n\n// EXTERNAL MODULE: ./node_modules/tiny-emitter/index.js\nvar tiny_emitter = __webpack_require__(279);\nvar tiny_emitter_default = /*#__PURE__*/__webpack_require__.n(tiny_emitter);\n// EXTERNAL MODULE: ./node_modules/good-listener/src/listen.js\nvar listen = __webpack_require__(370);\nvar listen_default = /*#__PURE__*/__webpack_require__.n(listen);\n// EXTERNAL MODULE: ./node_modules/select/src/select.js\nvar src_select = __webpack_require__(817);\nvar select_default = /*#__PURE__*/__webpack_require__.n(src_select);\n;// CONCATENATED MODULE: ./src/common/command.js\n/**\n * Executes a given operation type.\n * @param {String} type\n * @return {Boolean}\n */\nfunction command(type) {\n try {\n return document.execCommand(type);\n } catch (err) {\n return false;\n }\n}\n;// CONCATENATED MODULE: ./src/actions/cut.js\n\n\n/**\n * Cut action wrapper.\n * @param {String|HTMLElement} target\n * @return {String}\n */\n\nvar ClipboardActionCut = function ClipboardActionCut(target) {\n var selectedText = select_default()(target);\n command('cut');\n return selectedText;\n};\n\n/* harmony default export */ var actions_cut = (ClipboardActionCut);\n;// CONCATENATED MODULE: ./src/common/create-fake-element.js\n/**\n * Creates a fake textarea element with a value.\n * @param {String} value\n * @return {HTMLElement}\n */\nfunction createFakeElement(value) {\n var isRTL = document.documentElement.getAttribute('dir') === 'rtl';\n var fakeElement = document.createElement('textarea'); // Prevent zooming on iOS\n\n fakeElement.style.fontSize = '12pt'; // Reset box model\n\n fakeElement.style.border = '0';\n fakeElement.style.padding = '0';\n fakeElement.style.margin = '0'; // Move element out of screen horizontally\n\n fakeElement.style.position = 'absolute';\n fakeElement.style[isRTL ? 'right' : 'left'] = '-9999px'; // Move element to the same position vertically\n\n var yPosition = window.pageYOffset || document.documentElement.scrollTop;\n fakeElement.style.top = \"\".concat(yPosition, \"px\");\n fakeElement.setAttribute('readonly', '');\n fakeElement.value = value;\n return fakeElement;\n}\n;// CONCATENATED MODULE: ./src/actions/copy.js\n\n\n\n/**\n * Create fake copy action wrapper using a fake element.\n * @param {String} target\n * @param {Object} options\n * @return {String}\n */\n\nvar fakeCopyAction = function fakeCopyAction(value, options) {\n var fakeElement = createFakeElement(value);\n options.container.appendChild(fakeElement);\n var selectedText = select_default()(fakeElement);\n command('copy');\n fakeElement.remove();\n return selectedText;\n};\n/**\n * Copy action wrapper.\n * @param {String|HTMLElement} target\n * @param {Object} options\n * @return {String}\n */\n\n\nvar ClipboardActionCopy = function ClipboardActionCopy(target) {\n var options = arguments.length > 1 && arguments[1] !== undefined ? arguments[1] : {\n container: document.body\n };\n var selectedText = '';\n\n if (typeof target === 'string') {\n selectedText = fakeCopyAction(target, options);\n } else if (target instanceof HTMLInputElement && !['text', 'search', 'url', 'tel', 'password'].includes(target === null || target === void 0 ? void 0 : target.type)) {\n // If input type doesn't support `setSelectionRange`. Simulate it. https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement/setSelectionRange\n selectedText = fakeCopyAction(target.value, options);\n } else {\n selectedText = select_default()(target);\n command('copy');\n }\n\n return selectedText;\n};\n\n/* harmony default export */ var actions_copy = (ClipboardActionCopy);\n;// CONCATENATED MODULE: ./src/actions/default.js\nfunction _typeof(obj) { \"@babel/helpers - typeof\"; if (typeof Symbol === \"function\" && typeof Symbol.iterator === \"symbol\") { _typeof = function _typeof(obj) { return typeof obj; }; } else { _typeof = function _typeof(obj) { return obj && typeof Symbol === \"function\" && obj.constructor === Symbol && obj !== Symbol.prototype ? \"symbol\" : typeof obj; }; } return _typeof(obj); }\n\n\n\n/**\n * Inner function which performs selection from either `text` or `target`\n * properties and then executes copy or cut operations.\n * @param {Object} options\n */\n\nvar ClipboardActionDefault = function ClipboardActionDefault() {\n var options = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : {};\n // Defines base properties passed from constructor.\n var _options$action = options.action,\n action = _options$action === void 0 ? 'copy' : _options$action,\n container = options.container,\n target = options.target,\n text = options.text; // Sets the `action` to be performed which can be either 'copy' or 'cut'.\n\n if (action !== 'copy' && action !== 'cut') {\n throw new Error('Invalid \"action\" value, use either \"copy\" or \"cut\"');\n } // Sets the `target` property using an element that will be have its content copied.\n\n\n if (target !== undefined) {\n if (target && _typeof(target) === 'object' && target.nodeType === 1) {\n if (action === 'copy' && target.hasAttribute('disabled')) {\n throw new Error('Invalid \"target\" attribute. Please use \"readonly\" instead of \"disabled\" attribute');\n }\n\n if (action === 'cut' && (target.hasAttribute('readonly') || target.hasAttribute('disabled'))) {\n throw new Error('Invalid \"target\" attribute. You can\\'t cut text from elements with \"readonly\" or \"disabled\" attributes');\n }\n } else {\n throw new Error('Invalid \"target\" value, use a valid Element');\n }\n } // Define selection strategy based on `text` property.\n\n\n if (text) {\n return actions_copy(text, {\n container: container\n });\n } // Defines which selection strategy based on `target` property.\n\n\n if (target) {\n return action === 'cut' ? actions_cut(target) : actions_copy(target, {\n container: container\n });\n }\n};\n\n/* harmony default export */ var actions_default = (ClipboardActionDefault);\n;// CONCATENATED MODULE: ./src/clipboard.js\nfunction clipboard_typeof(obj) { \"@babel/helpers - typeof\"; if (typeof Symbol === \"function\" && typeof Symbol.iterator === \"symbol\") { clipboard_typeof = function _typeof(obj) { return typeof obj; }; } else { clipboard_typeof = function _typeof(obj) { return obj && typeof Symbol === \"function\" && obj.constructor === Symbol && obj !== Symbol.prototype ? \"symbol\" : typeof obj; }; } return clipboard_typeof(obj); }\n\nfunction _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError(\"Cannot call a class as a function\"); } }\n\nfunction _defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if (\"value\" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } }\n\nfunction _createClass(Constructor, protoProps, staticProps) { if (protoProps) _defineProperties(Constructor.prototype, protoProps); if (staticProps) _defineProperties(Constructor, staticProps); return Constructor; }\n\nfunction _inherits(subClass, superClass) { if (typeof superClass !== \"function\" && superClass !== null) { throw new TypeError(\"Super expression must either be null or a function\"); } subClass.prototype = Object.create(superClass && superClass.prototype, { constructor: { value: subClass, writable: true, configurable: true } }); if (superClass) _setPrototypeOf(subClass, superClass); }\n\nfunction _setPrototypeOf(o, p) { _setPrototypeOf = Object.setPrototypeOf || function _setPrototypeOf(o, p) { o.__proto__ = p; return o; }; return _setPrototypeOf(o, p); }\n\nfunction _createSuper(Derived) { var hasNativeReflectConstruct = _isNativeReflectConstruct(); return function _createSuperInternal() { var Super = _getPrototypeOf(Derived), result; if (hasNativeReflectConstruct) { var NewTarget = _getPrototypeOf(this).constructor; result = Reflect.construct(Super, arguments, NewTarget); } else { result = Super.apply(this, arguments); } return _possibleConstructorReturn(this, result); }; }\n\nfunction _possibleConstructorReturn(self, call) { if (call && (clipboard_typeof(call) === \"object\" || typeof call === \"function\")) { return call; } return _assertThisInitialized(self); }\n\nfunction _assertThisInitialized(self) { if (self === void 0) { throw new ReferenceError(\"this hasn't been initialised - super() hasn't been called\"); } return self; }\n\nfunction _isNativeReflectConstruct() { if (typeof Reflect === \"undefined\" || !Reflect.construct) return false; if (Reflect.construct.sham) return false; if (typeof Proxy === \"function\") return true; try { Date.prototype.toString.call(Reflect.construct(Date, [], function () {})); return true; } catch (e) { return false; } }\n\nfunction _getPrototypeOf(o) { _getPrototypeOf = Object.setPrototypeOf ? Object.getPrototypeOf : function _getPrototypeOf(o) { return o.__proto__ || Object.getPrototypeOf(o); }; return _getPrototypeOf(o); }\n\n\n\n\n\n\n/**\n * Helper function to retrieve attribute value.\n * @param {String} suffix\n * @param {Element} element\n */\n\nfunction getAttributeValue(suffix, element) {\n var attribute = \"data-clipboard-\".concat(suffix);\n\n if (!element.hasAttribute(attribute)) {\n return;\n }\n\n return element.getAttribute(attribute);\n}\n/**\n * Base class which takes one or more elements, adds event listeners to them,\n * and instantiates a new `ClipboardAction` on each click.\n */\n\n\nvar Clipboard = /*#__PURE__*/function (_Emitter) {\n _inherits(Clipboard, _Emitter);\n\n var _super = _createSuper(Clipboard);\n\n /**\n * @param {String|HTMLElement|HTMLCollection|NodeList} trigger\n * @param {Object} options\n */\n function Clipboard(trigger, options) {\n var _this;\n\n _classCallCheck(this, Clipboard);\n\n _this = _super.call(this);\n\n _this.resolveOptions(options);\n\n _this.listenClick(trigger);\n\n return _this;\n }\n /**\n * Defines if attributes would be resolved using internal setter functions\n * or custom functions that were passed in the constructor.\n * @param {Object} options\n */\n\n\n _createClass(Clipboard, [{\n key: \"resolveOptions\",\n value: function resolveOptions() {\n var options = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : {};\n this.action = typeof options.action === 'function' ? options.action : this.defaultAction;\n this.target = typeof options.target === 'function' ? options.target : this.defaultTarget;\n this.text = typeof options.text === 'function' ? options.text : this.defaultText;\n this.container = clipboard_typeof(options.container) === 'object' ? options.container : document.body;\n }\n /**\n * Adds a click event listener to the passed trigger.\n * @param {String|HTMLElement|HTMLCollection|NodeList} trigger\n */\n\n }, {\n key: \"listenClick\",\n value: function listenClick(trigger) {\n var _this2 = this;\n\n this.listener = listen_default()(trigger, 'click', function (e) {\n return _this2.onClick(e);\n });\n }\n /**\n * Defines a new `ClipboardAction` on each click event.\n * @param {Event} e\n */\n\n }, {\n key: \"onClick\",\n value: function onClick(e) {\n var trigger = e.delegateTarget || e.currentTarget;\n var action = this.action(trigger) || 'copy';\n var text = actions_default({\n action: action,\n container: this.container,\n target: this.target(trigger),\n text: this.text(trigger)\n }); // Fires an event based on the copy operation result.\n\n this.emit(text ? 'success' : 'error', {\n action: action,\n text: text,\n trigger: trigger,\n clearSelection: function clearSelection() {\n if (trigger) {\n trigger.focus();\n }\n\n window.getSelection().removeAllRanges();\n }\n });\n }\n /**\n * Default `action` lookup function.\n * @param {Element} trigger\n */\n\n }, {\n key: \"defaultAction\",\n value: function defaultAction(trigger) {\n return getAttributeValue('action', trigger);\n }\n /**\n * Default `target` lookup function.\n * @param {Element} trigger\n */\n\n }, {\n key: \"defaultTarget\",\n value: function defaultTarget(trigger) {\n var selector = getAttributeValue('target', trigger);\n\n if (selector) {\n return document.querySelector(selector);\n }\n }\n /**\n * Allow fire programmatically a copy action\n * @param {String|HTMLElement} target\n * @param {Object} options\n * @returns Text copied.\n */\n\n }, {\n key: \"defaultText\",\n\n /**\n * Default `text` lookup function.\n * @param {Element} trigger\n */\n value: function defaultText(trigger) {\n return getAttributeValue('text', trigger);\n }\n /**\n * Destroy lifecycle.\n */\n\n }, {\n key: \"destroy\",\n value: function destroy() {\n this.listener.destroy();\n }\n }], [{\n key: \"copy\",\n value: function copy(target) {\n var options = arguments.length > 1 && arguments[1] !== undefined ? arguments[1] : {\n container: document.body\n };\n return actions_copy(target, options);\n }\n /**\n * Allow fire programmatically a cut action\n * @param {String|HTMLElement} target\n * @returns Text cutted.\n */\n\n }, {\n key: \"cut\",\n value: function cut(target) {\n return actions_cut(target);\n }\n /**\n * Returns the support of the given action, or all actions if no action is\n * given.\n * @param {String} [action]\n */\n\n }, {\n key: \"isSupported\",\n value: function isSupported() {\n var action = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : ['copy', 'cut'];\n var actions = typeof action === 'string' ? [action] : action;\n var support = !!document.queryCommandSupported;\n actions.forEach(function (action) {\n support = support && !!document.queryCommandSupported(action);\n });\n return support;\n }\n }]);\n\n return Clipboard;\n}((tiny_emitter_default()));\n\n/* harmony default export */ var clipboard = (Clipboard);\n\n/***/ }),\n\n/***/ 828:\n/***/ (function(module) {\n\nvar DOCUMENT_NODE_TYPE = 9;\n\n/**\n * A polyfill for Element.matches()\n */\nif (typeof Element !== 'undefined' && !Element.prototype.matches) {\n var proto = Element.prototype;\n\n proto.matches = proto.matchesSelector ||\n proto.mozMatchesSelector ||\n proto.msMatchesSelector ||\n proto.oMatchesSelector ||\n proto.webkitMatchesSelector;\n}\n\n/**\n * Finds the closest parent that matches a selector.\n *\n * @param {Element} element\n * @param {String} selector\n * @return {Function}\n */\nfunction closest (element, selector) {\n while (element && element.nodeType !== DOCUMENT_NODE_TYPE) {\n if (typeof element.matches === 'function' &&\n element.matches(selector)) {\n return element;\n }\n element = element.parentNode;\n }\n}\n\nmodule.exports = closest;\n\n\n/***/ }),\n\n/***/ 438:\n/***/ (function(module, __unused_webpack_exports, __webpack_require__) {\n\nvar closest = __webpack_require__(828);\n\n/**\n * Delegates event to a selector.\n *\n * @param {Element} element\n * @param {String} selector\n * @param {String} type\n * @param {Function} callback\n * @param {Boolean} useCapture\n * @return {Object}\n */\nfunction _delegate(element, selector, type, callback, useCapture) {\n var listenerFn = listener.apply(this, arguments);\n\n element.addEventListener(type, listenerFn, useCapture);\n\n return {\n destroy: function() {\n element.removeEventListener(type, listenerFn, useCapture);\n }\n }\n}\n\n/**\n * Delegates event to a selector.\n *\n * @param {Element|String|Array} [elements]\n * @param {String} selector\n * @param {String} type\n * @param {Function} callback\n * @param {Boolean} useCapture\n * @return {Object}\n */\nfunction delegate(elements, selector, type, callback, useCapture) {\n // Handle the regular Element usage\n if (typeof elements.addEventListener === 'function') {\n return _delegate.apply(null, arguments);\n }\n\n // Handle Element-less usage, it defaults to global delegation\n if (typeof type === 'function') {\n // Use `document` as the first parameter, then apply arguments\n // This is a short way to .unshift `arguments` without running into deoptimizations\n return _delegate.bind(null, document).apply(null, arguments);\n }\n\n // Handle Selector-based usage\n if (typeof elements === 'string') {\n elements = document.querySelectorAll(elements);\n }\n\n // Handle Array-like based usage\n return Array.prototype.map.call(elements, function (element) {\n return _delegate(element, selector, type, callback, useCapture);\n });\n}\n\n/**\n * Finds closest match and invokes callback.\n *\n * @param {Element} element\n * @param {String} selector\n * @param {String} type\n * @param {Function} callback\n * @return {Function}\n */\nfunction listener(element, selector, type, callback) {\n return function(e) {\n e.delegateTarget = closest(e.target, selector);\n\n if (e.delegateTarget) {\n callback.call(element, e);\n }\n }\n}\n\nmodule.exports = delegate;\n\n\n/***/ }),\n\n/***/ 879:\n/***/ (function(__unused_webpack_module, exports) {\n\n/**\n * Check if argument is a HTML element.\n *\n * @param {Object} value\n * @return {Boolean}\n */\nexports.node = function(value) {\n return value !== undefined\n && value instanceof HTMLElement\n && value.nodeType === 1;\n};\n\n/**\n * Check if argument is a list of HTML elements.\n *\n * @param {Object} value\n * @return {Boolean}\n */\nexports.nodeList = function(value) {\n var type = Object.prototype.toString.call(value);\n\n return value !== undefined\n && (type === '[object NodeList]' || type === '[object HTMLCollection]')\n && ('length' in value)\n && (value.length === 0 || exports.node(value[0]));\n};\n\n/**\n * Check if argument is a string.\n *\n * @param {Object} value\n * @return {Boolean}\n */\nexports.string = function(value) {\n return typeof value === 'string'\n || value instanceof String;\n};\n\n/**\n * Check if argument is a function.\n *\n * @param {Object} value\n * @return {Boolean}\n */\nexports.fn = function(value) {\n var type = Object.prototype.toString.call(value);\n\n return type === '[object Function]';\n};\n\n\n/***/ }),\n\n/***/ 370:\n/***/ (function(module, __unused_webpack_exports, __webpack_require__) {\n\nvar is = __webpack_require__(879);\nvar delegate = __webpack_require__(438);\n\n/**\n * Validates all params and calls the right\n * listener function based on its target type.\n *\n * @param {String|HTMLElement|HTMLCollection|NodeList} target\n * @param {String} type\n * @param {Function} callback\n * @return {Object}\n */\nfunction listen(target, type, callback) {\n if (!target && !type && !callback) {\n throw new Error('Missing required arguments');\n }\n\n if (!is.string(type)) {\n throw new TypeError('Second argument must be a String');\n }\n\n if (!is.fn(callback)) {\n throw new TypeError('Third argument must be a Function');\n }\n\n if (is.node(target)) {\n return listenNode(target, type, callback);\n }\n else if (is.nodeList(target)) {\n return listenNodeList(target, type, callback);\n }\n else if (is.string(target)) {\n return listenSelector(target, type, callback);\n }\n else {\n throw new TypeError('First argument must be a String, HTMLElement, HTMLCollection, or NodeList');\n }\n}\n\n/**\n * Adds an event listener to a HTML element\n * and returns a remove listener function.\n *\n * @param {HTMLElement} node\n * @param {String} type\n * @param {Function} callback\n * @return {Object}\n */\nfunction listenNode(node, type, callback) {\n node.addEventListener(type, callback);\n\n return {\n destroy: function() {\n node.removeEventListener(type, callback);\n }\n }\n}\n\n/**\n * Add an event listener to a list of HTML elements\n * and returns a remove listener function.\n *\n * @param {NodeList|HTMLCollection} nodeList\n * @param {String} type\n * @param {Function} callback\n * @return {Object}\n */\nfunction listenNodeList(nodeList, type, callback) {\n Array.prototype.forEach.call(nodeList, function(node) {\n node.addEventListener(type, callback);\n });\n\n return {\n destroy: function() {\n Array.prototype.forEach.call(nodeList, function(node) {\n node.removeEventListener(type, callback);\n });\n }\n }\n}\n\n/**\n * Add an event listener to a selector\n * and returns a remove listener function.\n *\n * @param {String} selector\n * @param {String} type\n * @param {Function} callback\n * @return {Object}\n */\nfunction listenSelector(selector, type, callback) {\n return delegate(document.body, selector, type, callback);\n}\n\nmodule.exports = listen;\n\n\n/***/ }),\n\n/***/ 817:\n/***/ (function(module) {\n\nfunction select(element) {\n var selectedText;\n\n if (element.nodeName === 'SELECT') {\n element.focus();\n\n selectedText = element.value;\n }\n else if (element.nodeName === 'INPUT' || element.nodeName === 'TEXTAREA') {\n var isReadOnly = element.hasAttribute('readonly');\n\n if (!isReadOnly) {\n element.setAttribute('readonly', '');\n }\n\n element.select();\n element.setSelectionRange(0, element.value.length);\n\n if (!isReadOnly) {\n element.removeAttribute('readonly');\n }\n\n selectedText = element.value;\n }\n else {\n if (element.hasAttribute('contenteditable')) {\n element.focus();\n }\n\n var selection = window.getSelection();\n var range = document.createRange();\n\n range.selectNodeContents(element);\n selection.removeAllRanges();\n selection.addRange(range);\n\n selectedText = selection.toString();\n }\n\n return selectedText;\n}\n\nmodule.exports = select;\n\n\n/***/ }),\n\n/***/ 279:\n/***/ (function(module) {\n\nfunction E () {\n // Keep this empty so it's easier to inherit from\n // (via https://github.com/lipsmack from https://github.com/scottcorgan/tiny-emitter/issues/3)\n}\n\nE.prototype = {\n on: function (name, callback, ctx) {\n var e = this.e || (this.e = {});\n\n (e[name] || (e[name] = [])).push({\n fn: callback,\n ctx: ctx\n });\n\n return this;\n },\n\n once: function (name, callback, ctx) {\n var self = this;\n function listener () {\n self.off(name, listener);\n callback.apply(ctx, arguments);\n };\n\n listener._ = callback\n return this.on(name, listener, ctx);\n },\n\n emit: function (name) {\n var data = [].slice.call(arguments, 1);\n var evtArr = ((this.e || (this.e = {}))[name] || []).slice();\n var i = 0;\n var len = evtArr.length;\n\n for (i; i < len; i++) {\n evtArr[i].fn.apply(evtArr[i].ctx, data);\n }\n\n return this;\n },\n\n off: function (name, callback) {\n var e = this.e || (this.e = {});\n var evts = e[name];\n var liveEvents = [];\n\n if (evts && callback) {\n for (var i = 0, len = evts.length; i < len; i++) {\n if (evts[i].fn !== callback && evts[i].fn._ !== callback)\n liveEvents.push(evts[i]);\n }\n }\n\n // Remove event from queue to prevent memory leak\n // Suggested by https://github.com/lazd\n // Ref: https://github.com/scottcorgan/tiny-emitter/commit/c6ebfaa9bc973b33d110a84a307742b7cf94c953#commitcomment-5024910\n\n (liveEvents.length)\n ? e[name] = liveEvents\n : delete e[name];\n\n return this;\n }\n};\n\nmodule.exports = E;\nmodule.exports.TinyEmitter = E;\n\n\n/***/ })\n\n/******/ \t});\n/************************************************************************/\n/******/ \t// The module cache\n/******/ \tvar __webpack_module_cache__ = {};\n/******/ \t\n/******/ \t// The require function\n/******/ \tfunction __webpack_require__(moduleId) {\n/******/ \t\t// Check if module is in cache\n/******/ \t\tif(__webpack_module_cache__[moduleId]) {\n/******/ \t\t\treturn __webpack_module_cache__[moduleId].exports;\n/******/ \t\t}\n/******/ \t\t// Create a new module (and put it into the cache)\n/******/ \t\tvar module = __webpack_module_cache__[moduleId] = {\n/******/ \t\t\t// no module.id needed\n/******/ \t\t\t// no module.loaded needed\n/******/ \t\t\texports: {}\n/******/ \t\t};\n/******/ \t\n/******/ \t\t// Execute the module function\n/******/ \t\t__webpack_modules__[moduleId](module, module.exports, __webpack_require__);\n/******/ \t\n/******/ \t\t// Return the exports of the module\n/******/ \t\treturn module.exports;\n/******/ \t}\n/******/ \t\n/************************************************************************/\n/******/ \t/* webpack/runtime/compat get default export */\n/******/ \t!function() {\n/******/ \t\t// getDefaultExport function for compatibility with non-harmony modules\n/******/ \t\t__webpack_require__.n = function(module) {\n/******/ \t\t\tvar getter = module && module.__esModule ?\n/******/ \t\t\t\tfunction() { return module['default']; } :\n/******/ \t\t\t\tfunction() { return module; };\n/******/ \t\t\t__webpack_require__.d(getter, { a: getter });\n/******/ \t\t\treturn getter;\n/******/ \t\t};\n/******/ \t}();\n/******/ \t\n/******/ \t/* webpack/runtime/define property getters */\n/******/ \t!function() {\n/******/ \t\t// define getter functions for harmony exports\n/******/ \t\t__webpack_require__.d = function(exports, definition) {\n/******/ \t\t\tfor(var key in definition) {\n/******/ \t\t\t\tif(__webpack_require__.o(definition, key) && !__webpack_require__.o(exports, key)) {\n/******/ \t\t\t\t\tObject.defineProperty(exports, key, { enumerable: true, get: definition[key] });\n/******/ \t\t\t\t}\n/******/ \t\t\t}\n/******/ \t\t};\n/******/ \t}();\n/******/ \t\n/******/ \t/* webpack/runtime/hasOwnProperty shorthand */\n/******/ \t!function() {\n/******/ \t\t__webpack_require__.o = function(obj, prop) { return Object.prototype.hasOwnProperty.call(obj, prop); }\n/******/ \t}();\n/******/ \t\n/************************************************************************/\n/******/ \t// module exports must be returned from runtime so entry inlining is disabled\n/******/ \t// startup\n/******/ \t// Load entry module and return exports\n/******/ \treturn __webpack_require__(686);\n/******/ })()\n.default;\n});", "/*\n * Copyright (c) 2016-2025 Martin Donath \n *\n * Permission is hereby granted, free of charge, to any person obtaining a copy\n * of this software and associated documentation files (the \"Software\"), to\n * deal in the Software without restriction, including without limitation the\n * rights to use, copy, modify, merge, publish, distribute, sublicense, and/or\n * sell copies of the Software, and to permit persons to whom the Software is\n * furnished to do so, subject to the following conditions:\n *\n * The above copyright notice and this permission notice shall be included in\n * all copies or substantial portions of the Software.\n *\n * THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\n * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\n * FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE\n * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\n * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING\n * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS\n * IN THE SOFTWARE.\n */\n\nimport \"focus-visible\"\n\nimport {\n EMPTY,\n NEVER,\n Observable,\n Subject,\n defer,\n delay,\n filter,\n map,\n merge,\n mergeWith,\n shareReplay,\n switchMap\n} from \"rxjs\"\n\nimport { configuration, feature } from \"./_\"\nimport {\n at,\n getActiveElement,\n getOptionalElement,\n requestJSON,\n setLocation,\n setToggle,\n watchDocument,\n watchKeyboard,\n watchLocation,\n watchLocationTarget,\n watchMedia,\n watchPrint,\n watchScript,\n watchViewport\n} from \"./browser\"\nimport {\n getComponentElement,\n getComponentElements,\n mountAnnounce,\n mountBackToTop,\n mountConsent,\n mountContent,\n mountDialog,\n mountHeader,\n mountHeaderTitle,\n mountPalette,\n mountProgress,\n mountSearch,\n mountSearchHiglight,\n mountSidebar,\n mountSource,\n mountTableOfContents,\n mountTabs,\n watchHeader,\n watchMain\n} from \"./components\"\nimport {\n SearchIndex,\n setupClipboardJS,\n setupInstantNavigation,\n setupVersionSelector\n} from \"./integrations\"\nimport {\n patchEllipsis,\n patchIndeterminate,\n patchScrollfix,\n patchScrolllock\n} from \"./patches\"\nimport \"./polyfills\"\n\n/* ----------------------------------------------------------------------------\n * Functions - @todo refactor\n * ------------------------------------------------------------------------- */\n\n/**\n * Fetch search index\n *\n * @returns Search index observable\n */\nfunction fetchSearchIndex(): Observable {\n if (location.protocol === \"file:\") {\n return watchScript(\n `${new URL(\"search/search_index.js\", config.base)}`\n )\n .pipe(\n // @ts-ignore - @todo fix typings\n map(() => __index),\n shareReplay(1)\n )\n } else {\n return requestJSON(\n new URL(\"search/search_index.json\", config.base)\n )\n }\n}\n\n/* ----------------------------------------------------------------------------\n * Application\n * ------------------------------------------------------------------------- */\n\n/* Yay, JavaScript is available */\ndocument.documentElement.classList.remove(\"no-js\")\ndocument.documentElement.classList.add(\"js\")\n\n/* Set up navigation observables and subjects */\nconst document$ = watchDocument()\nconst location$ = watchLocation()\nconst target$ = watchLocationTarget(location$)\nconst keyboard$ = watchKeyboard()\n\n/* Set up media observables */\nconst viewport$ = watchViewport()\nconst tablet$ = watchMedia(\"(min-width: 960px)\")\nconst screen$ = watchMedia(\"(min-width: 1220px)\")\nconst print$ = watchPrint()\n\n/* Retrieve search index, if search is enabled */\nconst config = configuration()\nconst index$ = document.forms.namedItem(\"search\")\n ? fetchSearchIndex()\n : NEVER\n\n/* Set up Clipboard.js integration */\nconst alert$ = new Subject()\nsetupClipboardJS({ alert$ })\n\n/* Set up progress indicator */\nconst progress$ = new Subject()\n\n/* Set up instant navigation, if enabled */\nif (feature(\"navigation.instant\"))\n setupInstantNavigation({ location$, viewport$, progress$ })\n .subscribe(document$)\n\n/* Set up version selector */\nif (config.version?.provider === \"mike\")\n setupVersionSelector({ document$ })\n\n/* Always close drawer and search on navigation */\nmerge(location$, target$)\n .pipe(\n delay(125)\n )\n .subscribe(() => {\n setToggle(\"drawer\", false)\n setToggle(\"search\", false)\n })\n\n/* Set up global keyboard handlers */\nkeyboard$\n .pipe(\n filter(({ mode }) => mode === \"global\")\n )\n .subscribe(key => {\n switch (key.type) {\n\n /* Go to previous page */\n case \"p\":\n case \",\":\n const prev = getOptionalElement(\"link[rel=prev]\")\n if (typeof prev !== \"undefined\")\n setLocation(prev)\n break\n\n /* Go to next page */\n case \"n\":\n case \".\":\n const next = getOptionalElement(\"link[rel=next]\")\n if (typeof next !== \"undefined\")\n setLocation(next)\n break\n\n /* Expand navigation, see https://bit.ly/3ZjG5io */\n case \"Enter\":\n const active = getActiveElement()\n if (active instanceof HTMLLabelElement)\n active.click()\n }\n })\n\n/* Set up patches */\npatchEllipsis({ viewport$, document$ })\npatchIndeterminate({ document$, tablet$ })\npatchScrollfix({ document$ })\npatchScrolllock({ viewport$, tablet$ })\n\n/* Set up header and main area observable */\nconst header$ = watchHeader(getComponentElement(\"header\"), { viewport$ })\nconst main$ = document$\n .pipe(\n map(() => getComponentElement(\"main\")),\n switchMap(el => watchMain(el, { viewport$, header$ })),\n shareReplay(1)\n )\n\n/* Set up control component observables */\nconst control$ = merge(\n\n /* Consent */\n ...getComponentElements(\"consent\")\n .map(el => mountConsent(el, { target$ })),\n\n /* Dialog */\n ...getComponentElements(\"dialog\")\n .map(el => mountDialog(el, { alert$ })),\n\n /* Color palette */\n ...getComponentElements(\"palette\")\n .map(el => mountPalette(el)),\n\n /* Progress bar */\n ...getComponentElements(\"progress\")\n .map(el => mountProgress(el, { progress$ })),\n\n /* Search */\n ...getComponentElements(\"search\")\n .map(el => mountSearch(el, { index$, keyboard$ })),\n\n /* Repository information */\n ...getComponentElements(\"source\")\n .map(el => mountSource(el))\n)\n\n/* Set up content component observables */\nconst content$ = defer(() => merge(\n\n /* Announcement bar */\n ...getComponentElements(\"announce\")\n .map(el => mountAnnounce(el)),\n\n /* Content */\n ...getComponentElements(\"content\")\n .map(el => mountContent(el, { viewport$, target$, print$ })),\n\n /* Search highlighting */\n ...getComponentElements(\"content\")\n .map(el => feature(\"search.highlight\")\n ? mountSearchHiglight(el, { index$, location$ })\n : EMPTY\n ),\n\n /* Header */\n ...getComponentElements(\"header\")\n .map(el => mountHeader(el, { viewport$, header$, main$ })),\n\n /* Header title */\n ...getComponentElements(\"header-title\")\n .map(el => mountHeaderTitle(el, { viewport$, header$ })),\n\n /* Sidebar */\n ...getComponentElements(\"sidebar\")\n .map(el => el.getAttribute(\"data-md-type\") === \"navigation\"\n ? at(screen$, () => mountSidebar(el, { viewport$, header$, main$ }))\n : at(tablet$, () => mountSidebar(el, { viewport$, header$, main$ }))\n ),\n\n /* Navigation tabs */\n ...getComponentElements(\"tabs\")\n .map(el => mountTabs(el, { viewport$, header$ })),\n\n /* Table of contents */\n ...getComponentElements(\"toc\")\n .map(el => mountTableOfContents(el, {\n viewport$, header$, main$, target$\n })),\n\n /* Back-to-top button */\n ...getComponentElements(\"top\")\n .map(el => mountBackToTop(el, { viewport$, header$, main$, target$ }))\n))\n\n/* Set up component observables */\nconst component$ = document$\n .pipe(\n switchMap(() => content$),\n mergeWith(control$),\n shareReplay(1)\n )\n\n/* Subscribe to all components */\ncomponent$.subscribe()\n\n/* ----------------------------------------------------------------------------\n * Exports\n * ------------------------------------------------------------------------- */\n\nwindow.document$ = document$ /* Document observable */\nwindow.location$ = location$ /* Location subject */\nwindow.target$ = target$ /* Location target observable */\nwindow.keyboard$ = keyboard$ /* Keyboard observable */\nwindow.viewport$ = viewport$ /* Viewport observable */\nwindow.tablet$ = tablet$ /* Media tablet observable */\nwindow.screen$ = screen$ /* Media screen observable */\nwindow.print$ = print$ /* Media print observable */\nwindow.alert$ = alert$ /* Alert subject */\nwindow.progress$ = progress$ /* Progress indicator subject */\nwindow.component$ = component$ /* Component observable */\n", "/******************************************************************************\nCopyright (c) Microsoft Corporation.\n\nPermission to use, copy, modify, and/or distribute this software for any\npurpose with or without fee is hereby granted.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH\nREGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY\nAND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,\nINDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM\nLOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR\nOTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR\nPERFORMANCE OF THIS SOFTWARE.\n***************************************************************************** */\n/* global Reflect, Promise, SuppressedError, Symbol, Iterator */\n\nvar extendStatics = function(d, b) {\n extendStatics = Object.setPrototypeOf ||\n ({ __proto__: [] } instanceof Array && function (d, b) { d.__proto__ = b; }) ||\n function (d, b) { for (var p in b) if (Object.prototype.hasOwnProperty.call(b, p)) d[p] = b[p]; };\n return extendStatics(d, b);\n};\n\nexport function __extends(d, b) {\n if (typeof b !== \"function\" && b !== null)\n throw new TypeError(\"Class extends value \" + String(b) + \" is not a constructor or null\");\n extendStatics(d, b);\n function __() { this.constructor = d; }\n d.prototype = b === null ? Object.create(b) : (__.prototype = b.prototype, new __());\n}\n\nexport var __assign = function() {\n __assign = Object.assign || function __assign(t) {\n for (var s, i = 1, n = arguments.length; i < n; i++) {\n s = arguments[i];\n for (var p in s) if (Object.prototype.hasOwnProperty.call(s, p)) t[p] = s[p];\n }\n return t;\n }\n return __assign.apply(this, arguments);\n}\n\nexport function __rest(s, e) {\n var t = {};\n for (var p in s) if (Object.prototype.hasOwnProperty.call(s, p) && e.indexOf(p) < 0)\n t[p] = s[p];\n if (s != null && typeof Object.getOwnPropertySymbols === \"function\")\n for (var i = 0, p = Object.getOwnPropertySymbols(s); i < p.length; i++) {\n if (e.indexOf(p[i]) < 0 && Object.prototype.propertyIsEnumerable.call(s, p[i]))\n t[p[i]] = s[p[i]];\n }\n return t;\n}\n\nexport function __decorate(decorators, target, key, desc) {\n var c = arguments.length, r = c < 3 ? target : desc === null ? desc = Object.getOwnPropertyDescriptor(target, key) : desc, d;\n if (typeof Reflect === \"object\" && typeof Reflect.decorate === \"function\") r = Reflect.decorate(decorators, target, key, desc);\n else for (var i = decorators.length - 1; i >= 0; i--) if (d = decorators[i]) r = (c < 3 ? d(r) : c > 3 ? d(target, key, r) : d(target, key)) || r;\n return c > 3 && r && Object.defineProperty(target, key, r), r;\n}\n\nexport function __param(paramIndex, decorator) {\n return function (target, key) { decorator(target, key, paramIndex); }\n}\n\nexport function __esDecorate(ctor, descriptorIn, decorators, contextIn, initializers, extraInitializers) {\n function accept(f) { if (f !== void 0 && typeof f !== \"function\") throw new TypeError(\"Function expected\"); return f; }\n var kind = contextIn.kind, key = kind === \"getter\" ? \"get\" : kind === \"setter\" ? \"set\" : \"value\";\n var target = !descriptorIn && ctor ? contextIn[\"static\"] ? ctor : ctor.prototype : null;\n var descriptor = descriptorIn || (target ? Object.getOwnPropertyDescriptor(target, contextIn.name) : {});\n var _, done = false;\n for (var i = decorators.length - 1; i >= 0; i--) {\n var context = {};\n for (var p in contextIn) context[p] = p === \"access\" ? {} : contextIn[p];\n for (var p in contextIn.access) context.access[p] = contextIn.access[p];\n context.addInitializer = function (f) { if (done) throw new TypeError(\"Cannot add initializers after decoration has completed\"); extraInitializers.push(accept(f || null)); };\n var result = (0, decorators[i])(kind === \"accessor\" ? { get: descriptor.get, set: descriptor.set } : descriptor[key], context);\n if (kind === \"accessor\") {\n if (result === void 0) continue;\n if (result === null || typeof result !== \"object\") throw new TypeError(\"Object expected\");\n if (_ = accept(result.get)) descriptor.get = _;\n if (_ = accept(result.set)) descriptor.set = _;\n if (_ = accept(result.init)) initializers.unshift(_);\n }\n else if (_ = accept(result)) {\n if (kind === \"field\") initializers.unshift(_);\n else descriptor[key] = _;\n }\n }\n if (target) Object.defineProperty(target, contextIn.name, descriptor);\n done = true;\n};\n\nexport function __runInitializers(thisArg, initializers, value) {\n var useValue = arguments.length > 2;\n for (var i = 0; i < initializers.length; i++) {\n value = useValue ? initializers[i].call(thisArg, value) : initializers[i].call(thisArg);\n }\n return useValue ? value : void 0;\n};\n\nexport function __propKey(x) {\n return typeof x === \"symbol\" ? x : \"\".concat(x);\n};\n\nexport function __setFunctionName(f, name, prefix) {\n if (typeof name === \"symbol\") name = name.description ? \"[\".concat(name.description, \"]\") : \"\";\n return Object.defineProperty(f, \"name\", { configurable: true, value: prefix ? \"\".concat(prefix, \" \", name) : name });\n};\n\nexport function __metadata(metadataKey, metadataValue) {\n if (typeof Reflect === \"object\" && typeof Reflect.metadata === \"function\") return Reflect.metadata(metadataKey, metadataValue);\n}\n\nexport function __awaiter(thisArg, _arguments, P, generator) {\n function adopt(value) { return value instanceof P ? value : new P(function (resolve) { resolve(value); }); }\n return new (P || (P = Promise))(function (resolve, reject) {\n function fulfilled(value) { try { step(generator.next(value)); } catch (e) { reject(e); } }\n function rejected(value) { try { step(generator[\"throw\"](value)); } catch (e) { reject(e); } }\n function step(result) { result.done ? resolve(result.value) : adopt(result.value).then(fulfilled, rejected); }\n step((generator = generator.apply(thisArg, _arguments || [])).next());\n });\n}\n\nexport function __generator(thisArg, body) {\n var _ = { label: 0, sent: function() { if (t[0] & 1) throw t[1]; return t[1]; }, trys: [], ops: [] }, f, y, t, g = Object.create((typeof Iterator === \"function\" ? Iterator : Object).prototype);\n return g.next = verb(0), g[\"throw\"] = verb(1), g[\"return\"] = verb(2), typeof Symbol === \"function\" && (g[Symbol.iterator] = function() { return this; }), g;\n function verb(n) { return function (v) { return step([n, v]); }; }\n function step(op) {\n if (f) throw new TypeError(\"Generator is already executing.\");\n while (g && (g = 0, op[0] && (_ = 0)), _) try {\n if (f = 1, y && (t = op[0] & 2 ? y[\"return\"] : op[0] ? y[\"throw\"] || ((t = y[\"return\"]) && t.call(y), 0) : y.next) && !(t = t.call(y, op[1])).done) return t;\n if (y = 0, t) op = [op[0] & 2, t.value];\n switch (op[0]) {\n case 0: case 1: t = op; break;\n case 4: _.label++; return { value: op[1], done: false };\n case 5: _.label++; y = op[1]; op = [0]; continue;\n case 7: op = _.ops.pop(); _.trys.pop(); continue;\n default:\n if (!(t = _.trys, t = t.length > 0 && t[t.length - 1]) && (op[0] === 6 || op[0] === 2)) { _ = 0; continue; }\n if (op[0] === 3 && (!t || (op[1] > t[0] && op[1] < t[3]))) { _.label = op[1]; break; }\n if (op[0] === 6 && _.label < t[1]) { _.label = t[1]; t = op; break; }\n if (t && _.label < t[2]) { _.label = t[2]; _.ops.push(op); break; }\n if (t[2]) _.ops.pop();\n _.trys.pop(); continue;\n }\n op = body.call(thisArg, _);\n } catch (e) { op = [6, e]; y = 0; } finally { f = t = 0; }\n if (op[0] & 5) throw op[1]; return { value: op[0] ? op[1] : void 0, done: true };\n }\n}\n\nexport var __createBinding = Object.create ? (function(o, m, k, k2) {\n if (k2 === undefined) k2 = k;\n var desc = Object.getOwnPropertyDescriptor(m, k);\n if (!desc || (\"get\" in desc ? !m.__esModule : desc.writable || desc.configurable)) {\n desc = { enumerable: true, get: function() { return m[k]; } };\n }\n Object.defineProperty(o, k2, desc);\n}) : (function(o, m, k, k2) {\n if (k2 === undefined) k2 = k;\n o[k2] = m[k];\n});\n\nexport function __exportStar(m, o) {\n for (var p in m) if (p !== \"default\" && !Object.prototype.hasOwnProperty.call(o, p)) __createBinding(o, m, p);\n}\n\nexport function __values(o) {\n var s = typeof Symbol === \"function\" && Symbol.iterator, m = s && o[s], i = 0;\n if (m) return m.call(o);\n if (o && typeof o.length === \"number\") return {\n next: function () {\n if (o && i >= o.length) o = void 0;\n return { value: o && o[i++], done: !o };\n }\n };\n throw new TypeError(s ? \"Object is not iterable.\" : \"Symbol.iterator is not defined.\");\n}\n\nexport function __read(o, n) {\n var m = typeof Symbol === \"function\" && o[Symbol.iterator];\n if (!m) return o;\n var i = m.call(o), r, ar = [], e;\n try {\n while ((n === void 0 || n-- > 0) && !(r = i.next()).done) ar.push(r.value);\n }\n catch (error) { e = { error: error }; }\n finally {\n try {\n if (r && !r.done && (m = i[\"return\"])) m.call(i);\n }\n finally { if (e) throw e.error; }\n }\n return ar;\n}\n\n/** @deprecated */\nexport function __spread() {\n for (var ar = [], i = 0; i < arguments.length; i++)\n ar = ar.concat(__read(arguments[i]));\n return ar;\n}\n\n/** @deprecated */\nexport function __spreadArrays() {\n for (var s = 0, i = 0, il = arguments.length; i < il; i++) s += arguments[i].length;\n for (var r = Array(s), k = 0, i = 0; i < il; i++)\n for (var a = arguments[i], j = 0, jl = a.length; j < jl; j++, k++)\n r[k] = a[j];\n return r;\n}\n\nexport function __spreadArray(to, from, pack) {\n if (pack || arguments.length === 2) for (var i = 0, l = from.length, ar; i < l; i++) {\n if (ar || !(i in from)) {\n if (!ar) ar = Array.prototype.slice.call(from, 0, i);\n ar[i] = from[i];\n }\n }\n return to.concat(ar || Array.prototype.slice.call(from));\n}\n\nexport function __await(v) {\n return this instanceof __await ? (this.v = v, this) : new __await(v);\n}\n\nexport function __asyncGenerator(thisArg, _arguments, generator) {\n if (!Symbol.asyncIterator) throw new TypeError(\"Symbol.asyncIterator is not defined.\");\n var g = generator.apply(thisArg, _arguments || []), i, q = [];\n return i = Object.create((typeof AsyncIterator === \"function\" ? AsyncIterator : Object).prototype), verb(\"next\"), verb(\"throw\"), verb(\"return\", awaitReturn), i[Symbol.asyncIterator] = function () { return this; }, i;\n function awaitReturn(f) { return function (v) { return Promise.resolve(v).then(f, reject); }; }\n function verb(n, f) { if (g[n]) { i[n] = function (v) { return new Promise(function (a, b) { q.push([n, v, a, b]) > 1 || resume(n, v); }); }; if (f) i[n] = f(i[n]); } }\n function resume(n, v) { try { step(g[n](v)); } catch (e) { settle(q[0][3], e); } }\n function step(r) { r.value instanceof __await ? Promise.resolve(r.value.v).then(fulfill, reject) : settle(q[0][2], r); }\n function fulfill(value) { resume(\"next\", value); }\n function reject(value) { resume(\"throw\", value); }\n function settle(f, v) { if (f(v), q.shift(), q.length) resume(q[0][0], q[0][1]); }\n}\n\nexport function __asyncDelegator(o) {\n var i, p;\n return i = {}, verb(\"next\"), verb(\"throw\", function (e) { throw e; }), verb(\"return\"), i[Symbol.iterator] = function () { return this; }, i;\n function verb(n, f) { i[n] = o[n] ? function (v) { return (p = !p) ? { value: __await(o[n](v)), done: false } : f ? f(v) : v; } : f; }\n}\n\nexport function __asyncValues(o) {\n if (!Symbol.asyncIterator) throw new TypeError(\"Symbol.asyncIterator is not defined.\");\n var m = o[Symbol.asyncIterator], i;\n return m ? m.call(o) : (o = typeof __values === \"function\" ? __values(o) : o[Symbol.iterator](), i = {}, verb(\"next\"), verb(\"throw\"), verb(\"return\"), i[Symbol.asyncIterator] = function () { return this; }, i);\n function verb(n) { i[n] = o[n] && function (v) { return new Promise(function (resolve, reject) { v = o[n](v), settle(resolve, reject, v.done, v.value); }); }; }\n function settle(resolve, reject, d, v) { Promise.resolve(v).then(function(v) { resolve({ value: v, done: d }); }, reject); }\n}\n\nexport function __makeTemplateObject(cooked, raw) {\n if (Object.defineProperty) { Object.defineProperty(cooked, \"raw\", { value: raw }); } else { cooked.raw = raw; }\n return cooked;\n};\n\nvar __setModuleDefault = Object.create ? (function(o, v) {\n Object.defineProperty(o, \"default\", { enumerable: true, value: v });\n}) : function(o, v) {\n o[\"default\"] = v;\n};\n\nexport function __importStar(mod) {\n if (mod && mod.__esModule) return mod;\n var result = {};\n if (mod != null) for (var k in mod) if (k !== \"default\" && Object.prototype.hasOwnProperty.call(mod, k)) __createBinding(result, mod, k);\n __setModuleDefault(result, mod);\n return result;\n}\n\nexport function __importDefault(mod) {\n return (mod && mod.__esModule) ? mod : { default: mod };\n}\n\nexport function __classPrivateFieldGet(receiver, state, kind, f) {\n if (kind === \"a\" && !f) throw new TypeError(\"Private accessor was defined without a getter\");\n if (typeof state === \"function\" ? receiver !== state || !f : !state.has(receiver)) throw new TypeError(\"Cannot read private member from an object whose class did not declare it\");\n return kind === \"m\" ? f : kind === \"a\" ? f.call(receiver) : f ? f.value : state.get(receiver);\n}\n\nexport function __classPrivateFieldSet(receiver, state, value, kind, f) {\n if (kind === \"m\") throw new TypeError(\"Private method is not writable\");\n if (kind === \"a\" && !f) throw new TypeError(\"Private accessor was defined without a setter\");\n if (typeof state === \"function\" ? receiver !== state || !f : !state.has(receiver)) throw new TypeError(\"Cannot write private member to an object whose class did not declare it\");\n return (kind === \"a\" ? f.call(receiver, value) : f ? f.value = value : state.set(receiver, value)), value;\n}\n\nexport function __classPrivateFieldIn(state, receiver) {\n if (receiver === null || (typeof receiver !== \"object\" && typeof receiver !== \"function\")) throw new TypeError(\"Cannot use 'in' operator on non-object\");\n return typeof state === \"function\" ? receiver === state : state.has(receiver);\n}\n\nexport function __addDisposableResource(env, value, async) {\n if (value !== null && value !== void 0) {\n if (typeof value !== \"object\" && typeof value !== \"function\") throw new TypeError(\"Object expected.\");\n var dispose, inner;\n if (async) {\n if (!Symbol.asyncDispose) throw new TypeError(\"Symbol.asyncDispose is not defined.\");\n dispose = value[Symbol.asyncDispose];\n }\n if (dispose === void 0) {\n if (!Symbol.dispose) throw new TypeError(\"Symbol.dispose is not defined.\");\n dispose = value[Symbol.dispose];\n if (async) inner = dispose;\n }\n if (typeof dispose !== \"function\") throw new TypeError(\"Object not disposable.\");\n if (inner) dispose = function() { try { inner.call(this); } catch (e) { return Promise.reject(e); } };\n env.stack.push({ value: value, dispose: dispose, async: async });\n }\n else if (async) {\n env.stack.push({ async: true });\n }\n return value;\n}\n\nvar _SuppressedError = typeof SuppressedError === \"function\" ? SuppressedError : function (error, suppressed, message) {\n var e = new Error(message);\n return e.name = \"SuppressedError\", e.error = error, e.suppressed = suppressed, e;\n};\n\nexport function __disposeResources(env) {\n function fail(e) {\n env.error = env.hasError ? new _SuppressedError(e, env.error, \"An error was suppressed during disposal.\") : e;\n env.hasError = true;\n }\n var r, s = 0;\n function next() {\n while (r = env.stack.pop()) {\n try {\n if (!r.async && s === 1) return s = 0, env.stack.push(r), Promise.resolve().then(next);\n if (r.dispose) {\n var result = r.dispose.call(r.value);\n if (r.async) return s |= 2, Promise.resolve(result).then(next, function(e) { fail(e); return next(); });\n }\n else s |= 1;\n }\n catch (e) {\n fail(e);\n }\n }\n if (s === 1) return env.hasError ? Promise.reject(env.error) : Promise.resolve();\n if (env.hasError) throw env.error;\n }\n return next();\n}\n\nexport default {\n __extends,\n __assign,\n __rest,\n __decorate,\n __param,\n __metadata,\n __awaiter,\n __generator,\n __createBinding,\n __exportStar,\n __values,\n __read,\n __spread,\n __spreadArrays,\n __spreadArray,\n __await,\n __asyncGenerator,\n __asyncDelegator,\n __asyncValues,\n __makeTemplateObject,\n __importStar,\n __importDefault,\n __classPrivateFieldGet,\n __classPrivateFieldSet,\n __classPrivateFieldIn,\n __addDisposableResource,\n __disposeResources,\n};\n", "/**\n * Returns true if the object is a function.\n * @param value The value to check\n */\nexport function isFunction(value: any): value is (...args: any[]) => any {\n return typeof value === 'function';\n}\n", "/**\n * Used to create Error subclasses until the community moves away from ES5.\n *\n * This is because compiling from TypeScript down to ES5 has issues with subclassing Errors\n * as well as other built-in types: https://github.com/Microsoft/TypeScript/issues/12123\n *\n * @param createImpl A factory function to create the actual constructor implementation. The returned\n * function should be a named function that calls `_super` internally.\n */\nexport function createErrorClass(createImpl: (_super: any) => any): T {\n const _super = (instance: any) => {\n Error.call(instance);\n instance.stack = new Error().stack;\n };\n\n const ctorFunc = createImpl(_super);\n ctorFunc.prototype = Object.create(Error.prototype);\n ctorFunc.prototype.constructor = ctorFunc;\n return ctorFunc;\n}\n", "import { createErrorClass } from './createErrorClass';\n\nexport interface UnsubscriptionError extends Error {\n readonly errors: any[];\n}\n\nexport interface UnsubscriptionErrorCtor {\n /**\n * @deprecated Internal implementation detail. Do not construct error instances.\n * Cannot be tagged as internal: https://github.com/ReactiveX/rxjs/issues/6269\n */\n new (errors: any[]): UnsubscriptionError;\n}\n\n/**\n * An error thrown when one or more errors have occurred during the\n * `unsubscribe` of a {@link Subscription}.\n */\nexport const UnsubscriptionError: UnsubscriptionErrorCtor = createErrorClass(\n (_super) =>\n function UnsubscriptionErrorImpl(this: any, errors: (Error | string)[]) {\n _super(this);\n this.message = errors\n ? `${errors.length} errors occurred during unsubscription:\n${errors.map((err, i) => `${i + 1}) ${err.toString()}`).join('\\n ')}`\n : '';\n this.name = 'UnsubscriptionError';\n this.errors = errors;\n }\n);\n", "/**\n * Removes an item from an array, mutating it.\n * @param arr The array to remove the item from\n * @param item The item to remove\n */\nexport function arrRemove(arr: T[] | undefined | null, item: T) {\n if (arr) {\n const index = arr.indexOf(item);\n 0 <= index && arr.splice(index, 1);\n }\n}\n", "import { isFunction } from './util/isFunction';\nimport { UnsubscriptionError } from './util/UnsubscriptionError';\nimport { SubscriptionLike, TeardownLogic, Unsubscribable } from './types';\nimport { arrRemove } from './util/arrRemove';\n\n/**\n * Represents a disposable resource, such as the execution of an Observable. A\n * Subscription has one important method, `unsubscribe`, that takes no argument\n * and just disposes the resource held by the subscription.\n *\n * Additionally, subscriptions may be grouped together through the `add()`\n * method, which will attach a child Subscription to the current Subscription.\n * When a Subscription is unsubscribed, all its children (and its grandchildren)\n * will be unsubscribed as well.\n */\nexport class Subscription implements SubscriptionLike {\n public static EMPTY = (() => {\n const empty = new Subscription();\n empty.closed = true;\n return empty;\n })();\n\n /**\n * A flag to indicate whether this Subscription has already been unsubscribed.\n */\n public closed = false;\n\n private _parentage: Subscription[] | Subscription | null = null;\n\n /**\n * The list of registered finalizers to execute upon unsubscription. Adding and removing from this\n * list occurs in the {@link #add} and {@link #remove} methods.\n */\n private _finalizers: Exclude[] | null = null;\n\n /**\n * @param initialTeardown A function executed first as part of the finalization\n * process that is kicked off when {@link #unsubscribe} is called.\n */\n constructor(private initialTeardown?: () => void) {}\n\n /**\n * Disposes the resources held by the subscription. May, for instance, cancel\n * an ongoing Observable execution or cancel any other type of work that\n * started when the Subscription was created.\n */\n unsubscribe(): void {\n let errors: any[] | undefined;\n\n if (!this.closed) {\n this.closed = true;\n\n // Remove this from it's parents.\n const { _parentage } = this;\n if (_parentage) {\n this._parentage = null;\n if (Array.isArray(_parentage)) {\n for (const parent of _parentage) {\n parent.remove(this);\n }\n } else {\n _parentage.remove(this);\n }\n }\n\n const { initialTeardown: initialFinalizer } = this;\n if (isFunction(initialFinalizer)) {\n try {\n initialFinalizer();\n } catch (e) {\n errors = e instanceof UnsubscriptionError ? e.errors : [e];\n }\n }\n\n const { _finalizers } = this;\n if (_finalizers) {\n this._finalizers = null;\n for (const finalizer of _finalizers) {\n try {\n execFinalizer(finalizer);\n } catch (err) {\n errors = errors ?? [];\n if (err instanceof UnsubscriptionError) {\n errors = [...errors, ...err.errors];\n } else {\n errors.push(err);\n }\n }\n }\n }\n\n if (errors) {\n throw new UnsubscriptionError(errors);\n }\n }\n }\n\n /**\n * Adds a finalizer to this subscription, so that finalization will be unsubscribed/called\n * when this subscription is unsubscribed. If this subscription is already {@link #closed},\n * because it has already been unsubscribed, then whatever finalizer is passed to it\n * will automatically be executed (unless the finalizer itself is also a closed subscription).\n *\n * Closed Subscriptions cannot be added as finalizers to any subscription. Adding a closed\n * subscription to a any subscription will result in no operation. (A noop).\n *\n * Adding a subscription to itself, or adding `null` or `undefined` will not perform any\n * operation at all. (A noop).\n *\n * `Subscription` instances that are added to this instance will automatically remove themselves\n * if they are unsubscribed. Functions and {@link Unsubscribable} objects that you wish to remove\n * will need to be removed manually with {@link #remove}\n *\n * @param teardown The finalization logic to add to this subscription.\n */\n add(teardown: TeardownLogic): void {\n // Only add the finalizer if it's not undefined\n // and don't add a subscription to itself.\n if (teardown && teardown !== this) {\n if (this.closed) {\n // If this subscription is already closed,\n // execute whatever finalizer is handed to it automatically.\n execFinalizer(teardown);\n } else {\n if (teardown instanceof Subscription) {\n // We don't add closed subscriptions, and we don't add the same subscription\n // twice. Subscription unsubscribe is idempotent.\n if (teardown.closed || teardown._hasParent(this)) {\n return;\n }\n teardown._addParent(this);\n }\n (this._finalizers = this._finalizers ?? []).push(teardown);\n }\n }\n }\n\n /**\n * Checks to see if a this subscription already has a particular parent.\n * This will signal that this subscription has already been added to the parent in question.\n * @param parent the parent to check for\n */\n private _hasParent(parent: Subscription) {\n const { _parentage } = this;\n return _parentage === parent || (Array.isArray(_parentage) && _parentage.includes(parent));\n }\n\n /**\n * Adds a parent to this subscription so it can be removed from the parent if it\n * unsubscribes on it's own.\n *\n * NOTE: THIS ASSUMES THAT {@link _hasParent} HAS ALREADY BEEN CHECKED.\n * @param parent The parent subscription to add\n */\n private _addParent(parent: Subscription) {\n const { _parentage } = this;\n this._parentage = Array.isArray(_parentage) ? (_parentage.push(parent), _parentage) : _parentage ? [_parentage, parent] : parent;\n }\n\n /**\n * Called on a child when it is removed via {@link #remove}.\n * @param parent The parent to remove\n */\n private _removeParent(parent: Subscription) {\n const { _parentage } = this;\n if (_parentage === parent) {\n this._parentage = null;\n } else if (Array.isArray(_parentage)) {\n arrRemove(_parentage, parent);\n }\n }\n\n /**\n * Removes a finalizer from this subscription that was previously added with the {@link #add} method.\n *\n * Note that `Subscription` instances, when unsubscribed, will automatically remove themselves\n * from every other `Subscription` they have been added to. This means that using the `remove` method\n * is not a common thing and should be used thoughtfully.\n *\n * If you add the same finalizer instance of a function or an unsubscribable object to a `Subscription` instance\n * more than once, you will need to call `remove` the same number of times to remove all instances.\n *\n * All finalizer instances are removed to free up memory upon unsubscription.\n *\n * @param teardown The finalizer to remove from this subscription\n */\n remove(teardown: Exclude): void {\n const { _finalizers } = this;\n _finalizers && arrRemove(_finalizers, teardown);\n\n if (teardown instanceof Subscription) {\n teardown._removeParent(this);\n }\n }\n}\n\nexport const EMPTY_SUBSCRIPTION = Subscription.EMPTY;\n\nexport function isSubscription(value: any): value is Subscription {\n return (\n value instanceof Subscription ||\n (value && 'closed' in value && isFunction(value.remove) && isFunction(value.add) && isFunction(value.unsubscribe))\n );\n}\n\nfunction execFinalizer(finalizer: Unsubscribable | (() => void)) {\n if (isFunction(finalizer)) {\n finalizer();\n } else {\n finalizer.unsubscribe();\n }\n}\n", "import { Subscriber } from './Subscriber';\nimport { ObservableNotification } from './types';\n\n/**\n * The {@link GlobalConfig} object for RxJS. It is used to configure things\n * like how to react on unhandled errors.\n */\nexport const config: GlobalConfig = {\n onUnhandledError: null,\n onStoppedNotification: null,\n Promise: undefined,\n useDeprecatedSynchronousErrorHandling: false,\n useDeprecatedNextContext: false,\n};\n\n/**\n * The global configuration object for RxJS, used to configure things\n * like how to react on unhandled errors. Accessible via {@link config}\n * object.\n */\nexport interface GlobalConfig {\n /**\n * A registration point for unhandled errors from RxJS. These are errors that\n * cannot were not handled by consuming code in the usual subscription path. For\n * example, if you have this configured, and you subscribe to an observable without\n * providing an error handler, errors from that subscription will end up here. This\n * will _always_ be called asynchronously on another job in the runtime. This is because\n * we do not want errors thrown in this user-configured handler to interfere with the\n * behavior of the library.\n */\n onUnhandledError: ((err: any) => void) | null;\n\n /**\n * A registration point for notifications that cannot be sent to subscribers because they\n * have completed, errored or have been explicitly unsubscribed. By default, next, complete\n * and error notifications sent to stopped subscribers are noops. However, sometimes callers\n * might want a different behavior. For example, with sources that attempt to report errors\n * to stopped subscribers, a caller can configure RxJS to throw an unhandled error instead.\n * This will _always_ be called asynchronously on another job in the runtime. This is because\n * we do not want errors thrown in this user-configured handler to interfere with the\n * behavior of the library.\n */\n onStoppedNotification: ((notification: ObservableNotification, subscriber: Subscriber) => void) | null;\n\n /**\n * The promise constructor used by default for {@link Observable#toPromise toPromise} and {@link Observable#forEach forEach}\n * methods.\n *\n * @deprecated As of version 8, RxJS will no longer support this sort of injection of a\n * Promise constructor. If you need a Promise implementation other than native promises,\n * please polyfill/patch Promise as you see appropriate. Will be removed in v8.\n */\n Promise?: PromiseConstructorLike;\n\n /**\n * If true, turns on synchronous error rethrowing, which is a deprecated behavior\n * in v6 and higher. This behavior enables bad patterns like wrapping a subscribe\n * call in a try/catch block. It also enables producer interference, a nasty bug\n * where a multicast can be broken for all observers by a downstream consumer with\n * an unhandled error. DO NOT USE THIS FLAG UNLESS IT'S NEEDED TO BUY TIME\n * FOR MIGRATION REASONS.\n *\n * @deprecated As of version 8, RxJS will no longer support synchronous throwing\n * of unhandled errors. All errors will be thrown on a separate call stack to prevent bad\n * behaviors described above. Will be removed in v8.\n */\n useDeprecatedSynchronousErrorHandling: boolean;\n\n /**\n * If true, enables an as-of-yet undocumented feature from v5: The ability to access\n * `unsubscribe()` via `this` context in `next` functions created in observers passed\n * to `subscribe`.\n *\n * This is being removed because the performance was severely problematic, and it could also cause\n * issues when types other than POJOs are passed to subscribe as subscribers, as they will likely have\n * their `this` context overwritten.\n *\n * @deprecated As of version 8, RxJS will no longer support altering the\n * context of next functions provided as part of an observer to Subscribe. Instead,\n * you will have access to a subscription or a signal or token that will allow you to do things like\n * unsubscribe and test closed status. Will be removed in v8.\n */\n useDeprecatedNextContext: boolean;\n}\n", "import type { TimerHandle } from './timerHandle';\ntype SetTimeoutFunction = (handler: () => void, timeout?: number, ...args: any[]) => TimerHandle;\ntype ClearTimeoutFunction = (handle: TimerHandle) => void;\n\ninterface TimeoutProvider {\n setTimeout: SetTimeoutFunction;\n clearTimeout: ClearTimeoutFunction;\n delegate:\n | {\n setTimeout: SetTimeoutFunction;\n clearTimeout: ClearTimeoutFunction;\n }\n | undefined;\n}\n\nexport const timeoutProvider: TimeoutProvider = {\n // When accessing the delegate, use the variable rather than `this` so that\n // the functions can be called without being bound to the provider.\n setTimeout(handler: () => void, timeout?: number, ...args) {\n const { delegate } = timeoutProvider;\n if (delegate?.setTimeout) {\n return delegate.setTimeout(handler, timeout, ...args);\n }\n return setTimeout(handler, timeout, ...args);\n },\n clearTimeout(handle) {\n const { delegate } = timeoutProvider;\n return (delegate?.clearTimeout || clearTimeout)(handle as any);\n },\n delegate: undefined,\n};\n", "import { config } from '../config';\nimport { timeoutProvider } from '../scheduler/timeoutProvider';\n\n/**\n * Handles an error on another job either with the user-configured {@link onUnhandledError},\n * or by throwing it on that new job so it can be picked up by `window.onerror`, `process.on('error')`, etc.\n *\n * This should be called whenever there is an error that is out-of-band with the subscription\n * or when an error hits a terminal boundary of the subscription and no error handler was provided.\n *\n * @param err the error to report\n */\nexport function reportUnhandledError(err: any) {\n timeoutProvider.setTimeout(() => {\n const { onUnhandledError } = config;\n if (onUnhandledError) {\n // Execute the user-configured error handler.\n onUnhandledError(err);\n } else {\n // Throw so it is picked up by the runtime's uncaught error mechanism.\n throw err;\n }\n });\n}\n", "/* tslint:disable:no-empty */\nexport function noop() { }\n", "import { CompleteNotification, NextNotification, ErrorNotification } from './types';\n\n/**\n * A completion object optimized for memory use and created to be the\n * same \"shape\" as other notifications in v8.\n * @internal\n */\nexport const COMPLETE_NOTIFICATION = (() => createNotification('C', undefined, undefined) as CompleteNotification)();\n\n/**\n * Internal use only. Creates an optimized error notification that is the same \"shape\"\n * as other notifications.\n * @internal\n */\nexport function errorNotification(error: any): ErrorNotification {\n return createNotification('E', undefined, error) as any;\n}\n\n/**\n * Internal use only. Creates an optimized next notification that is the same \"shape\"\n * as other notifications.\n * @internal\n */\nexport function nextNotification(value: T) {\n return createNotification('N', value, undefined) as NextNotification;\n}\n\n/**\n * Ensures that all notifications created internally have the same \"shape\" in v8.\n *\n * TODO: This is only exported to support a crazy legacy test in `groupBy`.\n * @internal\n */\nexport function createNotification(kind: 'N' | 'E' | 'C', value: any, error: any) {\n return {\n kind,\n value,\n error,\n };\n}\n", "import { config } from '../config';\n\nlet context: { errorThrown: boolean; error: any } | null = null;\n\n/**\n * Handles dealing with errors for super-gross mode. Creates a context, in which\n * any synchronously thrown errors will be passed to {@link captureError}. Which\n * will record the error such that it will be rethrown after the call back is complete.\n * TODO: Remove in v8\n * @param cb An immediately executed function.\n */\nexport function errorContext(cb: () => void) {\n if (config.useDeprecatedSynchronousErrorHandling) {\n const isRoot = !context;\n if (isRoot) {\n context = { errorThrown: false, error: null };\n }\n cb();\n if (isRoot) {\n const { errorThrown, error } = context!;\n context = null;\n if (errorThrown) {\n throw error;\n }\n }\n } else {\n // This is the general non-deprecated path for everyone that\n // isn't crazy enough to use super-gross mode (useDeprecatedSynchronousErrorHandling)\n cb();\n }\n}\n\n/**\n * Captures errors only in super-gross mode.\n * @param err the error to capture\n */\nexport function captureError(err: any) {\n if (config.useDeprecatedSynchronousErrorHandling && context) {\n context.errorThrown = true;\n context.error = err;\n }\n}\n", "import { isFunction } from './util/isFunction';\nimport { Observer, ObservableNotification } from './types';\nimport { isSubscription, Subscription } from './Subscription';\nimport { config } from './config';\nimport { reportUnhandledError } from './util/reportUnhandledError';\nimport { noop } from './util/noop';\nimport { nextNotification, errorNotification, COMPLETE_NOTIFICATION } from './NotificationFactories';\nimport { timeoutProvider } from './scheduler/timeoutProvider';\nimport { captureError } from './util/errorContext';\n\n/**\n * Implements the {@link Observer} interface and extends the\n * {@link Subscription} class. While the {@link Observer} is the public API for\n * consuming the values of an {@link Observable}, all Observers get converted to\n * a Subscriber, in order to provide Subscription-like capabilities such as\n * `unsubscribe`. Subscriber is a common type in RxJS, and crucial for\n * implementing operators, but it is rarely used as a public API.\n */\nexport class Subscriber extends Subscription implements Observer {\n /**\n * A static factory for a Subscriber, given a (potentially partial) definition\n * of an Observer.\n * @param next The `next` callback of an Observer.\n * @param error The `error` callback of an\n * Observer.\n * @param complete The `complete` callback of an\n * Observer.\n * @return A Subscriber wrapping the (partially defined)\n * Observer represented by the given arguments.\n * @deprecated Do not use. Will be removed in v8. There is no replacement for this\n * method, and there is no reason to be creating instances of `Subscriber` directly.\n * If you have a specific use case, please file an issue.\n */\n static create(next?: (x?: T) => void, error?: (e?: any) => void, complete?: () => void): Subscriber {\n return new SafeSubscriber(next, error, complete);\n }\n\n /** @deprecated Internal implementation detail, do not use directly. Will be made internal in v8. */\n protected isStopped: boolean = false;\n /** @deprecated Internal implementation detail, do not use directly. Will be made internal in v8. */\n protected destination: Subscriber | Observer; // this `any` is the escape hatch to erase extra type param (e.g. R)\n\n /**\n * @deprecated Internal implementation detail, do not use directly. Will be made internal in v8.\n * There is no reason to directly create an instance of Subscriber. This type is exported for typings reasons.\n */\n constructor(destination?: Subscriber | Observer) {\n super();\n if (destination) {\n this.destination = destination;\n // Automatically chain subscriptions together here.\n // if destination is a Subscription, then it is a Subscriber.\n if (isSubscription(destination)) {\n destination.add(this);\n }\n } else {\n this.destination = EMPTY_OBSERVER;\n }\n }\n\n /**\n * The {@link Observer} callback to receive notifications of type `next` from\n * the Observable, with a value. The Observable may call this method 0 or more\n * times.\n * @param value The `next` value.\n */\n next(value: T): void {\n if (this.isStopped) {\n handleStoppedNotification(nextNotification(value), this);\n } else {\n this._next(value!);\n }\n }\n\n /**\n * The {@link Observer} callback to receive notifications of type `error` from\n * the Observable, with an attached `Error`. Notifies the Observer that\n * the Observable has experienced an error condition.\n * @param err The `error` exception.\n */\n error(err?: any): void {\n if (this.isStopped) {\n handleStoppedNotification(errorNotification(err), this);\n } else {\n this.isStopped = true;\n this._error(err);\n }\n }\n\n /**\n * The {@link Observer} callback to receive a valueless notification of type\n * `complete` from the Observable. Notifies the Observer that the Observable\n * has finished sending push-based notifications.\n */\n complete(): void {\n if (this.isStopped) {\n handleStoppedNotification(COMPLETE_NOTIFICATION, this);\n } else {\n this.isStopped = true;\n this._complete();\n }\n }\n\n unsubscribe(): void {\n if (!this.closed) {\n this.isStopped = true;\n super.unsubscribe();\n this.destination = null!;\n }\n }\n\n protected _next(value: T): void {\n this.destination.next(value);\n }\n\n protected _error(err: any): void {\n try {\n this.destination.error(err);\n } finally {\n this.unsubscribe();\n }\n }\n\n protected _complete(): void {\n try {\n this.destination.complete();\n } finally {\n this.unsubscribe();\n }\n }\n}\n\n/**\n * This bind is captured here because we want to be able to have\n * compatibility with monoid libraries that tend to use a method named\n * `bind`. In particular, a library called Monio requires this.\n */\nconst _bind = Function.prototype.bind;\n\nfunction bind any>(fn: Fn, thisArg: any): Fn {\n return _bind.call(fn, thisArg);\n}\n\n/**\n * Internal optimization only, DO NOT EXPOSE.\n * @internal\n */\nclass ConsumerObserver implements Observer {\n constructor(private partialObserver: Partial>) {}\n\n next(value: T): void {\n const { partialObserver } = this;\n if (partialObserver.next) {\n try {\n partialObserver.next(value);\n } catch (error) {\n handleUnhandledError(error);\n }\n }\n }\n\n error(err: any): void {\n const { partialObserver } = this;\n if (partialObserver.error) {\n try {\n partialObserver.error(err);\n } catch (error) {\n handleUnhandledError(error);\n }\n } else {\n handleUnhandledError(err);\n }\n }\n\n complete(): void {\n const { partialObserver } = this;\n if (partialObserver.complete) {\n try {\n partialObserver.complete();\n } catch (error) {\n handleUnhandledError(error);\n }\n }\n }\n}\n\nexport class SafeSubscriber extends Subscriber {\n constructor(\n observerOrNext?: Partial> | ((value: T) => void) | null,\n error?: ((e?: any) => void) | null,\n complete?: (() => void) | null\n ) {\n super();\n\n let partialObserver: Partial>;\n if (isFunction(observerOrNext) || !observerOrNext) {\n // The first argument is a function, not an observer. The next\n // two arguments *could* be observers, or they could be empty.\n partialObserver = {\n next: (observerOrNext ?? undefined) as ((value: T) => void) | undefined,\n error: error ?? undefined,\n complete: complete ?? undefined,\n };\n } else {\n // The first argument is a partial observer.\n let context: any;\n if (this && config.useDeprecatedNextContext) {\n // This is a deprecated path that made `this.unsubscribe()` available in\n // next handler functions passed to subscribe. This only exists behind a flag\n // now, as it is *very* slow.\n context = Object.create(observerOrNext);\n context.unsubscribe = () => this.unsubscribe();\n partialObserver = {\n next: observerOrNext.next && bind(observerOrNext.next, context),\n error: observerOrNext.error && bind(observerOrNext.error, context),\n complete: observerOrNext.complete && bind(observerOrNext.complete, context),\n };\n } else {\n // The \"normal\" path. Just use the partial observer directly.\n partialObserver = observerOrNext;\n }\n }\n\n // Wrap the partial observer to ensure it's a full observer, and\n // make sure proper error handling is accounted for.\n this.destination = new ConsumerObserver(partialObserver);\n }\n}\n\nfunction handleUnhandledError(error: any) {\n if (config.useDeprecatedSynchronousErrorHandling) {\n captureError(error);\n } else {\n // Ideal path, we report this as an unhandled error,\n // which is thrown on a new call stack.\n reportUnhandledError(error);\n }\n}\n\n/**\n * An error handler used when no error handler was supplied\n * to the SafeSubscriber -- meaning no error handler was supplied\n * do the `subscribe` call on our observable.\n * @param err The error to handle\n */\nfunction defaultErrorHandler(err: any) {\n throw err;\n}\n\n/**\n * A handler for notifications that cannot be sent to a stopped subscriber.\n * @param notification The notification being sent.\n * @param subscriber The stopped subscriber.\n */\nfunction handleStoppedNotification(notification: ObservableNotification, subscriber: Subscriber) {\n const { onStoppedNotification } = config;\n onStoppedNotification && timeoutProvider.setTimeout(() => onStoppedNotification(notification, subscriber));\n}\n\n/**\n * The observer used as a stub for subscriptions where the user did not\n * pass any arguments to `subscribe`. Comes with the default error handling\n * behavior.\n */\nexport const EMPTY_OBSERVER: Readonly> & { closed: true } = {\n closed: true,\n next: noop,\n error: defaultErrorHandler,\n complete: noop,\n};\n", "/**\n * Symbol.observable or a string \"@@observable\". Used for interop\n *\n * @deprecated We will no longer be exporting this symbol in upcoming versions of RxJS.\n * Instead polyfill and use Symbol.observable directly *or* use https://www.npmjs.com/package/symbol-observable\n */\nexport const observable: string | symbol = (() => (typeof Symbol === 'function' && Symbol.observable) || '@@observable')();\n", "/**\n * This function takes one parameter and just returns it. Simply put,\n * this is like `(x: T): T => x`.\n *\n * ## Examples\n *\n * This is useful in some cases when using things like `mergeMap`\n *\n * ```ts\n * import { interval, take, map, range, mergeMap, identity } from 'rxjs';\n *\n * const source$ = interval(1000).pipe(take(5));\n *\n * const result$ = source$.pipe(\n * map(i => range(i)),\n * mergeMap(identity) // same as mergeMap(x => x)\n * );\n *\n * result$.subscribe({\n * next: console.log\n * });\n * ```\n *\n * Or when you want to selectively apply an operator\n *\n * ```ts\n * import { interval, take, identity } from 'rxjs';\n *\n * const shouldLimit = () => Math.random() < 0.5;\n *\n * const source$ = interval(1000);\n *\n * const result$ = source$.pipe(shouldLimit() ? take(5) : identity);\n *\n * result$.subscribe({\n * next: console.log\n * });\n * ```\n *\n * @param x Any value that is returned by this function\n * @returns The value passed as the first parameter to this function\n */\nexport function identity(x: T): T {\n return x;\n}\n", "import { identity } from './identity';\nimport { UnaryFunction } from '../types';\n\nexport function pipe(): typeof identity;\nexport function pipe(fn1: UnaryFunction): UnaryFunction;\nexport function pipe(fn1: UnaryFunction, fn2: UnaryFunction): UnaryFunction;\nexport function pipe(fn1: UnaryFunction, fn2: UnaryFunction, fn3: UnaryFunction): UnaryFunction;\nexport function pipe(\n fn1: UnaryFunction,\n fn2: UnaryFunction,\n fn3: UnaryFunction,\n fn4: UnaryFunction\n): UnaryFunction;\nexport function pipe(\n fn1: UnaryFunction,\n fn2: UnaryFunction,\n fn3: UnaryFunction,\n fn4: UnaryFunction,\n fn5: UnaryFunction\n): UnaryFunction;\nexport function pipe(\n fn1: UnaryFunction,\n fn2: UnaryFunction,\n fn3: UnaryFunction,\n fn4: UnaryFunction,\n fn5: UnaryFunction,\n fn6: UnaryFunction\n): UnaryFunction;\nexport function pipe(\n fn1: UnaryFunction,\n fn2: UnaryFunction,\n fn3: UnaryFunction,\n fn4: UnaryFunction,\n fn5: UnaryFunction,\n fn6: UnaryFunction,\n fn7: UnaryFunction\n): UnaryFunction;\nexport function pipe(\n fn1: UnaryFunction,\n fn2: UnaryFunction,\n fn3: UnaryFunction,\n fn4: UnaryFunction,\n fn5: UnaryFunction,\n fn6: UnaryFunction,\n fn7: UnaryFunction,\n fn8: UnaryFunction\n): UnaryFunction;\nexport function pipe(\n fn1: UnaryFunction,\n fn2: UnaryFunction,\n fn3: UnaryFunction,\n fn4: UnaryFunction,\n fn5: UnaryFunction,\n fn6: UnaryFunction,\n fn7: UnaryFunction,\n fn8: UnaryFunction,\n fn9: UnaryFunction\n): UnaryFunction;\nexport function pipe(\n fn1: UnaryFunction,\n fn2: UnaryFunction,\n fn3: UnaryFunction,\n fn4: UnaryFunction,\n fn5: UnaryFunction,\n fn6: UnaryFunction,\n fn7: UnaryFunction,\n fn8: UnaryFunction,\n fn9: UnaryFunction,\n ...fns: UnaryFunction[]\n): UnaryFunction;\n\n/**\n * pipe() can be called on one or more functions, each of which can take one argument (\"UnaryFunction\")\n * and uses it to return a value.\n * It returns a function that takes one argument, passes it to the first UnaryFunction, and then\n * passes the result to the next one, passes that result to the next one, and so on. \n */\nexport function pipe(...fns: Array>): UnaryFunction {\n return pipeFromArray(fns);\n}\n\n/** @internal */\nexport function pipeFromArray(fns: Array>): UnaryFunction {\n if (fns.length === 0) {\n return identity as UnaryFunction;\n }\n\n if (fns.length === 1) {\n return fns[0];\n }\n\n return function piped(input: T): R {\n return fns.reduce((prev: any, fn: UnaryFunction) => fn(prev), input as any);\n };\n}\n", "import { Operator } from './Operator';\nimport { SafeSubscriber, Subscriber } from './Subscriber';\nimport { isSubscription, Subscription } from './Subscription';\nimport { TeardownLogic, OperatorFunction, Subscribable, Observer } from './types';\nimport { observable as Symbol_observable } from './symbol/observable';\nimport { pipeFromArray } from './util/pipe';\nimport { config } from './config';\nimport { isFunction } from './util/isFunction';\nimport { errorContext } from './util/errorContext';\n\n/**\n * A representation of any set of values over any amount of time. This is the most basic building block\n * of RxJS.\n */\nexport class Observable implements Subscribable {\n /**\n * @deprecated Internal implementation detail, do not use directly. Will be made internal in v8.\n */\n source: Observable | undefined;\n\n /**\n * @deprecated Internal implementation detail, do not use directly. Will be made internal in v8.\n */\n operator: Operator | undefined;\n\n /**\n * @param subscribe The function that is called when the Observable is\n * initially subscribed to. This function is given a Subscriber, to which new values\n * can be `next`ed, or an `error` method can be called to raise an error, or\n * `complete` can be called to notify of a successful completion.\n */\n constructor(subscribe?: (this: Observable, subscriber: Subscriber) => TeardownLogic) {\n if (subscribe) {\n this._subscribe = subscribe;\n }\n }\n\n // HACK: Since TypeScript inherits static properties too, we have to\n // fight against TypeScript here so Subject can have a different static create signature\n /**\n * Creates a new Observable by calling the Observable constructor\n * @param subscribe the subscriber function to be passed to the Observable constructor\n * @return A new observable.\n * @deprecated Use `new Observable()` instead. Will be removed in v8.\n */\n static create: (...args: any[]) => any = (subscribe?: (subscriber: Subscriber) => TeardownLogic) => {\n return new Observable(subscribe);\n };\n\n /**\n * Creates a new Observable, with this Observable instance as the source, and the passed\n * operator defined as the new observable's operator.\n * @param operator the operator defining the operation to take on the observable\n * @return A new observable with the Operator applied.\n * @deprecated Internal implementation detail, do not use directly. Will be made internal in v8.\n * If you have implemented an operator using `lift`, it is recommended that you create an\n * operator by simply returning `new Observable()` directly. See \"Creating new operators from\n * scratch\" section here: https://rxjs.dev/guide/operators\n */\n lift(operator?: Operator): Observable {\n const observable = new Observable();\n observable.source = this;\n observable.operator = operator;\n return observable;\n }\n\n subscribe(observerOrNext?: Partial> | ((value: T) => void)): Subscription;\n /** @deprecated Instead of passing separate callback arguments, use an observer argument. Signatures taking separate callback arguments will be removed in v8. Details: https://rxjs.dev/deprecations/subscribe-arguments */\n subscribe(next?: ((value: T) => void) | null, error?: ((error: any) => void) | null, complete?: (() => void) | null): Subscription;\n /**\n * Invokes an execution of an Observable and registers Observer handlers for notifications it will emit.\n *\n * Use it when you have all these Observables, but still nothing is happening.\n *\n * `subscribe` is not a regular operator, but a method that calls Observable's internal `subscribe` function. It\n * might be for example a function that you passed to Observable's constructor, but most of the time it is\n * a library implementation, which defines what will be emitted by an Observable, and when it be will emitted. This means\n * that calling `subscribe` is actually the moment when Observable starts its work, not when it is created, as it is often\n * the thought.\n *\n * Apart from starting the execution of an Observable, this method allows you to listen for values\n * that an Observable emits, as well as for when it completes or errors. You can achieve this in two\n * of the following ways.\n *\n * The first way is creating an object that implements {@link Observer} interface. It should have methods\n * defined by that interface, but note that it should be just a regular JavaScript object, which you can create\n * yourself in any way you want (ES6 class, classic function constructor, object literal etc.). In particular, do\n * not attempt to use any RxJS implementation details to create Observers - you don't need them. Remember also\n * that your object does not have to implement all methods. If you find yourself creating a method that doesn't\n * do anything, you can simply omit it. Note however, if the `error` method is not provided and an error happens,\n * it will be thrown asynchronously. Errors thrown asynchronously cannot be caught using `try`/`catch`. Instead,\n * use the {@link onUnhandledError} configuration option or use a runtime handler (like `window.onerror` or\n * `process.on('error)`) to be notified of unhandled errors. Because of this, it's recommended that you provide\n * an `error` method to avoid missing thrown errors.\n *\n * The second way is to give up on Observer object altogether and simply provide callback functions in place of its methods.\n * This means you can provide three functions as arguments to `subscribe`, where the first function is equivalent\n * of a `next` method, the second of an `error` method and the third of a `complete` method. Just as in case of an Observer,\n * if you do not need to listen for something, you can omit a function by passing `undefined` or `null`,\n * since `subscribe` recognizes these functions by where they were placed in function call. When it comes\n * to the `error` function, as with an Observer, if not provided, errors emitted by an Observable will be thrown asynchronously.\n *\n * You can, however, subscribe with no parameters at all. This may be the case where you're not interested in terminal events\n * and you also handled emissions internally by using operators (e.g. using `tap`).\n *\n * Whichever style of calling `subscribe` you use, in both cases it returns a Subscription object.\n * This object allows you to call `unsubscribe` on it, which in turn will stop the work that an Observable does and will clean\n * up all resources that an Observable used. Note that cancelling a subscription will not call `complete` callback\n * provided to `subscribe` function, which is reserved for a regular completion signal that comes from an Observable.\n *\n * Remember that callbacks provided to `subscribe` are not guaranteed to be called asynchronously.\n * It is an Observable itself that decides when these functions will be called. For example {@link of}\n * by default emits all its values synchronously. Always check documentation for how given Observable\n * will behave when subscribed and if its default behavior can be modified with a `scheduler`.\n *\n * #### Examples\n *\n * Subscribe with an {@link guide/observer Observer}\n *\n * ```ts\n * import { of } from 'rxjs';\n *\n * const sumObserver = {\n * sum: 0,\n * next(value) {\n * console.log('Adding: ' + value);\n * this.sum = this.sum + value;\n * },\n * error() {\n * // We actually could just remove this method,\n * // since we do not really care about errors right now.\n * },\n * complete() {\n * console.log('Sum equals: ' + this.sum);\n * }\n * };\n *\n * of(1, 2, 3) // Synchronously emits 1, 2, 3 and then completes.\n * .subscribe(sumObserver);\n *\n * // Logs:\n * // 'Adding: 1'\n * // 'Adding: 2'\n * // 'Adding: 3'\n * // 'Sum equals: 6'\n * ```\n *\n * Subscribe with functions ({@link deprecations/subscribe-arguments deprecated})\n *\n * ```ts\n * import { of } from 'rxjs'\n *\n * let sum = 0;\n *\n * of(1, 2, 3).subscribe(\n * value => {\n * console.log('Adding: ' + value);\n * sum = sum + value;\n * },\n * undefined,\n * () => console.log('Sum equals: ' + sum)\n * );\n *\n * // Logs:\n * // 'Adding: 1'\n * // 'Adding: 2'\n * // 'Adding: 3'\n * // 'Sum equals: 6'\n * ```\n *\n * Cancel a subscription\n *\n * ```ts\n * import { interval } from 'rxjs';\n *\n * const subscription = interval(1000).subscribe({\n * next(num) {\n * console.log(num)\n * },\n * complete() {\n * // Will not be called, even when cancelling subscription.\n * console.log('completed!');\n * }\n * });\n *\n * setTimeout(() => {\n * subscription.unsubscribe();\n * console.log('unsubscribed!');\n * }, 2500);\n *\n * // Logs:\n * // 0 after 1s\n * // 1 after 2s\n * // 'unsubscribed!' after 2.5s\n * ```\n *\n * @param observerOrNext Either an {@link Observer} with some or all callback methods,\n * or the `next` handler that is called for each value emitted from the subscribed Observable.\n * @param error A handler for a terminal event resulting from an error. If no error handler is provided,\n * the error will be thrown asynchronously as unhandled.\n * @param complete A handler for a terminal event resulting from successful completion.\n * @return A subscription reference to the registered handlers.\n */\n subscribe(\n observerOrNext?: Partial> | ((value: T) => void) | null,\n error?: ((error: any) => void) | null,\n complete?: (() => void) | null\n ): Subscription {\n const subscriber = isSubscriber(observerOrNext) ? observerOrNext : new SafeSubscriber(observerOrNext, error, complete);\n\n errorContext(() => {\n const { operator, source } = this;\n subscriber.add(\n operator\n ? // We're dealing with a subscription in the\n // operator chain to one of our lifted operators.\n operator.call(subscriber, source)\n : source\n ? // If `source` has a value, but `operator` does not, something that\n // had intimate knowledge of our API, like our `Subject`, must have\n // set it. We're going to just call `_subscribe` directly.\n this._subscribe(subscriber)\n : // In all other cases, we're likely wrapping a user-provided initializer\n // function, so we need to catch errors and handle them appropriately.\n this._trySubscribe(subscriber)\n );\n });\n\n return subscriber;\n }\n\n /** @internal */\n protected _trySubscribe(sink: Subscriber): TeardownLogic {\n try {\n return this._subscribe(sink);\n } catch (err) {\n // We don't need to return anything in this case,\n // because it's just going to try to `add()` to a subscription\n // above.\n sink.error(err);\n }\n }\n\n /**\n * Used as a NON-CANCELLABLE means of subscribing to an observable, for use with\n * APIs that expect promises, like `async/await`. You cannot unsubscribe from this.\n *\n * **WARNING**: Only use this with observables you *know* will complete. If the source\n * observable does not complete, you will end up with a promise that is hung up, and\n * potentially all of the state of an async function hanging out in memory. To avoid\n * this situation, look into adding something like {@link timeout}, {@link take},\n * {@link takeWhile}, or {@link takeUntil} amongst others.\n *\n * #### Example\n *\n * ```ts\n * import { interval, take } from 'rxjs';\n *\n * const source$ = interval(1000).pipe(take(4));\n *\n * async function getTotal() {\n * let total = 0;\n *\n * await source$.forEach(value => {\n * total += value;\n * console.log('observable -> ' + value);\n * });\n *\n * return total;\n * }\n *\n * getTotal().then(\n * total => console.log('Total: ' + total)\n * );\n *\n * // Expected:\n * // 'observable -> 0'\n * // 'observable -> 1'\n * // 'observable -> 2'\n * // 'observable -> 3'\n * // 'Total: 6'\n * ```\n *\n * @param next A handler for each value emitted by the observable.\n * @return A promise that either resolves on observable completion or\n * rejects with the handled error.\n */\n forEach(next: (value: T) => void): Promise;\n\n /**\n * @param next a handler for each value emitted by the observable\n * @param promiseCtor a constructor function used to instantiate the Promise\n * @return a promise that either resolves on observable completion or\n * rejects with the handled error\n * @deprecated Passing a Promise constructor will no longer be available\n * in upcoming versions of RxJS. This is because it adds weight to the library, for very\n * little benefit. If you need this functionality, it is recommended that you either\n * polyfill Promise, or you create an adapter to convert the returned native promise\n * to whatever promise implementation you wanted. Will be removed in v8.\n */\n forEach(next: (value: T) => void, promiseCtor: PromiseConstructorLike): Promise;\n\n forEach(next: (value: T) => void, promiseCtor?: PromiseConstructorLike): Promise {\n promiseCtor = getPromiseCtor(promiseCtor);\n\n return new promiseCtor((resolve, reject) => {\n const subscriber = new SafeSubscriber({\n next: (value) => {\n try {\n next(value);\n } catch (err) {\n reject(err);\n subscriber.unsubscribe();\n }\n },\n error: reject,\n complete: resolve,\n });\n this.subscribe(subscriber);\n }) as Promise;\n }\n\n /** @internal */\n protected _subscribe(subscriber: Subscriber): TeardownLogic {\n return this.source?.subscribe(subscriber);\n }\n\n /**\n * An interop point defined by the es7-observable spec https://github.com/zenparsing/es-observable\n * @return This instance of the observable.\n */\n [Symbol_observable]() {\n return this;\n }\n\n /* tslint:disable:max-line-length */\n pipe(): Observable;\n pipe(op1: OperatorFunction): Observable;\n pipe(op1: OperatorFunction, op2: OperatorFunction): Observable;\n pipe(op1: OperatorFunction, op2: OperatorFunction, op3: OperatorFunction): Observable;\n pipe(\n op1: OperatorFunction,\n op2: OperatorFunction,\n op3: OperatorFunction,\n op4: OperatorFunction\n ): Observable;\n pipe(\n op1: OperatorFunction,\n op2: OperatorFunction,\n op3: OperatorFunction,\n op4: OperatorFunction,\n op5: OperatorFunction\n ): Observable;\n pipe(\n op1: OperatorFunction,\n op2: OperatorFunction,\n op3: OperatorFunction,\n op4: OperatorFunction,\n op5: OperatorFunction,\n op6: OperatorFunction\n ): Observable;\n pipe(\n op1: OperatorFunction,\n op2: OperatorFunction,\n op3: OperatorFunction,\n op4: OperatorFunction,\n op5: OperatorFunction,\n op6: OperatorFunction,\n op7: OperatorFunction\n ): Observable;\n pipe(\n op1: OperatorFunction,\n op2: OperatorFunction,\n op3: OperatorFunction,\n op4: OperatorFunction,\n op5: OperatorFunction,\n op6: OperatorFunction,\n op7: OperatorFunction,\n op8: OperatorFunction\n ): Observable;\n pipe(\n op1: OperatorFunction,\n op2: OperatorFunction,\n op3: OperatorFunction,\n op4: OperatorFunction,\n op5: OperatorFunction,\n op6: OperatorFunction,\n op7: OperatorFunction,\n op8: OperatorFunction,\n op9: OperatorFunction\n ): Observable;\n pipe(\n op1: OperatorFunction,\n op2: OperatorFunction,\n op3: OperatorFunction,\n op4: OperatorFunction,\n op5: OperatorFunction,\n op6: OperatorFunction,\n op7: OperatorFunction,\n op8: OperatorFunction,\n op9: OperatorFunction,\n ...operations: OperatorFunction[]\n ): Observable;\n /* tslint:enable:max-line-length */\n\n /**\n * Used to stitch together functional operators into a chain.\n *\n * ## Example\n *\n * ```ts\n * import { interval, filter, map, scan } from 'rxjs';\n *\n * interval(1000)\n * .pipe(\n * filter(x => x % 2 === 0),\n * map(x => x + x),\n * scan((acc, x) => acc + x)\n * )\n * .subscribe(x => console.log(x));\n * ```\n *\n * @return The Observable result of all the operators having been called\n * in the order they were passed in.\n */\n pipe(...operations: OperatorFunction[]): Observable {\n return pipeFromArray(operations)(this);\n }\n\n /* tslint:disable:max-line-length */\n /** @deprecated Replaced with {@link firstValueFrom} and {@link lastValueFrom}. Will be removed in v8. Details: https://rxjs.dev/deprecations/to-promise */\n toPromise(): Promise;\n /** @deprecated Replaced with {@link firstValueFrom} and {@link lastValueFrom}. Will be removed in v8. Details: https://rxjs.dev/deprecations/to-promise */\n toPromise(PromiseCtor: typeof Promise): Promise;\n /** @deprecated Replaced with {@link firstValueFrom} and {@link lastValueFrom}. Will be removed in v8. Details: https://rxjs.dev/deprecations/to-promise */\n toPromise(PromiseCtor: PromiseConstructorLike): Promise;\n /* tslint:enable:max-line-length */\n\n /**\n * Subscribe to this Observable and get a Promise resolving on\n * `complete` with the last emission (if any).\n *\n * **WARNING**: Only use this with observables you *know* will complete. If the source\n * observable does not complete, you will end up with a promise that is hung up, and\n * potentially all of the state of an async function hanging out in memory. To avoid\n * this situation, look into adding something like {@link timeout}, {@link take},\n * {@link takeWhile}, or {@link takeUntil} amongst others.\n *\n * @param [promiseCtor] a constructor function used to instantiate\n * the Promise\n * @return A Promise that resolves with the last value emit, or\n * rejects on an error. If there were no emissions, Promise\n * resolves with undefined.\n * @deprecated Replaced with {@link firstValueFrom} and {@link lastValueFrom}. Will be removed in v8. Details: https://rxjs.dev/deprecations/to-promise\n */\n toPromise(promiseCtor?: PromiseConstructorLike): Promise {\n promiseCtor = getPromiseCtor(promiseCtor);\n\n return new promiseCtor((resolve, reject) => {\n let value: T | undefined;\n this.subscribe(\n (x: T) => (value = x),\n (err: any) => reject(err),\n () => resolve(value)\n );\n }) as Promise;\n }\n}\n\n/**\n * Decides between a passed promise constructor from consuming code,\n * A default configured promise constructor, and the native promise\n * constructor and returns it. If nothing can be found, it will throw\n * an error.\n * @param promiseCtor The optional promise constructor to passed by consuming code\n */\nfunction getPromiseCtor(promiseCtor: PromiseConstructorLike | undefined) {\n return promiseCtor ?? config.Promise ?? Promise;\n}\n\nfunction isObserver(value: any): value is Observer {\n return value && isFunction(value.next) && isFunction(value.error) && isFunction(value.complete);\n}\n\nfunction isSubscriber(value: any): value is Subscriber {\n return (value && value instanceof Subscriber) || (isObserver(value) && isSubscription(value));\n}\n", "import { Observable } from '../Observable';\nimport { Subscriber } from '../Subscriber';\nimport { OperatorFunction } from '../types';\nimport { isFunction } from './isFunction';\n\n/**\n * Used to determine if an object is an Observable with a lift function.\n */\nexport function hasLift(source: any): source is { lift: InstanceType['lift'] } {\n return isFunction(source?.lift);\n}\n\n/**\n * Creates an `OperatorFunction`. Used to define operators throughout the library in a concise way.\n * @param init The logic to connect the liftedSource to the subscriber at the moment of subscription.\n */\nexport function operate(\n init: (liftedSource: Observable, subscriber: Subscriber) => (() => void) | void\n): OperatorFunction {\n return (source: Observable) => {\n if (hasLift(source)) {\n return source.lift(function (this: Subscriber, liftedSource: Observable) {\n try {\n return init(liftedSource, this);\n } catch (err) {\n this.error(err);\n }\n });\n }\n throw new TypeError('Unable to lift unknown Observable type');\n };\n}\n", "import { Subscriber } from '../Subscriber';\n\n/**\n * Creates an instance of an `OperatorSubscriber`.\n * @param destination The downstream subscriber.\n * @param onNext Handles next values, only called if this subscriber is not stopped or closed. Any\n * error that occurs in this function is caught and sent to the `error` method of this subscriber.\n * @param onError Handles errors from the subscription, any errors that occur in this handler are caught\n * and send to the `destination` error handler.\n * @param onComplete Handles completion notification from the subscription. Any errors that occur in\n * this handler are sent to the `destination` error handler.\n * @param onFinalize Additional teardown logic here. This will only be called on teardown if the\n * subscriber itself is not already closed. This is called after all other teardown logic is executed.\n */\nexport function createOperatorSubscriber(\n destination: Subscriber,\n onNext?: (value: T) => void,\n onComplete?: () => void,\n onError?: (err: any) => void,\n onFinalize?: () => void\n): Subscriber {\n return new OperatorSubscriber(destination, onNext, onComplete, onError, onFinalize);\n}\n\n/**\n * A generic helper for allowing operators to be created with a Subscriber and\n * use closures to capture necessary state from the operator function itself.\n */\nexport class OperatorSubscriber extends Subscriber {\n /**\n * Creates an instance of an `OperatorSubscriber`.\n * @param destination The downstream subscriber.\n * @param onNext Handles next values, only called if this subscriber is not stopped or closed. Any\n * error that occurs in this function is caught and sent to the `error` method of this subscriber.\n * @param onError Handles errors from the subscription, any errors that occur in this handler are caught\n * and send to the `destination` error handler.\n * @param onComplete Handles completion notification from the subscription. Any errors that occur in\n * this handler are sent to the `destination` error handler.\n * @param onFinalize Additional finalization logic here. This will only be called on finalization if the\n * subscriber itself is not already closed. This is called after all other finalization logic is executed.\n * @param shouldUnsubscribe An optional check to see if an unsubscribe call should truly unsubscribe.\n * NOTE: This currently **ONLY** exists to support the strange behavior of {@link groupBy}, where unsubscription\n * to the resulting observable does not actually disconnect from the source if there are active subscriptions\n * to any grouped observable. (DO NOT EXPOSE OR USE EXTERNALLY!!!)\n */\n constructor(\n destination: Subscriber,\n onNext?: (value: T) => void,\n onComplete?: () => void,\n onError?: (err: any) => void,\n private onFinalize?: () => void,\n private shouldUnsubscribe?: () => boolean\n ) {\n // It's important - for performance reasons - that all of this class's\n // members are initialized and that they are always initialized in the same\n // order. This will ensure that all OperatorSubscriber instances have the\n // same hidden class in V8. This, in turn, will help keep the number of\n // hidden classes involved in property accesses within the base class as\n // low as possible. If the number of hidden classes involved exceeds four,\n // the property accesses will become megamorphic and performance penalties\n // will be incurred - i.e. inline caches won't be used.\n //\n // The reasons for ensuring all instances have the same hidden class are\n // further discussed in this blog post from Benedikt Meurer:\n // https://benediktmeurer.de/2018/03/23/impact-of-polymorphism-on-component-based-frameworks-like-react/\n super(destination);\n this._next = onNext\n ? function (this: OperatorSubscriber, value: T) {\n try {\n onNext(value);\n } catch (err) {\n destination.error(err);\n }\n }\n : super._next;\n this._error = onError\n ? function (this: OperatorSubscriber, err: any) {\n try {\n onError(err);\n } catch (err) {\n // Send any errors that occur down stream.\n destination.error(err);\n } finally {\n // Ensure finalization.\n this.unsubscribe();\n }\n }\n : super._error;\n this._complete = onComplete\n ? function (this: OperatorSubscriber) {\n try {\n onComplete();\n } catch (err) {\n // Send any errors that occur down stream.\n destination.error(err);\n } finally {\n // Ensure finalization.\n this.unsubscribe();\n }\n }\n : super._complete;\n }\n\n unsubscribe() {\n if (!this.shouldUnsubscribe || this.shouldUnsubscribe()) {\n const { closed } = this;\n super.unsubscribe();\n // Execute additional teardown if we have any and we didn't already do so.\n !closed && this.onFinalize?.();\n }\n }\n}\n", "import { Subscription } from '../Subscription';\n\ninterface AnimationFrameProvider {\n schedule(callback: FrameRequestCallback): Subscription;\n requestAnimationFrame: typeof requestAnimationFrame;\n cancelAnimationFrame: typeof cancelAnimationFrame;\n delegate:\n | {\n requestAnimationFrame: typeof requestAnimationFrame;\n cancelAnimationFrame: typeof cancelAnimationFrame;\n }\n | undefined;\n}\n\nexport const animationFrameProvider: AnimationFrameProvider = {\n // When accessing the delegate, use the variable rather than `this` so that\n // the functions can be called without being bound to the provider.\n schedule(callback) {\n let request = requestAnimationFrame;\n let cancel: typeof cancelAnimationFrame | undefined = cancelAnimationFrame;\n const { delegate } = animationFrameProvider;\n if (delegate) {\n request = delegate.requestAnimationFrame;\n cancel = delegate.cancelAnimationFrame;\n }\n const handle = request((timestamp) => {\n // Clear the cancel function. The request has been fulfilled, so\n // attempting to cancel the request upon unsubscription would be\n // pointless.\n cancel = undefined;\n callback(timestamp);\n });\n return new Subscription(() => cancel?.(handle));\n },\n requestAnimationFrame(...args) {\n const { delegate } = animationFrameProvider;\n return (delegate?.requestAnimationFrame || requestAnimationFrame)(...args);\n },\n cancelAnimationFrame(...args) {\n const { delegate } = animationFrameProvider;\n return (delegate?.cancelAnimationFrame || cancelAnimationFrame)(...args);\n },\n delegate: undefined,\n};\n", "import { createErrorClass } from './createErrorClass';\n\nexport interface ObjectUnsubscribedError extends Error {}\n\nexport interface ObjectUnsubscribedErrorCtor {\n /**\n * @deprecated Internal implementation detail. Do not construct error instances.\n * Cannot be tagged as internal: https://github.com/ReactiveX/rxjs/issues/6269\n */\n new (): ObjectUnsubscribedError;\n}\n\n/**\n * An error thrown when an action is invalid because the object has been\n * unsubscribed.\n *\n * @see {@link Subject}\n * @see {@link BehaviorSubject}\n *\n * @class ObjectUnsubscribedError\n */\nexport const ObjectUnsubscribedError: ObjectUnsubscribedErrorCtor = createErrorClass(\n (_super) =>\n function ObjectUnsubscribedErrorImpl(this: any) {\n _super(this);\n this.name = 'ObjectUnsubscribedError';\n this.message = 'object unsubscribed';\n }\n);\n", "import { Operator } from './Operator';\nimport { Observable } from './Observable';\nimport { Subscriber } from './Subscriber';\nimport { Subscription, EMPTY_SUBSCRIPTION } from './Subscription';\nimport { Observer, SubscriptionLike, TeardownLogic } from './types';\nimport { ObjectUnsubscribedError } from './util/ObjectUnsubscribedError';\nimport { arrRemove } from './util/arrRemove';\nimport { errorContext } from './util/errorContext';\n\n/**\n * A Subject is a special type of Observable that allows values to be\n * multicasted to many Observers. Subjects are like EventEmitters.\n *\n * Every Subject is an Observable and an Observer. You can subscribe to a\n * Subject, and you can call next to feed values as well as error and complete.\n */\nexport class Subject extends Observable implements SubscriptionLike {\n closed = false;\n\n private currentObservers: Observer[] | null = null;\n\n /** @deprecated Internal implementation detail, do not use directly. Will be made internal in v8. */\n observers: Observer[] = [];\n /** @deprecated Internal implementation detail, do not use directly. Will be made internal in v8. */\n isStopped = false;\n /** @deprecated Internal implementation detail, do not use directly. Will be made internal in v8. */\n hasError = false;\n /** @deprecated Internal implementation detail, do not use directly. Will be made internal in v8. */\n thrownError: any = null;\n\n /**\n * Creates a \"subject\" by basically gluing an observer to an observable.\n *\n * @deprecated Recommended you do not use. Will be removed at some point in the future. Plans for replacement still under discussion.\n */\n static create: (...args: any[]) => any = (destination: Observer, source: Observable): AnonymousSubject => {\n return new AnonymousSubject(destination, source);\n };\n\n constructor() {\n // NOTE: This must be here to obscure Observable's constructor.\n super();\n }\n\n /** @deprecated Internal implementation detail, do not use directly. Will be made internal in v8. */\n lift(operator: Operator): Observable {\n const subject = new AnonymousSubject(this, this);\n subject.operator = operator as any;\n return subject as any;\n }\n\n /** @internal */\n protected _throwIfClosed() {\n if (this.closed) {\n throw new ObjectUnsubscribedError();\n }\n }\n\n next(value: T) {\n errorContext(() => {\n this._throwIfClosed();\n if (!this.isStopped) {\n if (!this.currentObservers) {\n this.currentObservers = Array.from(this.observers);\n }\n for (const observer of this.currentObservers) {\n observer.next(value);\n }\n }\n });\n }\n\n error(err: any) {\n errorContext(() => {\n this._throwIfClosed();\n if (!this.isStopped) {\n this.hasError = this.isStopped = true;\n this.thrownError = err;\n const { observers } = this;\n while (observers.length) {\n observers.shift()!.error(err);\n }\n }\n });\n }\n\n complete() {\n errorContext(() => {\n this._throwIfClosed();\n if (!this.isStopped) {\n this.isStopped = true;\n const { observers } = this;\n while (observers.length) {\n observers.shift()!.complete();\n }\n }\n });\n }\n\n unsubscribe() {\n this.isStopped = this.closed = true;\n this.observers = this.currentObservers = null!;\n }\n\n get observed() {\n return this.observers?.length > 0;\n }\n\n /** @internal */\n protected _trySubscribe(subscriber: Subscriber): TeardownLogic {\n this._throwIfClosed();\n return super._trySubscribe(subscriber);\n }\n\n /** @internal */\n protected _subscribe(subscriber: Subscriber): Subscription {\n this._throwIfClosed();\n this._checkFinalizedStatuses(subscriber);\n return this._innerSubscribe(subscriber);\n }\n\n /** @internal */\n protected _innerSubscribe(subscriber: Subscriber) {\n const { hasError, isStopped, observers } = this;\n if (hasError || isStopped) {\n return EMPTY_SUBSCRIPTION;\n }\n this.currentObservers = null;\n observers.push(subscriber);\n return new Subscription(() => {\n this.currentObservers = null;\n arrRemove(observers, subscriber);\n });\n }\n\n /** @internal */\n protected _checkFinalizedStatuses(subscriber: Subscriber) {\n const { hasError, thrownError, isStopped } = this;\n if (hasError) {\n subscriber.error(thrownError);\n } else if (isStopped) {\n subscriber.complete();\n }\n }\n\n /**\n * Creates a new Observable with this Subject as the source. You can do this\n * to create custom Observer-side logic of the Subject and conceal it from\n * code that uses the Observable.\n * @return Observable that this Subject casts to.\n */\n asObservable(): Observable {\n const observable: any = new Observable();\n observable.source = this;\n return observable;\n }\n}\n\nexport class AnonymousSubject extends Subject {\n constructor(\n /** @deprecated Internal implementation detail, do not use directly. Will be made internal in v8. */\n public destination?: Observer,\n source?: Observable\n ) {\n super();\n this.source = source;\n }\n\n next(value: T) {\n this.destination?.next?.(value);\n }\n\n error(err: any) {\n this.destination?.error?.(err);\n }\n\n complete() {\n this.destination?.complete?.();\n }\n\n /** @internal */\n protected _subscribe(subscriber: Subscriber): Subscription {\n return this.source?.subscribe(subscriber) ?? EMPTY_SUBSCRIPTION;\n }\n}\n", "import { Subject } from './Subject';\nimport { Subscriber } from './Subscriber';\nimport { Subscription } from './Subscription';\n\n/**\n * A variant of Subject that requires an initial value and emits its current\n * value whenever it is subscribed to.\n */\nexport class BehaviorSubject extends Subject {\n constructor(private _value: T) {\n super();\n }\n\n get value(): T {\n return this.getValue();\n }\n\n /** @internal */\n protected _subscribe(subscriber: Subscriber): Subscription {\n const subscription = super._subscribe(subscriber);\n !subscription.closed && subscriber.next(this._value);\n return subscription;\n }\n\n getValue(): T {\n const { hasError, thrownError, _value } = this;\n if (hasError) {\n throw thrownError;\n }\n this._throwIfClosed();\n return _value;\n }\n\n next(value: T): void {\n super.next((this._value = value));\n }\n}\n", "import { TimestampProvider } from '../types';\n\ninterface DateTimestampProvider extends TimestampProvider {\n delegate: TimestampProvider | undefined;\n}\n\nexport const dateTimestampProvider: DateTimestampProvider = {\n now() {\n // Use the variable rather than `this` so that the function can be called\n // without being bound to the provider.\n return (dateTimestampProvider.delegate || Date).now();\n },\n delegate: undefined,\n};\n", "import { Subject } from './Subject';\nimport { TimestampProvider } from './types';\nimport { Subscriber } from './Subscriber';\nimport { Subscription } from './Subscription';\nimport { dateTimestampProvider } from './scheduler/dateTimestampProvider';\n\n/**\n * A variant of {@link Subject} that \"replays\" old values to new subscribers by emitting them when they first subscribe.\n *\n * `ReplaySubject` has an internal buffer that will store a specified number of values that it has observed. Like `Subject`,\n * `ReplaySubject` \"observes\" values by having them passed to its `next` method. When it observes a value, it will store that\n * value for a time determined by the configuration of the `ReplaySubject`, as passed to its constructor.\n *\n * When a new subscriber subscribes to the `ReplaySubject` instance, it will synchronously emit all values in its buffer in\n * a First-In-First-Out (FIFO) manner. The `ReplaySubject` will also complete, if it has observed completion; and it will\n * error if it has observed an error.\n *\n * There are two main configuration items to be concerned with:\n *\n * 1. `bufferSize` - This will determine how many items are stored in the buffer, defaults to infinite.\n * 2. `windowTime` - The amount of time to hold a value in the buffer before removing it from the buffer.\n *\n * Both configurations may exist simultaneously. So if you would like to buffer a maximum of 3 values, as long as the values\n * are less than 2 seconds old, you could do so with a `new ReplaySubject(3, 2000)`.\n *\n * ### Differences with BehaviorSubject\n *\n * `BehaviorSubject` is similar to `new ReplaySubject(1)`, with a couple of exceptions:\n *\n * 1. `BehaviorSubject` comes \"primed\" with a single value upon construction.\n * 2. `ReplaySubject` will replay values, even after observing an error, where `BehaviorSubject` will not.\n *\n * @see {@link Subject}\n * @see {@link BehaviorSubject}\n * @see {@link shareReplay}\n */\nexport class ReplaySubject extends Subject {\n private _buffer: (T | number)[] = [];\n private _infiniteTimeWindow = true;\n\n /**\n * @param _bufferSize The size of the buffer to replay on subscription\n * @param _windowTime The amount of time the buffered items will stay buffered\n * @param _timestampProvider An object with a `now()` method that provides the current timestamp. This is used to\n * calculate the amount of time something has been buffered.\n */\n constructor(\n private _bufferSize = Infinity,\n private _windowTime = Infinity,\n private _timestampProvider: TimestampProvider = dateTimestampProvider\n ) {\n super();\n this._infiniteTimeWindow = _windowTime === Infinity;\n this._bufferSize = Math.max(1, _bufferSize);\n this._windowTime = Math.max(1, _windowTime);\n }\n\n next(value: T): void {\n const { isStopped, _buffer, _infiniteTimeWindow, _timestampProvider, _windowTime } = this;\n if (!isStopped) {\n _buffer.push(value);\n !_infiniteTimeWindow && _buffer.push(_timestampProvider.now() + _windowTime);\n }\n this._trimBuffer();\n super.next(value);\n }\n\n /** @internal */\n protected _subscribe(subscriber: Subscriber): Subscription {\n this._throwIfClosed();\n this._trimBuffer();\n\n const subscription = this._innerSubscribe(subscriber);\n\n const { _infiniteTimeWindow, _buffer } = this;\n // We use a copy here, so reentrant code does not mutate our array while we're\n // emitting it to a new subscriber.\n const copy = _buffer.slice();\n for (let i = 0; i < copy.length && !subscriber.closed; i += _infiniteTimeWindow ? 1 : 2) {\n subscriber.next(copy[i] as T);\n }\n\n this._checkFinalizedStatuses(subscriber);\n\n return subscription;\n }\n\n private _trimBuffer() {\n const { _bufferSize, _timestampProvider, _buffer, _infiniteTimeWindow } = this;\n // If we don't have an infinite buffer size, and we're over the length,\n // use splice to truncate the old buffer values off. Note that we have to\n // double the size for instances where we're not using an infinite time window\n // because we're storing the values and the timestamps in the same array.\n const adjustedBufferSize = (_infiniteTimeWindow ? 1 : 2) * _bufferSize;\n _bufferSize < Infinity && adjustedBufferSize < _buffer.length && _buffer.splice(0, _buffer.length - adjustedBufferSize);\n\n // Now, if we're not in an infinite time window, remove all values where the time is\n // older than what is allowed.\n if (!_infiniteTimeWindow) {\n const now = _timestampProvider.now();\n let last = 0;\n // Search the array for the first timestamp that isn't expired and\n // truncate the buffer up to that point.\n for (let i = 1; i < _buffer.length && (_buffer[i] as number) <= now; i += 2) {\n last = i;\n }\n last && _buffer.splice(0, last + 1);\n }\n }\n}\n", "import { Scheduler } from '../Scheduler';\nimport { Subscription } from '../Subscription';\nimport { SchedulerAction } from '../types';\n\n/**\n * A unit of work to be executed in a `scheduler`. An action is typically\n * created from within a {@link SchedulerLike} and an RxJS user does not need to concern\n * themselves about creating and manipulating an Action.\n *\n * ```ts\n * class Action extends Subscription {\n * new (scheduler: Scheduler, work: (state?: T) => void);\n * schedule(state?: T, delay: number = 0): Subscription;\n * }\n * ```\n */\nexport class Action extends Subscription {\n constructor(scheduler: Scheduler, work: (this: SchedulerAction, state?: T) => void) {\n super();\n }\n /**\n * Schedules this action on its parent {@link SchedulerLike} for execution. May be passed\n * some context object, `state`. May happen at some point in the future,\n * according to the `delay` parameter, if specified.\n * @param state Some contextual data that the `work` function uses when called by the\n * Scheduler.\n * @param delay Time to wait before executing the work, where the time unit is implicit\n * and defined by the Scheduler.\n * @return A subscription in order to be able to unsubscribe the scheduled work.\n */\n public schedule(state?: T, delay: number = 0): Subscription {\n return this;\n }\n}\n", "import type { TimerHandle } from './timerHandle';\ntype SetIntervalFunction = (handler: () => void, timeout?: number, ...args: any[]) => TimerHandle;\ntype ClearIntervalFunction = (handle: TimerHandle) => void;\n\ninterface IntervalProvider {\n setInterval: SetIntervalFunction;\n clearInterval: ClearIntervalFunction;\n delegate:\n | {\n setInterval: SetIntervalFunction;\n clearInterval: ClearIntervalFunction;\n }\n | undefined;\n}\n\nexport const intervalProvider: IntervalProvider = {\n // When accessing the delegate, use the variable rather than `this` so that\n // the functions can be called without being bound to the provider.\n setInterval(handler: () => void, timeout?: number, ...args) {\n const { delegate } = intervalProvider;\n if (delegate?.setInterval) {\n return delegate.setInterval(handler, timeout, ...args);\n }\n return setInterval(handler, timeout, ...args);\n },\n clearInterval(handle) {\n const { delegate } = intervalProvider;\n return (delegate?.clearInterval || clearInterval)(handle as any);\n },\n delegate: undefined,\n};\n", "import { Action } from './Action';\nimport { SchedulerAction } from '../types';\nimport { Subscription } from '../Subscription';\nimport { AsyncScheduler } from './AsyncScheduler';\nimport { intervalProvider } from './intervalProvider';\nimport { arrRemove } from '../util/arrRemove';\nimport { TimerHandle } from './timerHandle';\n\nexport class AsyncAction extends Action {\n public id: TimerHandle | undefined;\n public state?: T;\n // @ts-ignore: Property has no initializer and is not definitely assigned\n public delay: number;\n protected pending: boolean = false;\n\n constructor(protected scheduler: AsyncScheduler, protected work: (this: SchedulerAction, state?: T) => void) {\n super(scheduler, work);\n }\n\n public schedule(state?: T, delay: number = 0): Subscription {\n if (this.closed) {\n return this;\n }\n\n // Always replace the current state with the new state.\n this.state = state;\n\n const id = this.id;\n const scheduler = this.scheduler;\n\n //\n // Important implementation note:\n //\n // Actions only execute once by default, unless rescheduled from within the\n // scheduled callback. This allows us to implement single and repeat\n // actions via the same code path, without adding API surface area, as well\n // as mimic traditional recursion but across asynchronous boundaries.\n //\n // However, JS runtimes and timers distinguish between intervals achieved by\n // serial `setTimeout` calls vs. a single `setInterval` call. An interval of\n // serial `setTimeout` calls can be individually delayed, which delays\n // scheduling the next `setTimeout`, and so on. `setInterval` attempts to\n // guarantee the interval callback will be invoked more precisely to the\n // interval period, regardless of load.\n //\n // Therefore, we use `setInterval` to schedule single and repeat actions.\n // If the action reschedules itself with the same delay, the interval is not\n // canceled. If the action doesn't reschedule, or reschedules with a\n // different delay, the interval will be canceled after scheduled callback\n // execution.\n //\n if (id != null) {\n this.id = this.recycleAsyncId(scheduler, id, delay);\n }\n\n // Set the pending flag indicating that this action has been scheduled, or\n // has recursively rescheduled itself.\n this.pending = true;\n\n this.delay = delay;\n // If this action has already an async Id, don't request a new one.\n this.id = this.id ?? this.requestAsyncId(scheduler, this.id, delay);\n\n return this;\n }\n\n protected requestAsyncId(scheduler: AsyncScheduler, _id?: TimerHandle, delay: number = 0): TimerHandle {\n return intervalProvider.setInterval(scheduler.flush.bind(scheduler, this), delay);\n }\n\n protected recycleAsyncId(_scheduler: AsyncScheduler, id?: TimerHandle, delay: number | null = 0): TimerHandle | undefined {\n // If this action is rescheduled with the same delay time, don't clear the interval id.\n if (delay != null && this.delay === delay && this.pending === false) {\n return id;\n }\n // Otherwise, if the action's delay time is different from the current delay,\n // or the action has been rescheduled before it's executed, clear the interval id\n if (id != null) {\n intervalProvider.clearInterval(id);\n }\n\n return undefined;\n }\n\n /**\n * Immediately executes this action and the `work` it contains.\n */\n public execute(state: T, delay: number): any {\n if (this.closed) {\n return new Error('executing a cancelled action');\n }\n\n this.pending = false;\n const error = this._execute(state, delay);\n if (error) {\n return error;\n } else if (this.pending === false && this.id != null) {\n // Dequeue if the action didn't reschedule itself. Don't call\n // unsubscribe(), because the action could reschedule later.\n // For example:\n // ```\n // scheduler.schedule(function doWork(counter) {\n // /* ... I'm a busy worker bee ... */\n // var originalAction = this;\n // /* wait 100ms before rescheduling the action */\n // setTimeout(function () {\n // originalAction.schedule(counter + 1);\n // }, 100);\n // }, 1000);\n // ```\n this.id = this.recycleAsyncId(this.scheduler, this.id, null);\n }\n }\n\n protected _execute(state: T, _delay: number): any {\n let errored: boolean = false;\n let errorValue: any;\n try {\n this.work(state);\n } catch (e) {\n errored = true;\n // HACK: Since code elsewhere is relying on the \"truthiness\" of the\n // return here, we can't have it return \"\" or 0 or false.\n // TODO: Clean this up when we refactor schedulers mid-version-8 or so.\n errorValue = e ? e : new Error('Scheduled action threw falsy error');\n }\n if (errored) {\n this.unsubscribe();\n return errorValue;\n }\n }\n\n unsubscribe() {\n if (!this.closed) {\n const { id, scheduler } = this;\n const { actions } = scheduler;\n\n this.work = this.state = this.scheduler = null!;\n this.pending = false;\n\n arrRemove(actions, this);\n if (id != null) {\n this.id = this.recycleAsyncId(scheduler, id, null);\n }\n\n this.delay = null!;\n super.unsubscribe();\n }\n }\n}\n", "import { Action } from './scheduler/Action';\nimport { Subscription } from './Subscription';\nimport { SchedulerLike, SchedulerAction } from './types';\nimport { dateTimestampProvider } from './scheduler/dateTimestampProvider';\n\n/**\n * An execution context and a data structure to order tasks and schedule their\n * execution. Provides a notion of (potentially virtual) time, through the\n * `now()` getter method.\n *\n * Each unit of work in a Scheduler is called an `Action`.\n *\n * ```ts\n * class Scheduler {\n * now(): number;\n * schedule(work, delay?, state?): Subscription;\n * }\n * ```\n *\n * @deprecated Scheduler is an internal implementation detail of RxJS, and\n * should not be used directly. Rather, create your own class and implement\n * {@link SchedulerLike}. Will be made internal in v8.\n */\nexport class Scheduler implements SchedulerLike {\n public static now: () => number = dateTimestampProvider.now;\n\n constructor(private schedulerActionCtor: typeof Action, now: () => number = Scheduler.now) {\n this.now = now;\n }\n\n /**\n * A getter method that returns a number representing the current time\n * (at the time this function was called) according to the scheduler's own\n * internal clock.\n * @return A number that represents the current time. May or may not\n * have a relation to wall-clock time. May or may not refer to a time unit\n * (e.g. milliseconds).\n */\n public now: () => number;\n\n /**\n * Schedules a function, `work`, for execution. May happen at some point in\n * the future, according to the `delay` parameter, if specified. May be passed\n * some context object, `state`, which will be passed to the `work` function.\n *\n * The given arguments will be processed an stored as an Action object in a\n * queue of actions.\n *\n * @param work A function representing a task, or some unit of work to be\n * executed by the Scheduler.\n * @param delay Time to wait before executing the work, where the time unit is\n * implicit and defined by the Scheduler itself.\n * @param state Some contextual data that the `work` function uses when called\n * by the Scheduler.\n * @return A subscription in order to be able to unsubscribe the scheduled work.\n */\n public schedule(work: (this: SchedulerAction, state?: T) => void, delay: number = 0, state?: T): Subscription {\n return new this.schedulerActionCtor(this, work).schedule(state, delay);\n }\n}\n", "import { Scheduler } from '../Scheduler';\nimport { Action } from './Action';\nimport { AsyncAction } from './AsyncAction';\nimport { TimerHandle } from './timerHandle';\n\nexport class AsyncScheduler extends Scheduler {\n public actions: Array> = [];\n /**\n * A flag to indicate whether the Scheduler is currently executing a batch of\n * queued actions.\n * @internal\n */\n public _active: boolean = false;\n /**\n * An internal ID used to track the latest asynchronous task such as those\n * coming from `setTimeout`, `setInterval`, `requestAnimationFrame`, and\n * others.\n * @internal\n */\n public _scheduled: TimerHandle | undefined;\n\n constructor(SchedulerAction: typeof Action, now: () => number = Scheduler.now) {\n super(SchedulerAction, now);\n }\n\n public flush(action: AsyncAction): void {\n const { actions } = this;\n\n if (this._active) {\n actions.push(action);\n return;\n }\n\n let error: any;\n this._active = true;\n\n do {\n if ((error = action.execute(action.state, action.delay))) {\n break;\n }\n } while ((action = actions.shift()!)); // exhaust the scheduler queue\n\n this._active = false;\n\n if (error) {\n while ((action = actions.shift()!)) {\n action.unsubscribe();\n }\n throw error;\n }\n }\n}\n", "import { AsyncAction } from './AsyncAction';\nimport { AsyncScheduler } from './AsyncScheduler';\n\n/**\n *\n * Async Scheduler\n *\n * Schedule task as if you used setTimeout(task, duration)\n *\n * `async` scheduler schedules tasks asynchronously, by putting them on the JavaScript\n * event loop queue. It is best used to delay tasks in time or to schedule tasks repeating\n * in intervals.\n *\n * If you just want to \"defer\" task, that is to perform it right after currently\n * executing synchronous code ends (commonly achieved by `setTimeout(deferredTask, 0)`),\n * better choice will be the {@link asapScheduler} scheduler.\n *\n * ## Examples\n * Use async scheduler to delay task\n * ```ts\n * import { asyncScheduler } from 'rxjs';\n *\n * const task = () => console.log('it works!');\n *\n * asyncScheduler.schedule(task, 2000);\n *\n * // After 2 seconds logs:\n * // \"it works!\"\n * ```\n *\n * Use async scheduler to repeat task in intervals\n * ```ts\n * import { asyncScheduler } from 'rxjs';\n *\n * function task(state) {\n * console.log(state);\n * this.schedule(state + 1, 1000); // `this` references currently executing Action,\n * // which we reschedule with new state and delay\n * }\n *\n * asyncScheduler.schedule(task, 3000, 0);\n *\n * // Logs:\n * // 0 after 3s\n * // 1 after 4s\n * // 2 after 5s\n * // 3 after 6s\n * ```\n */\n\nexport const asyncScheduler = new AsyncScheduler(AsyncAction);\n\n/**\n * @deprecated Renamed to {@link asyncScheduler}. Will be removed in v8.\n */\nexport const async = asyncScheduler;\n", "import { AsyncAction } from './AsyncAction';\nimport { Subscription } from '../Subscription';\nimport { QueueScheduler } from './QueueScheduler';\nimport { SchedulerAction } from '../types';\nimport { TimerHandle } from './timerHandle';\n\nexport class QueueAction extends AsyncAction {\n constructor(protected scheduler: QueueScheduler, protected work: (this: SchedulerAction, state?: T) => void) {\n super(scheduler, work);\n }\n\n public schedule(state?: T, delay: number = 0): Subscription {\n if (delay > 0) {\n return super.schedule(state, delay);\n }\n this.delay = delay;\n this.state = state;\n this.scheduler.flush(this);\n return this;\n }\n\n public execute(state: T, delay: number): any {\n return delay > 0 || this.closed ? super.execute(state, delay) : this._execute(state, delay);\n }\n\n protected requestAsyncId(scheduler: QueueScheduler, id?: TimerHandle, delay: number = 0): TimerHandle {\n // If delay exists and is greater than 0, or if the delay is null (the\n // action wasn't rescheduled) but was originally scheduled as an async\n // action, then recycle as an async action.\n\n if ((delay != null && delay > 0) || (delay == null && this.delay > 0)) {\n return super.requestAsyncId(scheduler, id, delay);\n }\n\n // Otherwise flush the scheduler starting with this action.\n scheduler.flush(this);\n\n // HACK: In the past, this was returning `void`. However, `void` isn't a valid\n // `TimerHandle`, and generally the return value here isn't really used. So the\n // compromise is to return `0` which is both \"falsy\" and a valid `TimerHandle`,\n // as opposed to refactoring every other instanceo of `requestAsyncId`.\n return 0;\n }\n}\n", "import { AsyncScheduler } from './AsyncScheduler';\n\nexport class QueueScheduler extends AsyncScheduler {\n}\n", "import { QueueAction } from './QueueAction';\nimport { QueueScheduler } from './QueueScheduler';\n\n/**\n *\n * Queue Scheduler\n *\n * Put every next task on a queue, instead of executing it immediately\n *\n * `queue` scheduler, when used with delay, behaves the same as {@link asyncScheduler} scheduler.\n *\n * When used without delay, it schedules given task synchronously - executes it right when\n * it is scheduled. However when called recursively, that is when inside the scheduled task,\n * another task is scheduled with queue scheduler, instead of executing immediately as well,\n * that task will be put on a queue and wait for current one to finish.\n *\n * This means that when you execute task with `queue` scheduler, you are sure it will end\n * before any other task scheduled with that scheduler will start.\n *\n * ## Examples\n * Schedule recursively first, then do something\n * ```ts\n * import { queueScheduler } from 'rxjs';\n *\n * queueScheduler.schedule(() => {\n * queueScheduler.schedule(() => console.log('second')); // will not happen now, but will be put on a queue\n *\n * console.log('first');\n * });\n *\n * // Logs:\n * // \"first\"\n * // \"second\"\n * ```\n *\n * Reschedule itself recursively\n * ```ts\n * import { queueScheduler } from 'rxjs';\n *\n * queueScheduler.schedule(function(state) {\n * if (state !== 0) {\n * console.log('before', state);\n * this.schedule(state - 1); // `this` references currently executing Action,\n * // which we reschedule with new state\n * console.log('after', state);\n * }\n * }, 0, 3);\n *\n * // In scheduler that runs recursively, you would expect:\n * // \"before\", 3\n * // \"before\", 2\n * // \"before\", 1\n * // \"after\", 1\n * // \"after\", 2\n * // \"after\", 3\n *\n * // But with queue it logs:\n * // \"before\", 3\n * // \"after\", 3\n * // \"before\", 2\n * // \"after\", 2\n * // \"before\", 1\n * // \"after\", 1\n * ```\n */\n\nexport const queueScheduler = new QueueScheduler(QueueAction);\n\n/**\n * @deprecated Renamed to {@link queueScheduler}. Will be removed in v8.\n */\nexport const queue = queueScheduler;\n", "import { AsyncAction } from './AsyncAction';\nimport { AnimationFrameScheduler } from './AnimationFrameScheduler';\nimport { SchedulerAction } from '../types';\nimport { animationFrameProvider } from './animationFrameProvider';\nimport { TimerHandle } from './timerHandle';\n\nexport class AnimationFrameAction extends AsyncAction {\n constructor(protected scheduler: AnimationFrameScheduler, protected work: (this: SchedulerAction, state?: T) => void) {\n super(scheduler, work);\n }\n\n protected requestAsyncId(scheduler: AnimationFrameScheduler, id?: TimerHandle, delay: number = 0): TimerHandle {\n // If delay is greater than 0, request as an async action.\n if (delay !== null && delay > 0) {\n return super.requestAsyncId(scheduler, id, delay);\n }\n // Push the action to the end of the scheduler queue.\n scheduler.actions.push(this);\n // If an animation frame has already been requested, don't request another\n // one. If an animation frame hasn't been requested yet, request one. Return\n // the current animation frame request id.\n return scheduler._scheduled || (scheduler._scheduled = animationFrameProvider.requestAnimationFrame(() => scheduler.flush(undefined)));\n }\n\n protected recycleAsyncId(scheduler: AnimationFrameScheduler, id?: TimerHandle, delay: number = 0): TimerHandle | undefined {\n // If delay exists and is greater than 0, or if the delay is null (the\n // action wasn't rescheduled) but was originally scheduled as an async\n // action, then recycle as an async action.\n if (delay != null ? delay > 0 : this.delay > 0) {\n return super.recycleAsyncId(scheduler, id, delay);\n }\n // If the scheduler queue has no remaining actions with the same async id,\n // cancel the requested animation frame and set the scheduled flag to\n // undefined so the next AnimationFrameAction will request its own.\n const { actions } = scheduler;\n if (id != null && id === scheduler._scheduled && actions[actions.length - 1]?.id !== id) {\n animationFrameProvider.cancelAnimationFrame(id as number);\n scheduler._scheduled = undefined;\n }\n // Return undefined so the action knows to request a new async id if it's rescheduled.\n return undefined;\n }\n}\n", "import { AsyncAction } from './AsyncAction';\nimport { AsyncScheduler } from './AsyncScheduler';\n\nexport class AnimationFrameScheduler extends AsyncScheduler {\n public flush(action?: AsyncAction): void {\n this._active = true;\n // The async id that effects a call to flush is stored in _scheduled.\n // Before executing an action, it's necessary to check the action's async\n // id to determine whether it's supposed to be executed in the current\n // flush.\n // Previous implementations of this method used a count to determine this,\n // but that was unsound, as actions that are unsubscribed - i.e. cancelled -\n // are removed from the actions array and that can shift actions that are\n // scheduled to be executed in a subsequent flush into positions at which\n // they are executed within the current flush.\n let flushId;\n if (action) {\n flushId = action.id;\n } else {\n flushId = this._scheduled;\n this._scheduled = undefined;\n }\n\n const { actions } = this;\n let error: any;\n action = action || actions.shift()!;\n\n do {\n if ((error = action.execute(action.state, action.delay))) {\n break;\n }\n } while ((action = actions[0]) && action.id === flushId && actions.shift());\n\n this._active = false;\n\n if (error) {\n while ((action = actions[0]) && action.id === flushId && actions.shift()) {\n action.unsubscribe();\n }\n throw error;\n }\n }\n}\n", "import { AnimationFrameAction } from './AnimationFrameAction';\nimport { AnimationFrameScheduler } from './AnimationFrameScheduler';\n\n/**\n *\n * Animation Frame Scheduler\n *\n * Perform task when `window.requestAnimationFrame` would fire\n *\n * When `animationFrame` scheduler is used with delay, it will fall back to {@link asyncScheduler} scheduler\n * behaviour.\n *\n * Without delay, `animationFrame` scheduler can be used to create smooth browser animations.\n * It makes sure scheduled task will happen just before next browser content repaint,\n * thus performing animations as efficiently as possible.\n *\n * ## Example\n * Schedule div height animation\n * ```ts\n * // html:
\n * import { animationFrameScheduler } from 'rxjs';\n *\n * const div = document.querySelector('div');\n *\n * animationFrameScheduler.schedule(function(height) {\n * div.style.height = height + \"px\";\n *\n * this.schedule(height + 1); // `this` references currently executing Action,\n * // which we reschedule with new state\n * }, 0, 0);\n *\n * // You will see a div element growing in height\n * ```\n */\n\nexport const animationFrameScheduler = new AnimationFrameScheduler(AnimationFrameAction);\n\n/**\n * @deprecated Renamed to {@link animationFrameScheduler}. Will be removed in v8.\n */\nexport const animationFrame = animationFrameScheduler;\n", "import { Observable } from '../Observable';\nimport { SchedulerLike } from '../types';\n\n/**\n * A simple Observable that emits no items to the Observer and immediately\n * emits a complete notification.\n *\n * Just emits 'complete', and nothing else.\n *\n * ![](empty.png)\n *\n * A simple Observable that only emits the complete notification. It can be used\n * for composing with other Observables, such as in a {@link mergeMap}.\n *\n * ## Examples\n *\n * Log complete notification\n *\n * ```ts\n * import { EMPTY } from 'rxjs';\n *\n * EMPTY.subscribe({\n * next: () => console.log('Next'),\n * complete: () => console.log('Complete!')\n * });\n *\n * // Outputs\n * // Complete!\n * ```\n *\n * Emit the number 7, then complete\n *\n * ```ts\n * import { EMPTY, startWith } from 'rxjs';\n *\n * const result = EMPTY.pipe(startWith(7));\n * result.subscribe(x => console.log(x));\n *\n * // Outputs\n * // 7\n * ```\n *\n * Map and flatten only odd numbers to the sequence `'a'`, `'b'`, `'c'`\n *\n * ```ts\n * import { interval, mergeMap, of, EMPTY } from 'rxjs';\n *\n * const interval$ = interval(1000);\n * const result = interval$.pipe(\n * mergeMap(x => x % 2 === 1 ? of('a', 'b', 'c') : EMPTY),\n * );\n * result.subscribe(x => console.log(x));\n *\n * // Results in the following to the console:\n * // x is equal to the count on the interval, e.g. (0, 1, 2, 3, ...)\n * // x will occur every 1000ms\n * // if x % 2 is equal to 1, print a, b, c (each on its own)\n * // if x % 2 is not equal to 1, nothing will be output\n * ```\n *\n * @see {@link Observable}\n * @see {@link NEVER}\n * @see {@link of}\n * @see {@link throwError}\n */\nexport const EMPTY = new Observable((subscriber) => subscriber.complete());\n\n/**\n * @param scheduler A {@link SchedulerLike} to use for scheduling\n * the emission of the complete notification.\n * @deprecated Replaced with the {@link EMPTY} constant or {@link scheduled} (e.g. `scheduled([], scheduler)`). Will be removed in v8.\n */\nexport function empty(scheduler?: SchedulerLike) {\n return scheduler ? emptyScheduled(scheduler) : EMPTY;\n}\n\nfunction emptyScheduled(scheduler: SchedulerLike) {\n return new Observable((subscriber) => scheduler.schedule(() => subscriber.complete()));\n}\n", "import { SchedulerLike } from '../types';\nimport { isFunction } from './isFunction';\n\nexport function isScheduler(value: any): value is SchedulerLike {\n return value && isFunction(value.schedule);\n}\n", "import { SchedulerLike } from '../types';\nimport { isFunction } from './isFunction';\nimport { isScheduler } from './isScheduler';\n\nfunction last(arr: T[]): T | undefined {\n return arr[arr.length - 1];\n}\n\nexport function popResultSelector(args: any[]): ((...args: unknown[]) => unknown) | undefined {\n return isFunction(last(args)) ? args.pop() : undefined;\n}\n\nexport function popScheduler(args: any[]): SchedulerLike | undefined {\n return isScheduler(last(args)) ? args.pop() : undefined;\n}\n\nexport function popNumber(args: any[], defaultValue: number): number {\n return typeof last(args) === 'number' ? args.pop()! : defaultValue;\n}\n", "export const isArrayLike = ((x: any): x is ArrayLike => x && typeof x.length === 'number' && typeof x !== 'function');", "import { isFunction } from \"./isFunction\";\n\n/**\n * Tests to see if the object is \"thennable\".\n * @param value the object to test\n */\nexport function isPromise(value: any): value is PromiseLike {\n return isFunction(value?.then);\n}\n", "import { InteropObservable } from '../types';\nimport { observable as Symbol_observable } from '../symbol/observable';\nimport { isFunction } from './isFunction';\n\n/** Identifies an input as being Observable (but not necessary an Rx Observable) */\nexport function isInteropObservable(input: any): input is InteropObservable {\n return isFunction(input[Symbol_observable]);\n}\n", "import { isFunction } from './isFunction';\n\nexport function isAsyncIterable(obj: any): obj is AsyncIterable {\n return Symbol.asyncIterator && isFunction(obj?.[Symbol.asyncIterator]);\n}\n", "/**\n * Creates the TypeError to throw if an invalid object is passed to `from` or `scheduled`.\n * @param input The object that was passed.\n */\nexport function createInvalidObservableTypeError(input: any) {\n // TODO: We should create error codes that can be looked up, so this can be less verbose.\n return new TypeError(\n `You provided ${\n input !== null && typeof input === 'object' ? 'an invalid object' : `'${input}'`\n } where a stream was expected. You can provide an Observable, Promise, ReadableStream, Array, AsyncIterable, or Iterable.`\n );\n}\n", "export function getSymbolIterator(): symbol {\n if (typeof Symbol !== 'function' || !Symbol.iterator) {\n return '@@iterator' as any;\n }\n\n return Symbol.iterator;\n}\n\nexport const iterator = getSymbolIterator();\n", "import { iterator as Symbol_iterator } from '../symbol/iterator';\nimport { isFunction } from './isFunction';\n\n/** Identifies an input as being an Iterable */\nexport function isIterable(input: any): input is Iterable {\n return isFunction(input?.[Symbol_iterator]);\n}\n", "import { ReadableStreamLike } from '../types';\nimport { isFunction } from './isFunction';\n\nexport async function* readableStreamLikeToAsyncGenerator(readableStream: ReadableStreamLike): AsyncGenerator {\n const reader = readableStream.getReader();\n try {\n while (true) {\n const { value, done } = await reader.read();\n if (done) {\n return;\n }\n yield value!;\n }\n } finally {\n reader.releaseLock();\n }\n}\n\nexport function isReadableStreamLike(obj: any): obj is ReadableStreamLike {\n // We don't want to use instanceof checks because they would return\n // false for instances from another Realm, like an