search

F5Networks / f5-telemetry-streaming

F5 BIG-IP Telemetry Streaming
Apache License 2.0
56 stars 23 forks source link

Configuration should survive an upgrade #57

Open ryn9 opened 4 years ago

ryn9 commented 4 years ago

Is your feature request related to a problem? Please describe.

N/A

Describe the solution you'd like

TS configuration should survive an upgrade

Describe alternatives you've considered

Re-declaring after an upgrade is not optimal

Additional context

Per the current docs...

What if I upgrade my BIG-IP system, how to I migrate my Telemetry Streaming configuration?

When you upgrade your BIG-IP system, you simply install Telemetry Streaming on the upgraded BIG-IP system and re-deploy your declaration. For example, you installed Telemetry Streaming on your BIG-IP running version 13.1 and deployed a declaration. You decide to upgrade your BIG-IP system to 14.1. Once the upgrade to 14.1 is complete, you must install Telemetry Streaming on the BIG-IP. After you install Telemetry Streaming, you send the same declaration you used pre-upgrade to the 13.1 BIG-IP system. Your upgraded BIG-IP will then have the same configuration as the previous version.

dstokesf5 commented 4 years ago

@ryn9 Did you encounter some specific issues while upgrading a BIG-IP, or is this request based only on that documentation entry? I will be setting up my own experiments. However, if you have already tried this, I would love to get some more information.

The main issue I could see with upgrading a BIG-IP with Telemetry Streaming is possible corruption of the rest storage. This is functionality provided by the framework that Telemetry Streaming relies on. If there are problems there, we may not have a lot of options to correct it from within Telemetry Streaming.

ryn9 commented 4 years ago

@dstokesf5 this request is based off the documentation. please have documentation updated: If no longer true If there are only specific TS versions impacted If there are only specific BIGIP versions impacted

walterk82 commented 3 years ago

This behavior is confusing because it operates so much differently than AS3. AS3 also uses ltm datagroups as the persistent store rather than the internal rest storage.

dstokesf5 commented 3 years ago

Thank you for your feedback. I have added this feature request to our internal product backlog as AUTOTOOL-2598.

dashwood8691 commented 2 years ago

This seems to be fixed by ID 929213 (TMOS side fix).

After the fix, a new DB key iapplxrpm.timeout can be configured to extend the RPM build timeout. You may refer to the Bug Tracker for further information.

Bug ID 929213: iAppLX packages not rolled forward after BIG-IP upgrade

K04548517: F5 Telemetry Streaming responds with code 404 after BIG-IP configuration is restored from UCS