+1 from me. Good review comments! @Tom
Best Wishes,
Kai Qiang Wu (吴开强 Kennan）
IBM China System and Technology Lab, Beijing
E-mail: wk...@cn.ibm.com
Tel: 86-10-82451647
Address: Building 28(Ring Building), Zhong
Hi Sahara guys,
When sahara create a transient cluster, it create a trust with sahara admin
user.
https://github.com/openstack/sahara/blob/master/sahara/service/ops.py#L239-L240
https://github.com/openstack/sahara/blob/master/sahara/service/trusts.py#L79
When sahara deal with swift, it create a
+1 from me.
-- dims
On Thu, Jul 9, 2015 at 7:40 PM, Madhuri wrote:
> +1 to Tom for his great reviews.
>
> Regards,
> Madhuri
>
> On Fri, Jul 10, 2015 at 11:20 AM, Adrian Otto
> wrote:
>>
>> Team,
>>
>> Tom Cammann (tcammann) has become a valued Magnum contributor, and
>> consistent reviewer hel
Hi,
I'm deploying a swift 1.13 cluster on Ubuntu 14.04 and enabling
ceilometer in the proxy pipeline results in it not working.
The cause appears to be the log directory perms (note I am running the
proxy under Apache):
[Fri Jul 10 05:12:15.126214 2015] [:error] [pid 6844:tid
1400487799989
On 07/09/2015 07:06 PM, Andrew Woodward wrote:
> It has come to my attention that we spend an enormous amount of time in
> Fuel when switching between OpenStack releases. A good amount of this
> seems to be due to a chicken and the egg problem. We cant deploy updated
> packages with out updated m
Hi,
Can you describe what problems do you have with "bring code changes into a
live Devstack environment, and test them".
If you want a real-time Q&A experience you can ask your questions at
#murano on freenode.
Nikolay Starodubtsev
Software Engineer
Mirantis Inc.
Skype: dark_harlequine1
20
Cinder now doesn't check the existing resource when user lower the quota.
It's reasonable for admin can adjust the quota limit to lower level than
current usage.
But it also bring confusion that I have received to end user, they saw the
current usage
was more than limit, but they can't create resou
"Better late than never."
We have the pleasure to announce stable/kilo (6.0.0) release of 20
repositories, all part of Puppet OpenStack project:
puppet-ceilometer
puppet-cinder
puppet-designate
puppet-glance
puppet-heat
puppet-horizon
puppet-ironic
puppet-keystone
Hi,
Not sure if what I met if the same as yours.
In my case, "pep8 ." reported many errors located in the virtual environment
folder. In my case, things like:
./.venv/lib/python2.7/site-packages/virtualenv.py:260:13: E265 block comment
should start with '# '
To work around it, I use "pep8 ".
Hi guys
My problem looks simple:
Running "tox -e pep8", the result says ok, not pep8 mistakes.
Running "pep8 .", a lot of pep8 mistkes come out.
But in your project's tox.ini, there isn't such a long ignore list. So what
makes this difference happen?
Kun
Currently I found the spec about the trove monitoring framework in
https://review.openstack.org/#/c/186040/
And what's the process about that now?
We're developing MySQL and redis service upon trove. And we're glad to discuss
and contribute to this feature.
Sorry for the long delay, I'd like to help to review those patches, and I
don't find the patch about refactoring manage_existing flow in manager yet,
so maybe I can have a try.
2015-06-02 17:45 GMT+08:00 Dulko, Michal :
> Right now we’re working on refactoring current TaskFlow implementations
>
+1 to Tom for his great reviews.
Regards,
Madhuri
On Fri, Jul 10, 2015 at 11:20 AM, Adrian Otto
wrote:
> Team,
>
> Tom Cammann (tcammann) has become a valued Magnum contributor, and
> consistent reviewer helping us to shape the direction and quality of our
> new contributions. I nominate Tom to
Hi Glance experts,
I'd like to send this mail again, hope I can get help and suggest from
glance experts. The question is from a bug
https://bugs.launchpad.net/glance/+bug/1462315,
If an image-member is deleted, then create it again with the same
parameters, glance searches db to see if there is
Team,
Tom Cammann (tcammann) has become a valued Magnum contributor, and consistent
reviewer helping us to shape the direction and quality of our new
contributions. I nominate Tom to join the magnum-core team as our newest core
reviewer. Please respond with a +1 vote if you agree. Alternatively
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
First of all, apologies for my absence over the past couple of weeks. I
took some time off to spend with my daughter while she was on school
holidays, and then got ill! It never rains but it pours ;) While I was
out, our M release was nam
Thanks Vipin*, *it's very helpful.
2015-06-14 16:23 GMT+08:00 Vipin Balachandran :
> Sorry for the long delay. This is fixed in oslo.vmware 0.9.0.
>
>
> https://github.com/openstack/oslo.vmware/commit/a229faf8ba59724a4fda3f37d5a7473376f93d9c
>
>
>
>
>
> *From:* hao wang [mailto:sxmatch1...@gmail
On 2015-07-09 18:04:49 -0700 (-0700), Adam Lawson wrote:
> Yes I'm talking about vetting by legal since the community already
> vets via the usual process. Legal has stricter guidelines so we
> could start future vetting with legal to remove the options we
> can't use even if we wanted to. That's w
2 weeks seems too small for me. We easy can be in situation when fix for
medium bug is done, but SCF starts. And gap between SCF and release easily
can be more than a month. So, 2 months seems okay for me if speaking about
forcibly applying auto-abandon by major vote. And I'm personally against
suc
Yes I'm talking about vetting by legal since the community already vets via
the usual process. Legal has stricter guidelines so we could start future
vetting with legal to remove the options we can't use even if we wanted to.
That's where the inefficiency lies imho. The issue with this particular
s
Hi,
I am using puppet-swift to deploy a swift multi node cluster (Icehouse),
following the setup in supplied tests/site.pp. I am running into two
issues that seem to be related to the subject above:
1/ Errors when the storage replication services try to start before the
ring files exist. e.g
Team,
We held the IRC discussion as scheduled today 2015-07-09 at 23:30 in
#openstack-containers. We tried using Meetbot to log the meeting but that
apparently failed because we crossed the date line to July 10th before we ended
the meeting, so the transcript is available in two parts starting
On Thu, Jul 09, 2015 at 05:19:06PM +0530, Pradeep kumar wrote:
> Hi Hans,
> I did traced the function responsible for segmentation fault itz in file
> ceval.c. find below
>
> if (*next_instr == SETUP_FINALLY) {
> /* Make the last opcode before
>a try: fi
On 07/09/2015 07:16 PM, Adam Lawson wrote:
> It seems we have a golden opportunity here to improve efficiency by vetting
> names before we vote on them.
The vetting from the crowd was intended to happen on the wikipage. I'm
not sure how much vetting did take place but obviously not enough to
give
On Thu, Jul 9, 2015 at 4:49 PM, Ihar Hrachyshka wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 07/09/2015 10:55 AM, Antoni Segura Puimedon wrote:
>> Names: Kuryr - Czech name for Courier since it is delivering
>> networking to containers. v: apuimedo+1
>
> :) If you stick to it,
Hello,
I am wondering if there is any documentation for new contributors that
explains how to get up-to-speed with Murano development; something that
covers how to bring code changes into a live Devstack environment, and
test them.
I've looked at the Murano documentation online and have not bee
Hi Russell and Gurucharan,
On Thu, Jul 9, 2015 at 5:09 PM, Gurucharan Shetty wrote:
> Yes. Though the code that I have has been mostly written with OVN and
> Open vSwitch in mind, it uses Neutron APIs and integrates well with
> OpenStack. The docker plugin code that I have currently uses "no-auth
It seems we have a golden opportunity here to improve efficiency by vetting
names before we vote on them. Seems that voting for a bunch of names then
eliminating all of the top votes because they won't work doesn't strike me
as very efficient (i.e. why vote on names that MIGHT be valid).
The alter
It has come to my attention that we spend an enormous amount of time in
Fuel when switching between OpenStack releases. A good amount of this seems
to be due to a chicken and the egg problem. We cant deploy updated packages
with out updated manifests, and we we cant update (in that CI won't pass)
t
The is the expected, although security conservative approach to admin
endpoints in fuel, it does pretty much block all actions in keystone other
then auth from outside the cluster. It pre-dates me, and fuel 3.0.1; my
understanding of the intent here is that we don't want a compromise to
result in a
+1
On 10 July 2015 at 05:53, David Lyle wrote:
> On Thu, Jul 9, 2015 at 1:33 PM, Michael Krotscheck
> wrote:
>
>> Hey everyone!
>>
>> We've been hard at work getting some solid, shared code style rules in
>> place for our javascript code, and nobody's been more diligent about this
>> than Cindy
I think another important question is how to represent this to the user on
the login screen. "Keystone Endpoint:" matches the setting, but seems like
a weird choice to me. Is there a better terminology to use for the label
for this on the login screen?
I see the related selector has no label at al
That's a very good plan ("Initial feedback/triage") Mike.
thanks,
dims
On Thu, Jul 9, 2015 at 3:23 PM, Mike Scherbakov
wrote:
> +1 for just reusing existing script, and adjust it on the way. No need to
> immediately switch from infinite time to a couple of weeks, we can always
> adjust it later.
Hi Daniel,
answer is no - actually there is no strong dependency between public and
internal/admin endpoints. In your case keystone client ask keystone on
address 10.52.71.39 (which, I think, was provided by system
variable OS_AUTH_URL), auth on it and then keystone give endpoints list to
client.
+1 for just reusing existing script, and adjust it on the way. No need to
immediately switch from infinite time to a couple of weeks, we can always
adjust it later. But 1-2 month should be a good start already.
Our current stats [1] look just terrible. Before we enable an auto-abandon,
we need to
On 07/09/2015 12:21 PM, Tomoki Sekiyama wrote:
Hi all,
Just FYI, here is a sample script I'm using for testing os-brick which
attaches/detaches the cinder volume to the host using cinderclient and
os-brick:
https://gist.github.com/tsekiyama/ee56cc0a953368a179f9
"python attach.py " will attach
We often have bugs which create really poor User eXperience (UX) but our
current bug priority criteria prevent nearly all of them from being higher
than medium (as they nearly always have workarounds). We need to identify
what should qualify as a critical, or high UX defect so that they can
receive
We need this. Please find a tool which suites best, and we will let
Dmitry's team to enable it. I assume there is not such a thing in OpenStack
Infra (otherwise we could just reuse it).
Also, I would add a check, that any new bash file should not contain, let's
say, more than 50 lines. If it is la
Hi,
I'm running Fuel 6.1 and i've seen an interesting behavior which i think
match bug [1]
Basically the adminUrl & publicUrl part of keystone endpoint are different
And the result of that is that you can't run keystone cli - i.e create/list
tenants etc
keystone --debug tenant-list
/usr/local/l
On 07/09/2015 10:11 AM, Ihar Hrachyshka wrote:
> On 07/09/2015 09:01 AM, Artur Korzen wrote:
>> Hi all,
>
>> I've been researching the Neutron project as a part of work on
>> Openstack rolling upgrades, my primary assignments included
>> testing if there is no VM access downtime when performing
>
Hi Everyone,
Thanks for joining the service chaining project meeting on 7/9/2015. Here is
the link to the meeting logs:
http://eavesdrop.openstack.org/meetings/service_chaining/2015/
Thanks,
Cathy
__
OpenStack Development Ma
Hi all,
We are scheduled to publish 2015.1.1 Kilo point releases,
on Thursday July 16th for Ceilometer, Cinder, Glance, Heat, Horizon,
Ironic, Keystone, Neutron, Nova, Sahara and Trove.
We'd appreciate anyone who could test the candidate 2015.1.1 tarballs, which
include all changes aside from any
On 07/08/2015 03:38 AM, Csaba Henk wrote:
Hi,
I'm tossing in the term "dismantling" to indicate
the act of making a share less available
(deprovision (deny access to) / unmanage / delete
it).
I find it ambiguous what is to be done with
the share's data('s accessibility) upon
dismantling. Wrt. t
Thanks Ihar comments!
> > Is Neutron ready to be upgradable with minimal downtime of services
> > and no VM access downtime?
>
> As the ovs bug you refer to above, no, at least not in reference
> implementation. That's for data plane.
My understanding is that after the ovs neutron agent will be
On Thu, Jul 9, 2015 at 1:33 PM, Michael Krotscheck
wrote:
> Hey everyone!
>
> We've been hard at work getting some solid, shared code style rules in
> place for our javascript code, and nobody's been more diligent about this
> than Cindy Lu. Since we've managed to encapsulate our eslint configura
Apparently I sent this email twice... disregard this one
On 09/07/15 21:13 +0200, Flavio Percoco wrote:
Greetings,
I'd like to propose Stuart Mclaren for the glance-drivers team. Stuart
has a huge amount of knowledge about Glance's history, he knows the
Glance codebase well and he also has expe
Hello OpenStackers, hello TC,
Haikel and I have just submitted an update to the change to the governance
repo to add RPM packaging to the OpenStack projects:
https://review.openstack.org/#/c/191587
As a start there we'd like to do a dual PTL from Red Hat (Haikel) and SUSE
(myself) and we'd like
Greetings,
I'd like to propose Stuart Mclaren for the glance-drivers team. Stuart
has a huge amount of knowledge about Glance's history, he knows the
Glance codebase well and he also has experience in deploying and
maintaning Glance production environments.
Stuart has shown his interest in joini
On 10:58 Jun 29, Sheng Bo Hou wrote:
> Hi everyone,
>
> For folks who are working on Dell, Storpool and Infortrend drivers:
> I have got a new patch for https://review.openstack.org/#/c/180873. There
> is a change about how to implement the method update_migrated_volume for
> each driver.
> The
Hey everyone!
We've been hard at work getting some solid, shared code style rules in
place for our javascript code, and nobody's been more diligent about this
than Cindy Lu. Since we've managed to encapsulate our eslint configuration
into a separate project (much like hacking), I'd like to nominat
On 02:08 Jul 01, liuxinguo wrote:
> Hi Mike,
>
> We have solved the problem of Huawei CI, and it is running and reporting
> stably now. The logs is also ok to access.
>
> We will be very appreciate if you can have a consider of remove the -2 review
> to Huawei driver, thanks! ☺
> The following
On 08:49 Jun 23, Mike Perez wrote:
> There was a bug raised [1] from some large deployments that the Cinder
> client 1.2.0 and beyond is not working because of version discovery.
> Unfortunately it's not taking into account of deployments that have a
> proxy.
>
> Cinder client asks Keystone to fin
On 16:47 Jun 30, Mike Perez wrote:
> On 12:24 Jun 26, Matt Riedemann wrote:
>
> > So the question is, is everyone OK with this and ready to make that change?
>
> Thanks for all your work on this Matt.
>
> I'm fine with this. I say bite the bullet and we'll see the CI's surface that
> aren't ski
Hi all,
Just FYI, here is a sample script I'm using for testing os-brick which
attaches/detaches the cinder volume to the host using cinderclient and
os-brick:
https://gist.github.com/tsekiyama/ee56cc0a953368a179f9
"python attach.py " will attach the volume to the executed
host and shows a volum
Feel free to give input on the Mitaka proposal.
Tim
> -Original Message-
> From: Jonathan Bryce [mailto:jbr...@jbryce.com]
> Sent: 09 July 2015 20:52
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Openstack] Rescinding the M name decisio
On 21:48 Jul 06, Ivan Kolodyazhny wrote:
> Aslo, what do you think about moving cinderclient functional tests from
> experimental to non-voting queue to make it more public and run it with
> every patch to python-cinderclient?
I'm fine with this as long as the job has been stable since it was i
Greetings,
I'd like to propose Stuart Mclaren for the glance-drivers team. Stuart
has a huge amount of knowledge about Glance's history, he knows the
Glance codebase well and he also has experience in deploying and
maintaning Glance production environments.
Stuart has shown his interest in joini
On 08/07/15 18:12, Steve Baker wrote:
On 09/07/15 04:39, Zane Bitter wrote:
On 08/07/15 09:03, Sean Dague wrote:
Personally, I'm running out of steam on tags for this cycle, but Zane
brought up a good point in the TC meeting yesterday, which was that "it
would be nice to have tags for criteria
Greetings,
Before I even get started with this email, I'd like to make it clear
that I'm sending it out assuming the good faith of everyone and the
willingness of the Glance community to work together on improving our
workflow. We all do what we do on the best interests of the project.
My holida
> On Jul 9, 2015, at 9:35 AM, Russell Bryant wrote:
>
> On 07/09/2015 09:19 AM, Neil Jerram wrote:
>> In the hope of forestalling an unnecessary sub-thread...
>>
>> Mita was #1 in the vote, so has presumably already been ruled out by
>> OpenStack's legal review.
>
> That is correct.
Hi everyo
I missed this whole thread due to my mail filtering. Sorry about that.
Anyway, Ivan and I have an open Blueprint here:
https://blueprints.launchpad.net/cinder/+spec/use-cinder-without-nova
That starts the discussion of adding the end to end ability of attaching
a Cinder
volume to a host using
Ok, I guess I'll bite my own thread and provide some feedback:
We hold a glance-drivers meeting every week on Tuesdays at 14 UTC. In
this week's meetingi[0], we discussed a bit the problems we have in the
current workflow. Here's some feedback from that meeting. (Please,
other folks, do chime in
Thanks Steve.
From: Steve Martinelli [mailto:steve...@ca.ibm.com]
Sent: Thursday, July 09, 2015 11:01 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] openstack command line and --help for subcommands
Hey Sean, 1444983 has been reopened and assign
And I realized all of a sudden that even more interesting than unittest
framework itself would be some analog of Python mock for shell scripts.
Though I doubt that anyone ever really gone that far.
--
Best regards,
Oleg Gelbukh
On Thu, Jul 9, 2015 at 5:12 PM, Jeremy Stanley wrote:
> On 2015-07-
Excerpts from Sergey Kraynev's message of 2015-07-09 18:26:09 +0300:
> Hi community.
>
> I want to raise couple questions about openstack clients.
> In Heat we use other python-*clients for manipulating service's resources,
> but some stuff placed in shell.py modules and we are forced to duplicate
Had the same issue when I worked on the context selection menu for switching domain and project. I think it make sense to rename it to AVAILABLE_KEYSTONE_ENDPOINTS. Since it is local_settings.py, its going to affect some folks (maybe even break) until they also update their setting, something that
Hi all,
I was thinking about those who are packaging with venvs (and using the
version of a project in the venv file name); like what anvil[1] is now
capable of (and does this in the gate now[2]) or packaging via rpms
(which anvil also does) and they are going to be affected by the version
sh
Hey Sean, 1444983 has been reopened and assigned to you. Thanks!
https://bugs.launchpad.net/python-openstackclient/+bug/1444983
I am leaving 1251290 as invalid, since I feel it's a dupe of 1444983
Thanks,
Steve Martinelli
OpenStack Keystone Core
From: "Perry, Sean"
To: "OpenStack Deve
>
> > On Jul 9, 2015, at 10:59 AM, Monty Taylor wrote:
> >
> > Ghe has been doing a great job both in writing patches and reviewing for
> > os-client-config and I'd like to add him to the core team. He's got a
> > good handle on what we're doing, and more importantly what we're not
> doing.
>
+1
Minutes are available
http://eavesdrop.openstack.org/meetings/fuel/2015/fuel.2015-07-09-16.00.html
On Thu, Jul 9, 2015 at 8:16 AM Andrew Woodward wrote:
> Please note the IRC meeting is scheduled for 16:00 UTC in
> #openstack-meeting-alt today.
>
> Please review meeting agenda and update if the
I would think the python-openstackclient would smooth out a lot of the
rough edges particularly the find by name or id situation. It already does
that for many services neutron being the biggest gap. The
python-openstacksdk will eventually (soon) be able to address a lot of
those issues.
On Thu
> On Jul 9, 2015, at 10:59 AM, Monty Taylor wrote:
>
> Hey all!
>
> Ghe has been doing a great job both in writing patches and reviewing for
> os-client-config and I'd like to add him to the core team. He's got a
> good handle on what we're doing, and more importantly what we're not doing.
+1
Excellent. Can the tickets be assigned to me and re-opened?
From: Steve Martinelli [mailto:steve...@ca.ibm.com]
Sent: Wednesday, July 08, 2015 8:28 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] openstack command line and --help for subcommands
S
Hi,
we have just create some spec in etherpad for
"expiration-policies-for-executions".
This have been discussed already but in this we getting more into the
functionality details.
You are more than welcome to add your comments in this page :
https://etherpad.openstack.org/p/expiration-policie
What bugs exist on the Launch Instance based off Angular?
I'd like to help fix some.
-Rajat
On Tue, Jul 7, 2015 at 8:29 AM, Rob Cresswell (rcresswe) wrote:
> The current issue is that we can’t force Angular when we have so little
> code ourselves. The framework is fairly solid now, but there i
Hi, its a friendly reminder that if you what to discuss some topics at
Rally meetings, please add you topic to our Meeting agenda
https://wiki.openstack.org/wiki/Meetings/Rally#Agenda. Don't forget to
specify by whom led this topic. Add some information about topic(links,
etc.) Thank you for your a
On 2015-07-09 11:52:14 +0200 (+0200), Yanis Guenane wrote:
> In PuppetOpenstack we would like to use modulesync[1] in order to
> synchronize common file accross modules via a post-merged hook(WIP)[2].
>
> In order for this script to work modulesync needs to be installed on the
> nodes. Modulesync
Hi,
We have weekly Nova API meeting this week. The meeting is being held
tomorrow Friday UTC1200.
In other timezones the meeting is at:
EST 08:00 (Fri)
Japan 21:00 (Fri)
China 20:00 (Fri)
United Kingdom 13:00 (Fri)
The proposed agenda and meeting details are here:
https://wiki.openstack.org/wi
Dell - Internal Use - Confidential
UNSUBSCRIBE
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailma
Hi community.
I want to raise couple questions about openstack clients.
In Heat we use other python-*clients for manipulating service's resources,
but some stuff placed in shell.py modules and we are forced to duplicate
some existing code.
There are couple examples which I met last time:
- getti
Please note the IRC meeting is scheduled for 16:00 UTC in
#openstack-meeting-alt today.
Please review meeting agenda and update if there is something you wish to
discuss.
https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
--
--
Andrew Woodward
Mirantis
Fuel Community Ambassador
Cep
Yes. Though the code that I have has been mostly written with OVN and
Open vSwitch in mind, it uses Neutron APIs and integrates well with
OpenStack. The docker plugin code that I have currently uses "no-auth"
mode of Neutron, but there is no reason for it to not work with "auth"
(as shown in https:
Hey all!
Ghe has been doing a great job both in writing patches and reviewing for
os-client-config and I'd like to add him to the core team. He's got a
good handle on what we're doing, and more importantly what we're not doing.
Monty
__
On 07/09/2015 04:55 AM, Antoni Segura Puimedon wrote:
> Hi list,
>
> As the subject says, we are starting a new Neutron subproject that
> aims to service the Docker Container Network Model[1] by leveraging
> Neutron in a way similar to how Nova does.
>
> So far, while we set up a subproject, we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/09/2015 10:55 AM, Antoni Segura Puimedon wrote:
> Names: Kuryr - Czech name for Courier since it is delivering
> networking to containers. v: apuimedo+1
:) If you stick to it, make sure you provide info on how it's pronounced
.
Ihar
-BEGI
On Thu, Jul 9, 2015 at 3:55 AM, Antoni Segura Puimedon <
toni+openstac...@midokura.com> wrote:
> Hi list,
>
> As the subject says, we are starting a new Neutron subproject that
> aims to service the Docker Container Network Model[1] by leveraging
> Neutron in a way similar to how Nova does.
>
>
T
On 07/09/2015 09:19 AM, Neil Jerram wrote:
> In the hope of forestalling an unnecessary sub-thread...
>
> Mita was #1 in the vote, so has presumably already been ruled out by
> OpenStack's legal review.
That is correct.
--
Russell Bryant
On 7/9/15, 06:25, "Victor Stinner" wrote:
>Hi,
>
>gate-glance-python34 is now voting!
>
>Ian Cordasco and Erno Kuvaja approved my two last patches to port
>glance_store to Python 3: thanks. "tox -e py34" now pass successfully,
>cool! I proposed a "Make gate-glance_store-python34 voting, add gat
Sam thanks for the review / heads up, that's awesome!
--
Kevin Carter
From: Sam Yaple
Sent: Thursday, July 9, 2015 1:57 AM
To: Steven Dake (stdake)
Cc: OpenStack Development Mailing List (not for usage questions); Greg
DeKoenigsberg
Subject: Re: [openstack-dev
Hi to all,
Please, be informed that the following features
will enter Fuel Plugin Framework in 7.0 Fuel release:
- define a new role through Fuel Plugins [1]
- reserve VIP addresses via Fuel Plugin's metadata [2]
If you plan to develop a plugin for Fuel, take these changes into
consideration.
T
Excerpts from Robert Collins's message of 2015-07-08 13:31:52 +1200:
> I think we need a checklist of what to do when adding someeone to the
> release team - either library or servers.
>
> I just released python-cinderclient, and found out the hard way that
> my account doesn't have the right acce
On 2015-07-09 11:24:14 +0300 (+0300), Matthew Mosesohn wrote:
> What about bashate? It is already in use in several OpenStack projects?
[...]
It's a style checker (its name is an allusion to the "pep8" tool for
checking Python coding style conventions). And shellcheck (mentioned
later in this thre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/09/2015 09:01 AM, Artur Korzen wrote:
> Hi all,
>
> I've been researching the Neutron project as a part of work on
> Openstack rolling upgrades, my primary assignments included testing
> if there is no VM access downtime when performing upgrad
On 07/09/2015 10:02 AM, Doug Hellmann wrote:
> Excerpts from Robert Collins's message of 2015-07-09 11:17:41 +1200:
>> On 9 July 2015 at 11:02, Doug Hellmann wrote:
>>> Excerpts from Robert Collins's message of 2015-07-09 07:49:36 +1200:
I'd like to make the job run automatically immediately
Excerpts from Robert Collins's message of 2015-07-09 11:07:44 +1200:
> On 9 July 2015 at 09:08, Sean Dague wrote:
>
> > So I think the issue is that we used to have a manual process (reviewing
> > g-r adds), and some automated stuff that happens after that.
> >
> > Now we seem to have a manual pr
Excerpts from Robert Collins's message of 2015-07-09 11:17:41 +1200:
> On 9 July 2015 at 11:02, Doug Hellmann wrote:
> > Excerpts from Robert Collins's message of 2015-07-09 07:49:36 +1200:
> >> I'd like to make the job run automatically immediately that we cut a
> >> release of anything. And I'd
Or a database per python major version (or at least gracefully handle the
incompatibility).
--Morgan
Sent via mobile
> On Jul 9, 2015, at 06:43, Doug Hellmann wrote:
>
> Excerpts from Robert Collins's message of 2015-07-09 10:37:17 +1200:
>> I don't remember if this has previously been discu
Excerpts from Robert Collins's message of 2015-07-09 10:37:17 +1200:
> I don't remember if this has previously been discussed, but as our
> Python3 readiness increases folk are going to feel pain from testr due
> to a silly Python 2/3 incompatibility around dbm files.
>
> https://bugs.launchpad.ne
In the hope of forestalling an unnecessary sub-thread...
Mita was #1 in the vote, so has presumably already been ruled out by
OpenStack's legal review.
On 09/07/15 13:14, Mark Carlson wrote:
Isn't Mita a trademark of Kyocera they use for their copier business?
Folks should read up on Musashi
On 7/9/15, 01:34, "Flavio Percoco" wrote:
>On 08/07/15 22:52 +, Jeremy Stanley wrote:
>>On 2015-07-09 10:37:17 +1200 (+1200), Robert Collins wrote:
>>> So - I'm looking to:
>>>
>>> A) have a discussion and identify any issues with moving testr out of
>>> the venvs. (Note: this doesn't mean
1 - 100 of 138 matches
Mail list logo
