Minutes:
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-08-12-19.00.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-08-12-19.00.txt
Log:
http://eavesdrop.openstack.org/meetings/python_openstack
Hi all,
Between recent IRC meetings and the mid-cycle operators meetup, we've
heard things ranging from "is the SDK project still around" to "I
can't wait for this." I'm Brian Curtin from Rackspace and I'd like to
tell you what the python-openstacksdk [0][
On Thu, Feb 20, 2014 at 12:02 PM, Jesse Noller
wrote:
> Hi Everyone;
>
> Our first python-openstack meeting was awesome: and I really want to thank
> everyone who came, and for Doug teaching me the meeting bot :)
>
> Minutes:
> http://eavesdrop.openstack.org/meetings/python_openstacksdk/2
Reminder that tomorrow we're back on the meeting schedule after having
last week off. Extra special note that the meeting is moved up a day
to Tuesday instead of being on a Wednesday last time.
https://wiki.openstack.org/wiki/Meetings#python-openstacksdk_Meeting
Date/Time: Tuesday 4 March - 19:00
Today was the second python-openstacksdk meeting
Minutes:
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-03-04-19.00.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-03-04-19.00.txt
Log:
http
On Tue, Dec 9, 2014 at 9:05 AM, Sean Dague wrote:
> - [H305 H306 H307] Organize your imports according to the `Import order
> template`_ and `Real-world Import Order Examples`_ below.
>
> I think these remain reasonable guidelines, but H302 is exceptionally
> tricky to get right, and we keep not
On Tue, May 6, 2014 at 8:38 AM, Doug Hellmann
wrote:
> On Tue, May 6, 2014 at 8:02 AM, Thierry Carrez wrote:
>> Dean Troyer wrote:
>>> I want to open the discussion of an OpenStack Client Tools program
>>> proposal to a wider audience. It would initially consist of
>>> OpenStackClient and eventu
On Wed, May 7, 2014 at 7:38 AM, Doug Hellmann
wrote:
> On Tue, May 6, 2014 at 5:45 PM, Joe Gordon wrote:
>>
>>
>>
>> On Tue, May 6, 2014 at 6:54 AM, Dean Troyer wrote:
>>>
>>> On Tue, May 6, 2014 at 7:02 AM, Thierry Carrez
>>> wrote:
Would you take over the Python client libraries as
Next meeting will be 2014-05-27
Minutes:
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-05-20-19.00.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-05-20-19.00.txt
Log:
http://eavesdrop.op
On Tue, May 20, 2014 at 6:43 PM, Joe Gordon wrote:
>
>
> On Tue, May 20, 2014 at 1:37 PM, Brian Curtin wrote:
>>
>> Next meeting will be 2014-05-27
>>
>> Minutes:
>> http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.20
Meeting ended Tue May 27 20:00:28 2014 UTC
Minutes:
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-05-27-19.01.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-05-27-19.01.txt
Log:
http://e
On Sun, Jun 8, 2014 at 3:35 AM, Michael Bright wrote:
>
> I'm interested to know what is the status of the Python API of the
> python-novaclient, and the Python APIs of other OpenStack clients.
>
> On the github page it is written:
> "There's also a complete Python API, but it has not yet been
Meeting ended Tue Jun 10 19:59:25 2014 UTC
Minutes:
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-06-10-19.01.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-06-10-19.01.txt
Log:
http://eav
Meeting ended Tue Jun 17 19:59:32 2014 UTC.
Minutes:
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-06-17-19.00.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-06-17-19.00.txt
Log:
http://
Reminder that tomorrow is the python-openstacksdk meeting. Double
reminder that, where applicable, this is one hour later thanks to
Daylight Saving Time.
https://wiki.openstack.org/wiki/Meetings#python-openstacksdk_Meeting
Date/Time: Tuesday 4 March - 19:00 UTC / 1400 CDT
IRC channel: #openstack
We just wrapped up our weekly meeting, and the minutes and log are available.
Minutes:
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-03-11-19.00.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2
Reminder that tomorrow is the python-openstacksdk meeting.
https://wiki.openstack.org/wiki/Meetings#python-openstacksdk_Meeting
Date/Time: Tuesday 4 March - 19:00 UTC / 1400 CDT
IRC channel: #openstack-meeting-3
Meeting Agenda:
https://wiki.openstack.org/wiki/Meetings/PythonOpenStackSDK
Thanks everyone for another good meeting. Lots of good talk about
direction and where to take the current example.
Minutes:
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-03-18-19.00.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/python_op
Reminder that tomorrow is the python-openstacksdk meeting.
https://wiki.openstack.org/wiki/Meetings#python-openstacksdk_Meeting
Date/Time: Tuesday 25 March - 1900 UTC / 1400 CDT
IRC channel: #openstack-meeting-3
Meeting Agenda:
https://wiki.openstack.org/wiki/Meetings/PythonOpenStackSDK
Thanks for another good meeting. More code coming along, and a few
reviews out there to take a look at.
Minutes:
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-03-25-19.01.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/python_openstacksdk/
Reminder that tomorrow is the python-openstacksdk meeting.
https://wiki.openstack.org/wiki/Meetings#python-openstacksdk_Meeting
Date/Time: Tuesday 01 April - 1900 UTC / 1400 CDT
IRC channel: #openstack-meeting-3
Meeting Agenda:
https://wiki.openstack.org/wiki/Meetings/PythonOpenStackSDK
We've decided to cancel the project.
April Fools. Thanks all for another good meeting. We have some action
items to build on, so we should be rolling onward for next week.
Minutes:
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-04-01-19.00.html
Minute
Tomorrow is a scheduled python-openstacksdk meeting, although at least
myself and Alex Gaynor will not be available as we're in transit to
PyCon. I didn't hear from any others that they couldn't make the
meeting, so I'm guessing it will go on, just with someone else leading
it.
As Ed Leafe's propo
Minutes:
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-04-15-19.00.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-04-15-19.00.txt
Log:
http://eavesdrop.openstack.org/meetings/python_opens
Per the meeting yesterday, we're having a vote on which way to go
between Ed's and Jamie's proposals. If you have an opinion one way or
another, please make it known at
https://wiki.openstack.org/wiki/PythonOpenStackSDK/ClassDesignDecision
Voting ends at the end of the day UTC on Thursday. If you
Since a bunch of people had been asking at the Summit, and bunch of
them were interested in contributing, it seemed like a good idea to
put together some status on where the OpenStack SDK project is at.
What follows is the status section of a larger blog post on the SDK at
the Summit, available at
On Wed, Jun 25, 2014 at 10:18 PM, Aaron Rosen wrote:
> Hi,
>
> I'm looking at creating a new python-client and I was
> wondering if there was any on going effort to share code between the
> clients or not? I've looked at the code in python-novaclient and
> python-neutronclient and both of them se
Today was a relatively quick meeting, but a meeting nonetheless.
Minutes:
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-07-22-19.00.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-07-22-19.0
The following logs are from today's python-openstacksdk meeting
Minutes:
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-08-05-19.00.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-08-05-19.00.
Hi,
I just had a look at the python-swiftclient reviews in Gerrit and noticed that
Kui Shi and I are working on the same stuff, but I'm guessing Kui didn't see
that I had proposed a number of Python 3 changes from a few weeks ago. Now that
there are reviews and a web of dependent branches being
On Oct 12, 2013, at 5:59 PM, John Dickinson wrote:
> Co-reviewing each other's patches and discussing changes in #openstack-swift
> would be good ways to ensure that you are working in the same direction.
>
> --John
Kui ended up abandoning his changes and I'm going to review them to incorporat
On Jul 23, 2013, at 3:51 PM, Eric Windisch
mailto:e...@cloudscaling.com>>
wrote:
On Tue, Jul 23, 2013 at 4:41 PM, Logan McNaughton
mailto:lo...@bacoosta.com>> wrote:
I'm sure this has been asked before, but what exactly is the plan for Python 3
support?
Is the plan to support 2 and 3 at
On Jul 23, 2013, at 4:32 PM, Doug Hellmann
mailto:doug.hellm...@dreamhost.com>> wrote:
On Tue, Jul 23, 2013 at 4:41 PM, Logan McNaughton
mailto:lo...@bacoosta.com>> wrote:
I'm sure this has been asked before, but what exactly is the plan for Python 3
support?
Is the plan to support 2 and
On Jul 24, 2013, at 1:12 PM, Chuck Short
mailto:chuck.sh...@canonical.com>>
wrote:
Hi,
The use of mox (https://pypi.python.org/pypi/mox/0.5.3) across the test suites
in the Openstack project is quite extensive. This is probably due to the fact
that it is the most familiar mocking object fram
On Jul 24, 2013, at 1:27 PM, Eric Windisch
mailto:e...@cloudscaling.com>>
wrote:
Speaking of preferred ways to port, has there been any discussion about which
version takes precedence when we have to do different things? For example, with
imports, should we be trying the 2.x name first and fa
On Thu, May 12, 2016 at 1:24 AM, Joseph Robinson
wrote:
> Hi All, One reply inline:
>
> On 11/05/2016, 7:33 AM, "Lana Brindley" wrote:
>
>>On 10/05/16 20:08, Julien Danjou wrote:
>>> On Mon, May 09 2016, Matt Kassawara wrote:
>>>
So, before developer frustrations drive some or all projects t
On Sun, Feb 7, 2016 at 3:07 PM, Jay Pipes wrote:
> I would love to see the OpenStack contributor community take back the design
> summit to its original format and purpose and decouple it from the OpenStack
> Summit's conference portion.
>
> I believe the design summits should be organized by the
In the interest of moving towards a 1.0 release of OpenStack SDK,
we're going to halt accepting any new resources on existing services,
and any entirely new services. After release, we'll open back up and
both deepen and broaden our support for other OpenStack services.
We currently have a backlog
On Thu, Sep 17, 2015 at 12:26 PM, Kevin Benton wrote:
> Maybe it would be a good idea to switch to 23:59 AOE deadlines like many
> paper submissions use for academic conferences. That way there is never a
> need to convert TZs, you just get it in by the end of the day in your own
> time zone.
Thi
2015 at 1:17 PM, Kevin Benton wrote:
> How is it not what I described? Time zones become irrelevant if you get it
> in by the end of the day in your local time zone.
>
> https://en.wikipedia.org/wiki/Anywhere_on_Earth
>
> On Thu, Sep 17, 2015 at 10:30 AM, Brian Curtin wrot
On Thursday, June 18, 2015, Doug Hellmann wrote:
> Excerpts from Thomas Goirand's message of 2015-06-18 15:44:17 +0200:
> > Hi!
> >
> > tl;dr: skip this message, the subject line is enough! :)
> >
> > As per the subject line, we already have Python 3.5 in Debian (AFAICT,
> > from Debian Experimen
On Tue, Feb 10, 2015 at 1:57 PM, Min Pae wrote:
> I think most people would agree documentation is a good thing, and
> consistency is generally a good thing… is there an accepted standard on
> layout and minimum required fields?
>
> If not, should there be?
>
> For example
>
> - Heading (short de
On Wed, Feb 11, 2015 at 1:43 PM, Jeremy Stanley wrote:
> Also, if there are people on this list who feel like
> discussions here sometimes get negative or uncomfortable, I'm happy
> to point you to free software community mailing lists (more than I
> can count on all my fingers and toes) whose day
On Mon, Mar 16, 2015 at 10:08 AM, John Garbutt wrote:
> On 16 March 2015 at 14:15, Sean Dague wrote:
>> Our current top level shipped example paste.ini for Nova includes the
>> following set of endpoint definitions:
>>
>> [composite:osapi_compute]
>> use = call:nova.api.openstack.urlmap:urlmap_fa
On Tue, May 2, 2017 at 10:46 PM, Akira Yoshiyama
wrote:
> Hello all,
>
> I'm pleased to announce Yakumo, yet another unified OpenStack client
> library with an interactive shell. You can find Yakumo below:
>
>PyPI: https://pypi.python.org/pypi/yakumo/
>Github: https://github.com/yosshy/py
On Tue, Nov 29, 2016 at 7:48 AM, Ihar Hrachyshka wrote:
> Hi,
>
> It was ‘cubswin:)’ before, but now that Cubs won [1] it’s ‘gocubsgo’ [2].
>
> I hope it helps someone in the future.
>
> [1]
> http://www.chicagotribune.com/sports/baseball/cubs/ct-cubs-win-world-series-sullivan-spt-1103-20161102-s
On Tue, Jan 17, 2017 at 4:23 PM, Michael Gale
wrote:
> Hello,
>
> Does anyone know what the equivalent of the following command would be
> via the API?
> `openstack limits show --absolute --project `
>
> I am using an admin account to pull stats and information from a Mitaka
> environment, no
On Wed, Sep 21, 2016 at 8:15 AM, gordon chung wrote:
> i feel like this gets brought up every year. we block these patches in
> Telemetry projects unless they can be justified beyond the copy/paste
> description.
>
> in addition to this, please, PLEASE stop creating 'all project bugs'. i
> don't w
I'm currently facing what looks more and more like an impossible
problem in determining the root of each service on a given cloud. It
is apparently a free-for-all in how endpoints can be structured, and I
think we're out of ways to approach it that catch all of the ways that
all people can think of
On Wed, Oct 19, 2016 at 12:59 PM, Jay Pipes wrote:
> On 10/19/2016 05:32 PM, Brian Curtin wrote:
>>
>> I'm currently facing what looks more and more like an impossible
>> problem in determining the root of each service on a given cloud. It
>> is apparently a free
On Wed, Oct 19, 2016 at 2:03 PM, Sean Dague wrote:
> On 10/19/2016 01:40 PM, Brian Curtin wrote:
>> On Wed, Oct 19, 2016 at 12:59 PM, Jay Pipes wrote:
>>> On 10/19/2016 05:32 PM, Brian Curtin wrote:
>>>>
>>>> I'm currently facing what looks m
51 matches
Mail list logo
