<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/openstack/python-openstackclient.git/openstackclient/network/v2/security_group_rule.py, branch 5.8.0</title>
<subtitle>opendev.org: openstack/python-openstackclient
</subtitle>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/openstack/python-openstackclient.git/'/>
<entry>
<title>Get rid of tenant_id in the network commands</title>
<updated>2022-01-17T08:31:16+00:00</updated>
<author>
<name>Artem Goncharov</name>
<email>Artem.goncharov@gmail.com</email>
</author>
<published>2022-01-14T17:51:56+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/openstack/python-openstackclient.git/commit/?id=18dcd7c9f7bc4ca0909a1a29ae934ea7128c183a'/>
<id>18dcd7c9f7bc4ca0909a1a29ae934ea7128c183a</id>
<content type='text'>
Finally drop tenant_id completely from the networking service.

Change-Id: I5f62f2a76592eaaaed6703624e959df41a6ecc8f
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Finally drop tenant_id completely from the networking service.

Change-Id: I5f62f2a76592eaaaed6703624e959df41a6ecc8f
</pre>
</div>
</content>
</entry>
<entry>
<title>Hide location columns for network objects</title>
<updated>2021-12-16T19:33:04+00:00</updated>
<author>
<name>Dr. Jens Harbott</name>
<email>harbott@osism.tech</email>
</author>
<published>2021-12-16T15:38:41+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/openstack/python-openstackclient.git/commit/?id=90eb0ca4bb2570ec3812cbf15f5c9dc4f1b784a8'/>
<id>90eb0ca4bb2570ec3812cbf15f5c9dc4f1b784a8</id>
<content type='text'>
Network objects returned from the SDK include a location column which
has a reference to the cloud to which the object belongs. We don't want
to include them in CLI output where they are useless.
The solution implemented in [0] was dropped as a sideeffect in [1].

[0] https://review.opendev.org/c/openstack/python-openstackclient/+/679445
[1] https://review.opendev.org/c/openstack/python-openstackclient/+/815032

Signed-off-by: Dr. Jens Harbott &lt;harbott@osism.tech&gt;
Change-Id: I9a408d9721c9c57d752afaab520cd6ee379a5184
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Network objects returned from the SDK include a location column which
has a reference to the cloud to which the object belongs. We don't want
to include them in CLI output where they are useless.
The solution implemented in [0] was dropped as a sideeffect in [1].

[0] https://review.opendev.org/c/openstack/python-openstackclient/+/679445
[1] https://review.opendev.org/c/openstack/python-openstackclient/+/815032

Signed-off-by: Dr. Jens Harbott &lt;harbott@osism.tech&gt;
Change-Id: I9a408d9721c9c57d752afaab520cd6ee379a5184
</pre>
</div>
</content>
</entry>
<entry>
<title>Remove 'get_osc_show_columns_for_sdk_resource' duplicates</title>
<updated>2021-10-21T16:14:45+00:00</updated>
<author>
<name>Stephen Finucane</name>
<email>sfinucan@redhat.com</email>
</author>
<published>2021-10-08T17:06:11+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/openstack/python-openstackclient.git/commit/?id=30612bf62295720a21d39c4f589cfcefb7a86a2f'/>
<id>30612bf62295720a21d39c4f589cfcefb7a86a2f</id>
<content type='text'>
There were a number of 'get_osc_show_columns_for_sdk_resource' defined
in-tree. However, osc-lib has provided this method for some time (since
2.2.0, June 2020 [1] - our minimum version is currently 2.3.0) so
there's no need to provide our own copies. Remove them.

[1] https://github.com/openstack/osc-lib/commit/29a0c5a5

Change-Id: I25695f4f9a379dd691b7eaa1e3247164668ae77e
Signed-off-by: Stephen Finucane &lt;sfinucan@redhat.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
There were a number of 'get_osc_show_columns_for_sdk_resource' defined
in-tree. However, osc-lib has provided this method for some time (since
2.2.0, June 2020 [1] - our minimum version is currently 2.3.0) so
there's no need to provide our own copies. Remove them.

[1] https://github.com/openstack/osc-lib/commit/29a0c5a5

Change-Id: I25695f4f9a379dd691b7eaa1e3247164668ae77e
Signed-off-by: Stephen Finucane &lt;sfinucan@redhat.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Allow to send extra attributes in Neutron related commands</title>
<updated>2021-05-26T07:29:15+00:00</updated>
<author>
<name>Slawek Kaplonski</name>
<email>skaplons@redhat.com</email>
</author>
<published>2020-12-22T14:31:44+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/openstack/python-openstackclient.git/commit/?id=b26b7f3440d4f756c0b7906b93751d7e83a733f7'/>
<id>b26b7f3440d4f756c0b7906b93751d7e83a733f7</id>
<content type='text'>
To deprecate and drop support for neutronclient CLI and use only
OSC we need feature parity between OSC and neutronclient.
Last missing piece here is possibility to send in POST/PUT requests
unknown parameters to the Neutron server.
This patch adds such possibility to the OSC.

Change-Id: Iba09297c2be9fb9fa0be1b3dc65755277b79230e
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
To deprecate and drop support for neutronclient CLI and use only
OSC we need feature parity between OSC and neutronclient.
Last missing piece here is possibility to send in POST/PUT requests
unknown parameters to the Neutron server.
This patch adds such possibility to the OSC.

Change-Id: Iba09297c2be9fb9fa0be1b3dc65755277b79230e
</pre>
</div>
</content>
</entry>
<entry>
<title>Support remote-address-group in SG rules</title>
<updated>2021-01-12T16:55:24+00:00</updated>
<author>
<name>Hang Yang</name>
<email>hangyang@verizonmedia.com</email>
</author>
<published>2020-10-14T16:35:22+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/openstack/python-openstackclient.git/commit/?id=e01e59caeb56cb7bf4f38403b82d0a265b163098'/>
<id>e01e59caeb56cb7bf4f38403b82d0a265b163098</id>
<content type='text'>
Add support for using remote-address-group in security group rules.

Change-Id: Ib1972244d484839943bc3cda07519a6c6d4b945a
Implements: blueprint address-groups-in-sg-rules
Depends-On: https://review.opendev.org/755644
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add support for using remote-address-group in security group rules.

Change-Id: Ib1972244d484839943bc3cda07519a6c6d4b945a
Implements: blueprint address-groups-in-sg-rules
Depends-On: https://review.opendev.org/755644
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge "Always display direction for security group rules"</title>
<updated>2020-10-13T23:26:24+00:00</updated>
<author>
<name>Zuul</name>
<email>zuul@review.opendev.org</email>
</author>
<published>2020-10-13T23:26:24+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/openstack/python-openstackclient.git/commit/?id=2eeab20eca4b51feb6e81e8e59124f2b092e9b20'/>
<id>2eeab20eca4b51feb6e81e8e59124f2b092e9b20</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Revert "Format location columns in network commands"</title>
<updated>2020-06-17T10:09:36+00:00</updated>
<author>
<name>Jens Harbott (frickler)</name>
<email>j.harbott@x-ion.de</email>
</author>
<published>2020-06-17T10:07:12+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/openstack/python-openstackclient.git/commit/?id=a04172969a5e440af50127dfd27a80a6beb7ddb8'/>
<id>a04172969a5e440af50127dfd27a80a6beb7ddb8</id>
<content type='text'>
This reverts commit 6ee7b8d138e07bfc37c5cd887f7afa49cdabb02f.

Change-Id: I5f59959ba8a01aba49e29f4cb007397467344e58
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This reverts commit 6ee7b8d138e07bfc37c5cd887f7afa49cdabb02f.

Change-Id: I5f59959ba8a01aba49e29f4cb007397467344e58
</pre>
</div>
</content>
</entry>
<entry>
<title>Always display direction for security group rules</title>
<updated>2020-03-04T22:04:59+00:00</updated>
<author>
<name>Sam Morrison</name>
<email>sorrison@gmail.com</email>
</author>
<published>2020-02-25T01:52:01+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/openstack/python-openstackclient.git/commit/?id=e410e61d204d09eeb7bcf0a33e3858ef7b110dd3'/>
<id>e410e61d204d09eeb7bcf0a33e3858ef7b110dd3</id>
<content type='text'>
The --long option is still accepted but is now ignored.

Change-Id: I23dd9fa7cff310ee9a62ce32b843b822b93b7548
Story: #2007323
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The --long option is still accepted but is now ignored.

Change-Id: I23dd9fa7cff310ee9a62ce32b843b822b93b7548
Story: #2007323
</pre>
</div>
</content>
</entry>
<entry>
<title>Replace six.iteritems() with .items()</title>
<updated>2020-01-09T09:41:29+00:00</updated>
<author>
<name>lihaijing</name>
<email>lihaijing@fiberhome.com</email>
</author>
<published>2017-07-07T03:48:48+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/openstack/python-openstackclient.git/commit/?id=d15bbada73f81136c966007d9c564dd6cfb2fd9c'/>
<id>d15bbada73f81136c966007d9c564dd6cfb2fd9c</id>
<content type='text'>
1. As mentioned in [1], we should avoid using six.iteritems to achieve
   iterators. We can use dict.items instead, as it will return iterators
   in PY3 as well. And dict.items/keys will more readable.

2. In py2, the performance about list should be negligible,
   see the link [2].

[1] https://wiki.openstack.org/wiki/Python3
[2] http://lists.openstack.org/pipermail/openstack-dev/2015-June/066391.html

Co-Authored-By: Akihiro Motoki &lt;amotoki@gmail.com&gt;
Change-Id: I4b9edb326444264c0f6c4ad281acaac356a07e85
Implements: blueprint replace-iteritems-with-items
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
1. As mentioned in [1], we should avoid using six.iteritems to achieve
   iterators. We can use dict.items instead, as it will return iterators
   in PY3 as well. And dict.items/keys will more readable.

2. In py2, the performance about list should be negligible,
   see the link [2].

[1] https://wiki.openstack.org/wiki/Python3
[2] http://lists.openstack.org/pipermail/openstack-dev/2015-June/066391.html

Co-Authored-By: Akihiro Motoki &lt;amotoki@gmail.com&gt;
Change-Id: I4b9edb326444264c0f6c4ad281acaac356a07e85
Implements: blueprint replace-iteritems-with-items
</pre>
</div>
</content>
</entry>
<entry>
<title>neutron: autogenerate docs</title>
<updated>2019-11-01T19:24:30+00:00</updated>
<author>
<name>Eric Fried</name>
<email>openstack@fried.cc</email>
</author>
<published>2019-10-28T22:27:38+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/openstack/python-openstackclient.git/commit/?id=cd6c285cc6c2274e6b42cc452ba4a61a3487ca23'/>
<id>cd6c285cc6c2274e6b42cc452ba4a61a3487ca23</id>
<content type='text'>
$namespace = openstack.network.v2

The subcommand documents for $namespace were hardcoded and thus prone to
drift over time. This commit removes the hardcoded content and uses the
autoprogram-cliff directive to generate them automatically from the
subcommand configuration classes.

This one turned out to be quite involved, because we support both
neutron and nova-network. When running in a real cloud, the command
classes detect whether the neutron service is present, assume
nova-network if that service is not found, and only add parser options
relevant to the detected service. But the docs need to present both sets
of options. This was easy enough when they were hardcoded, but required
a bit of additional infrastructure for generated docs.

Change-Id: I426261eb1d86bcc68656aabd61f10b7f082da402
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
$namespace = openstack.network.v2

The subcommand documents for $namespace were hardcoded and thus prone to
drift over time. This commit removes the hardcoded content and uses the
autoprogram-cliff directive to generate them automatically from the
subcommand configuration classes.

This one turned out to be quite involved, because we support both
neutron and nova-network. When running in a real cloud, the command
classes detect whether the neutron service is present, assume
nova-network if that service is not found, and only add parser options
relevant to the detected service. But the docs need to present both sets
of options. This was easy enough when they were hardcoded, but required
a bit of additional infrastructure for generated docs.

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