https://github.com/stackforge/wsme/blob/0.6.2/setup.py (also in master)
File "/usr/lib64/python2.7/site-packages/wsme/types.py", line 15, in
import ipaddr as ipaddress
https://github.com/stackforge/wsme/blob/master/wsme/types.py#L12-L15
--
-- Mat
On 11/21/2014 10:42 AM, Jeremy Stanley wrote:
> On 2014-11-20 21:12:33 -0600 (-0600), Matthew Thode wrote:
>> https://github.com/stackforge/wsme/blob/0.6.2/setup.py (also in master)
> [...]
>
> Your message is terse so I'm not sure whether you're asking a
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
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
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
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
;
> -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
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
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
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
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
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
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
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)
_
>
> 0 -
> https://www.openstack.org/assets/survey/April-2016-User-Survey-Report.pdf
> (page
> 36)
>
> __________
> OpenStack De
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
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
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
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
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
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
@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
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
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
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
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
pendencies are expected to be without loops
(at least that's the case for us). In this case, I'd install oslotest
without tests, then install os-client-config with tests then reinstall
oslotest with tests.
--
-- Matthew Thode (prometheanfire
_
> 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
>
oslotest deps on os-client-config
2.2.1 version (which is vulnerable to 3 CVEs).
>
>
>
> Best Regards,
> Elena.
>
>
>
>
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsu
> 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
>
Some of the
at the end
- Don't strip out files in the repo when publishing to pip
- Publish an example init-script (systemd)
- I think this might be going away with wsgi
Docs:
- nginx wsgi examples
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP di
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
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
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/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
>
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
___
> 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
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
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
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
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
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
.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.
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
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
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 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 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
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
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
Gentoo at least.
We've had 1.3.1 available for some time now (though not stablized yet,
even then it will not mater). Are you not able to either create a
meta-package or package the two versions side by side (mutually
exclusive install of course)?
--
-- Matthew Thode (prometheanfire)
signatu
good fixes to have and should have been
> merged by now.
>
> Personally I've been trying to point out some of these in the
> #openstack-stable IRC channel when I see them so that we don't wait so
> long on these that they fall into a stable s
le branch HEADs at that time.
>
>> Thanks in advance for your feedback,
>
>> [1] https://etherpad.openstack.org/p/YVR-relmgt-stable-branch
>
>
> __
> OpenStack Development Mailing List (not for usa
y thinking of installing a file somewhere that references
what commit hash the package was sourced from. I'm thinking of doing
weekly releases.
Tarball generation would be nice.
You will get different checksums with tar and/or gzip, you can check the
extracted files and they should be
> __
> 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
&g
On 06/03/2015 06:47 AM, Sean Dague wrote:
> On 06/02/2015 10:40 PM, Matthew Thode wrote:
>> On 06/02/2015 05:41 PM, James E. Blair wrote:
>>> Hi,
>>>
>>> This came up at the TC meeting today, and I volunteered to provide an
>>> update from the discussio
t;
> What would be your preferred option ?
>
Either A or D are what I will likely do. Also, I'll likely build infra
on my end to generate ebuilds like B proposes.
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
ething. I think this is the standard way most
distros signify changes from the base package.
--
Matthew Thode
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage que
/23.253.251.73/
Let me know if you have questions,
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
this is
>> normal, but one-time.
>
> So, while I get that it's all equivalent, it's pretty unhuman friendly
> to specify this in this order. Can we get >(=)* first, != next, and
> <(=)* last
>
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
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
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
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
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/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
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
-neutron.spec#L700
>
>> Regards, /Ihar
>
>> /Ihar
>
>> __________
>
>
>
> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack
u...@lists.openstack.org?subject:unsubscribe>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Uns
known-good,
> we should use ~=1.2 (e.g. >=1.2, ==1.*), but with date based its
> harder to predict what will indicate a breaking version :). And of
> course for non-semver, 1.2.3 doesn't tell us whether 1.3 will be
> breaking, or even 1.2.4.
> - a known good version to base our
rest of openstack (and we'd have to
remove you from gr-updates eventually as well).
>
> Thanks!
>
>
> [1] https://github.com/openstack/requirements
> [2] https://github.com/openstack/nova-dpm
> [3] https://github.com/openstack/networking-dpm
> [4] https://github.com/open
After a short delay for reasons Openstack is now up to date on Gentoo.
Just `emerge =sys-cluster/openstack-meta-2017.1.` with your desired
use flags to pull in the head of the services stable branches and their
dependencies.
--
Matthew Thode (prometheanfire)
signature.asc
Description
, even if it's done perfectly. If
it's not done perfectly we have to deal with untangling the requirements
for a security update (or the like).
--
Matthew Thode (prometheanfire)
signature.asc
Descripti
gt;>> 3) Keep diskimage-builder under tripleo (EmilienM PTL).
> We don't want to carry this one anymore for the reasons mentioned in
> that thread.
>
As a sometimes contributor to DIB for Gentoo stuff I'm fine with moving
it out into it's own project under the big tent,
he
affected projects.
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...
dome+owner:dims-v
>
> Thanks,
> Dims
>
> On Wed, Mar 8, 2017 at 2:03 PM, Matthew Thode
> wrote:
>> So, pycrypto upstream is dead and has been for a while, we should look
>> at moving off of it for both bugfix and security reasons.
>>
>> Currently it
cific timeframe?
>
> Thanks for surfacing it Matthew.
>
> -amrith
Heh, thanks, I suspect a few things are fairly cross project for
requirements. Moving to new webob / eventlet / sqlalchemy for instance.
Is there a specific process we go through to do these?
--
Matthew Thode (prome
do stuff that
> upstream can't (or won't) do.
>
> Chris
Us distro folks don't like it either :P
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
s pbr.
mistral
os-apply-config
os-collect-config
os-refresh-config
os-vif
If these projects could make a release (something fetchable by pypi) off
of master that's all that's needed. They all have updated their
requirements in master, just no consumable release.
--
Matthew Thode
https://review.openstack.org/#/q/project:openstack/requirements+status:open+NOT+branch:master
We currently do not have anyone able to review/workflow these items and
it'd be nice if we could get some eyes on these reviews.
Thanks,
--
Matthew Thode (prometheanfire)
signature.asc
Descri
on irc as prometheanfire in the #openstack-requirements channel.
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubs
obably want to add a review criteria to the requirements list that
> projects using the cycle-with-milestone model are not added to the list
> to avoid this issue in the future.
>
> Doug
>
> ______
> OpenStack
On 05/30/2017 04:08 PM, Emilien Macchi wrote:
> On Tue, May 30, 2017 at 8:36 PM, Matthew Thode
> wrote:
>> We have a problem in requirements that projects that don't have the
>> cycle-with-intermediary release model (most of the cycle-with-milestones
>> mod
Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
>
>
>
&g
ck
> projects and their deliverables.
>
> A huge improvement from where PTLs in Mitaka and prior were manually
> tagging and signing deliverables, handling the release note process, and
> all other sorts of minutia that required extreme care and focus.
>
> A fine example of
lman/listinfo/openstack-dev
>
>
>
> --
> Davanum Srinivas :: https://twitter.com/dims
>
> ______
> OpenStack Development Mailing List (not for usage ques
t'd be good to be in sync. The
same could be said to many of the bumps that go through the requirements
project. One of the things we've been working on is divergent
requirements, where the goal is to keep making sure all projects test
against one set of upper-constraints, b
opment 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
> > >
> >
>
>
only affects a small
> number of projects, so the risk is fairly small.
>
> I assume you've done enough testing to feel comfortable that 4.5.2 will
> work better than 4.5.0 and 4.5.1?
>
> Doug
>
> ___
7;t see anything that worries me.
>
> From a requirements POV I'm +2 on a u-c bump -2 on a g-r bump.
>
> Yours Tony.
Agreed, the amount of projects that'd be impacted by a GR bump is too
high, but a UC bump is fine.
--
Matthew Thode (prometheanfire)
signature.asc
Descript
ease release this and take the new version in for requirements repo,
>
> https://review.openstack.org/490001
>
> Andreas
Looks fine here, are you looking for just a UC bump?
--
Matthew Thode (prometheanfire)
signatu
subscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
This is fine with me, it's not used anywhere at the moment so doesn't
look to have any knockon effects.
http://
time,
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
s)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
It sounds like you will need a requirements update as well, both UC and
maybe GR. GR would suck at this VERY late point. The cur
On 17-08-08 08:03:42, Matthew Thode wrote:
> On 17-08-08 16:11:53, Renat Akhmerov wrote:
> > Hi,
> >
> > We recently sent a patch [1] to release the version 3.1.2 of
> > python-mistralclient out of Pike branch. It was done after the date of
> > final client
e will
> be added to the core group in a few days.
>
> --
> Best,
> Samuel Cassiba
>
I haven't worked with him in an openstack chef way, but I've worked with
him through the OSUOSL. He's always been great to work with. IIRC the
OSUOSL also uses chef to deploy op
The current plan is to thaw requirements on Monday. If that happens
you'll need to be very careful in reviewing any bot updates from our
master (queens) to your master (pike).
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
___
ch if you can though.
If you have questions, feel free to reach out to me on irc
(prometheanfire on freenode, #openstack-requirements for the channel) or
email.
--
Matthew Thode (prometheanfire)
signature.asc
Descri
___
> 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
--
Matthew Thode (prometheanfire
channel.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
1 - 100 of 320 matches
Mail list logo
