I am concerned about some of the implications that are being discussed.
1) A WADL is part of documentation of an API. Nobody is going to object to more
documentation.
2) Being an open-source project, if somebody wants to commit to creating and
maintaining a WADL for a particular part of
On 10/27/2011 05:52 PM, Mark Nottingham wrote:
Generating WADL (or anything else) from code is fine, as long as we have the
processes / tools (e.g., CI) in place to assure that a trivial code change
doesn't make a backwards-incompatible change in what we expose to clients.
You bring up a
Frans,
the single node configuration of the Stackops Distro can work in very modest
environments. A P4 and 1.5GB should be enough if you want to deploy m1.tiny
instances with QEMU. If you want to manage the deployment in a training lab
probably you should check the tool.
Cheers
Diego
-
--
Diego
Hi everyone,
We are entering the bi-annual two-week period of meeting time disruption
! Europe ends DST on Sunday, Oct 30. The US ends DST on Sunday, Nov 6.
Other countries may vary...
The meeting times are announced in UTC time, so please doublecheck how
that translates in your timezone for the
thx for the reply..
i use this spec P4 1.5GB, Dell Optiplex i believe..
but i love if the spec that i create, confirmed good enough for student to
learn
F
2011/10/28 Diego Parrilla Santamaría diego.parrilla.santama...@gmail.com
Frans,
the single node configuration of the Stackops Distro
On 20 October 2011 08:45, Thierry Carrez thie...@openstack.org wrote:
James Bailey wrote:
On 19 October 2011 16:29, Russell Bryant rbry...@redhat.com wrote:
Hopefully it works out! I love FOSDEM.
One thing that might help the application is to note that you're willing to
increase the scope
When you look at the scalability issue solely from the perspective of the cloud
provider, requiring polling is the lazier, but not really more scalable
solution. Especially if you go nuts with caching. Then it might be even a bit
more scalable.
But when you look at the distributed systems use
Oh I can't take the credit at all, Jorge Williams created the xslts.
Turns out, David is still debugging so that examples show, but thanks for
the encouragement!
Anne
*Anne Gentle*
a...@openstack.org
my blog http://justwriteclick.com/ | my
Hi Alex,
Please use the Launchpad Answers area for asking questions like this.
http://answers.launchpad.net/nova
Thanks,
-jay
On Thu, Oct 27, 2011 at 6:07 AM, aliex_liu aliex_...@hotmail.com wrote:
I can log in the instance,and its status is running
but the rabbitmq.log always throw
Hi again, Alex,
The appropriate place to submit these things is either as a bug
report, or as a question on Launchpad Answers.
For questions like this (where you aren't sure if it is a bug or not),
use Launchpad Answers:
http://answers.launchpad.net/nova
Thanks!
-jay
On Thu, Oct 27, 2011 at
On Oct 28, 2011, at 8:11 AM, George Reese wrote:
Push notifications don't make your core system any more complex. You push the
change to a message queue and rely on another system to do the work.
The other system is scalable. It has no need to be stateless and can be run in
an on-demand
On Oct 28, 2011, at 12:39 AM, John Dickinson wrote:
The important thing is that code talks. If you want WADLs (or your flavor of
WADLs), make them! Stop trying to architect systems for architects. These
things are meant to be used. Let's focus on what is necessary for getting a
reliable
You are describing an all-purpose system, not one that supports the narrow
needs of IaaS state notifications.
There's no reason in this scenario to guarantee message delivery.
Sent from my iPhone
On Oct 28, 2011, at 10:09, Jorge Williams jorge.willi...@rackspace.com
wrote:
On Oct 28, 2011,
On Oct 28, 2011, at 10:04 AM, Ed Leafe wrote:
Swift had the advantage of starting out as a closed source project that
only had to serve a single master, and thus didn't need external
orchestration to keep it on track. Nova, OTOH, as a community development
effort, essentially had to
Jorge Williams wrote:
Push notifications don't make your core system any more complex. You push
the change to a message queue and rely on another system to do the work.
That is only true if the messaging system and the core system are largely
independent, which could have some implications
There are ways around that without guaranteed message delivery.
Sent from my iPhone
On Oct 28, 2011, at 11:41, Bryan Taylor btay...@rackspace.com wrote:
On 10/28/2011 10:33 AM, George Reese wrote:
There's no reason in this scenario to guarantee message delivery.
Usage, billing, support all
Hi Stackers,
For the Diablo release, I would like to use Keystone as the auth component...
Do I still need to use lazy provisioning (nova_auth_token.py) in my pipeline to
provision Nova projects (i.e., is Nova project creating still required)? Also,
is there an example of how the novarc
On Oct 28, 2011, at 10:33 AM, George Reese wrote:
You are describing an all-purpose system, not one that supports the narrow
needs of IaaS state notifications.
There's no reason in this scenario to guarantee message delivery.
Like I said, there are a lot of factors to consider. And
Huh? I didn't write that. George did.
On Oct 28, 2011, at 11:35 AM, Caitlin Bestler wrote:
Jorge Williams wrote:
Push notifications don't make your core system any more complex. You push
the change to a message queue and rely on another system to do the work.
That is only true if the
Hi guys,
Anyone got the link to download the patched euca tools that work with
keystone auth tokens to query the nova api ?
Regards
Lean
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe :
Thanks, pvo. This looks like good. We'd like to follow what other projects do.
Has there been any feedback on this BP? Will this be the way to handle things
in OpenStack?
The easiest way for us to handle this now for schema migrations to Keystone is
to follow Jesse's suggestion and use SQL
On Fri, Oct 28, 2011 at 1:39 AM, John Dickinson m...@not.mn wrote:
I am concerned about some of the implications that are being discussed.
1) A WADL is part of documentation of an API. Nobody is going to object to
more documentation.
2) Being an open-source project, if somebody wants to
Hey,
I never found out, in fact I only recall some mails exchange on a mailing list,
basically, there are two lines to change into :
/usr/local/lib/python2.6/dist-packages/keystone-1.0-py2.6.egg/keystone/middleware/ec2_token.py
# o = urlparse(FLAGS.keystone_ec1_url)
FWIW, my test machine at home is from System76. It's got 24G RAM and
an i7 12-core processor and runs OpenStack via devstack.sh pretty well
:) All for around $2400USD. You can get a 4-core, 16G system for aroun
$700USD a box.
http://system76.com
I've had laptops and desktops from them and I
The problem looks like that only users with role ['projectmanager',
'sysadmin'] can run instances. The demo user created by devstack only
has Member role. Not sure how it's mapped to the roles described in
http://docs.openstack.org/diablo/openstack-compute/admin/content/users-and-projects.html
Hello all,
We have officially completed the Gerrit/Github transition for Horizon. This is
the last time we'll have to move things for a while. I promise. :)
The official Horizon repo is now at:
https://github.com/openstack/horizon
Gerrit workflow instructions are here:
Couldn't agree more with this
On a side-note, I'm now going to sign all emails as
Weird,
-Matt
On 10/28/11 12:54 PM, Jay Pipes jaypi...@gmail.com wrote:
On Fri, Oct 28, 2011 at 1:39 AM, John Dickinson m...@not.mn wrote:
I am concerned about some of the implications that are being discussed.
2011/10/28 Frans Thamura fr...@meruvian.org:
2011/10/29 Jay Pipes jaypi...@gmail.com:
FWIW, my test machine at home is from System76. It's got 24G RAM and
an i7 12-core processor and runs OpenStack via devstack.sh pretty well
:) All for around $2400USD. You can get a 4-core, 16G system for
2011/10/29 Jay Pipes jaypi...@gmail.com:
FWIW, my test machine at home is from System76. It's got 24G RAM and
an i7 12-core processor and runs OpenStack via devstack.sh pretty well
:) All for around $2400USD. You can get a 4-core, 16G system for aroun
$700USD a box.
hi jay,
r u sure
Well said John.
-joe
On Oct 28, 2011, at 8:26 AM, John Dickinson wrote:
On Oct 28, 2011, at 10:04 AM, Ed Leafe wrote:
Swift had the advantage of starting out as a closed source project that
only had to serve a single master, and thus didn't need external
orchestration to keep it on
Liem,
There's some newer documentation that we just created at keystone.openstack.org
related to setting up and configuring Keystone. Look into the page at
http://keystone.openstack.org/configuring.html, which also has detail on how to
configure Nova to work with Keystone.
-joe
On Oct 28,
Hi Devin,
Should we expect a diablo/stable branch? I'm only asking because the old
branches are now gone.
Thanks,
Kiall
On Oct 28, 2011 9:48 p.m., Devin Carlen devin.car...@gmail.com wrote:
Hello all,
We have officially completed the Gerrit/Github transition for Horizon.
This is the last
Thanks, Heck... So, to use Nova with keystone, it appears that I do not need
to create Nova projects anymore. So, is there any other configuration I should
do to use the euc* tools with Keystone?
Liem
From: Joseph Heck [mailto:he...@me.com]
Sent: Friday, October 28, 2011 1:18 PM
To: Nguyen,
This is correct Unfortunately, you won't be able to use euca-upload-bundle
properly. I am trying to figure out a way to allow euca-upload-bundle to work,
but for now it will only work with deprecated auth.
Devstack shows how you can create users, tenants, roles and credentials in
keystone
This will be fixed shortly. Until then we do have tags:
https://github.com/openstack/horizon/tags
Thanks,
Devin
On Oct 28, 2011, at 1:53 PM, Kiall Mac Innes wrote:
Hi Devin,
Should we expect a diablo/stable branch? I'm only asking because the old
branches are now gone.
Thanks,
I'm working on that with the transition right now - we hope to get it back in
place shortly, and are working through some of the issues of getting this
backed with Gerrit now.
-joe
On Oct 28, 2011, at 1:53 PM, Kiall Mac Innes wrote:
Hi Devin,
Should we expect a diablo/stable branch? I'm
For the record, I'm currently running XenServer 6 inside of a VMWare
Fusion install on my Mac, with 2GB of RAM dedicated to the entire VM. I
created a new instance_type that creates 64MB instances. Works great so
far!
On 10/28/11 3:31 PM, Jay Pipes jaypi...@gmail.com wrote:
2011/10/28 Frans
Just add the ec2 credentials to keystone, apply the keystone patch mentioned
earlier if your using Diablo branches, and you're good to go.
Check out how devstack does it, While it's not a production platform, it's a
great reference.
Kiall
On Oct 28, 2011 10:42 p.m., Nguyen, Liem Manh
On Oct 27, 2011, at 10:20 PM, Bryan Taylor wrote:
Just to be clear we are talking about APIs fit for customer consumption here,
not internal integrations where both ends are under our control.
On 10/27/2011 11:38 AM, George Reese wrote:
I disagree. The web was designed specifically to
On Fri, Oct 28, 2011 at 7:18 PM, Stefano Maffulli stef...@openstack.org wrote:
On Fri, 2011-10-28 at 13:17 -0700, Joseph Heck wrote:
There's some newer documentation that we just created at
keystone.openstack.org related to setting up and configuring Keystone.
Look into the page at
On Fri, 2011-10-28 at 13:17 -0700, Joseph Heck wrote:
There's some newer documentation that we just created at
keystone.openstack.org related to setting up and configuring Keystone.
Look into the page at http://keystone.openstack.org/configuring.html,
which also has detail on how to configure
I like the idea - but I don't know what it would take to create it. I don't
think openstack.org or docs.openstack.org content sites are managed in a repo.
I believe I heard that Todd Morey was managing those sites, but I might be
wrong.
-joe
On Oct 28, 2011, at 4:38 PM, Stefano Maffulli
On Fri, 2011-10-28 at 19:26 -0400, Jay Pipes wrote:
All the core projects have developer-specific docs at
http://$PROJECT.openstack.org.
got it. I still wonder whether we should find a better home for these
docs and include them in a more visible path.
For example, if it was under
Stef -
As Jay mentioned, I was following the pattern that the core projects already
had in place.
The documentation embedded in the project (which is specifically aimed at
contributors) is in this setup. I haven't yet updated the docbook pieces (which
become docs.openstack.org HTML PDF)
Stef and others - the audience determines which website serves them best. Sites
with projectname.openstack.org are specifically for Python devs who need to get
a dev environment going.
The site segmentation is described on wiki.openstack.org/Documentation/HowTo.
Anne Gentle
Content Stacker
Hi Vish,
I just uploaded s3_token patches for swift and keystone to:
http://www.debian.or.jp/~yosshy/openstack-diablo
We have nova/glance/swift/keystone cluster with s3_token and patched
ec2_token for keystone.
We can upload image files, register them and run instances on them with
Euca2ools as
46 matches
Mail list logo
