On Sat, 10 Nov 2018 at 23:03, Thierry Carrez wrote:
>
> Robert Collins wrote:
> > There don't seem to be any topics defined for -discuss yet, I hope
> > there will be, as I'm certainly not in a position of enough bandwidth
> > to handle everything *stack related
On Sat, 10 Nov 2018 at 07:15, Jeremy Stanley wrote:
>
> REMINDER: The openstack, openstack-dev, openstack-sigs and
> openstack-operators mailing lists (to which this is being sent) will
> be replaced by a new openstack-disc...@lists.openstack.org mailing
> list. The new list is open for subscripti
On 26 March 2018 at 09:08, Doug Hellmann wrote:
> Excerpts from Doug Hellmann's message of 2018-03-25 16:04:11 -0400:
>> A few of the jobs failed because the dependencies were wrong. In a few
>> cases I was able to figure out what was wrong, but I can use some help
>> from project teams more famil
On 20 February 2018 at 04:39, Andrey Kurilin wrote:
> Can someone explain me the reason for including "tests" module into
> packages?
Namespacing the tests makes the test ids unique which is very helpful
for aggregating test data as we do. Including that in the tar.gz that
is uploaded to PyPI is
On 3 Feb. 2017 16:14, "Robert Collins" wrote:
This may help. http://jam-bazaar.blogspot.co.nz/2009/11/memory-
debugging-with-meliae.html
-rob
Oh, and if i recall correctly run snake run supports both heapy and meli
This may help.
http://jam-bazaar.blogspot.co.nz/2009/11/memory-debugging-with-meliae.html
-rob
On 3 Feb. 2017 10:39, "Armando M." wrote:
>
>
> On 2 February 2017 at 13:36, Ihar Hrachyshka wrote:
>
>> On Thu, Feb 2, 2017 at 7:44 AM, Matthew Treinish
>> wrote:
>> > Yeah, I'm curious about this
On 10 Nov 2016 9:29 PM, "Tony Breeds" wrote:
>
> On Thu, Nov 10, 2016 at 08:48:16PM +1300, Robert Collins wrote:
>
> > We generate multiline constraints whenever versions are different
> > between python 2 and 3 for the same package. That was happening when I
> &
On 10 November 2016 at 11:00, Tony Breeds wrote:
> On Thu, Nov 10, 2016 at 06:17:44AM +1300, Robert Collins wrote:
>> Sed doesn't exist on windows, whereas a python script can. Sed doesn't
>> handle multiple line constraints.
>
> I don't think that right now
Sed doesn't exist on windows, whereas a python script can. Sed doesn't
handle multiple line constraints.
Rob
On 10 Nov 2016 12:00 AM, "Ihar Hrachyshka" wrote:
>
> > On 8 Nov 2016, at 04:07, Tony Breeds wrote:
> >
> > On Sat, Sep 03, 2016 at 07:33:42PM +0200, Andreas Jaeger wrote:
> >> Reviewin
I'm not in Barcelona, but am interested : please do try to capture
some prose around the resulting design for us there-in-spirit folk.
-Rob
On 26 October 2016 at 01:50, Tony Breeds wrote:
> Hi All,
> I'd like to highlight a requirements session:
>
> https://www.openstack.org/summit/barcelona
On 31 August 2016 at 01:57, Clint Byrum wrote:
>
>
> It's simple, these are the holy SQL schema commandments:
>
> Don't delete columns, ignore them.
> Don't change columns, create new ones.
> When you create a column, give it a default that makes sense.
I'm sure you're aware of this but I think i
On 12 August 2016 at 12:09, Clay Gerrard wrote:
>
>
> On Fri, Aug 12, 2016 at 11:52 AM, Andreas Jaeger wrote:
>>
>> On 08/12/2016 08:37 PM, Clay Gerrard wrote:
>> >
>> > ... but ... it doesn't have a --install option? Do you know if that is
>> > strictly out-of-scope or roadmap or ... ?
>>
>>
>>
Fantastic news Andreas!
-Rob
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openst
On 11 Aug 2016 3:13 PM, "Ben Swartzlander" wrote:
>
> ...
>
> I still don't agree with this stance. Code doesn't just magically stop
working. Code breaks when things change which aren't version controlled
properly or when you have undeclared dependencies.
Well this is why the constraints work was
On 27 June 2016 at 13:20, Jens Rosenboom wrote:
> 2016-06-22 9:18 GMT+02:00 Victor Stinner :
>> Hi,
>>
>> Current status: only 3 projects are not ported yet to Python 3:
>>
>> * nova (76% done)
>> * trove (42%)
>> * swift (0%)
>>
>>https://wiki.openstack.org/wiki/Python3
>
> How should differe
Removing the pbr branch should be fine - it was an exceptional thing
to have that branch in the first place - pbr is consumed by releases
only, and due to its place in the dependency graph is very very very
hard to pin or cap.
-Rob
On 25 June 2016 at 12:37, Tony Breeds wrote:
> On Fri, Jun 24, 2
Sure. +1
On 17 June 2016 at 02:44, Davanum Srinivas wrote:
> Folks,
>
> At Austin the Release Management team reached a consensus to spin off
> with some new volunteers to take care of the requirements process and
> repository [1]. The following folks showed up and worked with me on
> getting fam
This might come across a little trolly/devils advocate, but I mulled
on it for a few days, and I think I need to send it, so... fingers
crossed you can extract some value from my questions.
On 15 June 2016 at 01:57, Thierry Carrez wrote:
> Hi everyone,
>
> I just proposed a new requirement for Op
On 12 June 2016 at 11:31, Thomas Goirand wrote:
> On 06/11/2016 05:02 AM, Robert Collins wrote:
...
> Then keystone.conf ends up installed in /usr/etc/keystone when setup.py
> install is used. With this configuration, it would be installed
> correctly within a venv.
Except tha
The underlying problem is as you say that distutils and setuptools and
wheel are all different, and until there is a PEP addressing this
*and* implemented in both wheel and setuptools, we won't get
consistent behaviour. I'm pretty sure Daniel Hoth is interested in
making this happen - there have be
On 19 May 2016 at 22:40, Dmitry Tantsur wrote:
>
>> You are correct that my position is subjective, but it is based on my
>> experiences trying to operate and deploy OpenStack in addition to
>> writing code. The draw of Go, in my experience, has been easily
>> deploying a single binary I've be
On 18 May 2016 at 19:55, Ihar Hrachyshka wrote:
>
>> On 18 May 2016, at 05:31, Darek Smigiel wrote:
>>
>> Hello Stable Maint Team,
>> It seems that python-neutronclient gate for Liberty is broken[1][2] by
>> update for keystoneclient. OpenStack proposal bot already sent update to
>> requirement
On 19 May 2016 at 01:40, Ihar Hrachyshka wrote:
> Great write-up. Do you plan to capture it e.g. in project guide?
It's already fully documented in the requirements repo README; if
there is no link to that from the project-guide, we should add one,
but I would not duplicate the content.
-Rob
__
On 17 May 2016 at 23:47, Davanum Srinivas wrote:
> Team,
>
> Let's meet in #openstack-meeting-cp channel at 12:00 UTC on May 18th:
> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016&month=5&day=18&hour=12&min=0&sec=0&p1=43&p2=240&p3=195&p4=166&p5=83&p6=281&p7=141
>
> We can deci
On 18 May 2016 at 00:54, Brian Rosmaita wrote:
>> Couple of examples:
>> 1. switching from "is_public=true" to "visibility=public"
>
>
> This was a major version change in the Images API. The 'is_public' boolean
> is in the original Images v1 API, 'visibility' was introduced with the
> Images v2
On 18 May 2016 at 07:32, Andre Florath wrote:
> Hi All!
>
> AFAIK the diskimage-builder started as a testing tool, but it looks
> that it evolves more and more into a general propose tool for creating
> docker and VM disk images.
We started as a fast, production, targeted image builder suitable f
On 13 May 2016 at 00:01, Thierry Carrez wrote:
> Robert Collins wrote:
>>
>> [...]
>> So, given that that is the model - why is language part of it? Yes,
>> there are minimum overheads to having a given language in CI [...]
>
>
> By "minimum" do you m
I'm going to try arguing the pro case.
The big tent has us bringing any *team* that want to work the way we
do: in the open, collaboratively, in concert with other teams, into
OpenStacks community.
Why are we using implementation language as a gate here?
I assert that most deployers don't fundam
nd chatting
via locks. Using an RPC model (similar to privsep) would probably be
more flexible and easier, with at most a small speed cost. Worth
trying a few things to get experience?
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
___
a good
pattern (on Linux), at least last I heard the underlying problems have
not been solved.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
OpenStack Development Mailing List (not for usage ques
-identity-provider
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?
being used in Designate (or OpenStack as a whole) are driving whatever
specific problem you've got?
I know that our current programming model is missing a lot of the
easily-correct improvements that have been created in the last few
decades (because our basic abstraction is t
TCP will rapidly run into
terrible scaling problems - quadratic overheads - with select.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
OpenStack Development Mailing List (not for usage
f
languages in play is a thing we want to do, we should make sure we're
actually using the best facilities of our existing languages first!
On the Designate side, PyPy got a 40% performance improvement over
CPython for a benchmark of Twisted's DNS component 6 years ago - and
Twis
On 10 May 2016 at 10:55, Anita Kuno wrote:
> On 05/09/2016 06:45 PM, Robert Collins wrote:
>> IIRC mediawiki provides RSS of changes... maybe just using the wiki
>> more would be a good start, and have zero infra costs?
>>
>> -Rob
>
> Well we are actually moving
ng List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
_
ribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
OpenStack Development Mailin
That won't get you running the new kernel; for that you need to change
the image itself.
-Rob
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsu
rojects: os-brick,
python-neutronclient etc etc: though I believe folks in such projects
are generally cautious as well.
The key thing here is that we already have to do backwards compat to
move folk off of a poor API onto a new one: all this policy says is
that the grace period needs to cross release boun
r how many other folk are trying to attempt such a thing -
anyone care to raise their metaphorical hand?
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
OpenStack Development Mailing List (not fo
hem rolled out and used), we can do our garbage collection
much more rapidly - even same-cycle.
https://etherpad.openstack.org/p/newton-backwards-compat-libs
-Rob
--
Robert Collins
Distinguished Technologist
HP Conve
onstitute a new team to put together a sizable POC (or
POCs - one per DB for a few DBs...) - an 80% thing - so folk can
actually assess how it look/feel at both a code and ops perspective.
Then, if the result *has met* those essential things, we should
actually have the a
on each other, because Nova depends on both and we want
to be able to actually install Nova.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
OpenStack Development Mailing List (not for usage questio
r constraints in
> another package on the system, the distro will just hold Nova back.
And presumably all of OpenStack.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
OpenStack Development Mailin
plode every few weeks would offset the cost of micromanaging every
> constraint update.
I also argued at the time that we should aim for entirely automated
check-and-update. This has stalled on not figuring out how to run e.g.
Neutron unit tests against requirements changes - our coverag
ints are federated out to
multiple trees.
Never needing any two projects to agree on compatible versions in CI
would allow us to change things without triggering a wedge...
possibly. *detailed* thought needed here - because consider for
instance the
r voice is heard.
>
> Thank you for another great round.
>
> Here's to Newton!
>
> Yours Tony.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http:
using - so whatever
$behind-the-abstraction setup they are using, but community accessible
and visible, unlike the current behind-corprorate-firewall setups.
I'm not saying this is better or worse, but it is different to the
tripleo approach of providing a Nova API endpoint for zuul.
-Ro
Hi everyone - I'm not submitting my hat for the ring this cycle - I
think its important we both share the work, and bring more folk up
into the position of having-been-on-the-TC. I promise to still hold
strong opinions weakly, and to discuss those in TC meetings :).
-Rob
--
Robert Co
Libraries
and clients however, are branching and being released from branches.
Do we merge release tags to master for them? If so, thats probably
perfect (though I haven't worked through it all in my head - public
holiday here so only paying partial attention)
_
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-b
So, I think we do need some aggressive means to bump master up past
the versions reserved for a stable branch, at the stable branches
creation.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
OpenStack
sult mod.__version__). Or you can alternatively query
the standard (https://www.python.org/dev/peps/pep-0345/ ) metadata
generated from python setup.py egg_info, if you prefer.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
On 25 March 2016 at 01:11, Alan Pevec wrote:
> 2016-03-24 2:21 GMT+01:00 Robert Collins :
>> Trunk will rapidly exceed mitaka's versions, leading to no confusion too.
>
> That's the case now, RC1 tags are reachable from both branches and
> master has more patches,
numbers that
> have not been tagged.
Thats ok, because thats an opt-in thing there - its not existing in
the same namespace as the mitaka builds for rdo, is it?
Trunk will rapidly exceed mitaka's versions, leading to no confusion too.
-Rob
--
ke tags early on every time. But I don't think we've got supporting
evidence that its more than you so far :).
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
OpenStack Devel
On 10 Mar 2016 2:58 AM, "Radomir Dopieralski"
wrote:
>
> On 03/09/2016 04:43 PM, Serg Melikyan wrote:
>>>
>>> This is exactly my first thought. The plugins *must* depend on Horizon,
>>> and they have to use the same versions of XStatic packages anyways,
>
> >> so why specify the dependencies twice
he beginning of this cycle, I'm convinced that this is a
useful opportunity for OpenStack as a whole, as well as for the
individuals that attend - I'm very glad you've been pushing
coordination of this forward. Thank you.
-Rob
--
Robert Collins
Distinguished Technologist
HP Conve
On 9 March 2016 at 14:23, Jeremy Stanley wrote:
> On 2016-03-09 13:57:45 +1300 (+1300), Robert Collins wrote:
>> On 9 March 2016 at 13:07, Jeremy Stanley wrote:
>> > On 2016-03-08 17:25:41 +1100 (+1100), Richard Jones wrote:
>> > [...]
>> >> SOLUTION 6 -
reak
every other user of xstatic when horizon updates'. :(.
So -> IRC and/or/perhaps voice?
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
OpenStack Development Mailing List (n
There is a fixture in pbr's test suite to create keys with out entropy use,
should be easy to adapt for user by Reno's tests.
On 1 Mar 2016 6:52 AM, "Thomas Goirand" wrote:
> On 02/29/2016 10:31 PM, Doug Hellmann wrote:
> >>> Give this a try and see if it works any better:
> >>> https://review.op
nne of complexity. I see from
http://www.rpm.org/ticket/56 that it only came in in RPM 4.10 - is RPM
4.10 available on all the RPM platforms we support? Including I guess
old RHEL's and stuff?
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
___
similar command for getting the deb version.
>
> I threw together https://review.openstack.org/#/c/285250/ with some
> additions to pbr's "info" command to expose these formats.
I'll review in detail on gerrit, but we probably want an optio
to-calculate a temporary "dev" version based on the lowest
> possible next version number which sorts after the most recent tag,
> but that's really only a reflection of what the next version should
> be _if_ all the changes since the last tag are trivial bug fixes.
No - its m
the corresponding Debian version
I don't think we expose that yet (but we should).
> - the corresponding RPM version.
As already mentioned, the rpm_version command exposes this.
-Rob
--
Robert Collins
Distinguished Techn
or Barbican : https://review.openstack.org/#/c/280014/
>
> What do you think?
>
> Thanks,
> Dims
>
>
> --
> Davanum Srinivas :: https://twitter.com/dims
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsu
s do change
things.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
h
ne should be importing 'unittest.mock', and 'mock' is the
dependency, not conditional on any given version of Python.
I'm sorry I didn't spot 268945 going through, or I would have -2'd it :(.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
o doing some reviews in oslo outside of pbr
itself - which she has said she is and can.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
OpenStack Development Mailing List (not for usage questions)
Unsu
tform to say to their organisation that the focus is X, don't
expect features to land - and that they are *expected* to help with
the cycle.
Without some framework, we're leaving those developers out in the co
gt; http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> --
> Davanum Srinivas :: https://twitter.com/dims
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ.
for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
_
sonally, I'm fine hacking on Twisted code - I quite like it
(particularly good Twisted code :)) - and since folk seem ok with that
aspect, great - thank you for raising the discussion here.
I look forward to hearing how it goes for Ironic.
-Rob
--
Rober
On 5 January 2016 at 12:04, Robert Collins wrote:
...
> Indeed -
> https://bitbucket.org/pypa/setuptools/commits/fb35fcade302fa828d34e6aff952ec2398f2c877?at=get_command_list
> - the failing bit AFAICT is indeed new code :/.
Ok, so I've paged this all in. Here's whats up, a
On 5 January 2016 at 12:01, Robert Collins wrote:
> On 5 January 2016 at 11:59, Robert Collins wrote:
>> This is odd indeed. pbr is not meant to have a dep on testrepository,
>> and you can see in
>> https://git.openstack.org/cgit/openstack-dev/pbr/tree/pbr/testr_command.py
On 5 January 2016 at 11:59, Robert Collins wrote:
> This is odd indeed. pbr is not meant to have a dep on testrepository,
> and you can see in
> https://git.openstack.org/cgit/openstack-dev/pbr/tree/pbr/testr_command.py#n150
> that we only access it if it is installed and we us
og.txt.gz
>> --
>> Matthias Runge
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...
to newer
better ones, they create long term maintenance work for oslo: so we
all need to work together to coordinate such things.
https://review.openstack.org/#/c/226157/12 is part of this - it is an
effort to bring consistency in expectations and process/patterns here.
-Rob
--
Robert
n updated, there's a review setting -constraints as the
expected pattern in the infra manual now.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
OpenStack Development Mailing List (not
ave bugs and code require
> backports to stable/liberty oslo-incubator for syncing to projects that use
> it.
I thought the thing to do was backport the application of the change
from the projects master?
-Rob
--
Robert Collins
Distinguished
hat thats correct, my suggestion would be that we either
make tox pip installed during jobs (across the board), so that we can
in fact control it with upper-constraints, or we work on functional
tests of new images before they go-live
-Rob
--
Robert Collins
Distinguished
gt; are failing to take up their share of things to be done. No, we should
> not increase more responsibility on Oslo team.
>
> -- Dims
>
> On Thu, Dec 10, 2015 at 8:25 AM, Robert Collins
> wrote:
> > On 10 December 2015 at 18:19, Davanum Srinivas
> wrote:
> >>
On 10 December 2015 at 18:19, Davanum Srinivas wrote:
> So clearly the deprecation process is not working as no one looks at
> the log messages and fix their own projects. Sigh!
I think we need some way to ensure that a deprecation has been done:
perhaps a job that we can run on each oslo project
https://review.openstack.org/#/c/226157/ is very close to consensus
now, at least as I read it. Please do weigh in this week, as I expect
the cross project meeting next week to be the last discussion of it
before it goes to the TC.
Cheers,
Rob
--
Robert Collins
Distinguished Technologist
HP
doesn't exist, and so its like step 2 was skipped. So - to avoid
confusing anyone, make sure you base the patch for step 3 on top of
the revision being tagged in step 2.
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
_
On 1 December 2015 at 08:37, Ben Nemec wrote:
> On 11/30/2015 12:42 PM, Joshua Harlow wrote:
>> Hi all,
>>
>> I just wanted to bring up an issue, possible solution and get feedback
>> on it from folks because it seems to be an on-going problem that shows
>> up not when an application is initially
https://wiki.debian.org/DebianBootstrap#Circular_dependencies.2Fstaged_builds
- covers the current state of the art, and should, AIUI, entirely
address your needs: you do one build that is just a pure build with no
tests-during-build-time, then when the build phase of everything is
covered, a sec
pip install nose
> nosetests .
i haven't seen any bug reports on testrepository vis-a-vis windows;
please do file them, otherwise I'll presume it works.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
_
t that makes me actually skeptical - the overheads of 2+3
single tree compat are really really low already, generally.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
OpenStack Development Mai
ve bitrot happening in docs jobs
across all of openstack, and its accruing project wide tech debt at an
unpleasant rate :(.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
OpenStack Development Maili
usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
rent discusion :)
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:un
d need the same robustness if we're trying to guarantee that the
comment is added.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
OpenStack Development Mailing List (not for us
nce they change the packages that one needs to not
use - but putting stuff in a user-install and not touching the system
packages is still superior and doesn't require any purging etc.
-Rob
--
Robert Collins
Dis
On 23 November 2015 at 22:33, Victor Stinner wrote:
> Hi,
>
> Would it be possible to use the "extra dependencies" thing in setup.cfg?
> Robert Collins started a similar change for Oslo DB for make DB drivers
> optional:
> https://review.openstack.org/#/c/184328/
&g
.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.op
that's terriblewhy are we doing that?
I know you know this, but yeah - don't do that :).
FWIW constraints *will* override that but liberty and above.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
___
On 17 November 2015 at 16:25, Jay Pipes wrote:
> On 11/15/2015 08:10 PM, Robert Collins wrote:
...
>
> Thanks, Robert, but unfortunately that didn't work. I still get the same
> problem:
>
> Downloading/unpacking .[fixtures]
> Could not find any downloads that satisfy
Yes, major version bump. As long as we don't have to change any consumers,
we have no backwards compatibility concerns because we deprecated 2.6 in
Juno. However i suspect we will have to change consumers specifically we
still had 2.6 jobs in liberty
On 17 Nov 2015 3:23 AM, "Davanum Srinivas" wrot
et remove python-pip python-virtualenv; install pip
using get-pip.py; sudo -H pip install virtualenv
More info here:
https://rbtcollins.wordpress.com/2015/07/12/bootstrapping-developer-environments-for-openstack/
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
___
1 - 100 of 1124 matches
Mail list logo
