I actually like the last option (sha) the most, even as a packager I can
just take the file and sort it if I want something more human readable.
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
y.
Part of the reason I've avoided packaging barbican is this page. That
and projects not really using it. I would like to see more projects
using barbican.
--
Matthew Thode (prometheanfire)
signature.asc
Description
necessitate a 4.0.2.1 release
* tag was removed, can hopefully be recovered for checkout/branch
Here's the upstream bug to browse at your leisure :)
https://github.com/rohe/pysaml2/issues/366
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital sign
in devconf.cz in a few weeks on this too. I hope to return
> with
> some additional feedback on using DIB for building container things.
>
I'd be interested in extending this to Gentoo at least. Need to reduce
the stage size somewhat. I wonder if stage2 is small enough..
docs will be worse without you. I do hope
you will be going on to greater things.
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not fo
On 11/23/2016 04:57 AM, Tony Breeds wrote:
> On Wed, Nov 23, 2016 at 04:39:30AM -0600, Matthew Thode wrote:
>> Does Openstack (infra) have a centralized calendar that teams could used
>> for reoccurring tasks/bugs? Something like this would be useful for
>> things rangi
usefulness for something like this for
audits the requirements team wishes to do to ensure no duplicate /
unmaintained libraries are used.
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital
hough, as we're really using the python module and not
> the binaries.
>
> --Adam
Is there a reason you are not using pecan?
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
then we're stuck with Octavia not being
> packageable in downstream distros.
That's not quite true for but is certainly true for most :P
* www-servers/gunicorn
Available versions: 19.1.1 ~19.3.0 ~19.4.5 {doc examples test
PYTHON_TARGETS="pypy python2_7 python3_3 py
most likely
> to be accepted of options 1 or 2.
>
> --Adam
Personally I'm happy with it being in gr, it's not the perfect place
though. (bindep would probably be better I feel, it's packaged on my
distro)
Do you need a specific version (bindep can't handle versions)
t; 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/openstack-dev
Awesome :D
Gentoo packages have been done for a few days with upgrades tested fro
https://bugs.launchpad.net/nova/+bug/1630448
At the moment I think the first bug is likely the cause of the second
bug, but don't have enough info to verify or fix it.
--
Matthew Thode (prometheanfire)
__
OpenStack D
'll wait for tony's feedback.
http://codesearch.openstack.org/?q=kuryr&i=nope&files=requirements.txt&repos=
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
_
his an FFE for that?
This would basically require a re-release (RC2) for all the projects at
this point.
http://codesearch.openstack.org/?q=swiftclient&i=nope&files=requirements.txt&repos=
--
-- Matthew Thode (prometheanfire)
signature
ked so far won't have a problem with this anyway as
they are using newer netaddr anyway (0.7.18 for both debian and gentoo
at least).
In short, if the releases and requirements teams are both fine with
this, ok :D (and tonyb is on both...)
--
-- Matthew Thode (
e of all
the things it impacts this late in the cycle. Is there ANY way we can
not merge this?
just some of the things that would need to be re-released
networking-ovn (just had their rc1)
os-net-config
os-vif
oslo.config
oslo.serialization
oslo.utils
oslo.versionedobjects
oslo.vmware
python-neu
'm currently running it on python 3
>> (through uwsgi).
>
> Is there a gate job to back that up?
>
> Doug
>
> __________
> OpenStack Development Mailing List (not for usage questions)
not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
It looks like this has limited impact so I'm ok with this. It (and the
keystonemiddleware ffe) are kinda late in the cycle th
t (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
Nothing in codesearch popped out at me so this looks fine.
--
-- Matthew Thode (prometheanfire)
signature.asc
De
t; Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
I think / thought keystone was supported on python 3 (maybe not all
features in mitaka though)
-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
Both of these are bumps to upper-constraints, which is good. Also, I
don't see a problem with downstream projects (as found via codesearch)
On 09/09/2016 04:24 PM, gordon chung wrote:
>
>
> On 09/09/16 03:45 PM, Matthew Thode wrote:
>> Does this mean that the minimum (GR needs raising as well)?
>
> iiuc, just the max or upper-constraints.
>
> cheers,
>
k, I already +2'd it as I think this
> 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/openstack-dev
>
Does this mean that the minimum (GR needs raising as well)?
--
-
..@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
I don't think this will impact and cause a rerelease for any project so
I'm fine with this.
e minimal supported version from
> 4.10.0+ to 4.13.3+ (when the later is even released; we are still at the
> stage of backport).
>
> Ihar
>
Ya that makes sense, the patch can be altered to just block 4.13.1,2
(assuming 4.13.3 really does fix it)
--
-- Ma
tack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
I think the backport/release and mask of the bad oslo.db should be enough.
--
-- Matthew
> 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/openstack-dev
>
Are you fine with the knock on effects tha
rt them to stable/newton) so this is
easier to merge.
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: ope
is is more minor than something more serious (not JUST
breaking testing).
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage
s (requirements) know when it's released
so we can make a feature freeze exception (and email the list with
[requirements][FFE] in the title).
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
___
On 08/18/2016 01:50 PM, Matt Riedemann wrote:
> On 8/18/2016 1:18 PM, Matthew Thode wrote:
>> Perhaps a better option would be to get oslo.db to run cross-project
>> checks like we do in requirements. That way the right team is covering
>> the usage of postgres and we stil
s://www.openstack.org/assets/survey/April-2016-User-Survey-Report.pdf
>
Perhaps a better option would be to get oslo.db to run cross-project
checks like we do in requirements. That way the right team is covering
the usage of postgres and we still have c
>
> I saw that Nova claims mod_wsgi is 'experimental'. Interested in it's
> really experimental or folks use it in production.
>
> Nick
I haven't found any docs on getting mod_wsgi working for glance do you
happen to have a link?
--
-- Matthew Thode (promethe
; https://www.openstack.org/assets/survey/April-2016-User-Survey-Report.pdf
>
I don't know about nova, but at least in keystone when I was testing
upgrades I found an error that had to be fixed before release of Mitaka.
Guess I'm part of the 4% :(
--
-- Matthew Thode (prometheanfire)
as well :D For me it's a case of having to test the packages I
build.
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
ted with uwsgi. I
should look into it again.
I even made a blog post about it a while back.
https://mthode.org/posts/2016/Mar/of-openstack-and-uwsgi/
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
___
g/cgit/openstack/keystone/tree/setup.cfg#n28
> |
>
> --
> - Brant
I look at it (as a packager), though it is somewhat dubious as to
whether or not what's there is actually needed. Having test-bindep
On 08/12/2016 01:47 PM, Andrey Pavlov wrote:
> ec2-api (and gce-api) already has this job, so I just add them to
> projects.txt, right?
>
> https://review.openstack.org/#/c/354899/
yep, looks good, +2
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digit
projects.txt
The relevant section of the readme is here.
https://github.com/openstack/requirements/#enforcement-in-projects
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
O
some subset :P
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:u
On 08/09/2016 01:37 PM, John Dickinson wrote:
> In that case, they are still co-installable, because the nova minimum
> satisfies both.
The requirements project currently advocates the use of
upper-requirements.txt as what is targeted for packagers. This is
what's tested.
--
-- Ma
On 08/09/2016 10:22 AM, Ian Cordasco wrote:
> -Original Message-
> From: Matthew Thode
> Reply: prometheanf...@gentoo.org , OpenStack
> Development Mailing List (not for usage questions)
>
> Date: August 9, 2016 at 09:53:53
> To: openstack-dev@lists.openstac
___
> 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/openstack-dev
>
One of the things
get better answers for your concerns.
>
> Thanks,
> Dims
>
To add, that list has been cleaned up since we first started, so there
was more on it then just that.
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
On 07/27/2016 04:08 PM, Jeremy Stanley wrote:
> On 2016-07-27 08:41:17 -0500 (-0500), Matthew Thode wrote:
>> We've started a period of self nomination in preparation for the
>> requirements project fully moving into project (as it's still under Doug
>> Hellmann).
/mailman/listinfo/openstack-dev
>
That's for the self nomination period. Immediately after that is when
the election would be, we may vote in the meeting that day for just one
of us to be put forward or do a normal election, I
On 07/27/2016 08:41 AM, Matthew Thode wrote:
> We've started a period of self nomination in preparation for the
> requirements project fully moving into project (as it's still under Doug
> Hellmann).
>
> We are gathering the self nominations here before w
hould also send an email to the openstack-dev list.
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: ope
On 07/22/2016 10:54 PM, Matthew Thode wrote:
> One of the things that seems to happen now and then is that an update to
> requirements breaks gate for other projects in some way. One thing that
> helps is cross project testing, though we do that on a one off basis I'd
> like to
le.html
So, my question to put to other projects is, which tests of yours do we
hit when requirements break things for you. This list will hopefully be
used to figure out what we can test our changes against to not cause the
badness.
Any notes on this would be appreciated :D
--
Matthew Thode
this kernel side.
http://lists.openwall.net/netdev/2015/02/18/2
I also package openstack for gentoo, which triggers things all over in
that side.
--
-- Matthew Thode (prometheanfire)
__
OpenStack Development Mailing List (n
though feel free to add your ++'s) I'd like to use this as a final
> call out in case any objections are wanting to be made. If none have
> been made by next Wednesday (6/8) I'll go ahead and add her to dib-core.
>
> Cheers,
> Greg
>
I'm good with it, no
kager here :D
The basic gist of it is that g-r.txt is what's expected to work and
u-c.txt is what's tested to work. There have been specs out there to
test a lower-contraints.txt file but I haven't seen it go anywhere quite
yet.
--
-- Matthew Thode (pr
nice to have just from a planning perspective.
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: opensta
gt; Doug
Thanks,
One of the bigger things I think would be good from spinning out a
team is to have scheduled meetings on IRC. Is there a way we can do
this without becoming an official project?
--
Matthew Thode (promethea
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
+1 because it still means something to me
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Deve
@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
https://etherpad.openstack.org/p/newton-backwards-compat-libs is about
the test matrix problem across releases.
Also, Gentoo at least supports partial up
of those downstream packagers I hope I'm not in that list.
This is my ordering of how I try and remediate a sec issue.
1. I try to apply the entire patch to affected versions.
2. If that doesn't work and I can remove the bad versions I do that.
3. If that doesn't work I have
bal requirements we would have to replace it with
> a lot of manual effort to push convergence overall.
>
Well said :D
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack
On 04/18/2016 02:10 PM, Jeremy Stanley wrote:
> On 2016-04-18 13:58:03 -0500 (-0500), Matthew Thode wrote:
>> Ya, I'd be happy to work more with upstream. I already review the
>> stable-reqs updates and watch them for the stable branches I package
>> for. No
ailman/listinfo/openstack-dev
>>>
>> As Sean stated, I didn't mean to come across as a threat, but it is the
>> most likely outcome of doing this. Yes, I could technically package a
>> venv but then I'd be concerned about security issues that come w
nv installed to /usr/local or /opt
>> exists bundling is not something that should be supported given the
>> issues it can have (update cadence and security issues mainly).
>
> That's a useful data point, but it comes across as a threat and I'm
> having trouble taking it as a
id, in my opinion, this percentage is this high because
> that's exactly what we suggest in install docs, once we came out with
> a solution we should fix it there as well.
>
>
> On 18 April 2016 at 10:23, Matthew Thode wrote:
>> On 04/18/2016 08:24 AM, Hayes, Graham wrot
>
> 0 -
> https://www.openstack.org/assets/survey/April-2016-User-Survey-Report.pdf
> (page
> 36)
>
> __________
> OpenStack De
e: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
If you will be in the other cross project sessions we can talk, we might
(or might not) share similar opinions :P
--
-- Matthew Thode (prometheanfire)
_
On 04/08/2016 03:16 PM, Thomas Goirand wrote:
> On 04/08/2016 07:47 PM, Matthew Thode wrote:
>> On 04/08/2016 11:47 AM, Thomas Goirand wrote:
>>> Another thing is that the Debian packages are the only ones available
>>> for many services, as Canonical doesn't
nly OS where it can be installed.
Saying that it's the only OS where some packages can be installed is not
nice to the other packagers /s
-- Matthew Thode (prometheanfire)
__
OpenStack Development Mailing List (not for u
While we have had 2016.1. packages (ebuilds that track the
stable/mitaka branches) and it has already seen deployment I'm now happy
to announce that now that the tarballs are up we also have ebuilds based
on the tags/tarballs.
--
Matthew Thode (prometheanfire)
signature.asc
Descri
On 03/27/2016 07:35 PM, Matt Riedemann wrote:
>
>
> On 3/27/2016 7:18 PM, Matthew Thode wrote:
>> On 03/27/2016 04:53 PM, Matt Riedemann wrote:
>>>
>>>
>>> On 3/25/2016 11:15 PM, Matthew Thode wrote:
>>>> I've finished packaging mita
On 03/27/2016 04:53 PM, Matt Riedemann wrote:
>
>
> On 3/25/2016 11:15 PM, Matthew Thode wrote:
>> I've finished packaging mitaka on Gentoo, won't be marked stable for
>> about a month. The version packaged is based off of the stable/mitaka
>> branch (noted
p in
testing if anyone knows where it is.
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: ope
On 03/25/2016 12:27 PM, Brant Knudson wrote:
>
>
> On Fri, Mar 25, 2016 at 9:54 AM, Matthew Thode
> mailto:prometheanf...@gentoo.org>> wrote:
>
> I'm updating the packaging for openstack in preparation for the release
> and need some info to update corr
On 03/25/2016 09:54 AM, Matthew Thode wrote:
> I'm updating the packaging for openstack in preparation for the release
> and need some info to update correctly. I'm specifically looking at the
> following services.
>
> I don't know if any of these services supp
wsgi/wsgi.py
neutron - probably - neutron/server/wsgi_pecan.py
nova - probably - both in nova/wsgi/
heat - probably - three under heat/httpd/
Don't think docs are out yet (which would likely have some of this
info), but any info you have around this would help.
--
-- Matthew Thode (prometh
>
Coming across a bit strong :P
While we (gentoo) are able to build the docs in our git branch based
ebuilds (sys-cluster/nova-2015.2. for liberty for example) we can't
do so in our tag based ebuilds don't think tarballs.openstack.org does
(or should) ship the .git folder. For us, building docs a
usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
I would like this to be the option we go with. I've wanted to add
another OS to OSA but need to fulfil other prerequisit
;
> -Sean
>
python wheel repo could help maybe?
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsub
le to unclog
> those updates
>
> thanks,
> Dims
>
> On Tue, Nov 3, 2015 at 2:37 PM, Matthew Thode
> wrote:
>> Are these constraints locked in place for the entire release cycle? It
>> doesn't look like the stable/liberty version has been updated since
le version).
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.ope
ibe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
I think doing a self signed CA can work fine, especially if the private
details are kept on the deployment host. The specific scenario I
envi
Didn't see a message on the announce list for that.
--
Matthew Thode (prometheanfire)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstac
discussions.
>
> I thought it was
> http://mitakadesignsummit.sched.org/event/0a2307779b4ab81892ba24de379e9dcc#.ViAMfd94u00
> that it was slated for, where its squarely on topic :)
>
> -Rob
>
I'd be nice if we can get this sorted, personally I can't make
d juno as fast as I could
because of how bad it became. kilo has been much better.
>> So, does this mean that I can just leave the packages uncapped and know
>> that they will work? Are there tests being run for this scenario?
>
> No, though I *want* us to get to that place, and t
On 10/15/2015 05:29 PM, Robert Collins wrote:
> On 16 October 2015 at 11:21, Matthew Thode wrote:
>> On 10/15/2015 05:12 PM, Robert Collins wrote:
>>> On 16 October 2015 at 08:10, Matthew Thode
>>> wrote:
>>>> On 10/15/2015 02:04 PM, Robert Collins
On 10/15/2015 05:12 PM, Robert Collins wrote:
> On 16 October 2015 at 08:10, Matthew Thode wrote:
>> On 10/15/2015 02:04 PM, Robert Collins wrote:
> ...
>>>> Where are my caps?
>>>
>>> The known good versions of dependencies for liberty are
>>> h
On 10/15/2015 02:17 PM, Matt Riedemann wrote:
>
>
> On 10/15/2015 2:10 PM, Matthew Thode wrote:
>> On 10/15/2015 02:04 PM, Robert Collins wrote:
>>> On 16 October 2015 at 08:01, Matthew Thode
>>> wrote:
>>>> So, this is my perspective in pack
On 10/15/2015 02:04 PM, Robert Collins wrote:
> On 16 October 2015 at 08:01, Matthew Thode wrote:
>> So, this is my perspective in packing liberty for Gentoo.
>>
>> We can have multiple versions of a package available to install, because
>> of this we generally d
package for liberty, I can see this
going very bad very quick.
Where are my caps?
--
Matthew Thode (prometheanfire)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.op
.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> Looks like the 2015.1.2 tag is up and now we need to bump the version to
> 2015.1.3 in setup.cfg for the projects, I don't see a series up for that
> yet but it's blocking anything from passing tests on stable/kilo now.
though hey -
> if Fedora and Debian and Ubuntu folk are all interested in figuring
> out a sustainable way forward, that would be great: please don't feel
> cut out, I'm just not expecting anything.
>
> If there are other approaches, great - please throw them u
t; Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
Thanks for the updated list. I'll get to packaging these now so I'll
hopefully have less work when liberty is tagged.
--
-- Matt
e
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
I think this is something we'd be interested in. A BP would be appreciated.
--
Matthew Thode (prometheanfire)
__
OpenStack Development M
On 09/14/2015 03:28 AM, Jesse Pretorius wrote:
> On 10 September 2015 at 19:21, Clint Byrum <mailto:cl...@fewbar.com>> wrote:
>
> Excerpts from Major Hayden's message of 2015-09-10 09:33:27 -0700:
> > Hash: SHA256
> >
> > On
On 09/10/2015 11:33 AM, Major Hayden wrote:
> On 09/10/2015 11:22 AM, Matthew Thode wrote:
>> Sane defaults can't be used? The two bugs you listed look fine to me as
>> default things to do.
>
> Thanks, Matthew. I tend to agree.
>
> I'm wondering if it wo
___
> 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/openstack-dev
>
Sane defaults can't be used? The two bugs yo
>
This might be useful in openstack-ansible if we are going to want to use
openstack-ansible for testing. Might want infra's feedback on that
though, also a spec would be in order (to openstack-ansible) for this.
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital
On 08/21/2015 05:59 PM, Robert Collins wrote:
> On 22 August 2015 at 10:57, Matthew Thode wrote:
>> Packaging for us is fairly easy, but it is annoying to have to add 5-6
>> deps each release, (which means we are adding cruft over time).
>
> We're adding functionali
gt; other issue that would be harder to test for.)
>
> Doug
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@li
On 08/20/2015 09:22 AM, Ian Cordasco wrote:
>
>
> On 8/19/15, 19:31, "Matthew Thode" wrote:
>
>> On 08/19/2015 07:22 PM, Ian Cordasco wrote:
>>> Questions in-line, but I'd appreciate a better summary
>>>
>>> On 8/19/15, 17:50, "M
On 08/19/2015 07:22 PM, Ian Cordasco wrote:
> Questions in-line, but I'd appreciate a better summary
>
> On 8/19/15, 17:50, "Matthew Thode" wrote:
>
>> I'll start by giving this out, but I'll also summarize the asks we had
>>from upstrea
201 - 300 of 320 matches
Mail list logo
