Difference between revisions of "Schedules Direct URL Change"
m (remove unused hostname) |
(Last touchs up b4 mentioning on the -users list.) |
||
Line 4: | Line 4: | ||
options for MythTV users. | options for MythTV users. | ||
− | Ideally, there would be a DNS change and the IP for the existing | + | Ideally, there would be a DNS change and the IP address for the existing (hard coded) hostname |
− | hard | + | would be pointed to a new IP address and no action would be |
required by MythTV SD users. However, the owner of that hostname (which | required by MythTV SD users. However, the owner of that hostname (which | ||
− | is not SD) could 'retire' that DNS record at any time. | + | is not SD) could 'retire' that DNS record at any time leaving MythTV SD users |
+ | out of service. | ||
== What '''must''' users do prior to November 1st, 2014? == | == What '''must''' users do prior to November 1st, 2014? == | ||
− | + | 0.27 and 0.28-pre users should keep their systems | |
+ | up to date with current fixes. The fix for this | ||
+ | issue hasn't been released as of the last update of | ||
+ | this Wiki. When released, information about it will be added here. | ||
+ | {| border="1" cellspacing="0" cellpadding="5" style="float: center;border-collapse:collapse; border-color:#8eabd0; background:#e7edf5" | ||
+ | |- style="background-color: lightsteelblue;" | ||
+ | |+ | ||
+ | |- style="background-color: lightsteelblue;" | ||
+ | ! scope="col" | Version | ||
+ | ! scope="col" | Commit | ||
+ | ! scope="col" | Release Date | ||
+ | |- | ||
+ | |0.27 | ||
+ | |{{shortgitcommit|TBA}} | ||
+ | |TBA | ||
+ | |- | ||
+ | |0.28-pre | ||
+ | |{{shortgitcommit|TBA}} | ||
+ | |TBA | ||
+ | |} | ||
+ | <br> | ||
== What '''must''' be done on November 1st. == | == What '''must''' be done on November 1st. == | ||
− | If | + | If the above was followed, nothing. |
− | |||
− | Users running 0.26 and below | + | Users running 0.26 and below should use the solution in the followng section. |
== Is there anything users can do to try the replacement now? == | == Is there anything users can do to try the replacement now? == | ||
Line 30: | Line 50: | ||
The new server is working well. But the more users testing it, | The new server is working well. But the more users testing it, | ||
− | the better. ( | + | the better. (It would be nice to discover any problems now rather than on 11/1.) |
− | Is the /etc/hosts entry a proper solution? No, because it points the | + | Is the /etc/hosts entry a proper solution? No, because it points the [[#Cast of characters (both of them.)|TMS-DD]] hostname to |
− | one of two Load Balancers in front of the SD host. It's not bad, it's | + | one of two Load Balancers in front of the SD host. |
− | + | Obviously, if that address were ever changed, the entry would become useless. | |
+ | It's not a bad solution, but it's certainly not as good as running on {{CurrentRelease}}. | ||
== Are there any other sources of information about the change? == | == Are there any other sources of information about the change? == | ||
Line 40: | Line 61: | ||
Yes. | Yes. | ||
− | The | + | The [http://forums.schedulesdirect.org/viewtopic.php?f=3&t=2578 announcement] from SD. |
List of [http://forums.schedulesdirect.org/viewtopic.php?f=8&t=2591 open issues], also from SD. | List of [http://forums.schedulesdirect.org/viewtopic.php?f=8&t=2591 open issues], also from SD. | ||
Line 71: | Line 92: | ||
== Can users that build from source make a change now? == | == Can users that build from source make a change now? == | ||
− | Yes | + | Yes, locate the line to change with the following command and |
− | |||
− | |||
replace the hostname with the new one above. Be prepared to | replace the hostname with the new one above. Be prepared to | ||
remove the change when the official commit is pushed. | remove the change when the official commit is pushed. |
Revision as of 05:09, 11 October 2014
Contents
- 1 Schedules Direct (SD) Changes
- 1.1 What must users do prior to November 1st, 2014?
- 1.2 What must be done on November 1st.
- 1.3 Is there anything users can do to try the replacement now?
- 1.4 Are there any other sources of information about the change?
- 1.5 Cast of characters (both of them.)
- 1.6 Can users that build from source make a change now?
Schedules Direct (SD) Changes
As some have heard, on November 1st, 2014, the existing SD service is changing. This Wiki is intended to be a short discussion of options for MythTV users.
Ideally, there would be a DNS change and the IP address for the existing (hard coded) hostname would be pointed to a new IP address and no action would be required by MythTV SD users. However, the owner of that hostname (which is not SD) could 'retire' that DNS record at any time leaving MythTV SD users out of service.
What must users do prior to November 1st, 2014?
0.27 and 0.28-pre users should keep their systems up to date with current fixes. The fix for this issue hasn't been released as of the last update of this Wiki. When released, information about it will be added here.
Version | Commit | Release Date |
---|---|---|
0.27 | TBA | TBA |
0.28-pre | TBA | TBA |
What must be done on November 1st.
If the above was followed, nothing.
Users running 0.26 and below should use the solution in the followng section.
Is there anything users can do to try the replacement now?
Yes, perhaps the simplest is to make the following entry in the backend's /etc/hosts file:
54.84.32.205 webservices.schedulesdirect.tmsdatadirect.com
The new server is working well. But the more users testing it, the better. (It would be nice to discover any problems now rather than on 11/1.)
Is the /etc/hosts entry a proper solution? No, because it points the TMS-DD hostname to one of two Load Balancers in front of the SD host. Obviously, if that address were ever changed, the entry would become useless. It's not a bad solution, but it's certainly not as good as running on 34.0.
Are there any other sources of information about the change?
Yes.
The announcement from SD.
List of open issues, also from SD.
The mythtv-users mailing list under the thread: Schedules Direct DataDirect replacement service testing. Or, it's archive). Please don't start new testing threads.
Discussions on the developer's channel.
Cast of characters (both of them.)
Abbreviated Name | URL | Description |
---|---|---|
TMS-DD | docs.tms.tribune.com webservices.schedulesdirect.tmsdatadirect.com | Tribune hosted Datadirect Server (going away) |
SD-DD | dd.schedulesdirect.org | SD hosted DataDirect Server |
Can users that build from source make a change now?
Yes, locate the line to change with the following command and replace the hostname with the new one above. Be prepared to remove the change when the official commit is pushed.
git grep webservices.schedulesdirect.tmsdatadirect.com