Re: [Openstack] OpenStack Compute API for Cactus (critical!)

2011-02-28 Thread Vishvananda Ishaya
We definitely wil need to be able to create volumes at the very least without using ec2. Justinsb has some prototype code available for this. Vish On Feb 28, 2011, at 2:53 PM, John Purrier wrote: Hi Erik, today we have compute, block/volume, and network all encompassed in nova. Along with

[Openstack] test dir in trunk

2011-02-25 Thread Vishvananda Ishaya
Looks like anne's doc branch added a dir called test to trunk with a whole bunch of stuff in it. Was this added on purpose? Vish ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe :

Re: [Openstack] Proposal to be a member of Nova Core ...

2011-02-24 Thread Vishvananda Ishaya
+1 (since it looks like i missed the list last time) On Feb 17, 2011, at 8:25 AM, Sandy Walsh wrote: I'd like to help out on the review process as per http://wiki.openstack.org/Governance/Approved/CoreDevProcess I like quiet walks in the park and black and white movies. -Sandy

Re: [Openstack] Should the OpenStack API re-use the EC2 credentials?

2011-02-23 Thread Vishvananda Ishaya
Hey Justin, Does it make any difference that the way the auth is (theoretically) supposed to work with the os api is that the user gets an auth token from an external auth server and then uses username / authtoken to actually contact the api? I think it is just faked out right now to use the

[Openstack] Build Failures on hudson

2011-02-13 Thread Vishvananda Ishaya
The intermittent failure on hudson may actually be due to a corrupted database from a previous test run. I have noticed it happen on my build server and removing nova.sqlite before running seems to fix it. Is it possible that hudson is sometimes not removing the nova.sqlite file between

Re: [Openstack] Network Service for L2/L3 Network Infrastructure blueprint

2011-01-31 Thread Vishvananda Ishaya
+1 On Jan 31, 2011, at 10:40 AM, John Purrier wrote: In order to bring this discussion to a close and get everyone on the same page for Cactus development, here is where we have landed: 1. We will *not* be separating the network and volume controllers and API servers from the Nova

Re: [Openstack] Network Service for L2/L3 Network Infrastructure blueprint

2011-01-28 Thread Vishvananda Ishaya
I agree. I think splitting glance into a separate project has actually slowed it down. We should keep network service in trunk for the moment. Also, there were a couple of networking blueprints that were combined at the last design summit into one presentation. The presentation was given by

Re: [Openstack] Network Service for L2/L3 Network Infrastructure blueprint

2011-01-28 Thread Vishvananda Ishaya
together as long as possible. Vish On Jan 28, 2011, at 9:45 AM, Jay Pipes wrote: On Fri, Jan 28, 2011 at 11:37 AM, Vishvananda Ishaya vishvana...@gmail.com wrote: I agree. I think splitting glance into a separate project has actually slowed it down. Massively disagree here. The only

Re: [Openstack] Nova session question

2010-12-06 Thread Vishvananda Ishaya
I suspect you are not loading the flags that are actually in use by the program. If you are running nova using sqllite, it is possible that your program is accessing a different sqlite database. you can do the following to use the same process for loading flags that nova does: import sys

Re: [Openstack] [Nova] smaller image available for testing

2010-12-02 Thread Vishvananda Ishaya
Finally got around to testing this. It is super useful. This should replace my silly ami-tiny for sure. Scripts in instance data is extremely useful. What do you think it would take to get one of these with a working version of openvpn (with openssl support)? Vish On Nov 10, 2010, at 9:56

<    2   3   4   5   6   7