Merge pull request #3115 from CenturyLinkCloud/ECLDE-3026

ECLDE-3026
CenturyLinkCloud · Dec 2, 2020 · 647b7ee · 647b7ee
2 parents 30ffe9b + e7b8384
commit 647b7ee
Showing 806 changed files with 4,377 additions and 4,228 deletions.
diff --git a/Accounts & Users/account-hierarchy-user-network-and-firewall-policy-primer.md b/Accounts & Users/account-hierarchy-user-network-and-firewall-policy-primer.md
@@ -9,7 +9,7 @@
 
 ### Overview
 
-CenturyLink Cloud provides a secure multi-tenant platform by strictly segmenting customer accounts from each other.  This includes a strict separation between customer accounts including: cloud servers, networks, users, firewall policies, and all associated metadata.  The ability to create hard fenced accounts has been fully extended to customers through the introduction of [Sub Accounts](../Accounts & Users/creating-a-sub-account.md).
+Lumen Cloud provides a secure multi-tenant platform by strictly segmenting customer accounts from each other.  This includes a strict separation between customer accounts including: cloud servers, networks, users, firewall policies, and all associated metadata.  The ability to create hard fenced accounts has been fully extended to customers through the introduction of [Sub Accounts](../Accounts & Users/creating-a-sub-account.md).
 
 ### Account and Subaccount Structure
 
@@ -41,7 +41,7 @@ Parent accounts can control firewall policies associated with parent-child netwo
 
 ### Service Catalog
 
-The [Service Catalog](../General/CenturyLinkCloud/getting-started-with-the-service-catalog.md) allows Account Administrators to enable or disable certain cloud platform services for users of individual parent or sub accounts.
+The [Service Catalog](../General/LumenCloud/getting-started-with-the-service-catalog.md) allows Account Administrators to enable or disable certain cloud platform services for users of individual parent or sub accounts.
 
 ![Service Catalog in account Hierarchy](../images/account-hierarchy-7.png)
 
@@ -53,4 +53,4 @@ Take note that accounts and Server Groups are very different.  Whereas accounts
 
 ### Considerations and Example Use Cases
 
-The CenturyLink Cloud services team is specially positioned to help customers design the most effective account hierarchy.  Note that account structure and naming cannot be changed once created (though subaccounts can always be created/removed).  
+The Lumen Cloud services team is specially positioned to help customers design the most effective account hierarchy.  Note that account structure and naming cannot be changed once created (though subaccounts can always be created/removed).  
diff --git a/Accounts & Users/add-centurylink-personnel-to-a-role-in-control.md b/Accounts & Users/add-centurylink-personnel-to-a-role-in-control.md
diff --git a/Accounts & Users/add-lumen-personnel-to-a-role-in-control.md b/Accounts & Users/add-lumen-personnel-to-a-role-in-control.md
@@ -0,0 +1,26 @@
+{{{
+  "title": "Add Lumen Personnel to a Role in Control",
+  "date": "11-14-2014",
+  "author": "Maurice Ramsey",
+  "attachments": [],
+  "contentIsHTML": false
+}}}
+
+**Description (goal/purpose)**
+
+When a Lumen employee requires access to a Role in a customer environment, the following procedures must be followed.
+
+**Audience**
+
+* Lumen Employees
+* Lumen Cloud Customers
+
+**Prerequisites**
+
+* Must have a Lumen Cloud Control Portal account (https://control.ctl.io).
+
+**Detailed Steps**
+
+**Option 1**: Request that the Lumen Cloud customer add you to the appropriate role. This is self-service for the customer.
+
+**Option 2**: Have the Lumen Cloud customer request you be added to the appropriate Role via the Lumen ticketing process. Make sure to include the specific Role(s) required and make sure the customer provides their Control Portal PIN for identity verification. Ensure the Lumen Cloud customer CC’s you on the request. Once the request is provided by the Lumen Cloud customer, permissions will be granted and the ticket will be processed per SLA.
diff --git a/Accounts & Users/applying-data-center-preferences.md b/Accounts & Users/applying-data-center-preferences.md
@@ -8,7 +8,7 @@
 
 ### Description
 
-CenturyLink Cloud customers can choose which data centers to make available to the users of an account. **Changing these settings has implications on the user experience, and how new data centers are exposed to the account.** Read the steps below to learn how to enable/disable data centers, and the implications on the API.
+Lumen Cloud customers can choose which data centers to make available to the users of an account. **Changing these settings has implications on the user experience, and how new data centers are exposed to the account.** Read the steps below to learn how to enable/disable data centers, and the implications on the API.
 
 ### Audience
 
@@ -31,4 +31,4 @@ CenturyLink Cloud customers can choose which data centers to make available to t
 ![Create Server](../images/data-center-create-server.png)
 1. A disabled data center is also unavailable for any API operations that use a data center parameter (e.g. [Get Data Center List](http://www.ctl.io/api-docs/v2#data-centers-get-data-center-list)).
 
-**Note:** If you apply data center preferences to your account, than any **new** CenturyLink Cloud data centers will **NOT** automatically show up in the Control Portal for you. You will need to come into the Data Center preferences page and manually enable the new data center. This behavior is in place to respect your conscious choice to show specific data centers.
+**Note:** If you apply data center preferences to your account, than any **new** Lumen Cloud data centers will **NOT** automatically show up in the Control Portal for you. You will need to come into the Data Center preferences page and manually enable the new data center. This behavior is in place to respect your conscious choice to show specific data centers.
diff --git a/Accounts & Users/best-practices-for-account-hierarchy.md b/Accounts & Users/best-practices-for-account-hierarchy.md
@@ -7,9 +7,9 @@
 }}}
 
 ### Overview
-CenturyLink Cloud’s Account Hierarchy management features allows customers granular enablement and demarcation of: users, systems, groups, networks,
-billing, reporting, and/or sub-accounts that reside within the CenturyLink Cloud platform. Customers with administrator access can create and manage these attributes
-within the CenturyLink Cloud Control Portal. It is strongly recommended organizations should consider the following factors, limitations, and best practices before they
+Lumen Cloud’s Account Hierarchy management features allows customers granular enablement and demarcation of: users, systems, groups, networks,
+billing, reporting, and/or sub-accounts that reside within the Lumen Cloud platform. Customers with administrator access can create and manage these attributes
+within the Lumen Cloud Control Portal. It is strongly recommended organizations should consider the following factors, limitations, and best practices before they
 embark on leveraging the aforementioned features.
 
 ### Factors that Influence Account Configuration
@@ -31,8 +31,8 @@ There are many factors that influence how a customer or reseller will configure
 * Accounts can’t be moved in their hierarchies
 
 * There is no “read-only” mode for users, role cascades.  Need to be careful about allowing access
-* Billing data out of Savvis/CenturyLink does not go down to server level only Account/Group
-* Additional detail on current spend can be found in the portal or through the API, but API data for invoices is not guaranteed to be aligned with Savvis/CenturyLink data (e.g. no tax)
+* Billing data out of Savvis/Lumen does not go down to server level only Account/Group
+* Additional detail on current spend can be found in the portal or through the API, but API data for invoices is not guaranteed to be aligned with Savvis/Lumen data (e.g. no tax)
 * No self-service ability to set custom pricing in the control portal
 
 ### Best Practices

diff --git a/Accounts & Users/closing-an-account.md b/Accounts & Users/closing-an-account.md
@@ -21,13 +21,13 @@ We're sorry to see you go. To make sure your off-boarding experience is as easy
 1. Ascertain all the services in use created by the account. Viewing the account's [Usage History][2] can help with this.
 2. Retrieve the data from those services. If you need help extracting a server or other data, you can request a billable [Service Task][3].
 3. Use the Control Portal or [API][4] to delete any actively billed services.
-    - __Services not deleted may accrue further charges before an account is completely deleted (e.g. server storage).__ Confirmation of account closure by the CenturyLink Cloud team doesn't necessarily mean that no further charges will accumulate, so you should ensure all services have been deleted __before__ requesting account closure.
+    - __Services not deleted may accrue further charges before an account is completely deleted (e.g. server storage).__ Confirmation of account closure by the Lumen Cloud team doesn't necessarily mean that no further charges will accumulate, so you should ensure all services have been deleted __before__ requesting account closure.
     - The account's OpenVPN server and network can't be deleted and can safely be ignored. These reside in the account's primary data center and aren't billed as they come with the account by default. The OpenVPN server will follow [platform naming conventions][5] using the name "VPN" (e.g. VA1ABCDVPN01).
 4. Please email [help@ctl.io][7] or [submit a separate ticket][8] to request the account to be closed.
     - There's no guarantee that any server data or configurations can be retrieved after this point.
 
 ### Final Invoice
-If you have completely deleted the account resources __before__ requesting account closure, you'll receive your final invoice from CenturyLink after the close of the current month.
+If you have completely deleted the account resources __before__ requesting account closure, you'll receive your final invoice from Lumen after the close of the current month.
 
 However, if you __didn't__ completely delete the account resourses as instructed in the steps above, they will continue to accrue charges until the account is finally deleted. This means you will receive an invoice for the current month __and__ an invoice for the resource usage accruing into the next month.
 

diff --git a/Accounts & Users/creating-a-sub-account.md b/Accounts & Users/creating-a-sub-account.md
@@ -6,7 +6,7 @@
 "contentIsHTML": false
 }}}
 
-CenturyLink Cloud supports the ability to create Sub accounts, which fall under a Parent account. Sub accounts have many advantages:
+Lumen Cloud supports the ability to create Sub accounts, which fall under a Parent account. Sub accounts have many advantages:
 
 * They are hierarchal - user account permissions flow from Parent account to Sub account, not up nor sideways 
 * They may be billed separately or to the Parent account 
@@ -15,7 +15,7 @@ CenturyLink Cloud supports the ability to create Sub accounts, which fall under
 
 ### Creating a Sub Account
 
-* On the left hand side of CenturyLink Cloud’s Control Portal, select Settings -> Sub Accounts.
+* On the left hand side of Lumen Cloud’s Control Portal, select Settings -> Sub Accounts.
 * Click the `+ create new account` button
 
 ### Organization Info
@@ -34,7 +34,7 @@ Further down in the page you wil see this section:
 
 ![sub-billing](../images/create-sub-account-billing.png)
 
-You may input a Default Primary DNS and a Default Secondary DNS IP address. This will be the DNS servers used when building a server in the platform.  Input IPv4 IP addresses into these fields. You may list your own environment's DNS servers, preferred public DNS servers, or the default CenturyLink Cloud datacenter DNS servers (172.17.1.26, 172.17.1.27). If you leave it blank, it will default to using the CenturyLink Cloud Datacenter DNS servers, which do allow for external DNS lookup.
+You may input a Default Primary DNS and a Default Secondary DNS IP address. This will be the DNS servers used when building a server in the platform.  Input IPv4 IP addresses into these fields. You may list your own environment's DNS servers, preferred public DNS servers, or the default Lumen Cloud datacenter DNS servers (172.17.1.26, 172.17.1.27). If you leave it blank, it will default to using the Lumen Cloud Datacenter DNS servers, which do allow for external DNS lookup.
 
 
 Bill to: Each Sub account generates an invoice. You have the option of submitting the invoice to the Parent account, or bill the Sub account directly.

diff --git a/Accounts & Users/creating-users.md b/Accounts & Users/creating-users.md
@@ -1,7 +1,7 @@
 {{{
   "title": "Creating Users",
   "date": "10-26-2017",
-  "author": "CenturyLink Cloud Customer Care",
+  "author": "Lumen Cloud Customer Care",
   "attachments": [],
   "contentIsHTML": false
 }}}
@@ -15,7 +15,7 @@ You can manage users on your account by going to the Control Portal > Settings >
 **Important Notes:** 
 * Permissions must be configured for a user after they are created in order to have access within the control. Learn more about [User Permissions](user-permissions.md).
 
-* A Control account username must be globally unique in the platform and cannot be reused, or otherwise reissued/migrated into a different Control account. If the user account is deleted, it cannot be reinstated or repurposed for another user. This constraint is currently an intentional design specification built into the CenturyLink Cloud Control platform.
+* A Control account username must be globally unique in the platform and cannot be reused, or otherwise reissued/migrated into a different Control account. If the user account is deleted, it cannot be reinstated or repurposed for another user. This constraint is currently an intentional design specification built into the Lumen Cloud Control platform.
 
 **Creating Users**
 1. Click the "Create New User" button.

diff --git a/Accounts & Users/practical-guide-for-using-roles.md b/Accounts & Users/practical-guide-for-using-roles.md
@@ -8,7 +8,7 @@
 
 ### Description
 
-CenturyLink Cloud currently offers eight roles that are available to assign users to. A brief description of each role is available on the [User Permissions page](../Accounts & Users/user-permissions.md), and a complete list of actions that can be performed by each role can be found in the [Role Permissions Matrix](../Accounts & Users/role-permissions-matrix.md). These roles were designed to align with job functions that are frequently found in many organizations, but they may not perfectly match up with the specific use cases or job titles found in your organization. This article will give some examples and guidelines for using roles and account hierarchies for managing security and access in the Control Portal.
+Lumen Cloud currently offers eight roles that are available to assign users to. A brief description of each role is available on the [User Permissions page](../Accounts & Users/user-permissions.md), and a complete list of actions that can be performed by each role can be found in the [Role Permissions Matrix](../Accounts & Users/role-permissions-matrix.md). These roles were designed to align with job functions that are frequently found in many organizations, but they may not perfectly match up with the specific use cases or job titles found in your organization. This article will give some examples and guidelines for using roles and account hierarchies for managing security and access in the Control Portal.
 
 ### Example Organizational Role Breakdown
 

diff --git a/Accounts & Users/role-permissions-matrix.md b/Accounts & Users/role-permissions-matrix.md
@@ -9,8 +9,8 @@
 
 ### Audience
 
-Any user of CenturyLink Cloud products and services.
+Any user of Lumen Cloud products and services.
 
 ### Overview
 
-View the [Role Permission Matrix](//www.ctl.io/role-permissions-matrix/) for CenturyLink Cloud.
+View the [Role Permission Matrix](//www.ctl.io/role-permissions-matrix/) for Lumen Cloud.
diff --git a/Accounts & Users/roles-faq.md b/Accounts & Users/roles-faq.md
@@ -8,7 +8,7 @@
 
 ### Description
 
-CenturyLink Cloud uses role-based access control (RBAC) for restricting system access for specific areas of the platform to authorized users only. There are currently eight roles available to choose from with varying degrees of access. These roles were designed to align with job functions that are generally found in most organizations.
+Lumen Cloud uses role-based access control (RBAC) for restricting system access for specific areas of the platform to authorized users only. There are currently eight roles available to choose from with varying degrees of access. These roles were designed to align with job functions that are generally found in most organizations.
 
 This FAQ addresses many commonly asked questions about roles. For more information about how these roles may best be used in the context of your organization, see the KB article titled [Practical Guide for Using Roles](../Accounts & Users/practical-guide-for-using-roles.md).
 
@@ -24,7 +24,7 @@ A: For a complete list of actions that can be performed in the platform broken d
 
 **Q: How are these roles different from the previous ones that were available?**
 
-A: Previously, CenturyLink Cloud offered a very small set of roles (called "area permissions") that allowed for broadly restricting large parts of the Control Portal for a few specialty users (such as a Billing Administrator). To perform the vast majority of activities in the platform, it was required to be an Account Administrator, which often meant opening up more permissions than were required for a user to complete their necessary tasks. The newer implementation supports more granularity of control as well as the ability for some users to have read-only access to some areas without the ability to change the configuration. Information on migrating existing users into the new roles model can be found in the [Roles Migration Guide](roles-migration-guide.md).
+A: Previously, Lumen Cloud offered a very small set of roles (called "area permissions") that allowed for broadly restricting large parts of the Control Portal for a few specialty users (such as a Billing Administrator). To perform the vast majority of activities in the platform, it was required to be an Account Administrator, which often meant opening up more permissions than were required for a user to complete their necessary tasks. The newer implementation supports more granularity of control as well as the ability for some users to have read-only access to some areas without the ability to change the configuration. Information on migrating existing users into the new roles model can be found in the [Roles Migration Guide](roles-migration-guide.md).
 
 **Q: Can I change a user's role through the API?**
 

diff --git a/Accounts & Users/roles-migration-guide.md b/Accounts & Users/roles-migration-guide.md
@@ -8,7 +8,7 @@
 
 ### Description
 
-CenturyLink Cloud uses role-based access control (RBAC) for restricting system access for specific areas of the platform to authorized users only. Prior to the release of the currently available eight roles that are designed to align with job functions generally found in most organizations, there was a much smaller and less scalable role set that resulted in a number of users being given more access than they needed to perform their job duties. The guidelines below will help customers migrate from using the four legacy roles to leveraging the eight new more granular ones.
+Lumen Cloud uses role-based access control (RBAC) for restricting system access for specific areas of the platform to authorized users only. Prior to the release of the currently available eight roles that are designed to align with job functions generally found in most organizations, there was a much smaller and less scalable role set that resulted in a number of users being given more access than they needed to perform their job duties. The guidelines below will help customers migrate from using the four legacy roles to leveraging the eight new more granular ones.
 
 ### Existing Roles Mapping