This article provides helpful information regarding the AppFog Product Retirement scheduled for Friday, June 29 2018 at 12:00 AM US Pacific Time (UTC-8). (Effectively Midnight on Thursday, June 28).
Does my AppFog account have any active applications and/or services running on AppFog?
To determine whether any applications and/or services are running, you must login to your AppFog account here: https://appfog.ctl.io/. After logging in, the AppFog dashboard displays a overview of all AppFog resource usage and charges to your account.
If the Current Hour charges are greater than $0/hour, than the running application and/or service instances must be deleted or migrated to another Cloud provider before June 29, 2018. If the Current Hour charges are equal to $0/hour, no further action is required.
What will happen to my AppFog applications and services on June 29, 2018?
Any application or service instances hosted on AppFog will no longer be available on June 29, 2018, including Relational DB database instances created via the Cloud Foundry CLI using the
cf create-service command. You are responsible for migrating your applications and data. CenturyLink is not responsible for any loss of data or loss of access to data after AppFog is retired.
Where should I migrate my AppFog applications and services?
We recommend migrating to a Certified Cloud Foundry platform. Certified Cloud Foundry platforms use the same core Cloud Foundry software to ensure application and skill portability across providers.
Two (2) popular Cloud Foundry platforms are listed below, but other options are listed on the certified platforms list.
How do I migrate my applications and data?
Note: This is not a comprehensive migration guide. Your specific migration steps may vary from those outlined below.
Once you have created an account your target (destination) Cloud Foundry platform, follow the steps below as high-level migration outline. As with any migration, first deploy and test the application in the target environment before re-directing inbound traffic to the migrated application. The Cloud Foundry CLI is required to perform the steps below.
General Migration Steps:
Connect to the AppFog region where your application and/or services are currently hosted (source). See the Login to AppFog using the Cloud Foundry CLI KB article for instructions.
Identify any database services your app is using. From the CLI command line, use
cf services | grep <APP_NAME>(where <APP_NAME> is the name of your application). You will need to migrate each database used by your application.
Recreate the database services on the target (destination) Cloud Foundry platform. Login to the target Cloud Foundry region (see the Login Using CLI KB article from Step 1).
Migrate the data from the existing (source) AppFog database to the target (destination) database. The Migrating a Database in Cloud Foundry guide is helpful.
Deploy your app to the target (destination) Cloud Foundry region.
- If you have a
manifest.ymlfile, simply run the
cf pushcommand. Refer to this article on Using a Manifest File.
- If you don't have a
manifest.ymlfile, execute the following commands:
cf push <APP_NAME> --no-start cf bind <APP_NAME> <SERVICE_NAME> cf start <APP_NAME>
- If you have a
After you have migrated your application(s) and database(s), you should test thoroughly to confirm they work as expected.
Finally, after your testing is complete, redirect traffic from your original (source) app to your target (destination) app by updating your CNAME records and configure the "route" to your target app. This Cloud Foundry article is a good overview for configuring "routes".
cf help will list all available Cloud Foundry CLI commands. For more information, see the Using Cloud Foundry CLI Tool KB article.
Can I get assistance with migrating my AppFog applications and services?
The CenturyLink Support team can not assist with outbound migrations, but will assist with any questions/issues relating to applications or databases hosted on AppFog.
You can submit support tickets via CenturyLink Cloud support or by emailing firstname.lastname@example.org. The response SLA is based on the support option for your account. Keep in mind, most Developer Support plans have an eight (8) hour response SLA.