vs. deep problem, let's not
assume deep and automatically cause a bunch of churn for everyone.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
distinction under the Reviewer
workload bullet item on the wiki page.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
are you signing up to do that review workload if not yourself?
That being said, there are always going to be human factors at play.
Not all commitments can always be met. I don't think we're going to
punish people who are acting in good faith.
--
-- James Slagle
suggesting here just looks at the problem differently,
it gives folks the opportunity to say, I'm going to focus on reviewing
these changes without dropping all my other reviews. And of course
this is just one of the criteria laid out on the wiki page before
approving a spec, amongst many.
--
-- James
questions about that if you have
any.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
a good addition to the core team.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
it is), then sure,
keep it all in contrib so that no one gets confused about why the
resources are there.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
(thread crossed into Sept)
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
On Wed, Sep 24, 2014 at 9:41 AM, James Slagle james.sla...@gmail.com wrote:
And it looks to me like what's being proposed here is that there is a
group of folks who intend to work on Knoll, and they are indicating
Oops, I meant Kolla, obviously :-).
--
-- James Slagle
On Wed, Sep 24, 2014 at 10:03 AM, Jay Pipes jaypi...@gmail.com wrote:
On 09/24/2014 09:41 AM, James Slagle wrote:
Meaning: exactly what you seem to claim is not possible due to some
perceived blessing, is indeed in fact happening, or trying to come
about.
:) Talking about something
.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Wed, Dec 11, 2013 at 10:35 AM, James Slagle james.sla...@gmail.com wrote:
On Wed, Dec 11, 2013 at 7:33 AM, Jiří Stránský ji...@redhat.com wrote:
1) Make a thicker python-tuskarclient and put the business logic there. Make
it consume other python-*clients. (This is an unusual approach though
to
a service class
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
to what is done for the undercloud.
I think most of that logic could be reimplemented to be done via direct calls
to the API using the client libs vs using a CLI. Not sure about
keystone-manage pki_setup though, would need to look into that.
--
-- James Slagle
://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
-- James Slagle
that first.
At the very least, this could be an easier way for developers to get
setup with tripleo to do a test overcloud deployment to develop on
things like Tuskar.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
as-is!
Great, thanks. I appreciate the feedback!
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
),
or use pre built vm's, etc.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
submit to help prove it out.
But, I'd like to start discussion on the approach now to see if there
are other ideas or major opposition to that approach.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
/README.md
for more info about that.
If you specified something that didn't exist, it should probably fail
with an error. The default behavior would still be installing from
git master source if you specified nothing though.
Thanks,
Kevin
From: James Slagle
about installation of the
components at image build time.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
. I'm proposing a way to install the OpenStack components
from packages at image build time.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
component that is known to work with the versions of dependent
software you already have installed.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
/garethbowles/building-netflixstreamingwithjenkins-juc
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
does.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Tue, Jan 7, 2014 at 11:20 PM, Robert Collins
robe...@robertcollins.net wrote:
On 8 January 2014 12:18, James Slagle james.sla...@gmail.com wrote:
Sure, the crux of the problem was likely that versions in the distro
were too old and they needed to be updated. But unless we take on
building
libraries
and increased image build time. Is anyone planning on making consolidated
venv's an option? Or perhaps even just using a consolidated venv as the
default where possible.
I'm not planning on it, but I like the idea quite a bit :).
--
-- James Slagle
that, the Overcloud would basically configure itself then callback to
Heat to indicate it all worked.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
log about *not* doing what I suggested
with the local machine os-refresh-config scripts :).
So, I think it's likely that Tuskar will need to orchestrate this
setup in some fasion.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev
of
downloading an image, modifying it, and saving it.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
/pipermail/openstack-dev/2013-August/013122.html
[2] https://wiki.openstack.org/wiki/NovaImageBuilding
[3] https://wiki.openstack.org/wiki/TaskFlow
[4] https://wiki.openstack.org/wiki/Mistral
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev
.
Ryan
- Original Message -
From: James Slagle james.sla...@gmail.com
To: OpenStack Development Mailing List openstack-dev@lists.openstack.org
Sent: Thursday, January 16, 2014 10:13:58 AM
Subject: [openstack-dev] [TripleO] milestone-proposed branches
At last summit, we talked about doing
On Thu, Jan 16, 2014 at 10:32 AM, Thierry Carrez thie...@openstack.org wrote:
James Slagle wrote:
[...]
And yes, I'm volunteering to do the work to support the above, and the
release work :).
Let me know if you have any question or need help. The process and tools
used for the integrated
prebuilt vm images vs
building from scratch. Also, given the pending patches around an all
in one Overcloud, we could work the seed back into this, and still be
at just 3 vm's.
Any other feedback welcome.
On Tue, Dec 24, 2013 at 11:50 AM, James Slagle james.sla...@gmail.com wrote:
I built some vm
or not. I'll look into it.
Thanks, I appreciate the feedback.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
this warranted a broader discussion.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
to seed and then do that.
Thanks for the feedback.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
(such as the
new Image Id) in order to perform the incremental update. Could this
be made available somehow in the metadata structure?
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman
, or attempts to reconcile them. Either way,
we have to express the differences.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
straightforward
implementation that could be used on any distro. But, TripleO
shouldn't necessarily *enforce* that it's used. It doesn't have to be
an all-or-nothing type approach IMO.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev
On Wed, Jan 22, 2014 at 6:46 PM, Thierry Carrez thie...@openstack.org
wrote:
James Slagle wrote:
I read through that wiki page. I did have a couple of questions:
Who usually runs through the steps there? You? or a project member?
Me for integrated projects (and most incubated ones
On Tue, Mar 4, 2014 at 2:08 AM, Thierry Carrez thie...@openstack.org wrote:
Robert Collins wrote:
On 3 March 2014 23:12, Thierry Carrez thie...@openstack.org wrote:
James Slagle wrote:
I'd like to ask that the following repositories for TripleO be included
in next week's cutting of icehouse-3
developer
to help us out here.
Jirka
[1] https://bugs.launchpad.net/nova/+bug/917850
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
-- James Slagle
we've also achieved
another layer of On OpenStack.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-reviewers-180.txt
Thank you for your consideration!
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
with -core responsibilities.
In this months review:
- James Slagle for -core
- Arata Notsu to be removed from -core
- Devananda van der veen to be removed from -core
Existing -core members are eligible to vote - please indicate your
opinion on each of the three changes above in reply
most folks
open to grammar corrections if English is not their native language
b/c they want to learn and fix the mistakes.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
, elements) to
build images, etc.
Thoughts on this approach?
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Tue, Nov 19, 2013 at 6:57 PM, Robert Collins
robe...@robertcollins.net wrote:
On 20 November 2013 10:40, James Slagle james.sla...@gmail.com wrote:
I'd like to propose an idea around a simplified and complimentary version of
devtest that makes it easier for someone to get started and try
can try even sooner
- It may turn out we want this option in the long run ... a figure it
out all out for me
type of approach, so it wouldn't be wasted effort.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
track process to get them back on core is reasonable.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
,
...
},
dib : {
command-line : ,
version: .
}
}
Could keep adding additional things like list of elements used, build time, etc.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
On Wed, Dec 4, 2013 at 2:10 PM, Robert Collins
robe...@robertcollins.net wrote:
On 5 December 2013 06:55, James Slagle james.sla...@gmail.com wrote:
On Wed, Dec 4, 2013 at 2:12 AM, Robert Collins
Jan, Jordan, Martyn, Jiri and Jaromir are still actively contributing
to TripleO and OpenStack
on core
- the *average* of 1 review/day is a very low bar
I think it's prudent and can't really object to removing these
individuals from core, so +1 for the removal.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
be nice.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
part of the entire deployment
process, so I think having a use case for it makes sense.
Nice work on the use cases Liz, thanks for pulling them together.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
is not guaranteed, I agree with some of the
other sentiments in this thread: that we should at least try if there
are easy things we can do.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
, they're in the epel repositories.
On DEB systems, use Percona XtraDB Cluster packages.
If packages are in the distro, use distro packages. If packages are
not in the distro, use upstream packages.
If anything doesn't match those principles, it is a bug.
--
-- James Slagle
On Wed, Jul 9, 2014 at 11:52 AM, Clint Byrum cl...@fewbar.com wrote:
So, I propose that we add jonpaul-sullivan and lxsli to the TripleO core
reviewer team.
I'm +1 to adding both as core reviewers, I've found their reviews to
be well reasoned and consistent.
--
-- James Slagle
objecting to the fact that
TripleO allows people to *choose* to use LIO?
As was explained in the review[1], Tgt is the default for TripleO. If
you want to use LIO, TripleO offers that choice, just like Cinder
does.
[1] https://review.openstack.org/#/c/78463/
--
-- James Slagle
dates are. Additionally, we
haven't defined or talked about if we'd have an exception process to
the freeze if someone wanted to propose an exception.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
that
provided some override json/yaml for os-collect-config during their
image builds.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Mon, Apr 7, 2014 at 7:50 PM, Robert Collins
robe...@robertcollins.net wrote:
tl;dr: 3 more core members to propose:
bnemec
greghaynes
jdob
+1 to all. I've valued the feedback from these individuals as both
fellow reviewers and on my submitted patches.
--
-- James Slagle
up to date
and accurate as possible.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
/Summit/Juno/Etherpads
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-tripleo-and-docker
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
in our specs, and when I had one, unit tests failed. We actually do
have data model stuff in Tuskar and our json structures in tripleo.
Anyway, just my $0.02.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
that?
Or is tuskar-ui conversation already happening in #openstack-horizon?
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
programs may be
organized in the future, or what different paths that story may take.
Thanks for your consideration!
[1] http://lists.openstack.org/pipermail/openstack-dev/2014-April/031772.html
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack
projects, depending on if there's interest
from the community for that support.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
the first 2 bullet points on the etherpad are
pretty related actually (Adam's OpenStack Setup and James Polley's
Pathways into TripleO).
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
unfortunately.
James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
solution until
there's better support in WSME.
Here's the commit with all the details:
https://github.com/tuskar/tuskar/commit/16d3fec0e7d28be04252ad6b779ca6460b4918f5
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
...@hp.com
Distinguished Technologist
HP Converged Cloud
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
-- James Slagle
due to IPMI/RMCP isolation within the rack.
+ Doesn't necessarily preclude Idea 0
[1] http://fedorapeople.org/~slagle/drawing0.png
[2] http://fedorapeople.org/~slagle/drawing1.png
[3] http://fedorapeople.org/~slagle/drawing2.png
--
-- James Slagle
, thanks for sharing!
No problem, appreciate the time it took to read through it and reply :).
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
that that can be shared in a public trello for tripleo, the
better for
everyone.
--
-- James Slagle
--
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
% of the 20 cores active the last 90 days.
I believe this vote has carried. Please welcome James Polley to the
TripleO core reviewer team. :)
I'm a little late to the party, but it was a +1 from me as well. James
has been doing really valuable reviews for a while now.
--
-- James Slagle
who would choose this route.
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin
reasons. We might as well start when we intend to end up, especially
since Tuskar API is already under openstack/. If anyone ends up
surfacing any objections, that will become known on the review.
--
-- James Slagle
--
-- James Slagle
--
__
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
of characters: Keystone/Glance/Neutron/Swift.
Thanks.
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
://review.openstack.org/#/c/158410/
[2] http://lists.openstack.org/pipermail/openstack-dev/2015-February/056618.html
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack
/tripleo-specs/specs/juno/tripleo-on-openstack.html
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
On Mon, Apr 6, 2015 at 3:11 PM, James Slagle james.sla...@gmail.com wrote:
I've created an etherpad for for TripleO to track the topics we'd like
to discuss at the Liberty Summit:
https://etherpad.openstack.org/p/tripleo-liberty-proposed-sessions
It's also linked from the main Design Summit
.
this said, I prefer myself to leave some air for a (future?) non-pacemaker
scenario, but I still wanted to point out the reason why the conditionals
are there in the first place
--
-- James Slagle
--
__
OpenStack
and you'd no
longer like to serve on the core team, please let me know.
I also plan to remove Alexis Lee from core, who previously has
expressed that he'd be stepping away from TripleO for a while. Alexis,
thank you for reviews and contributions!
--
-- James Slagle
Thanks for the replies everyone. I've added Giulio and Steve to
tripleo-core, and removed Jon-Paul and Alexis.
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack
: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
-meeting-time
--
-- James Slagle
--
__
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
If you have something you'd like to propose to discuss, please add it
to the etherpad.
Thanks
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
for your consideration!
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman
want to avoid the reimplementation of that logic
(and I think we do).
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
this :).
Either way, I agree it makes sense to have the ability to give a set
of folks +2 on dib, and not all the tripleo repos in the process, so
that dib is able to grow it's team of core reviewers.
--
-- James Slagle
/mailman/listinfo/openstack-dev
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin
__
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
--
-- James Slagle
1 - 100 of 268 matches
Mail list logo
