Fixed the wiki.
We need to work on a new DevCloud2 image with some new features like
s3 store backed by Riak [1] thrown in. Also built atop veewee+vagrant and
a standard basebox like Rohit did earlier. May be even deploy it on a
basebox that can be spun up on a CloudStack deployment. Would ease a
Min, Thanks.
This step needs to be updated to the devCloud wiki page. I lost tracking
of emails about this.
Kelven
On 6/26/13 2:28 PM, "Min Chen" wrote:
>Based on earlier Prasanna's email,
>
>pip install requests
>
>
>Should fix this.
>
>Thanks
>-min
>
>On 6/26/13 12:54 PM, "Kelven Yang" wrot
Based on earlier Prasanna's email,
pip install requests
Should fix this.
Thanks
-min
On 6/26/13 12:54 PM, "Kelven Yang" wrote:
>I've workaround this issue by deploying a basic zone using shared storage
>with Standard UI instead of python scripts (I added another NFS export for
>primary stora
I've workaround this issue by deploying a basic zone using shared storage
with Standard UI instead of python scripts (I added another NFS export for
primary storage in devCloud Xen VM), but would be nice to know why it
failed in python deployment phase.
Kelven
On 6/26/13 11:50 AM, "Kelven Yang"
I have another devCloud issue, after starting up the management server and
trying to deploy a basic zone configuration, I got following error. It
looks that I'm missing some step that requests python module is not
generated?
By the way, I'm in vmsync branch, but it should have been sync-ed with
ma
Just another update to say that after shutting down the system vms and
restarting the management server, the systemvms have started back up
again now so this is good progress for me and answers my original
problem that I had with devcloud setup.
Tom.
On Wed, 2013-06-26 at 13:57 +0900, Thomas O'Do
Thank you Prasanna. I've over this hurdle now. Those last fixes in
master seem to have worked the magic. I was able to start the mgmt
server and do a deploysvr... I'm now going to shut it down as per the
devcloud doc and restart and see if that works.
Tom.
On Wed, 2013-06-26 at 09:37 +0530, Prasa
Yeah a recent merge resulted in the error. The integration was
happening with the SSP Stratosphere SDN controller. That bug is now
fixed on master. You can pull down the latest.
When you see a line like "Notifying management server start in Xms"
you know the API server is ready and listening for r
Hi Prasanna,
Probably different. I've just blown away "cloudstack" and re-cloned it.
I'm on the master branch. I've done the following:
mvn -P developer,systemvm clean install
mvn -P developer -pl developer,tools/devcloud -Ddeploydb
mvn -pl :cloud-client-ui jetty:run
The last step, I en
On Tue, Jun 25, 2013 at 05:39:05PM +0900, Thomas O'Dowd wrote:
> Ah, I see the object_store branch was merged to master on the 20th so I
> guess I don't need to test that branch explicitly. However, I've now
> checked out and pulled master and am running into the problem where the
> management serv
Ah, I see the object_store branch was merged to master on the 20th so I
guess I don't need to test that branch explicitly. However, I've now
checked out and pulled master and am running into the problem where the
management server doesn't start up properly so I can't even get as far
as this any mor
11 matches
Mail list logo
