Skip to content

Commit a91f564

Browse files
allmightyspiffallmightyspiff
committed
api disruption release note
1 parent 82959b1 commit a91f564

20 files changed

Lines changed: 1025 additions & 555 deletions

File tree

‎index.html‎

Lines changed: 77 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -99,6 +99,83 @@
9999
<h1>Release Notes</h1>
100100
<div class="col-md-9">
101101

102+
<div class="well well-sm release-note example col-md-12">
103+
<h3>
104+
<a href="https://softlayer.github.io/release_notes/2018/20180301/"> March 1, 2018</a>
105+
<br>
106+
</h3>
107+
<div class="container">
108+
<div class="row">
109+
<div class="col-md-8">
110+
111+
112+
<h1 id="span-style-color-red-api-service-disruption-march-1st-2018-span"><span style="color:red">API SERVICE DISRUPTION: March 1st, 2018</span></h1>
113+
114+
<p>IBM Cloud will stop supporting TLS 1.0 and 1.1 on api.softlayer.com and api.service.softlayer.com</p>
115+
116+
<h2 id="what-is-happening">What Is Happening?</h2>
117+
118+
<p>On March 1, 2018 at 0900 UTC (0300 CDT) IBM Cloud Infrastructure will stop supporting TLS 1.0 and 1.1 encryption on api.softlayer.com and api.service.softlayer.com; these API endpoints will only support callers using TLS 1.2 encryption levels or higher.</p>
119+
120+
<h2 id="when-will-it-happen">When Will It Happen?</h2>
121+
122+
<p>On March 1, 2018 at 0900 UTC (0300 CDT) TLS 1.0 and TLS 1.1 will no longer be supported and TLS 1.2+ is required.</p>
123+
124+
<h2 id="who-will-this-affect">Who Will This Affect?</h2>
125+
126+
<p>Any users with code or services that reference the softlayer.com API endpoints for IBM Cloud Infrastructure services with encryption levels older than TLS 1.2.</p>
127+
128+
<p>Confirming and Testing Upgrades to TLS 1.2 or Higher The enhanced security configuration is currently enforced on alternate endpoints. You can test your services against them now to ensure there will be no disruption once the primary endpoints receive the updated configuration:</p>
129+
130+
<ul>
131+
<li>api-dev.softlayer.com (instead of api.softlayer.com)</li>
132+
<li>api-dev.service.softlayer.com (instead of api.service.softlayer.com)</li>
133+
</ul>
134+
135+
<p>These alternative endpoints only use encryption levels TLS 1.2 or higher. Successfully testing your code and services against these alternative endpoints means your code and services will work properly on the transition date. These alternative endpoints will only be available until the transition date.</p>
136+
137+
<h2 id="what-do-i-do-next">What Do I Do Next?</h2>
138+
139+
<ol>
140+
<li>Test your service against the alternative endpoints listed above.</li>
141+
<li>If your code and service work as expected then update your production code to utilize TLS 1.2 in the current production environment and current production endpoints. Once that is complete no further action is required on your part.</li>
142+
<li>If your code or service fails change your code to utilize TLS 1.2 and test against the alternative endpoints and upon working properly update production.</li>
143+
</ol>
144+
145+
<ul>
146+
<li>The current production environment supports TLS 1.0, TLS 1.1 and TLS 1.2.</li>
147+
<li>Once you have completed your TLS 1.2 testing against the temporary end points you can make your production code changes to utilize the production TLS 1.2 at any time prior to March 1, 2018.</li>
148+
<li>Once your production environment is utilizing TLS 1.2 you have no further action.</li>
149+
<li>If you make your production changes before March 1, 2018 you should see no impact on March 1, 2018 when TLS 1.0 and TLS 1.1 are no longer available.</li>
150+
</ul>
151+
152+
<h2 id="what-will-happen-if-i-make-no-change">What Will Happen If I Make No Change?</h2>
153+
154+
<p>If you make no change and your code or services do not support encryption levels TLS 1.2 or higher, you will start to experience connection errors on the transition date. These errors may appear as &ldquo;transport errors&rdquo; and contain messages like SSLV3_ALERT_HANDSHAKE_FAILURE. Your code and services will no longer function until you upgrade it to support TLS 1.2 or higher.</p>
155+
156+
<p>If My Code Starts Failing Do I Have Any Temporary Recourse?
157+
If you start to experience connection errors on the transition date, the best course of action is to upgrade your code or services to support TLS 1.2 or higher. If you cannot do that immediately, there will be alternative endpoints provided temporarily to allow you to upgrade your code or services:</p>
158+
159+
<ul>
160+
<li>api-deprecated.softlayer.com (instead of api.softlayer.com)</li>
161+
<li>api-deprecated.service.softlayer.com (instead of api.service.softlayer.com)</li>
162+
</ul>
163+
164+
<p>These endpoints will become available on the transition date, and will continue to support TLS 1.0 and 1.1. You can change failing code or services to use these endpoints temporarily while you upgrade your systems to support TLS 1.2 or higher. These endpoints will only be available until March 30, 2018 to allow you to make this transition. You must upgrade all your systems and start using the standard API endpoints by March 1, 2018.</p>
165+
166+
<h2 id="why-are-we-making-this-change">Why Are We Making This Change?</h2>
167+
168+
<p>This is part of IBM&rsquo;s commitment to offering a cloud that is secure to the core and in alignment with industry best practices for security and data privacy.</p>
169+
170+
</div>
171+
</div>
172+
</div>
173+
</div>
174+
175+
176+
177+
178+
102179
<div class="well well-sm release-note example col-md-12">
103180
<h3>
104181
<a href="https://softlayer.github.io/release_notes/2018/20180216/"> February 16, 2018</a>
@@ -519,46 +596,6 @@ <h4 id="backend">Backend</h4>
519596

520597

521598

522-
<div class="well well-sm release-note example col-md-12">
523-
<h3>
524-
<a href="https://softlayer.github.io/release_notes/2017/20171120/"> November 20, 2017</a>
525-
<br>
526-
</h3>
527-
<div class="container">
528-
<div class="row">
529-
<div class="col-md-8">
530-
531-
532-
<h4 id="portal">Portal</h4>
533-
534-
<ul>
535-
<li>Fixed an issue where a dedicated VSI would get marked as public if the order was edited.</li>
536-
<li>Fixed an issue where editing a Bare Metal Server order would make the order invalid.</li>
537-
</ul>
538-
539-
<h4 id="api">API</h4>
540-
541-
<ul>
542-
<li>Enforce the same set of input requirements for <a href="http://sldn.softlayer.com/reference/services/SoftLayer_User_Customer/createObject">SoftLayer_User_Customer::CreateObject</a> in a linked account, as for a non-linked account.</li>
543-
</ul>
544-
545-
<h4 id="backend">Backend</h4>
546-
547-
<ul>
548-
<li>Fixed an issue with cloud-init provisioning not configuring the gateway properly</li>
549-
<li>Fixed an issue preventing local disk -&gt; San disk migration from upgrading properly.</li>
550-
<li>Fixed a bug that allowed both a CIDR and IP address to be specified together in the remoteIp field of a security group rule.</li>
551-
</ul>
552-
553-
</div>
554-
</div>
555-
</div>
556-
</div>
557-
558-
559-
560-
561-
562599
</div>
563600

564601

‎index.xml‎

Lines changed: 69 additions & 49 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,75 @@
66
<language>en-US</language>
77
<author>Enthusiastic Hugo User</author>
88
<rights>Copyright (c) 2014, Enthusiastic Hugo User; all rights reserved.</rights>
9-
<updated>Fri, 16 Feb 2018 00:00:00 UTC</updated>
9+
<updated>Thu, 01 Mar 2018 00:00:00 UTC</updated>
10+
11+
<item>
12+
<title>API SERVICE DISRUPTION March 1, 2018</title>
13+
<link>https://softlayer.github.io/release_notes/2018/20180301/</link>
14+
<pubDate>Thu, 01 Mar 2018 00:00:00 UTC</pubDate>
15+
<author>Enthusiastic Hugo User</author>
16+
<guid>https://softlayer.github.io/release_notes/2018/20180301/</guid>
17+
<description>
18+
19+
&lt;h1 id=&#34;span-style-color-red-api-service-disruption-march-1st-2018-span&#34;&gt;&lt;span style=&#34;color:red&#34;&gt;API SERVICE DISRUPTION: March 1st, 2018&lt;/span&gt;&lt;/h1&gt;
20+
21+
&lt;p&gt;IBM Cloud will stop supporting TLS 1.0 and 1.1 on api.softlayer.com and api.service.softlayer.com&lt;/p&gt;
22+
23+
&lt;h2 id=&#34;what-is-happening&#34;&gt;What Is Happening?&lt;/h2&gt;
24+
25+
&lt;p&gt;On March 1, 2018 at 0900 UTC (0300 CDT) IBM Cloud Infrastructure will stop supporting TLS 1.0 and 1.1 encryption on api.softlayer.com and api.service.softlayer.com; these API endpoints will only support callers using TLS 1.2 encryption levels or higher.&lt;/p&gt;
26+
27+
&lt;h2 id=&#34;when-will-it-happen&#34;&gt;When Will It Happen?&lt;/h2&gt;
28+
29+
&lt;p&gt;On March 1, 2018 at 0900 UTC (0300 CDT) TLS 1.0 and TLS 1.1 will no longer be supported and TLS 1.2+ is required.&lt;/p&gt;
30+
31+
&lt;h2 id=&#34;who-will-this-affect&#34;&gt;Who Will This Affect?&lt;/h2&gt;
32+
33+
&lt;p&gt;Any users with code or services that reference the softlayer.com API endpoints for IBM Cloud Infrastructure services with encryption levels older than TLS 1.2.&lt;/p&gt;
34+
35+
&lt;p&gt;Confirming and Testing Upgrades to TLS 1.2 or Higher The enhanced security configuration is currently enforced on alternate endpoints. You can test your services against them now to ensure there will be no disruption once the primary endpoints receive the updated configuration:&lt;/p&gt;
36+
37+
&lt;ul&gt;
38+
&lt;li&gt;api-dev.softlayer.com (instead of api.softlayer.com)&lt;/li&gt;
39+
&lt;li&gt;api-dev.service.softlayer.com (instead of api.service.softlayer.com)&lt;/li&gt;
40+
&lt;/ul&gt;
41+
42+
&lt;p&gt;These alternative endpoints only use encryption levels TLS 1.2 or higher. Successfully testing your code and services against these alternative endpoints means your code and services will work properly on the transition date. These alternative endpoints will only be available until the transition date.&lt;/p&gt;
43+
44+
&lt;h2 id=&#34;what-do-i-do-next&#34;&gt;What Do I Do Next?&lt;/h2&gt;
45+
46+
&lt;ol&gt;
47+
&lt;li&gt;Test your service against the alternative endpoints listed above.&lt;/li&gt;
48+
&lt;li&gt;If your code and service work as expected then update your production code to utilize TLS 1.2 in the current production environment and current production endpoints. Once that is complete no further action is required on your part.&lt;/li&gt;
49+
&lt;li&gt;If your code or service fails change your code to utilize TLS 1.2 and test against the alternative endpoints and upon working properly update production.&lt;/li&gt;
50+
&lt;/ol&gt;
51+
52+
&lt;ul&gt;
53+
&lt;li&gt;The current production environment supports TLS 1.0, TLS 1.1 and TLS 1.2.&lt;/li&gt;
54+
&lt;li&gt;Once you have completed your TLS 1.2 testing against the temporary end points you can make your production code changes to utilize the production TLS 1.2 at any time prior to March 1, 2018.&lt;/li&gt;
55+
&lt;li&gt;Once your production environment is utilizing TLS 1.2 you have no further action.&lt;/li&gt;
56+
&lt;li&gt;If you make your production changes before March 1, 2018 you should see no impact on March 1, 2018 when TLS 1.0 and TLS 1.1 are no longer available.&lt;/li&gt;
57+
&lt;/ul&gt;
58+
59+
&lt;h2 id=&#34;what-will-happen-if-i-make-no-change&#34;&gt;What Will Happen If I Make No Change?&lt;/h2&gt;
60+
61+
&lt;p&gt;If you make no change and your code or services do not support encryption levels TLS 1.2 or higher, you will start to experience connection errors on the transition date. These errors may appear as &amp;ldquo;transport errors&amp;rdquo; and contain messages like SSLV3_ALERT_HANDSHAKE_FAILURE. Your code and services will no longer function until you upgrade it to support TLS 1.2 or higher.&lt;/p&gt;
62+
63+
&lt;p&gt;If My Code Starts Failing Do I Have Any Temporary Recourse?
64+
If you start to experience connection errors on the transition date, the best course of action is to upgrade your code or services to support TLS 1.2 or higher. If you cannot do that immediately, there will be alternative endpoints provided temporarily to allow you to upgrade your code or services:&lt;/p&gt;
65+
66+
&lt;ul&gt;
67+
&lt;li&gt;api-deprecated.softlayer.com (instead of api.softlayer.com)&lt;/li&gt;
68+
&lt;li&gt;api-deprecated.service.softlayer.com (instead of api.service.softlayer.com)&lt;/li&gt;
69+
&lt;/ul&gt;
70+
71+
&lt;p&gt;These endpoints will become available on the transition date, and will continue to support TLS 1.0 and 1.1. You can change failing code or services to use these endpoints temporarily while you upgrade your systems to support TLS 1.2 or higher. These endpoints will only be available until March 30, 2018 to allow you to make this transition. You must upgrade all your systems and start using the standard API endpoints by March 1, 2018.&lt;/p&gt;
72+
73+
&lt;h2 id=&#34;why-are-we-making-this-change&#34;&gt;Why Are We Making This Change?&lt;/h2&gt;
74+
75+
&lt;p&gt;This is part of IBM&amp;rsquo;s commitment to offering a cloud that is secure to the core and in alignment with industry best practices for security and data privacy.&lt;/p&gt;
76+
</description>
77+
</item>
1078

1179
<item>
1280
<title>Release notes: February 16, 2018</title>
@@ -903,54 +971,6 @@ def create_vsi():
903971

904972
if __name__ == &#39;__main__&#39;:
905973
create_vsi()
906-
&lt;/code&gt;&lt;/pre&gt;
907-
</description>
908-
</item>
909-
910-
<item>
911-
<title>Create a new virtual server and attach Security Groups</title>
912-
<link>https://softlayer.github.io/ruby/vsisecgroups/</link>
913-
<pubDate>Mon, 30 Oct 2017 00:00:00 UTC</pubDate>
914-
<author>Enthusiastic Hugo User</author>
915-
<guid>https://softlayer.github.io/ruby/vsisecgroups/</guid>
916-
<description>&lt;p&gt;To get a list of Security Groups you can attach to a Virtual Guest you can run the following code:&lt;/p&gt;
917-
918-
&lt;pre&gt;&lt;code class=&#34;language-ruby&#34;&gt;require &#39;softlayer_api&#39;
919-
require &#39;pp&#39;
920-
921-
client = SoftLayer::Client.new(:timeout =&amp;gt; 120)
922-
923-
getGroups = client[&#39;Network_SecurityGroup&#39;].getAllObjects
924-
925-
pp getGroups
926-
&lt;/code&gt;&lt;/pre&gt;
927-
928-
&lt;p&gt;Once you have the Security Group IDs you would like to use you can plug them in to the following example:&lt;/p&gt;
929-
930-
&lt;pre&gt;&lt;code class=&#34;language-ruby&#34;&gt;require &#39;softlayer_api&#39;
931-
require &#39;pp&#39;
932-
933-
client = SoftLayer::Client.new(:timeout =&amp;gt; 120)
934-
935-
productOrder = {
936-
&#39;hostname&#39; =&amp;gt; &#39;rubysectest&#39;,
937-
&#39;domain&#39; =&amp;gt; &#39;cde.services&#39;,
938-
&#39;datacenter&#39; =&amp;gt; {&#39;name&#39; =&amp;gt; &#39;dal05&#39;},
939-
&#39;startCpus&#39; =&amp;gt; 2, # 2 x 2.0 GHz Cores
940-
&#39;maxMemory&#39; =&amp;gt; 2048, # 4GB RAM
941-
&#39;private_network_only&#39; =&amp;gt; false,
942-
&#39;dedicated_host_only&#39; =&amp;gt; false,
943-
&#39;operatingSystemReferenceCode&#39; =&amp;gt; &#39;UBUNTU_LATEST_64&#39;, # Latest Ubuntu LTS
944-
&#39;localDiskFlag&#39; =&amp;gt; false, # Use a SAN disk
945-
&#39;public_security_groups&#39; =&amp;gt; [43507],
946-
&#39;private_security_groups&#39; =&amp;gt; [43511],
947-
&#39;hourly&#39; =&amp;gt; false # Charge me for hourly use, rather than monthly.
948-
}
949-
950-
order = client[&#39;Virtual_Guest&#39;].createObject(productOrder)
951-
952-
pp order
953-
954974
&lt;/code&gt;&lt;/pre&gt;
955975
</description>
956976
</item>

‎page/10/index.html‎

Lines changed: 39 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -99,6 +99,45 @@
9999
<h1>Release Notes</h1>
100100
<div class="col-md-9">
101101

102+
<div class="well well-sm release-note example col-md-12">
103+
<h3>
104+
<a href="https://softlayer.github.io/release_notes/2016/20160201/"> February 1, 2016</a>
105+
<br>
106+
</h3>
107+
<div class="container">
108+
<div class="row">
109+
<div class="col-md-8">
110+
111+
112+
<h4 id="portal">Portal</h4>
113+
114+
<ul>
115+
<li>Resolved an issue that was preventing the portal from properly enabling Private VLAN spanning.</li>
116+
</ul>
117+
118+
<h4 id="api">API</h4>
119+
120+
<ul>
121+
<li>Exposed <a href="http://sldn.softlayer.com/reference/services/SoftLayer_User_Customer/getAllowedHardwareIds">getAllowedHardwareIds</a> and <a href="http://sldn.softlayer.com/reference/services/SoftLayer_User_Customer/getAllowedVirtualGuestIds">getAllowedVirtualGuestIds</a> to the <a href="http://sldn.softlayer.com/reference/services/SoftLayer_User_Customer">SoftLayer_User_Customer</a> service. This helps with API timeout issues on accounts with a large amount of Bare Metal Servers and or Virtual Guests.</li>
122+
<li>Resolved an issue where calling <a href="http://sldn.softlayer.com/reference/services/SoftLayer_Virtual_Guest_Block_Device_Template_Group/denySharingAccess">denySharingAccess</a> would cause an image template to go in to an inconsistent state.</li>
123+
</ul>
124+
125+
<h4 id="backend">Backend</h4>
126+
127+
<ul>
128+
<li>Added the ability to specify userdata to <a href="http://www.softlayer.com/info/hourly-bare-metal-servers">Hourly Bare Metal Servers</a></li>
129+
<li>Enabled the automatic migration of local disk VSIs on disabled hosts on VSI power off or reboot.</li>
130+
</ul>
131+
132+
</div>
133+
</div>
134+
</div>
135+
</div>
136+
137+
138+
139+
140+
102141
<div class="well well-sm release-note example col-md-12">
103142
<h3>
104143
<a href="https://softlayer.github.io/release_notes/2016/20160125/"> January 25, 2016</a>
@@ -546,40 +585,6 @@ <h4 id="api">API</h4>
546585

547586

548587

549-
<div class="well well-sm release-note example col-md-12">
550-
<h3>
551-
<a href="https://softlayer.github.io/release_notes/2015/20151130/"> November 30, 2015</a>
552-
<br>
553-
</h3>
554-
<div class="container">
555-
<div class="row">
556-
<div class="col-md-8">
557-
558-
559-
<h4 id="portal">Portal</h4>
560-
561-
<ul>
562-
<li>Added an error message when trying to order from a datacenter your account does not have access to.</li>
563-
</ul>
564-
565-
<h4 id="api">API</h4>
566-
567-
<ul>
568-
<li>Fixed an issue that was causing migration failures of local disk VSI&rsquo;s to SAN disk VSI&rsquo;s when a metadata disk was attached.</li>
569-
<li>Fixed an issue that was causing the preset.totalMinimumHourlyFee to be rounded to the nearest integer when using Hardware.getCreateObjectOptions on hourly bare metal servers.</li>
570-
<li>Users must now have permission to access a Hardware or VSI to be able to request an upgrade.</li>
571-
<li>Fixed an issue where large sized metadata/userdata was causing timeouts during the provisioning process.</li>
572-
</ul>
573-
574-
</div>
575-
</div>
576-
</div>
577-
</div>
578-
579-
580-
581-
582-
583588
</div>
584589

585590

0 commit comments

Comments
 (0)