<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/openstack/nova.git/api-ref/source/server-security-groups.inc, branch master</title>
<subtitle>opendev.org: openstack/nova.git
</subtitle>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/'/>
<entry>
<title>api-ref: Fix parameters in server-security-groups</title>
<updated>2017-07-10T14:02:13+00:00</updated>
<author>
<name>Takashi NATSUME</name>
<email>natsume.takashi@lab.ntt.co.jp</email>
</author>
<published>2017-06-22T08:40:47+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/commit/?id=3f96ec6490c72d3646813f1a9d3ee38773ec1823'/>
<id>3f96ec6490c72d3646813f1a9d3ee38773ec1823</id>
<content type='text'>
Change-Id: Ie8dc3252603ce77910e1addb67cdc8844369dfca
Implements: blueprint api-ref-in-rst-pike
Closes-Bug: #1699732
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Change-Id: Ie8dc3252603ce77910e1addb67cdc8844369dfca
Implements: blueprint api-ref-in-rst-pike
Closes-Bug: #1699732
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix 'server' and 'instance' occurrence in api-ref</title>
<updated>2017-03-28T02:54:11+00:00</updated>
<author>
<name>ghanshyam</name>
<email>ghanshyammann@gmail.com</email>
</author>
<published>2017-03-27T09:22:10+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/commit/?id=49cade591fd3431322f3b2a9f13b0cd732f667fa'/>
<id>49cade591fd3431322f3b2a9f13b0cd732f667fa</id>
<content type='text'>
some api-ref have sentence like '..for a server instance'
which is inconsistent and confusing as we use server for VM terminology.
I think here 'instance' word is being considered object of server which
is wrong.

We should always mention server only.

part of bp:api-ref-in-rst-pike

Change-Id: I32afe56cfc66b34b76d1f7e1b507d3d5e722e6a1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
some api-ref have sentence like '..for a server instance'
which is inconsistent and confusing as we use server for VM terminology.
I think here 'instance' word is being considered object of server which
is wrong.

We should always mention server only.

part of bp:api-ref-in-rst-pike

Change-Id: I32afe56cfc66b34b76d1f7e1b507d3d5e722e6a1
</pre>
</div>
</content>
</entry>
<entry>
<title>API Ref: update server_id params</title>
<updated>2016-11-11T19:01:51+00:00</updated>
<author>
<name>Karen Bradshaw</name>
<email>kbhawkey@gmail.com</email>
</author>
<published>2016-10-10T18:50:17+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/commit/?id=168a50057032ad8cc028aabc261733bebb50a51d'/>
<id>168a50057032ad8cc028aabc261733bebb50a51d</id>
<content type='text'>
- Update server_id params to be of type path.
- Cleaned up os-getConsoleOutput action string.
- Made empty response body description more consistent.
  Review and change as needed.

Implements: bp/api-ref-in-rst-ocata

Change-Id: Ie1e299d2b93188240b18138eba9f5b908a1078a4
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
- Update server_id params to be of type path.
- Cleaned up os-getConsoleOutput action string.
- Made empty response body description more consistent.
  Review and change as needed.

Implements: bp/api-ref-in-rst-ocata

Change-Id: Ie1e299d2b93188240b18138eba9f5b908a1078a4
</pre>
</div>
</content>
</entry>
<entry>
<title>Separate api-ref for list security groups by server</title>
<updated>2016-07-21T07:42:57+00:00</updated>
<author>
<name>ghanshyam</name>
<email>ghanshyam.mann@nectechnologies.in</email>
</author>
<published>2016-07-21T07:42:57+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/commit/?id=bceeecc296c56b29de079cd4f65b6165ecc22a55'/>
<id>bceeecc296c56b29de079cd4f65b6165ecc22a55</id>
<content type='text'>
All proxy APIs are now deprecated which includes
sec grp APIs also.

But list sec grps by server API-
(/servers/{server_id}/os-security-groups) is not
deprecated so this should be separated from deprecated
sec grp APIs in api-ref.

Partially implements blueprint deprecate-api-proxies

Change-Id: I9f9e2cf5f8e390cecd9e1794a0af1a3fcc24f149
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
All proxy APIs are now deprecated which includes
sec grp APIs also.

But list sec grps by server API-
(/servers/{server_id}/os-security-groups) is not
deprecated so this should be separated from deprecated
sec grp APIs in api-ref.

Partially implements blueprint deprecate-api-proxies

Change-Id: I9f9e2cf5f8e390cecd9e1794a0af1a3fcc24f149
</pre>
</div>
</content>
</entry>
</feed>
