Topics

cflinuxfs2 --> cflinuxfs3 transition

Josh Collins
 

Hi CF Community,


As of cf-deployment v6.0 (Nov 5, 2018) cf-d will deploy with support for both cflinuxfs2 and cflinuxfs3 stacks (with cflinuxfs2 continuing to be the default stack).


In cf-deployment v7.0, to be published early in December, cflinuxfs3 will become the default stack (cflinuxfs2 will continue to be supported, but will no longer be default).


Once cflinuxfs3 is the default, new apps that are pushed will be staged with cflinuxfs3 unless new apps that are pushed set the stack explicitly to cflinuxfs2. The stack property is “sticky,” so all existing apps will remain associated with cflinuxfs2 unless they are manually migrated to cflinuxfs3 (or deleted and re-created).


Both stacks will be supported for several months to allow app developers and operators time to migrate all apps from cflinuxfs2 to cflinuxfs3.


Canonical will cease support for Ubuntu 14.04 LTS (Trusty) in April 2019. Therefore, at the end of March 2019, cflinuxfs2 will be removed from cf-deployment and all apps that haven’t been migrated will crash when the foundation is upgraded.


Thanks!

Josh Collins & Stephen Levine


Krannich, Bernd
 

Hi Josh, all,

 

I assume many people are currently in the process of moving off of cflinuxfs2 to cflinuxfs3.

 

I was trying to figure out a good (and quick) way to see which apps haven’t done the move yet. Looking into the Cloud Controller tables, I was hoping that the apps table would contain a reference to the stack or at least the buildpack table (which has a reference to the stack), but it seems like this is not how things work.

 

What are the additional Cloud Controller tables to consider when formulating a join to answer the question: Which apps are still on cflinuxfs2?

 

Thanks in advance,

Bernd

 

From: <cf-dev@...> on behalf of Josh Collins <jcollins@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Saturday, 3. November 2018 at 04:40
To: "cf-dev@..." <cf-dev@...>
Subject: [cf-dev] cflinuxfs2 --> cflinuxfs3 transition

 

Hi CF Community,

 

As of cf-deployment v6.0 (Nov 5, 2018) cf-d will deploy with support for both cflinuxfs2 and cflinuxfs3 stacks (with cflinuxfs2 continuing to be the default stack).

 

In cf-deployment v7.0, to be published early in December, cflinuxfs3 will become the default stack (cflinuxfs2 will continue to be supported, but will no longer be default).

 

Once cflinuxfs3 is the default, new apps that are pushed will be staged with cflinuxfs3 unless new apps that are pushed set the stack explicitly to cflinuxfs2. The stack property is “sticky,” so all existing apps will remain associated with cflinuxfs2 unless they are manually migrated to cflinuxfs3 (or deleted and re-created).

 

Both stacks will be supported for several months to allow app developers and operators time to migrate all apps from cflinuxfs2 to cflinuxfs3.

 

Canonical will cease support for Ubuntu 14.04 LTS (Trusty) in April 2019. Therefore, at the end of March 2019, cflinuxfs2 will be removed from cf-deployment and all apps that haven’t been migrated will crash when the foundation is upgraded.

 

Thanks!

Josh Collins & Stephen Levine

 

Stanislav German-Evtushenko
 

Hi Bernd,

You may want to try this https://github.com/rakutentech/cf-tools/blob/master/cf-applist.sh

Best regards,
Stanislav

Krannich, Bernd
 

Hi Stanislav,

 

Thank you very much for the pointer. I forgot to mention my reason to look into the Cloud Controller tables directly: It might take me quite some time to pull the data via the Cloud Controller API. So if possible, I’d like to take a more direct route to collect the data.

 

Thanks,

Bernd

 

From: <cf-dev@...> on behalf of Stanislav German-Evtushenko <s.germanevtushenko@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Thursday, 31. January 2019 at 15:32
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] cflinuxfs2 --> cflinuxfs3 transition

 

Hi Bernd,

You may want to try this https://github.com/rakutentech/cf-tools/blob/master/cf-applist.sh

Best regards,
Stanislav

Elliott Shanks
 

Bernd,

My name is Elliott Shanks and I'm a new PM on the CF Core Buildpacks Team. We have recently introduced a cf-cli plugin called stack-auditor which would accomplish exactly what you are looking to do. It includes an audit command (audit-stack) to show all applications and their respective stacks as well as a command to change the stack (change-stack) of any particular app. You can download the plugin at:


Not only would I recommend this approach for your current needs, but would love to gather some feedback from you about the stack-auditor plugin after you have had a chance to use it. We are actively contributing to the plugin and would welcome any feedback in an attempt to make this a perfect tool for everyone who still needs to migrate applications over to cflinuxfs3.

Feel free to let me know if you have any questions while using the tool. I'd be happy to help.

Thanks a bunch,
Elliott Shanks


On Thu, Jan 31, 2019 at 7:04 AM Krannich, Bernd <bernd.krannich@...> wrote:

Hi Josh, all,

 

I assume many people are currently in the process of moving off of cflinuxfs2 to cflinuxfs3.

 

I was trying to figure out a good (and quick) way to see which apps haven’t done the move yet. Looking into the Cloud Controller tables, I was hoping that the apps table would contain a reference to the stack or at least the buildpack table (which has a reference to the stack), but it seems like this is not how things work.

 

What are the additional Cloud Controller tables to consider when formulating a join to answer the question: Which apps are still on cflinuxfs2?

 

Thanks in advance,

Bernd

 

From: <cf-dev@...> on behalf of Josh Collins <jcollins@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Saturday, 3. November 2018 at 04:40
To: "cf-dev@..." <cf-dev@...>
Subject: [cf-dev] cflinuxfs2 --> cflinuxfs3 transition

 

Hi CF Community,

 

As of cf-deployment v6.0 (Nov 5, 2018) cf-d will deploy with support for both cflinuxfs2 and cflinuxfs3 stacks (with cflinuxfs2 continuing to be the default stack).

 

In cf-deployment v7.0, to be published early in December, cflinuxfs3 will become the default stack (cflinuxfs2 will continue to be supported, but will no longer be default).

 

Once cflinuxfs3 is the default, new apps that are pushed will be staged with cflinuxfs3 unless new apps that are pushed set the stack explicitly to cflinuxfs2. The stack property is “sticky,” so all existing apps will remain associated with cflinuxfs2 unless they are manually migrated to cflinuxfs3 (or deleted and re-created).

 

Both stacks will be supported for several months to allow app developers and operators time to migrate all apps from cflinuxfs2 to cflinuxfs3.

 

Canonical will cease support for Ubuntu 14.04 LTS (Trusty) in April 2019. Therefore, at the end of March 2019, cflinuxfs2 will be removed from cf-deployment and all apps that haven’t been migrated will crash when the foundation is upgraded.

 

Thanks!

Josh Collins & Stephen Levine

 



--
Respectfully, 

Elliott Shanks
Manager, Engineering

Krannich, Bernd
 

Hi Elliott,

 

Nice to e-meet you and thank you very much for the pointer!

 

Finding out how to build the plugin, I created a PR adding this part to the readme: https://github.com/cloudfoundry/stack-auditor/pull/2

 

Additionally, I have tried the plugin on our biggest Cloud Foundry landscape and here is my feedback:

  • The plugin took a bit longer than 30 mins to collect the overall status of the system using `cf audit-stack` and an admin user. This is more a result of the size of our Cloud Foundry landscape. So, I guess even knowing about the plugin I’d still wish for a SQL join that I hope would give me the same overview with what I’d hope to be a much shorter runtime.
  • I think the plugin is still a nice self-service for individual org owners planning and executing a switch, so thank you very much for providing it!
  • Regarding the output, one use case I keep having for any such tool is to be able to dump things into a CSV so that I can analyze the data in Excel later on. Here, it would help if either the plugin would offer a special output format or offer an option to quote “nasty” things like orgs and spaces containing blanks.

 

I hope this helps as an additional input.

 

Thanks & Regards,

Bernd

 

From: <cf-dev@...> on behalf of Elliott Shanks <eshanks@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Thursday, 31. January 2019 at 16:08
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] cflinuxfs2 --> cflinuxfs3 transition

 

Bernd,

 

My name is Elliott Shanks and I'm a new PM on the CF Core Buildpacks Team. We have recently introduced a cf-cli plugin called stack-auditor which would accomplish exactly what you are looking to do. It includes an audit command (audit-stack) to show all applications and their respective stacks as well as a command to change the stack (change-stack) of any particular app. You can download the plugin at:

 

 

Not only would I recommend this approach for your current needs, but would love to gather some feedback from you about the stack-auditor plugin after you have had a chance to use it. We are actively contributing to the plugin and would welcome any feedback in an attempt to make this a perfect tool for everyone who still needs to migrate applications over to cflinuxfs3.

 

Feel free to let me know if you have any questions while using the tool. I'd be happy to help.

 

Thanks a bunch,

Elliott Shanks

 

 

On Thu, Jan 31, 2019 at 7:04 AM Krannich, Bernd <bernd.krannich@...> wrote:

Hi Josh, all,

 

I assume many people are currently in the process of moving off of cflinuxfs2 to cflinuxfs3.

 

I was trying to figure out a good (and quick) way to see which apps haven’t done the move yet. Looking into the Cloud Controller tables, I was hoping that the apps table would contain a reference to the stack or at least the buildpack table (which has a reference to the stack), but it seems like this is not how things work.

 

What are the additional Cloud Controller tables to consider when formulating a join to answer the question: Which apps are still on cflinuxfs2?

 

Thanks in advance,

Bernd

 

From: <cf-dev@...> on behalf of Josh Collins <jcollins@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Saturday, 3. November 2018 at 04:40
To: "cf-dev@..." <cf-dev@...>
Subject: [cf-dev] cflinuxfs2 --> cflinuxfs3 transition

 

Hi CF Community,

 

As of cf-deployment v6.0 (Nov 5, 2018) cf-d will deploy with support for both cflinuxfs2 and cflinuxfs3 stacks (with cflinuxfs2 continuing to be the default stack).

 

In cf-deployment v7.0, to be published early in December, cflinuxfs3 will become the default stack (cflinuxfs2 will continue to be supported, but will no longer be default).

 

Once cflinuxfs3 is the default, new apps that are pushed will be staged with cflinuxfs3 unless new apps that are pushed set the stack explicitly to cflinuxfs2. The stack property is “sticky,” so all existing apps will remain associated with cflinuxfs2 unless they are manually migrated to cflinuxfs3 (or deleted and re-created).

 

Both stacks will be supported for several months to allow app developers and operators time to migrate all apps from cflinuxfs2 to cflinuxfs3.

 

Canonical will cease support for Ubuntu 14.04 LTS (Trusty) in April 2019. Therefore, at the end of March 2019, cflinuxfs2 will be removed from cf-deployment and all apps that haven’t been migrated will crash when the foundation is upgraded.

 

Thanks!

Josh Collins & Stephen Levine

 


 

--

Respectfully, 

 

Elliott Shanks

Manager, Engineering

Stanislav German-Evtushenko
 

Hi Bernd,

If performance is a concern how about using cfdot?
`cfdot desired-lrps | jq -r '[ .log_guid, .rootfs ] | @tsv`
will give you (instantly):
```
7bc7eef4-121d-4879-bac1-d738c54faa3a    preloaded:cflinuxfs2
2d04940f-ceb1-4884-8cf7-47fd70a0a39c    preloaded:cflinuxfs2
c3c18f43-58df-429d-bb2e-895e621c1a6d    preloaded:cflinuxfs3
5b070c85-85cd-4717-bb59-ce3fd889efad    docker:///xxx/yyy#latest
```
Where the first field is application guid.

Regards,
Stanislav

Connor Braa
 

Hi Bernd!

If you need to use SQL to figure out which apps still use the old stack, you'll want to join apps across the buildpack_lifecycle_data table's app_guid column. but there are lots of possible complications in terms of treating that as a source of truth. 

For one, entries in that table where `stack` is nil indicate that the default stack should be used, but when upgrading your stack, you may have changed the default from cflinuxfs2 to 3, and in doing so made it very difficult to tell which stack is actually running for a given app (ie whether you'll need to restage). The ruby code handling that table is also pretty nontrivial, so there _might_ be some edge cases around droplet copying that mean the result of a straightforward join won't get you exactly what you need.

Generally, the SQL approach is going to be a bit error prone, but if your deployment is very big, I understand why it might be a necessary first step. Stanislav's approach using cfdot is going to get you much closer to the absolute truth of what is running cflinuxfs2, and a good audit will probably use both at different stages. 

Best,
Connor


On Thu, Jan 31, 2019 at 5:04 AM Krannich, Bernd <bernd.krannich@...> wrote:

Hi Josh, all,

 

I assume many people are currently in the process of moving off of cflinuxfs2 to cflinuxfs3.

 

I was trying to figure out a good (and quick) way to see which apps haven’t done the move yet. Looking into the Cloud Controller tables, I was hoping that the apps table would contain a reference to the stack or at least the buildpack table (which has a reference to the stack), but it seems like this is not how things work.

 

What are the additional Cloud Controller tables to consider when formulating a join to answer the question: Which apps are still on cflinuxfs2?

 

Thanks in advance,

Bernd

 

From: <cf-dev@...> on behalf of Josh Collins <jcollins@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Saturday, 3. November 2018 at 04:40
To: "cf-dev@..." <cf-dev@...>
Subject: [cf-dev] cflinuxfs2 --> cflinuxfs3 transition

 

Hi CF Community,

 

As of cf-deployment v6.0 (Nov 5, 2018) cf-d will deploy with support for both cflinuxfs2 and cflinuxfs3 stacks (with cflinuxfs2 continuing to be the default stack).

 

In cf-deployment v7.0, to be published early in December, cflinuxfs3 will become the default stack (cflinuxfs2 will continue to be supported, but will no longer be default).

 

Once cflinuxfs3 is the default, new apps that are pushed will be staged with cflinuxfs3 unless new apps that are pushed set the stack explicitly to cflinuxfs2. The stack property is “sticky,” so all existing apps will remain associated with cflinuxfs2 unless they are manually migrated to cflinuxfs3 (or deleted and re-created).

 

Both stacks will be supported for several months to allow app developers and operators time to migrate all apps from cflinuxfs2 to cflinuxfs3.

 

Canonical will cease support for Ubuntu 14.04 LTS (Trusty) in April 2019. Therefore, at the end of March 2019, cflinuxfs2 will be removed from cf-deployment and all apps that haven’t been migrated will crash when the foundation is upgraded.

 

Thanks!

Josh Collins & Stephen Levine

 

Krannich, Bernd
 

Hi Connor, Hi Stanislav,

 

Thank you very much for your suggestions!

 

I tried out both of them now and can confirm that both are much quicker (sub-second for the SQL, few seconds for cfdot) than going via the Cloud Controller (either self-scripted or via the stack-auditor plugin).

 

And, I think I can confirm the general recommendations given in this thread:

  • Use the existing means via Cloud Controller if you are responsible for apps in one or few CF orgs
  • Use cfdot and the Cloud Controller tables to get an overview on the overall state of the system if you have the corresponding admin access

 

Thank you very much again to everybody for your suggestions!

 

Regards,

Bernd

 

From: <cf-dev@...> on behalf of Connor Braa <cbraa@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Friday, 1. February 2019 at 21:01
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] cflinuxfs2 --> cflinuxfs3 transition

 

Hi Bernd!

 

If you need to use SQL to figure out which apps still use the old stack, you'll want to join apps across the buildpack_lifecycle_data table's app_guid column. but there are lots of possible complications in terms of treating that as a source of truth. 

 

For one, entries in that table where `stack` is nil indicate that the default stack should be used, but when upgrading your stack, you may have changed the default from cflinuxfs2 to 3, and in doing so made it very difficult to tell which stack is actually running for a given app (ie whether you'll need to restage). The ruby code handling that table is also pretty nontrivial, so there _might_ be some edge cases around droplet copying that mean the result of a straightforward join won't get you exactly what you need.

 

Generally, the SQL approach is going to be a bit error prone, but if your deployment is very big, I understand why it might be a necessary first step. Stanislav's approach using cfdot is going to get you much closer to the absolute truth of what is running cflinuxfs2, and a good audit will probably use both at different stages. 

 

Best,

Connor

 

On Thu, Jan 31, 2019 at 5:04 AM Krannich, Bernd <bernd.krannich@...> wrote:

Hi Josh, all,

 

I assume many people are currently in the process of moving off of cflinuxfs2 to cflinuxfs3.

 

I was trying to figure out a good (and quick) way to see which apps haven’t done the move yet. Looking into the Cloud Controller tables, I was hoping that the apps table would contain a reference to the stack or at least the buildpack table (which has a reference to the stack), but it seems like this is not how things work.

 

What are the additional Cloud Controller tables to consider when formulating a join to answer the question: Which apps are still on cflinuxfs2?

 

Thanks in advance,

Bernd

 

From: <cf-dev@...> on behalf of Josh Collins <jcollins@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Saturday, 3. November 2018 at 04:40
To: "cf-dev@..." <cf-dev@...>
Subject: [cf-dev] cflinuxfs2 --> cflinuxfs3 transition

 

Hi CF Community,

 

As of cf-deployment v6.0 (Nov 5, 2018) cf-d will deploy with support for both cflinuxfs2 and cflinuxfs3 stacks (with cflinuxfs2 continuing to be the default stack).

 

In cf-deployment v7.0, to be published early in December, cflinuxfs3 will become the default stack (cflinuxfs2 will continue to be supported, but will no longer be default).

 

Once cflinuxfs3 is the default, new apps that are pushed will be staged with cflinuxfs3 unless new apps that are pushed set the stack explicitly to cflinuxfs2. The stack property is “sticky,” so all existing apps will remain associated with cflinuxfs2 unless they are manually migrated to cflinuxfs3 (or deleted and re-created).

 

Both stacks will be supported for several months to allow app developers and operators time to migrate all apps from cflinuxfs2 to cflinuxfs3.

 

Canonical will cease support for Ubuntu 14.04 LTS (Trusty) in April 2019. Therefore, at the end of March 2019, cflinuxfs2 will be removed from cf-deployment and all apps that haven’t been migrated will crash when the foundation is upgraded.

 

Thanks!

Josh Collins & Stephen Levine

 

Elliott Shanks
 

Bernd,

Thank you so much for using the stack-auditor plugin and providing feedback. I've got a story in our tracker for your pull request: https://www.pivotaltracker.com/story/show/163698676.

We have been aware of some potential performance limitations for the audit-stack command on large orgs and intend to see how we can reduce that response time. I am a fan of your export idea as well. I'd love to understand your use case a little further in order to make stack-auditor a one-and-done tool for cflinuxfs3 migration purposes. Would you be open to a 30 minute conversation at some point in the near future? 

Thanks again!

Elliott Shanks


On Fri, Feb 1, 2019 at 10:38 AM Krannich, Bernd <bernd.krannich@...> wrote:

Hi Elliott,

 

Nice to e-meet you and thank you very much for the pointer!

 

Finding out how to build the plugin, I created a PR adding this part to the readme: https://github.com/cloudfoundry/stack-auditor/pull/2

 

Additionally, I have tried the plugin on our biggest Cloud Foundry landscape and here is my feedback:

  • The plugin took a bit longer than 30 mins to collect the overall status of the system using `cf audit-stack` and an admin user. This is more a result of the size of our Cloud Foundry landscape. So, I guess even knowing about the plugin I’d still wish for a SQL join that I hope would give me the same overview with what I’d hope to be a much shorter runtime.
  • I think the plugin is still a nice self-service for individual org owners planning and executing a switch, so thank you very much for providing it!
  • Regarding the output, one use case I keep having for any such tool is to be able to dump things into a CSV so that I can analyze the data in Excel later on. Here, it would help if either the plugin would offer a special output format or offer an option to quote “nasty” things like orgs and spaces containing blanks.

 

I hope this helps as an additional input.

 

Thanks & Regards,

Bernd

 

From: <cf-dev@...> on behalf of Elliott Shanks <eshanks@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Thursday, 31. January 2019 at 16:08
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] cflinuxfs2 --> cflinuxfs3 transition

 

Bernd,

 

My name is Elliott Shanks and I'm a new PM on the CF Core Buildpacks Team. We have recently introduced a cf-cli plugin called stack-auditor which would accomplish exactly what you are looking to do. It includes an audit command (audit-stack) to show all applications and their respective stacks as well as a command to change the stack (change-stack) of any particular app. You can download the plugin at:

 

 

Not only would I recommend this approach for your current needs, but would love to gather some feedback from you about the stack-auditor plugin after you have had a chance to use it. We are actively contributing to the plugin and would welcome any feedback in an attempt to make this a perfect tool for everyone who still needs to migrate applications over to cflinuxfs3.

 

Feel free to let me know if you have any questions while using the tool. I'd be happy to help.

 

Thanks a bunch,

Elliott Shanks

 

 

On Thu, Jan 31, 2019 at 7:04 AM Krannich, Bernd <bernd.krannich@...> wrote:

Hi Josh, all,

 

I assume many people are currently in the process of moving off of cflinuxfs2 to cflinuxfs3.

 

I was trying to figure out a good (and quick) way to see which apps haven’t done the move yet. Looking into the Cloud Controller tables, I was hoping that the apps table would contain a reference to the stack or at least the buildpack table (which has a reference to the stack), but it seems like this is not how things work.

 

What are the additional Cloud Controller tables to consider when formulating a join to answer the question: Which apps are still on cflinuxfs2?

 

Thanks in advance,

Bernd

 

From: <cf-dev@...> on behalf of Josh Collins <jcollins@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Saturday, 3. November 2018 at 04:40
To: "cf-dev@..." <cf-dev@...>
Subject: [cf-dev] cflinuxfs2 --> cflinuxfs3 transition

 

Hi CF Community,

 

As of cf-deployment v6.0 (Nov 5, 2018) cf-d will deploy with support for both cflinuxfs2 and cflinuxfs3 stacks (with cflinuxfs2 continuing to be the default stack).

 

In cf-deployment v7.0, to be published early in December, cflinuxfs3 will become the default stack (cflinuxfs2 will continue to be supported, but will no longer be default).

 

Once cflinuxfs3 is the default, new apps that are pushed will be staged with cflinuxfs3 unless new apps that are pushed set the stack explicitly to cflinuxfs2. The stack property is “sticky,” so all existing apps will remain associated with cflinuxfs2 unless they are manually migrated to cflinuxfs3 (or deleted and re-created).

 

Both stacks will be supported for several months to allow app developers and operators time to migrate all apps from cflinuxfs2 to cflinuxfs3.

 

Canonical will cease support for Ubuntu 14.04 LTS (Trusty) in April 2019. Therefore, at the end of March 2019, cflinuxfs2 will be removed from cf-deployment and all apps that haven’t been migrated will crash when the foundation is upgraded.

 

Thanks!

Josh Collins & Stephen Levine

 


 

--

Respectfully, 

 

Elliott Shanks

Manager, Engineering



--
Respectfully, 

Elliott Shanks
Manager, Engineering

Krannich, Bernd
 

Hi Elliott,

 

Yes, sure. Feel free to schedule a meeting with me.

 

Thanks,

Bernd

 

From: <cf-dev@...> on behalf of Elliott Shanks <eshanks@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Monday, 4. February 2019 at 16:19
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] cflinuxfs2 --> cflinuxfs3 transition

 

Bernd,

 

Thank you so much for using the stack-auditor plugin and providing feedback. I've got a story in our tracker for your pull request: https://www.pivotaltracker.com/story/show/163698676.

 

We have been aware of some potential performance limitations for the audit-stack command on large orgs and intend to see how we can reduce that response time. I am a fan of your export idea as well. I'd love to understand your use case a little further in order to make stack-auditor a one-and-done tool for cflinuxfs3 migration purposes. Would you be open to a 30 minute conversation at some point in the near future? 

 

Thanks again!

 

Elliott Shanks

 

On Fri, Feb 1, 2019 at 10:38 AM Krannich, Bernd <bernd.krannich@...> wrote:

Hi Elliott,

 

Nice to e-meet you and thank you very much for the pointer!

 

Finding out how to build the plugin, I created a PR adding this part to the readme: https://github.com/cloudfoundry/stack-auditor/pull/2

 

Additionally, I have tried the plugin on our biggest Cloud Foundry landscape and here is my feedback:

  • The plugin took a bit longer than 30 mins to collect the overall status of the system using `cf audit-stack` and an admin user. This is more a result of the size of our Cloud Foundry landscape. So, I guess even knowing about the plugin I’d still wish for a SQL join that I hope would give me the same overview with what I’d hope to be a much shorter runtime.
  • I think the plugin is still a nice self-service for individual org owners planning and executing a switch, so thank you very much for providing it!
  • Regarding the output, one use case I keep having for any such tool is to be able to dump things into a CSV so that I can analyze the data in Excel later on. Here, it would help if either the plugin would offer a special output format or offer an option to quote “nasty” things like orgs and spaces containing blanks.

 

I hope this helps as an additional input.

 

Thanks & Regards,

Bernd

 

From: <cf-dev@...> on behalf of Elliott Shanks <eshanks@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Thursday, 31. January 2019 at 16:08
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] cflinuxfs2 --> cflinuxfs3 transition

 

Bernd,

 

My name is Elliott Shanks and I'm a new PM on the CF Core Buildpacks Team. We have recently introduced a cf-cli plugin called stack-auditor which would accomplish exactly what you are looking to do. It includes an audit command (audit-stack) to show all applications and their respective stacks as well as a command to change the stack (change-stack) of any particular app. You can download the plugin at:

 

 

Not only would I recommend this approach for your current needs, but would love to gather some feedback from you about the stack-auditor plugin after you have had a chance to use it. We are actively contributing to the plugin and would welcome any feedback in an attempt to make this a perfect tool for everyone who still needs to migrate applications over to cflinuxfs3.

 

Feel free to let me know if you have any questions while using the tool. I'd be happy to help.

 

Thanks a bunch,

Elliott Shanks

 

 

On Thu, Jan 31, 2019 at 7:04 AM Krannich, Bernd <bernd.krannich@...> wrote:

Hi Josh, all,

 

I assume many people are currently in the process of moving off of cflinuxfs2 to cflinuxfs3.

 

I was trying to figure out a good (and quick) way to see which apps haven’t done the move yet. Looking into the Cloud Controller tables, I was hoping that the apps table would contain a reference to the stack or at least the buildpack table (which has a reference to the stack), but it seems like this is not how things work.

 

What are the additional Cloud Controller tables to consider when formulating a join to answer the question: Which apps are still on cflinuxfs2?

 

Thanks in advance,

Bernd

 

From: <cf-dev@...> on behalf of Josh Collins <jcollins@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Saturday, 3. November 2018 at 04:40
To: "cf-dev@..." <cf-dev@...>
Subject: [cf-dev] cflinuxfs2 --> cflinuxfs3 transition

 

Hi CF Community,

 

As of cf-deployment v6.0 (Nov 5, 2018) cf-d will deploy with support for both cflinuxfs2 and cflinuxfs3 stacks (with cflinuxfs2 continuing to be the default stack).

 

In cf-deployment v7.0, to be published early in December, cflinuxfs3 will become the default stack (cflinuxfs2 will continue to be supported, but will no longer be default).

 

Once cflinuxfs3 is the default, new apps that are pushed will be staged with cflinuxfs3 unless new apps that are pushed set the stack explicitly to cflinuxfs2. The stack property is “sticky,” so all existing apps will remain associated with cflinuxfs2 unless they are manually migrated to cflinuxfs3 (or deleted and re-created).

 

Both stacks will be supported for several months to allow app developers and operators time to migrate all apps from cflinuxfs2 to cflinuxfs3.

 

Canonical will cease support for Ubuntu 14.04 LTS (Trusty) in April 2019. Therefore, at the end of March 2019, cflinuxfs2 will be removed from cf-deployment and all apps that haven’t been migrated will crash when the foundation is upgraded.

 

Thanks!

Josh Collins & Stephen Levine

 


 

--

Respectfully, 

 

Elliott Shanks

Manager, Engineering


 

--

Respectfully, 

 

Elliott Shanks

Manager, Engineering