On Wed, Sep 7, 2016 at 10:19 AM, Dean Troyer wrote:
> I created the OSC session Etherpad[0] to start tracking these topic
> suggestions.
>
> [0]https://etherpad.openstack.org/p/osc-otaka-summit
>
/me sighs loudly
I wish I could blame the lack of caffeine, but alas, that URL
On Wed, Sep 7, 2016 at 9:48 AM, Steve Martinelli
wrote:
> There's been a bug filed against OSC to implement ospurge for cleaning up
> resources in (compute, network, storage, image and identity) [1] for a
> while now. As Jordan said, this is something we want to be
There's been a bug filed against OSC to implement ospurge for cleaning up
resources in (compute, network, storage, image and identity) [1] for a
while now. As Jordan said, this is something we want to be modular, and
pluggable, so other OSC plugins could extend this clean up command.
[1]
On Wed, Sep 7, 2016 at 4:18 PM, Boris Bobrov wrote:
> Hello,
>
> I wonder if it would be worth integrating ospurge into openstackclient.
>
> Are there any osc sessions planned at the summit?
>
>
> Hi,
I am the current "PTL" of the openstack/ospurge project. The project is
Hello,
I wonder if it would be worth integrating ospurge into openstackclient.
Are there any osc sessions planned at the summit?
On 09/07/2016 04:05 PM, John Davidge wrote:
Hello,
During the Mitaka cycle we merged a new feature into the
python-neutronclient called ’neutron purge’. This
On 07 Sep 2016, at 15:05, John Davidge
> wrote:
Hello,
During the Mitaka cycle we merged a new feature into the python-neutronclient
called ’neutron purge’. This enables a simple CLI command that deletes all of
the neutron
On 07 Sep 2016, at 15:05, John Davidge
> wrote:
Hello,
During the Mitaka cycle we merged a new feature into the python-neutronclient
called ’neutron purge’. This enables a simple CLI command that deletes all of
the neutron
Hello,
During the Mitaka cycle we merged a new feature into the python-neutronclient
called 'neutron purge'. This enables a simple CLI command that deletes all of
the neutron resources owned by a given tenant. It's documented in the
networking guide[1].
We did this in response to feedback