On Mon, Sep 22, 2014 at 12:27:40PM -0400, Jay Pipes wrote:
OK, so we had our inaugural OpenStack Bootstrapping Hour last Friday. Thanks
to Sean and Dan for putting up with my rambling about unittest and mock
stuff. And thanks to one of my pugs, Winnie, for, according to Shrews,
looking like
On Fri, Oct 24, 2014 at 06:45:27PM +, Tim Bell wrote:
SFR and Bouyeges are common providers but don't know for the 1 month deals
as to which is the best.
Based entirely on one website and 0 local knowledge certainly Bouyeges does.
I used: http://prepaidwithdata.wikia.com/wiki/France
Hi All,
I'm looking for a description of which linux distributions we as
developers expect to support openstack on. I haven't found anything that
summerises this.
So far the closest I've come is:
1) http://docs.openstack.org/index.html
We have:
Installation Guide for Debian 7
On Tue, Nov 18, 2014 at 07:33:54AM -0500, Sean Dague wrote:
Or just abandon and let people restore. I think handling the logic /
policy for the edge cases isn't worth it when the author can very easily
hit the restore button to get their patch back (and fresh for another 4w).
As a non-core
Hi All,
I was going to make an iCal feed for all the openstack meetings.
I discovered I was waaay behind the times and one exists and is linked from
https://wiki.openstack.org/wiki/Meetings
With some of the post Paris changes it's a little out of date. I'm really
happy to help maintain it
On Wed, Nov 19, 2014 at 01:24:03PM +0100, Thierry Carrez wrote:
The iCal is currently maintained by Anne (annegentle) and myself. In
parallel, a small group is building a gerrit-powered agenda so that we
can describe meetings in YAML and check for conflicts automatically, and
build the ics
On Fri, Nov 14, 2014 at 09:43:45AM +0100, Thierry Carrez wrote:
Thanks Thierry
If you are after the list of distributions with a well-known packaging
of OpenStack then yes, the union of those two lists + Gentoo sounds
accurate to me.
I have to admit I expect this to be a litle more
Hi All,
I'd like to accomplish 2 things with this message:
1) Unblock (one way or another) https://review.openstack.org/#/c/123957
2) Create some form of consensus on when it's okay to add temporary code to
nova to work around bugs in external utilities.
So some background on this specific
Hello Wiki masters,
Is there anyway to extend the session length on the wiki? In my current
work flow I login to the wiki do work and then get distracted by code/IRC when
I go back to the wiki I'm almost always logged out (I'm guessing due to
inactivity). It feels like this is about 30mins
Hi All,
In the most recent team meeting we briefly discussed: [1] where the
console.log grows indefinitely, eventually causing guest stalls. I mentioned
that I was working on a spec to fix this issue.
My original plan was fairly similar to [2] In that we'd switch libvirt/qemu to
using a
On Fri, Dec 05, 2014 at 02:26:46PM +, Jeremy Stanley wrote:
On 2014-12-04 18:37:48 -0700 (-0700), Carl Baldwin wrote:
+1 I've been meaning to say something like this but never got
around to it. Thanks for speaking up.
https://storyboard.openstack.org/#!/story/1172753
I think Ryan
On Mon, Dec 22, 2014 at 04:36:02PM -0800, Surojit Pathak wrote:
Hi Daniel,
Having GA to do graceful restart is nice option. But if it were to just
preserve the same console file, even 'virsh reboot' achieves the purpose. As
I explained in my original analysis, Nova seems to have not taken the
On Mon, Dec 22, 2014 at 07:16:27PM -0800, Surojit Pathak wrote:
Hi Tony,
Can you please share some details of the effort, in terms of reference?
Well the initial discussions started with qemu at:
http://lists.nongnu.org/archive/html/qemu-devel/2014-12/msg00765.html
and then here:
On Tue, Jan 27, 2015 at 04:27:21AM +, Adrian Otto wrote:
Tony,
That would be terrific. Which iCal feed were you thinking of? I was planning
on making something similar to this:
Sorry Adrian I was a little off topic.
I was thinking that when you settle on a schedule for your regular
On Thu, Feb 05, 2015 at 11:13:50PM +0100, Sylvain Bauza wrote:
I was always considering stuck reviews as reviews where 2 or more cores were
disagreeing between themselves so that it was needing a debate discussion
during the meeting.
I was under the same impression.
Stuck reviews were for
On Fri, Feb 20, 2015 at 07:27:33AM +0100, Philipp Marek wrote:
Potentially corrupted images are bad; depending on the affected data it
might only be diagnosed some time after installation, so IMO the fix is
needed.
Sure but there is a (potentially hefty) performance impact.
Only a minor
On Fri, Jan 23, 2015 at 03:14:18PM -0700, Steven Dake wrote:
On 01/23/2015 02:46 PM, Adrian Otto wrote:
Steven,
Thanks for this email to capture and relay this decision from our IRC team
meeting this week! I thought it might be helpful if I made a team calendar
with an iCal feed that our
On Mon, Feb 16, 2015 at 01:39:21PM +1300, Robert Collins wrote:
Just ran across this from bug
https://bugs.launchpad.net/nova/+bug/1398999. Is there some way to
signal to libvirt that some block devices shouldn't be migrated by it
but instead are known to be networked etc? Or put another way,
Hi all,
In September I started working on a simple (but controvertial) fix in
nova[1]
to avoid some disk corruption issues. John kindly ran with a similar fix to
cinder[2].
John's review ended up in merge conflict so I tried my own version [3].
While (trying) to add workarounds to nova
On Mon, Mar 30, 2015 at 10:00:44AM -0400, Sean Dague wrote:
I've been attempting to clean up the bug tracker, one of the continued
inconsistencies that are in the Nova tracker is the use of 'Triaged'.
https://wiki.openstack.org/wiki/BugTriage
If the bug contains the solution, or a patch,
On Fri, Feb 20, 2015 at 06:03:46PM +0100, Markus Zoeller wrote:
It seems to me that the blueprint serial-ports[1] didn't implement
everything which was described in its spec. If one of you could have a
look at the following examples and help me to understand if these
observations are
On Fri, Feb 20, 2015 at 12:40:34PM +0100, Philipp Marek wrote:
Well, do you want fast or working/consistent images?
Sure I often said I'll take slow and correct over fast and buggy anyday.
Oh, okay... with the safe default being derived from the qemu version ;)
Umm excuse my ignorance but
On Wed, Mar 25, 2015 at 03:23:29PM +, Bailey, Darragh wrote:
I was looking at using the meetings service
(https://wiki.openstack.org/wiki/Meetings) to run and log a meeting on a
stackforge project (git-upstream -
http://git.openstack.org/cgit/stackforge/git-upstream), which seems to
On Tue, May 05, 2015 at 06:22:47PM +0300, Mikhail Dubov wrote:
Hi Rally team,
as mentioned in another message from me in this list, we have decided to
use the meeting time on Wednesdays at 14:00 UTC for our *usual weekly
meeting in #openstack-meeting*.
This meeting time and channel will
On Thu, May 07, 2015 at 01:31:07PM +0300, Mikhail Dubov wrote:
We have decided to stay in *#openstack-meeting* but have our meetings *on
Mondays at 1400 UTC*. Hope that this time there will be no conflicts.
We will also have the internal release meeting in *#openstack-rally* one
hour before
On Wed, May 06, 2015 at 12:11:16PM -0500, JJ Asghar wrote:
Hey everyone!
As we move forward with our big tent move[1] Jan suggested we move from our
traditional IRC meeting in our main channel #openstack-chef to one of the
official OpenStack meeting channels[2].
Sounds like a good idea :)
On Wed, May 06, 2015 at 05:09:07PM +0300, Mikhail Dubov wrote:
many thanks for noticing it, I didn't see it for some reason while looking
at the iCal file / checking the wiki.
No problem. Seeing conflicts is non-trivial. with 90+meetings in 4+ IRC
channels.
We will use another time then.
On Sun, May 10, 2015 at 08:49:11PM +, Steven Dake (stdake) wrote:
I have closed the doodle poll for our new meeting times. We will be meeting
in #openstack-meeting-3 (yes there is that much contention for our time slots
– must be a reason ;).
The times are:
Weekly Wednesday 1600 UTC
On Thu, May 14, 2015 at 04:52:23PM +0200, Thierry Carrez wrote:
So apparently the workshop has a max capacity of 40 people and folks
have to register in advance - they can't just show up to the session
without pre-registering. It would therefore be slightly
counter-productive to add it the
Hi All,
I have reasons but I need to use Ubuntu 15.04 and devstack. CLearly I can
run:
FORCE=yes ./stack.sh
and with a couple of patches I get a devstack up and running *For my
config/system*
I'm wondering what are the requirements for accepting something like:
-if [[ ! ${DISTRO} =~
On Fri, May 15, 2015 at 01:35:06PM +1000, Ian Wienand wrote:
On 05/15/2015 01:05 PM, Tony Breeds wrote:
I'm wondering what are the requirements for accepting something
like:
-if [[ ! ${DISTRO} =~
(precise|trusty|7.0|wheezy|sid|testing|jessie|f20|f21|rhel7) ]]; then
+if [[ ! ${DISTRO
Hi All,
Is there any chance we can get the Ally Skills Workshop added to the
schedule (specifally the design summit schedule)?
https://adainitiative.org/2015/04/register-now-ally-skills-workshop-at-openstack-summit-2015/
It'd be nice to see it on the schedule so I don't keep windering why
On Fri, Jun 05, 2015 at 01:18:57AM +, Gareth wrote:
As we could generate data dynamically, it is possible to develop a web UI
for it which shows real-time and readable scheduler table, provides
download link of custom meetings group, etc.
Sure I'm working on the second part (albeit
Hi All,
We've been using the new gerrit based irc-meetings repo for about 3 week
now. There have been teething troubles but by and large I think things are
going well. People have identified some tooling changes/enhancements that
we're workign on, buyt that's another thread.
A couple of
On Thu, Jun 11, 2015 at 11:33:14AM +0800, 苌智 wrote:
I met problem when run git review. It says that ssh: connect to host
review.openstack.org port 29418: No route to host . There is no response
when I run telnet review.openstack.org 29418. And my screen only displays
Trying
On Thu, May 28, 2015 at 01:18:01PM +0100, Daniel P. Berrange wrote:
There are a huge number of openstack meetings now, but I think that
each individual person will only be interested in a handful of them.
Adding the irc-meetings.ical to a calendar app really pollutes your
personal schedule,
On Fri, May 29, 2015 at 10:42:58AM +0530, yatin kumbhare wrote:
Great Work!
New meetings or meeting changes would be proposed in Gerrit, and
check/gate tests would make sure that there aren't any conflict.
--Will this tell upfront, that in any given day of week, which are all
meeting
On Wed, Jul 01, 2015 at 03:55:53AM +0200, Thomas Goirand wrote:
Please don't do this. This is the kind of job to be done by package
maintainers in distribution, because mostly, Python maintainers wouldn't
know how to do things correctly. Here we've got a good example: the bash
completion
Hi All,
I'm pretty new to this but I'll ask anyway. python-novaclient contains a
bash completion script . When installed from pypi this script isn't packaged
(and therefore it isn't installed).
I created https://review.openstack.org/#/c/196919/ to gather feedback on:
a) this this a thing we
On Thu, Jul 02, 2015 at 03:26:41AM +0200, Thomas Goirand wrote:
Use the source, luke! Or write yourself a small shell script...
I have, and I'm pretty sure that's where this conversation started.
If you attempt to address this, you're making my life miserable. Please
don't do it, thanks.
On Wed, Jul 01, 2015 at 03:28:06PM +, Ian Cordasco wrote:
So for people using the clients to talk to arbitrary clouds from their
personal computer (that can be running more than just linux) we need to
fix this. The problem is that if the person is installing a wheel or using
a new enough
On Wed, Jul 01, 2015 at 02:13:50PM +, Jeremy Stanley wrote:
On 2015-07-01 12:08:46 +1000 (+1000), Tony Breeds wrote:
Okay so I take you point no problem, but I'm not running distro
packages and I still want completions. There must be a way to
package the file to at least make it easier
On Wed, Jul 01, 2015 at 01:33:03PM +0200, Thomas Goirand wrote:
The file has nothing to do in /usr/share/doc either. By per the debian
policy manual: we shouldn't rely on /usr/share/doc, as it can be removed
entirely by the users. /usr/share/python-novaclient could be a place,
but really, the
On Wed, Jul 01, 2015 at 11:07:30PM +, Perry, Sean wrote:
BTW, see dh_bash-completion from the debhelper package. When in doubt about
packaging on a deb based distro look at the debhelper tools source (which is
perl).
-Original Message-
From: Perry, Sean
Sent: Wednesday, July
On Mon, Aug 17, 2015 at 03:51:46PM -0500, Matt Riedemann wrote:
What version of taskflow is installed? Cinder 2014.2.3 requires this
version of taskflow [1]:
taskflow=0.4,0.7.0
Which should get you taskflow 0.6.2, and taskflow 0.6.2 has this requirement
[2] for futures:
On Thu, Aug 20, 2015 at 02:12:44PM +0300, Eduard Matei wrote:
Hi,
ATM our workaround is to manually pip install futures==2.2.0 before running
stack.sh
Yeah that's what I did. You can also add that command to tools/fixup.sh
Any idea when an official fix will be available?
We're workign
On Tue, Aug 18, 2015 at 10:04:56PM +, Jeremy Stanley wrote:
On 2015-08-18 15:48:08 -0500 (-0500), Matt Riedemann wrote:
[...]
You'd also have to raise the cap on swiftclient in g-r stable/juno
to python-swiftclient=2.2.0,2.4.0.
[...]
Followed by stable point releases of everything
Hi All,
Firstly I apologise for the rambling nature of this email. There's a lot
of context/data here and I'm not sure of the best way to present it.
In [1] we discovered that stable/juno devstack is broken. After a little
digging
we opened [2] This required creating a stable/juno branch
On Fri, Aug 14, 2015 at 04:00:23AM +, Guo, Ruijing wrote:
I need to reboot hosts and restart openstack services. In this case, screen
may not help.
If you need to reboot the host then you shoudl re-run ./stack.sh
Yours Tony.
pgpVjQSWy881w.pgp
Description: PGP signature
On Fri, Aug 14, 2015 at 11:31:07AM +0800, Rui Chen wrote:
I use *screen* in devstack, Ctrl+c kill services, then restart it in
console.
Please try the following cmd in your devstack environment, and read some
docs.
*screen -r stack*
On Fri, Aug 14, 2015 at 04:01:20AM +, Guo, Ruijing wrote:
Yes. I like this idea to restart all services including nova, neutron,
cinder, etc:)
You can *probably* use
HOST=devstack.domain ./stack-smash.sh '.*'
to restart all the services running under devstack.
Note my list of windows
On Mon, Aug 10, 2015 at 01:34:03PM -0400, Andrew Laski wrote:
I'm only one data point, but we have a short TTL on tokens so it is not
something that our users could reasonably due. And the Nova default TTL is
10 minutes, which is also out of bookmarking range IMO.
So that's a good point. If
On Mon, Aug 10, 2015 at 07:16:43PM -0600, Matt Fischer wrote:
I'm not excited about making this the default until token revocations don't
impact performance the way that they do now. I don't know how often this
would get exercised though, but the impact of 100+ token revokes is
noticeable on
On Tue, Aug 11, 2015 at 08:24:10PM -0600, Matt Fischer wrote:
It was covered some here:
http://lists.openstack.org/pipermail/openstack-dev/2015-July/069658.html
and some graphs here: http://www.mattfischer.com/blog/?p=672
tl;dr is that having revoked tokens affects keystone token validation
On Mon, Aug 03, 2015 at 04:49:59PM +0100, Alexis Lee wrote:
Dugger, Donald D said on Mon, Aug 03, 2015 at 05:39:49AM +:
Also note that, although many capabilities can be represented by
simple key/value pairs (e.g. the presence of a specific special
instruction) that is not true for all
Hi All,
Nova has bug: https://bugs.launchpad.net/nova/+bug/1447679 (service No-VNC
(port 6080) doesn't require authentication).
Which explains that if you know the 'token'[1] associated with an instances
console you can get access to said console without otherwise proving that you
should be
On Fri, Nov 06, 2015 at 05:08:59PM +1100, Tony Breeds wrote:
> 4. Create a capabilitioes API of some description, that can be queried so
> that
> consumers (horizon) can known
Thanks everyone for the input. I'm going to go with the simple first step that
Sean described as it s
On Fri, Nov 06, 2015 at 02:42:20PM -0500, Sean Dague wrote:
> The upstream strategy has been make upgrades unexciting, and then folks
> can move forward easily.
>
> I would really like to unpack what those various reasons are that people
> are trapped. Because figuring out why they feel that way
On Fri, Nov 06, 2015 at 10:12:21AM -0800, Clint Byrum wrote:
> The argument in the original post, I think, is that we should not
> stand in the way of the vendors continuing to collaborate on stable
> maintenance in the upstream context after the EOL date. We already have
> distro vendors doing
On Fri, Nov 06, 2015 at 06:42:05PM +, Jeremy Stanley wrote:
> On 2015-11-06 10:12:21 -0800 (-0800), Clint Byrum wrote:
> [...]
> > Note that it's not just backporters though. It's infra resources too.
>
> Aye, there's the rub. We don't just EOL these branches for fun or
> because we hate old
On Fri, Nov 06, 2015 at 09:20:08AM -0600, Matt Riedemann wrote:
> It also extends the life and number of tests that need to be run against
> things in Tempest, which already runs several dozen jobs per change proposed
> today (since Tempest is branchless).
Okay this is something that I hadn't
On Fri, Nov 06, 2015 at 12:30:19PM +, John Garbutt wrote:
> Ideally, I would like us to fill out that pagination part first.
It seems the person leading this within the API-WG is AWOL so ...
> If we can't get global agreement quickly, we should at least get a
> Nova API wide standard
On Thu, Nov 12, 2015 at 02:40:19PM +0100, Alan Pevec wrote:
> AFAICT there are at least two blockers for 2014.2.4:
> - horizon - django_openstack_auth issue Tony mentions in
> https://review.openstack.org/172826
Horizon itself is fine BUT gets caught up in a mess of g-r updates. The issue
at
On Fri, Nov 06, 2015 at 05:15:18PM +1100, Tony Breeds wrote:
> Hello all,
>
> I'll start by acknowledging that this is a big and complex issue and I
> do not claim to be across all the view points, nor do I claim to be
> particularly persuasive ;P
>
> Having stated t
Hi All,
Around the middle of October a spec [1] was uploaded to add pagination
support to the os-hypervisors API. While I recognize the use case it seemed
like adding another pagination implementation wasn't an awesome idea.
Today I see 3 more requests to add pagination to APIs [2]
Perhaps
On Thu, Nov 05, 2015 at 01:09:36PM +1100, Tony Breeds wrote:
> Hi All,
> Around the middle of October a spec [1] was uploaded to add pagination
> support to the os-hypervisors API. While I recognize the use case it seemed
> like adding another pagination implementation wasn't an
Hello all,
I came across [1] which is notionally an ironic bug in that horizon presents
VM operations (like suspend) to users. Clearly these options don't make sense
to ironic which can be confusing.
There is a horizon fix that just disables migrate/suspened and other functaions
if the
Hello all,
I'll start by acknowledging that this is a big and complex issue and I
do not claim to be across all the view points, nor do I claim to be
particularly persuasive ;P
Having stated that, I'd like to seek constructive feedback on the idea of
keeping Juno around for a little longer.
On Thu, Nov 05, 2015 at 09:52:07PM +, Sean M. Collins wrote:
> I'll make sure to name the variable appropriately. Some ideas:
>
> SEAN_COLLINS_CREEPY_BASEMENT_DEVSTACK_LAB
> SEANS_DISCOUNT_DEVSTACK_EMPORIUM
> ANT_SIZED_SSD
ALL_YOUR_DISK_ARE_BELONG_TO_SCREEN?
Yours Tony.
pgp8xQipI_y6j.pgp
On Fri, Oct 16, 2015 at 03:32:21PM -0400, Doug Hellmann wrote:
> Excerpts from Tony Breeds's message of 2015-10-16 22:21:27 +1100:
> > Hi All,
> > We have an issue for any review that causes a new commit to ceilometer,
> > it
> > will fail with[1]:
> >
> > ValueError: git history
Hi All,
We have an issue for any review that causes a new commit to ceilometer, it
will fail with[1]:
ValueError: git history requires a target version of
pbr.version.SemanticVersion(5.0.1), but target version is
pbr.version.SemanticVersion(5.0.0)
Switching to post-versioning[2]
Hi Everybody,
So it looks to me like we recently updated logstash.openstack.org to a
newer version of kibabna?
I'll very openly admit that my logstash fu is wanting but I'm having a little
trouble
1) I can't work out how to after performing my query/filtering share the
results (for
On Sat, Oct 17, 2015 at 08:56:01AM +1100, Tony Breeds wrote:
> We actually need both https://review.openstack.org/233854
> and https://review.openstack.org/#/c/235536 to land at this point.
Okay https://review.openstack.org/233854 has merged
https://review.openstack.org/#/c/235536 is in
On Tue, Oct 13, 2015 at 05:08:29PM -0700, Zaro wrote:
> Hello All,
>
> The openstack-infra team would like to upgrade from our Gerrit 2.8 to
> Gerrit 2.11. We are proposing to do the upgrade shortly after the
> Mitaka summit. The main motivation behind the upgrade is to allow us
> to take
On Thu, Oct 08, 2015 at 11:08:06PM +0530, Rahul Arora wrote:
> Hi Team
>
> I am trying to run Openstack KILO release on my powerpc platform.I am able
> to cross compile all the KILO related packages using yocto framework.But
> while running the following command i am getting below error messages.
Hello all,
Voting has now closed in the Magnum PTL election. Thanks again to Adrian
and Hongbin for running.
Please join me in extending congratulations Adrian in retaining is role as PTL.
The results can be seen here:
http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_306b9309f2f39e38
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: finally:
On Mon, Aug 24, 2015 at 08:03:38AM -0400, Davanum Srinivas wrote:
Tony,
+1 to open Bugs and Reviews. I'll help move things along.
Hi Dims,
I've created:
https://bugs.launchpad.net/oslo.messaging/+bug/1488737
https://bugs.launchpad.net/oslo.utils/+bug/1488746
On Wed, Aug 26, 2015 at 03:11:56PM -0400, Doug Hellmann wrote:
Tony,
Thanks for digging into this!
No problem. It seemed like such a simple thing :/
I should be able to help, but right now we're ramping up for the L3
feature freeze and there are a lot of release-related activities going
On Fri, Aug 28, 2015 at 11:12:43AM +1200, Robert Collins wrote:
I'm pretty sure it *will* be EOL'd. OTOH thats 10 weeks of fixes folk
can get. I think you should do it if you've the stomach for it, and if
its going to help someone. I can aid by cutting library releases for
you I think
Hi All,
We have the test in $subject that is used for most (if not all) libraries
via the 'lib-forward-testing' job-group it's aim to to "test their proposed
commits to ensure they don't break OpenStack on their next release." [1]
This is of course a good idea.
The problem I;'m having is
Nominations for OpenStack PTLs (Program Technical Leads) are now open and will
remain open until September 17, 05:59 UTC.
All candidacies must be submitted as a text file to the openstack/election
repository as explained on the wiki[0].
In order to be an eligible candidate (and be allowed to
Hi all,
In trying to fix a few stable/juno issues we need to release a new version
of ceilometerclient for stable/juno. This email is to try and raise awareness
so that if the proposal is bonkers [1] we can come up with something better.
This isn't currently possible due to the current caps
On Wed, Aug 26, 2015 at 03:11:56PM -0400, Doug Hellmann wrote:
> Tony,
>
> Thanks for digging into this!
>
> I should be able to help, but right now we're ramping up for the L3
> feature freeze and there are a lot of release-related activities going
> on. Can this wait a few weeks for things to
On Fri, Sep 11, 2015 at 10:24:17AM +1000, Tony Breeds wrote:
> Nominations for OpenStack PTLs (Program Technical Leads) are now open and will
> remain open until September 17, 05:59 UTC.
>
> All candidacies must be submitted as a text file to the openstack/election
> reposito
On Tue, Sep 15, 2015 at 12:52:40PM -0400, Doug Hellmann wrote:
> I've created the branches for oslo.utils and oslotest, as requested.
> There are patches up for each to update the .gitreview file, which will
> make it easier to land the patches to update whatever requirements
> settings need to
A quick reminder that we are in the last hours for PTL candidate announcements.
If you want to stand for PTL, don't delay, follow the instructions on the
wikipage and make sure we know your intentions:
https://wiki.openstack.org/wiki/PTL_Elections_September_2015
Make sure your candidacy have
Hi all,
The recent relapse of oslo.utils 1.4.1[1] (for juno) is valid in kilo. The
juno global-requirements for Babel are not compatible with kilo so nothing can
get through grenade :(
We're working it
https://bugs.launchpad.net/oslo.utils/+bug/1496678
Yours Tony.
[1]
On Thu, Sep 17, 2015 at 03:01:53PM +1000, Tony Breeds wrote:
> Hi all,
> The recent relapse of oslo.utils 1.4.1[1] (for juno) is valid in kilo.
> The
> juno global-requirements for Babel are not compatible with kilo so nothing can
> get through grenade :(
>
> We'
On Thu, Sep 17, 2015 at 03:34:30PM +1000, Tony Breeds wrote:
> On Thu, Sep 17, 2015 at 03:01:53PM +1000, Tony Breeds wrote:
> > Hi all,
> > The recent relapse of oslo.utils 1.4.1[1] (for juno) is valid in kilo.
> > The
> > juno global-requirements for Babel are
On Thu, Sep 17, 2015 at 06:22:47AM -0400, Davanum Srinivas wrote:
> Tony,
> Looks like the ban is holding up:
> https://review.openstack.org/#/c/224429/
Sorry yes. Robert Collins pointed out that my new quicker plan wasn't going to
work so we went back to the original ban 1.4.1 solution.
It
On Thu, Sep 17, 2015 at 10:05:20AM -0500, Douglas Mendizábal wrote:
> I think someone jumped the gun on this thread. According to the wiki
> [1] the cutoff time is not until 5:59 UTC, which
> doesn't happen for another few hours. [2]
>
> Am I missing something?
From the wiki[0]:
---
Timeline
On Wed, Sep 16, 2015 at 11:40:28AM -0700, melanie witt wrote:
> Today I was informed that google forms are blocked in China [1], so I wanted
> to mention it here so we can consider an alternate way to collect submissions
> from those who might not be able to access the form.
I'll act as an
If you are a Foundation individual member and had a commit in one of Magnum's
projects[0] over the Kilo-Liberty timeframe (September 18, 2014 06:00 UTC to
September 18, 2015 05:59 UTC) then you are eligible to vote. You should find
your email with a link to the Condorcet page to cast your vote in
On Thu, Oct 01, 2015 at 05:48:25PM -0500, Kevin L. Mitchell wrote:
> It looks like Pillow (pulled in by blockdiag, pulled in by
> sphinxcontrib-seqdiag, in test-requirements.txt of nova and probably
> others) had a 3.0.0 release today, and now the gate is breaking because
> libjpeg isn't available
On Fri, Oct 02, 2015 at 03:34:47PM +1300, Robert Collins wrote:
> On 2 October 2015 at 12:00, Kevin L. Mitchell
> wrote:
> > On Thu, 2015-10-01 at 15:53 -0700, Clark Boylan wrote:
> >> On Thu, Oct 1, 2015, at 03:48 PM, Kevin L. Mitchell wrote:
> >> > It looks like
On Wed, Sep 23, 2015 at 08:47:31PM -0400, Chuck Short wrote:
> Hi,
>
> We would like to do a stable/kilo branch release, next Thursday. In order
> to do that I would like to freeze the branches on Friday. Cut some test
> tarballs on Tuesday and release on Thursday. Does anyone have an opinnon on
Hi All,
As most of you will have seen we used a gerrit based workflow for this PTL
election (and will use the same system for the upcoming TC election).
As a trial it went well, Tristan and I wrote a few tools to help the process
along. However I'd like to take advantage of a work session in
Candidate proposals for the Technical Committee positions (6 positions) are now
open and will remain open until October 1, 05:59 UTC.
All candidacies must be submitted as a text file to the openstack/election
repository as explained on the wiki[0].
Candidates for the Technical Committee
On Thu, Dec 03, 2015 at 07:42:43PM -0600, Matt Riedemann wrote:
> I already mentioned this to sdague before the nova meeting today (these are
> the things I think about while driving in the middle of nowhere), but option
> #3 won't work because boot from UEFI requires libvirt>=1.9.0, which we
1 - 100 of 633 matches
Mail list logo