Another thought, as we envision moving OpenStack forward we will likely be
including code and projects that are not written in Python. Being forward
looking should we structure openstack-common to segment along language lines?
John
-Original Message-
From:
Some clarification and a suggestion regarding Nova and the two new proposed
services (Network/Volume).
To be clear, Nova today contains both volume and network services. We can
specify, attach, and manage block devices and also specify network related
items, such as IP assignment and VLAN
=openstack@lists.launchpad.net] On Behalf
Of Thierry Carrez
Sent: Friday, January 28, 2011 1:52 PM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] Network Service for L2/L3 Network Infrastructure
blueprint
John Purrier wrote:
Here is the suggestion. It is clear from the response on the list
code for this
milestone.
John
From: Andy Smith [mailto:andys...@gmail.com]
Sent: Friday, January 28, 2011 12:45 PM
To: John Purrier
Cc: Rick Clark; Jay Pipes; Ewan Mellor; Søren Hansen;
openstack@lists.launchpad.net
Subject: Re: [Openstack] Network Service for L2/L3 Network Infrastructure
.
We will target the Diablo design summit to discuss and review the progress made
on these services and determine if the best approach to the project has been
made.
Thoughts?
John
From: Andy Smith [mailto:andys...@gmail.com]
Sent: Friday, January 28, 2011 4:06 PM
To: John Purrier
Cc
I would suggest that the theme(s) for the Cactus release be:
a. Deployability. This includes consistent packaging and deployment tools
support; but also includes good consistent documentation, approachability to
the project (how quickly can a novice get a running system going for proof
of
I think Glen is on the right track here. Having the account_ID be a string
with no connotation for Nova allows two benefits: 1) deployments can create
the arbitrary organizational models that fit their particular DC, physical,
and logical structures, and 2) the Nova code is simpler as the
Bumping this to the top of the list. One of the key deliverables for Cactus
is a complete and usable OpenStack Compute API. This means that using only
the API and tools that interact with the OpenStack Compute API Nova can be
installed and configured; once running all of the Nova features and
I agree, this is exactly where we want to take the network services for
OpenStack. The goal should be to decouple Compute from Network, with an eye
toward a project separation post-Cactus (this should have a lot of
discussion at the next design summit). For Cactus we have explicitly kept
the
And we are back to the discussion about orchestration... Given the
flexibility of the OpenStack system and the goals of independently
horizontally scaling services I think we will need to address this head on.
#3 is the most difficult, but is also the right answer for the project as we
look
@lists.launchpad.net
[mailto:openstack-bounces+john=openstack@lists.launchpad.net] On Behalf
Of Jay Pipes
Sent: Thursday, February 24, 2011 12:20 PM
To: Eric Day
Cc: Josh Kearney; so...@openstack.org; Andy Smith;
openstack@lists.launchpad.net; John Purrier; Rick Clark
Subject: Re: [Openstack
-bounces+john=openstack@lists.launchpad.net
[mailto:openstack-bounces+john=openstack@lists.launchpad.net] On Behalf
Of Devin Carlen
Sent: Thursday, February 24, 2011 4:34 PM
To: Jay Pipes
Cc: Josh Kearney; so...@openstack.org; Andy Smith;
openstack@lists.launchpad.net; John Purrier; Rick Clark
Good work folks!
Do we understand what the dependencies/deltas are to support RHEL5 series
releases? Has anybody done this?
John
-Original Message-
From: openstack-bounces+john=openstack@lists.launchpad.net
[mailto:openstack-bounces+john=openstack@lists.launchpad.net] On Behalf
for these services. We may also need to up-version these service
API's between Cactus and Diablo as they are currently under heavy discussion
and design.
John
From: Erik Carlin [mailto:erik.car...@rackspace.com]
Sent: Monday, February 28, 2011 3:16 PM
To: John Purrier; openstack@lists.launchpad.net
I know that creiht is looking at this for Rackspace. Chuck, anything to add
to this discussion?
John
-Original Message-
From: openstack-bounces+john=openstack@lists.launchpad.net
[mailto:openstack-bounces+john=openstack@lists.launchpad.net] On Behalf
Of Adam Johnson
Sent: Monday,
Agree that this is a tricky technical issue, and I agree that the issue of
management of Authn and Authz should be external to Nova and all other
OpenStack components.
I believe there are two fundamental problems to be solved and that we will
confuse ourselves if we try to mix them together:
Hi Thierry, in addition to the technical sessions for Nova, Swift, and
Glance at the design summit, I have asked Stephen to add Project and
Release management. You will own the time slots, once the PTL's are on
board we will discuss how best to schedule the sessions.
Thanks,
John
-Original
The problem we've been having revolves around the fact that we have
dozens of developers working on Nova, with no real guidance as to the
long-term direction of the project, and teams just doing whatever the
heck they want to, without ML discussion and blueprints, and then
expecting people to
Well deserved, Justin. You have been a great contributor to the project!
John
-Original Message-
From: openstack-bounces+john=openstack@lists.launchpad.net
[mailto:openstack-bounces+john=openstack@lists.launchpad.net] On Behalf
Of Justin Santa Barbara
Sent: Friday, April 15, 2011
Rick, we have set up a top level LP project futurestack and moved all of
the associated but not official projects to be children of this. Feel free
to link the new network projects here if you want, it allows us to have a
single LP spot to go to in order to see the activity on these projects.
should probably wait
to comment on that part until I get back in the office next week. Are things
moving to github? If so, what all is staying on launchpad? Didn't John
Purrier form a new integration team with Monty and others to maintain
packaging
Vish, this is good stuff. We should pick this up in glance and swift, either
sharing a common effort with nova or specifying for each project the same
documentation that Vish is suggesting.
Heads up for other projects that are looking to be affiliated or incubated
projects, it will save time
On initial reading this is great stuff. As Josh McKenty pointed out you
should relocate the wiki page and then create a blueprint so we can track
the project.
I will have some specific responses and a couple of questions after spending
some time grokking the proposal.
John (johnpur)
Monty, this is great stuff, glad to see significant movement on the
CI/testing front.
The OpenStack PPB has claimed the hour prior to the OpenStack weekly
meeting, can you go 2 hours earlier?
Thanks,
John
-Original Message-
From: openstack-bounces+john=openstack@lists.launchpad.net
Nice work by all in hitting this milestone!
johnpur
On Jun 30, 2011, at 10:47 AM, Thierry Carrez thie...@openstack.org wrote:
Hello everyone,
Another four weeks, another milestone ! In the spirit of getting
features out to the world as soon as possible, today sees the
availability of the
)
John Dickinson (notmyname)(Rackspace))
Vish Ishaya (vishy)(Rackspace)
Josh Kearney (jk0)(Rackspace)
Joshua McKenty (jmckenty)(Piston)
Ewan Mellor (ewanmellor)(Citrix)
Jay Pipes (jaypipes)(Rackspace)
John Purrier (johnpur)(HP)
Monty Taylor (mordred)(Rackspace)
Paul Voccio (pvo)(Rackspace)
Ziad
+1.
Interesting scenarios open up if we can have the scheduler intelligently
direct workloads based on config/metadata.
johnpur
From: openstack-bounces+john=openstack@lists.launchpad.net
[mailto:openstack-bounces+john=openstack@lists.launchpad.net] On Behalf
Of Vishvananda
Congratulations to everyone in the OpenStack community for achieving this
milestone!
John
-Original Message-
From: openstack-bounces+john=openstack@lists.launchpad.net
[mailto:openstack-bounces+john=openstack@lists.launchpad.net] On Behalf
Of Thierry Carrez
Sent: Thursday, April
Hi all, recently there was a post by Zdnet about some folks that are
implementing VDI (virtual desktop) integrated with OpenStack. I would like
to get in touch with the project, if anyone knows of or are part of the
effort.
Thanks,
John
John Purrier
j...@openstack.com
(206) 930-0788
http
This is great info, John. Thanks.
John
John Purrier
j...@openstack.com
(206) 930-0788
http://www.linkedin.com/in/johnpur
On 8/10/12 9:31 AM, John Dickinson m...@not.mn wrote:
In a standard swift deployment, the proxy server is running behind a load
balancer and/or an SSL terminator
an open PaaS over your OpenStack infrastructure will significantly help your
developers and operational teams.
John
John Purrier
Chief Technology Officer appfog.com http://www.appfog.com
jpurr...@appfog.com
j...@openstack.com
About: johnpur http://www.linkedin.com/in/johnpur
From: Frans Thamura fr
I am OK with whatever the group decides.
John
-Original Message-
From: openstack-poc-bounces+john=openstack@lists.launchpad.net
[mailto:openstack-poc-bounces+john=openstack@lists.launchpad.net] On
Behalf Of Ewan Mellor
Sent: Thursday, March 24, 2011 10:01 AM
To: Jonathan Bryce;
Silly rabbit, Trix are for kids... Wait, what channel am I on?
-Original Message-
From: openstack-poc-bounces+john=openstack@lists.launchpad.net
[mailto:openstack-poc-bounces+john=openstack@lists.launchpad.net] On
Behalf Of Vishvananda Ishaya
Sent: Monday, May 09, 2011 11:21 AM
I think there is still much fuzziness in the incubation description. What
are the incubation assets? Define what some access to community
resources means. etc.
Also, and perhaps this is just a matter of timing, but how do we think of
projects like Lunr, Quantum, Melange, Burrow, etc.?
I would add this, it fleshes details on the core project definition.
John
-Original Message-
From: openstack-poc-bounces+john=openstack@lists.launchpad.net
[mailto:openstack-poc-bounces+john=openstack@lists.launchpad.net] On
Behalf Of Thierry Carrez
Sent: Thursday, May 19, 2011
Guys, I suggest we turn down the heat and rhetoric on this. We all are working
to make OpenStack great, and need to work through our internal
issues/disagreements in concise and professional manners.
Prior to anyone doing anything regarding projects moving to GitHub, let's get a
plan on the
@lists.launchpad.net] On
Behalf Of Thierry Carrez
Sent: Monday, June 13, 2011 1:48 PM
To: openstack-poc@lists.launchpad.net
Subject: Re: [Openstack-poc] Meeting tomorrow
John Purrier wrote:
Does it make sense to discuss the state/progress on the GitHub migration
project? I think someone needs to set some
an agreed to position as to what is within the OpenStack charter and what is
clearly not.
John
From: Joshua McKenty [mailto:j...@piston.cc]
Sent: Tuesday, June 14, 2011 5:08 AM
To: Jay Pipes
Cc: John Purrier; openstack-poc@lists.launchpad.net
Subject: Re: [Openstack-poc] Meeting tomorrow
I
OK.
-Original Message-
From: openstack-poc-bounces+john=openstack@lists.launchpad.net
[mailto:openstack-poc-bounces+john=openstack@lists.launchpad.net] On
Behalf Of Jonathan Bryce
Sent: Monday, October 03, 2011 1:38 PM
To: openstack-poc@lists.launchpad.net
Subject: [Openstack-poc]
39 matches
Mail list logo
