date:20121130

I think that there is a missing info in the blog entry (
http://rohityadav.in/logs/devcloud/)

This command should be executed after compilation to deploy config in the
DB of the management server :

mvn -P developer -pl tools/devcloud -Ddeploysvr

But we get this error :

Traceback (most recent call last):
File ../marvin/marvin/deployDataCenter.py, line 21, in module
import cloudstackTestClient
File
/opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackTestClient.py,
line 20, in module
import dbConnection
File
/opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/dbConnection.py,
line 18, in module
import mysql

On Thu, Nov 29, 2012 at 3:37 PM, Hieu Le hieul...@gmail.com wrote:

Great news, thank you Rohit !

I think you can tweak in devcloud project by adding more options in maven
to set up advance zone instead of basic zone in devcloud VM (devcloud.cfg
is just basic).

On Thu, Nov 29, 2012 at 8:46 PM, Rohit Yadav rohit.ya...@citrix.com
wrote:

One more thing, if you are developing inside DevCloud, you'll have to
make
sure host ip is 192.168.56.10 (or if you change the ip from
/etc/network/interfaces) and make sure you've mkisofs preinstalled. I've
fixed this issue in the image which I'll upload later sometime, but the
change is simply to compile and install mkisofs (there was no default pkg
in debian).

Regards.

From: sebgoa [run...@gmail.com]
Sent: Thursday, November 29, 2012 6:49 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: New DevCloud Appliance

On Nov 28, 2012, at 7:49 PM, Rohit Yadav wrote:

Already did that, just git pull:

https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=commitdiff;h=af12a25a608cdef45547a4da83515f57fd6129bf

Let me know if there are any other issues.

I am using it as a host and nfs server, running the mgt server on my
laptop. Everything works fine, except that the tiny linux VM never gets
available. I tried to register it, but it never gets to the ready
stage.

thoughts ?

-sebastien

Regards.

On 28-Nov-2012, at 8:28 AM, Sebastien Goasguen run...@gmail.com
wrote:

Rohit, small tweak maybe:

Since you set 192.168.56.10, the tools/devcloud/devcloud.cfg needs to
be updated (was 192.168.56.2)

-sebastien

On Nov 28, 2012, at 3:08 AM, Rohit Yadav rohit.ya...@citrix.com
wrote:

I finally got the new DevCloud appliance working and tested in
different appliances, thanks to Prasanna. The new appliance can be used
both as a all in a box solution like the original DevCloud or you can run
mgmt server and mysql on your host os and use it as a Xen server host and
NFS infrastructure. It's about 862MB, and the whole setup can run within
1G
RAM if you disable console proxy vm from global settings, also you may
run
multiple DevClouds.

It's available for download from:
http://people.apache.org/~bhaisaab/cloudstack/devcloud

More details on the blog:
http://rohityadav.in/logs/devcloud/

Please try the new appliance and report any issues.
Also help write a page on cwiki.a.o. Thanks.

Regards.

Le Quang Hieu

Specialist – Core Cloud Computing Dept

Cloud Computing Research Center

Viettel Research and Development Institute

No. 380 Lac Long Quan Str, Tay Ho Dist, Hanoi, Vietnam

Mobile: (84) 974616850

--
Charles Moulliard
Apache Committer / Sr. Enterprise Architect (RedHat)
Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com

Re: New DevCloud Appliance

Charles, looks to me like a missing dependency in Rohit's image, try:

root@devcloud:~# easy_install mysql-connector-python
Searching for mysql-connector-python
Reading http://pypi.python.org/simple/mysql-connector-python/
Reading http://dev.mysql.com/doc/connector-python/en/index.html
Reading http://dev.mysql.com/usingmysql/python/
Reading http://dev.mysql.com/downloads/connector/python/
Best match: mysql-connector-python 1.0.7
Downloading 
http://cdn.mysql.com/Downloads/Connector-Python/mysql-connector-python-1.0.7.zip
Processing mysql-connector-python-1.0.7.zip
Running mysql-connector-python-1.0.7/setup.py -q bdist_egg --dist-dir 
/tmp/easy_install-AaNj6M/mysql-connector-python-1.0.7/egg-dist-tmp-fFnbZX
zip_safe flag not set; analyzing archive contents...
Adding mysql-connector-python 1.0.7 to easy-install.pth file

Installed 
/usr/local/lib/python2.7/dist-packages/mysql_connector_python-1.0.7-py2.7.egg
Processing dependencies for mysql-connector-python
Finished processing dependencies for mysql-connector-python
root@devcloud:~# python
Python 2.7.3rc2 (default, Apr 22 2012, 22:35:38) 
[GCC 4.6.3] on linux2
Type help, copyright, credits or license for more information.
 import mysql
 



On Nov 30, 2012, at 11:45 AM, Charles Moulliard ch0...@gmail.com wrote:

 I think that there is a missing info in the blog entry (
 http://rohityadav.in/logs/devcloud/)
 
 This command should be executed after compilation to deploy config in the
 DB of the management server :
 
 mvn -P developer -pl tools/devcloud -Ddeploysvr
 
 But we get this error :
 
 Traceback (most recent call last):
  File ../marvin/marvin/deployDataCenter.py, line 21, in module
import cloudstackTestClient
  File
 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackTestClient.py,
 line 20, in module
import dbConnection
  File
 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/dbConnection.py,
 line 18, in module
import mysql
 
 
 
 On Thu, Nov 29, 2012 at 3:37 PM, Hieu Le hieul...@gmail.com wrote:
 
 Great news, thank you Rohit !
 
 I think you can tweak in devcloud project by adding more options in maven
 to set up advance zone instead of basic zone in devcloud VM (devcloud.cfg
 is just basic).
 
 On Thu, Nov 29, 2012 at 8:46 PM, Rohit Yadav rohit.ya...@citrix.com
 wrote:
 
 One more thing, if you are developing inside DevCloud, you'll have to
 make
 sure host ip is 192.168.56.10 (or if you change the ip from
 /etc/network/interfaces) and make sure you've mkisofs preinstalled. I've
 fixed this issue in the image which I'll upload later sometime, but the
 change is simply to compile and install mkisofs (there was no default pkg
 in debian).
 
 Regards.
 
 From: sebgoa [run...@gmail.com]
 Sent: Thursday, November 29, 2012 6:49 PM
 To: cloudstack-dev@incubator.apache.org
 Subject: Re: New DevCloud Appliance
 
 On Nov 28, 2012, at 7:49 PM, Rohit Yadav wrote:
 
 Already did that, just git pull:
 
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=commitdiff;h=af12a25a608cdef45547a4da83515f57fd6129bf
 
 Let me know if there are any other issues.
 
 I am using it as a host and nfs server, running the mgt server on my
 laptop. Everything works fine, except that the tiny linux VM never gets
 available. I tried to register it, but it never gets to the ready
 stage.
 
 thoughts ?
 
 -sebastien
 
 
 Regards.
 
 On 28-Nov-2012, at 8:28 AM, Sebastien Goasguen run...@gmail.com
 wrote:
 
 Rohit, small tweak maybe:
 
 Since you set 192.168.56.10, the tools/devcloud/devcloud.cfg needs to
 be updated (was 192.168.56.2)
 
 -sebastien
 
 On Nov 28, 2012, at 3:08 AM, Rohit Yadav rohit.ya...@citrix.com
 wrote:
 
 I finally got the new DevCloud appliance working and tested in
 different appliances, thanks to Prasanna. The new appliance can be used
 both as a all in a box solution like the original DevCloud or you can run
 mgmt server and mysql on your host os and use it as a Xen server host and
 NFS infrastructure. It's about 862MB, and the whole setup can run within
 1G
 RAM if you disable console proxy vm from global settings, also you may
 run
 multiple DevClouds.
 
 It's available for download from:
 http://people.apache.org/~bhaisaab/cloudstack/devcloud
 
 More details on the blog:
 http://rohityadav.in/logs/devcloud/
 
 Please try the new appliance and report any issues.
 Also help write a page on cwiki.a.o. Thanks.
 
 Regards.
 
 
 
 
 
 
 --
 
 
 
 Le Quang Hieu
 
 Specialist – Core Cloud Computing  Dept
 
 Cloud Computing Research Center
 
 Viettel Research and Development Institute
 
 No. 380 Lac Long Quan Str, Tay Ho Dist, Hanoi, Vietnam
 
 Mobile: (84) 974616850
 
 
 
 
 -- 
 Charles Moulliard
 Apache Committer / Sr. Enterprise Architect (RedHat)
 Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com

Review Request: Default admin user account will not be created in clean setup

2012-11-30 Thread Hiroaki Kawai


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/8293/
---

Review request for cloudstack.


Description
---

Current com.cloud.server.ConfigurationServerImpl#saveUser tries to insert an 
admin user entity into database, but the sql leaves password field unspecified. 
This will always fail because the database schema declares password field NOT 
NULL. This patch will fix database schema, and add missing logging when this 
sql execution failed.


Diffs
-

  server/src/com/cloud/server/ConfigurationServerImpl.java d2f0bb0 
  setup/db/create-schema.sql fff084e 

Diff: https://reviews.apache.org/r/8293/diff/


Testing
---


Thanks,

Hiroaki Kawai

Re: Review Request: Default admin user account will not be created in clean setup

2012-11-30 Thread Hiroaki Kawai


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/8293/
---

(Updated Nov. 30, 2012, 11:09 a.m.)


Review request for cloudstack.


Description (updated)
---

Current com.cloud.server.ConfigurationServerImpl#saveUser tries to insert an 
admin user entity into database, but the sql leaves password field unspecified. 
This will always fail because the database schema declares password field NOT 
NULL. This patch will fix database schema, and add missing logging when this 
sql execution failed.

This happens only on current master:HEAD.


Diffs
-

  server/src/com/cloud/server/ConfigurationServerImpl.java d2f0bb0 
  setup/db/create-schema.sql fff084e 

Diff: https://reviews.apache.org/r/8293/diff/


Testing
---


Thanks,

Hiroaki Kawai

Re: New DevCloud Appliance

Have installed the missing mysql python package but there is a mysql error
now :

mvn -P developer -pl tools/devcloud -Ddeploysvr
[INFO] Scanning for projects...
[INFO]

[INFO]

[INFO] Building Apache CloudStack Developer Tools 4.1.0-SNAPSHOT
[INFO]

[INFO]
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @
cloud-devcloud ---
[INFO]
[INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @
cloud-devcloud ---
[INFO]
[INFO] --- exec-maven-plugin:1.2.1:exec (default) @ cloud-devcloud ---
Traceback (most recent call last):
  File ../marvin/marvin/deployDataCenter.py, line 435, in module
deploy.deploy()
  File ../marvin/marvin/deployDataCenter.py, line 418, in deploy
self.loadCfg()
  File ../marvin/marvin/deployDataCenter.py, line 394, in loadCfg
apiKey, securityKey = self.registerApiKey()
  File ../marvin/marvin/deployDataCenter.py, line 334, in registerApiKey
listuserRes = self.testClient.getApiClient().listUsers(listuser)
  File
/opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackAPI/cloudstackAPIClient.py,
line 358, in listUsers
response = self.connection.make_request(command, response)
  File
/opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py,
line 177, in make_request
result = self.make_request_without_auth(commandName, requests)
  File
/opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py,
line 108, in make_request_without_auth
self.connection = urllib2.urlopen(%s://%s:%d%s?%s%(self.protocol,
self.mgtSvr, self.port, self.path, requestUrl))
  File /usr/lib/python2.7/urllib2.py, line 126, in urlopen
return _opener.open(url, data, timeout)
  File /usr/lib/python2.7/urllib2.py, line 400, in open
response = self._open(req, data)
  File /usr/lib/python2.7/urllib2.py, line 418, in _open
'_open', req)
  File /usr/lib/python2.7/urllib2.py, line 378, in _call_chain
result = func(*args)
  File /usr/lib/python2.7/urllib2.py, line 1207, in http_open
return self.do_open(httplib.HTTPConnection, req)
  File /usr/lib/python2.7/urllib2.py, line 1177, in do_open
raise URLError(err)
urllib2.URLError: urlopen error [Errno 111] Connection refused



On Fri, Nov 30, 2012 at 11:55 AM, Sebastien Goasguen run...@gmail.comwrote:

 Charles, looks to me like a missing dependency in Rohit's image, try:

 root@devcloud:~# easy_install mysql-connector-python
 Searching for mysql-connector-python
 Reading http://pypi.python.org/simple/mysql-connector-python/
 Reading http://dev.mysql.com/doc/connector-python/en/index.html
 Reading http://dev.mysql.com/usingmysql/python/
 Reading http://dev.mysql.com/downloads/connector/python/
 Best match: mysql-connector-python 1.0.7
 Downloading
 http://cdn.mysql.com/Downloads/Connector-Python/mysql-connector-python-1.0.7.zip
 Processing mysql-connector-python-1.0.7.zip
 Running mysql-connector-python-1.0.7/setup.py -q bdist_egg --dist-dir
 /tmp/easy_install-AaNj6M/mysql-connector-python-1.0.7/egg-dist-tmp-fFnbZX
 zip_safe flag not set; analyzing archive contents...
 Adding mysql-connector-python 1.0.7 to easy-install.pth file

 Installed
 /usr/local/lib/python2.7/dist-packages/mysql_connector_python-1.0.7-py2.7.egg
 Processing dependencies for mysql-connector-python
 Finished processing dependencies for mysql-connector-python
 root@devcloud:~# python
 Python 2.7.3rc2 (default, Apr 22 2012, 22:35:38)
 [GCC 4.6.3] on linux2
 Type help, copyright, credits or license for more information.
  import mysql
 



 On Nov 30, 2012, at 11:45 AM, Charles Moulliard ch0...@gmail.com wrote:

  I think that there is a missing info in the blog entry (
  http://rohityadav.in/logs/devcloud/)
 
  This command should be executed after compilation to deploy config in the
  DB of the management server :
 
  mvn -P developer -pl tools/devcloud -Ddeploysvr
 
  But we get this error :
 
  Traceback (most recent call last):
   File ../marvin/marvin/deployDataCenter.py, line 21, in module
 import cloudstackTestClient
   File
 
 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackTestClient.py,
  line 20, in module
 import dbConnection
   File
 
 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/dbConnection.py,
  line 18, in module
 import mysql
 
 
 
  On Thu, Nov 29, 2012 at 3:37 PM, Hieu Le hieul...@gmail.com wrote:
 
  Great news, thank you Rohit !
 
  I think you can tweak in devcloud project by adding more options in
 maven
  to set up advance zone instead of basic zone in devcloud VM
 (devcloud.cfg
  is just basic).
 
  On Thu, Nov 29, 2012 at 8:46 PM, Rohit Yadav rohit.ya...@citrix.com
  wrote:
 
  One more thing, if you are developing inside DevCloud, you'll have to
  make
  sure host ip is 192.168.56.10 (or if you change the ip from
  /etc/network/interfaces) and make sure you've mkisofs

Review Request: Store NetworkServiceProvider connectivity service configuration in database.

2012-11-30 Thread Hiroaki Kawai


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/8294/
---

Review request for cloudstack.


Description
---

There are 13 services defined in com.cloud.network.Network.Service , but db 
schema has 12 services with connecitivity missing in 
`cloud`.`physical_network_service_providers` . This patch will fix this. In the 
cloudstack api response, we'll see Connectivity service is enabled in NiciraNvp 
network service provider servicelist like this:

{
listnetworkserviceprovidersresponse: {
count: 1,
networkserviceprovider: [
{
physicalnetworkid: 80bf64a1-c5ca-4eb1-810e-76917a317d59,
servicelist: [
Connectivity
],
name: NiciraNvp,
destinationphysicalnetworkid: 0,
state: Disabled,
id: efb45f75-9fd7-43aa-9937-b5c871971c00
}
]
}
}


Diffs
-

  api/src/com/cloud/network/PhysicalNetworkServiceProvider.java 1b91311 
  packaging/centos63/package.sh 83c0e5e 
  server/src/com/cloud/network/dao/PhysicalNetworkServiceProviderVO.java 
12b08af 
  server/src/com/cloud/upgrade/dao/Upgrade40to41.java 5067f39 
  setup/db/create-schema.sql fff084e 
  setup/db/db/schema-40to41.sql PRE-CREATION 

Diff: https://reviews.apache.org/r/8294/diff/


Testing
---


Thanks,

Hiroaki Kawai

[ACS401] Freeze for 4.0.1 pushed to Tuesday

2012-11-30 Thread Joe Brockmeier

Hi all, 

We still have a few blocker bugs for 4.0.1 and a few more things I'd
like to merge for 4.0.1 before freeze. 

I'm going to push the freeze to Tuesday of next week (December 4), and
adjust the rest of the schedule accordingly. 

Best, 

Joe
-- 
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

Re: back in the game, deploying to devcloud

Rohit,

I've spent quite a bit of time fixing all the veewee and vagrant
configs in tools devcloud, and also re-rewirting the puppet stuff.  I
understand that you create the image yourself because it's a hassle to
do so yourself.  My work has alleviated that problem.

RIght now the fruit of my labor is a fully ready configured vm, I just
need instructions on how to deploy the build to it.  There is nothing
on http://rohityadav.in/logs/devcloud that mentnions how to do so.

- James

On Fri, Nov 30, 2012 at 2:51 AM, Rohit Yadav rohit.ya...@citrix.com wrote:
 James, I see your point, this will probably be fixed later on. We need to fix 
 the veewee and vagrant configs in tools/devcloud.
 Right now I created only the image as most people would not want to create 
 their own. If you're looking to create your own, checkout diy section of 
 http://rohityadav.in/logs/devcloud
 The problem is I've used Debian Wheezy, configuring the vagrant box was 
 tricky also some packages like mkisofs and maven3 will have to fetched as 
 they are not on distro's repos.
 Any help in fixing these scripts would be great.

 Regards.

 
 From: James Martin [jmar...@basho.com]
 Sent: Friday, November 30, 2012 1:10 PM
 To: cloudstack-dev@incubator.apache.org
 Subject: Re: back in the game, deploying to devcloud

 Just to clear things up -- I'm not using an image at all.  I'm working
 on the stuff that builds devcloud.  I'd like devcloud to be part of
 the source tree, not something external that you download.  I feel
 this makes for a cleaner development experience and forces the
 creation of the devcloud image to remain in the core codebase.

 The goal is to be able, from the cloudstack project root:

 cd tools/devcloud
 vagrant up
 vagrant ssh

 In order for this to work it requires a vagrant basebox, and a vagrant
 xenbox.  Currently in my fork these are built cleanly with veewee,
 vagrant, and puppet via a shell script by simply:

 cd tools/devcloud/deps
 ./boxer.sh -b all

 And you end up with:

 vagrant box list
 devcloudbase (virtualbox)
 devcloudbase-xen (virtualbox)

 Once those vagrant boxes are completed you'd run,

 cd ../
 vagrant up
 vagrant ssh

 vagrant ssh
 Welcome to Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-29-generic-pae i686)

  * Documentation:  https://help.ubuntu.com/
 Last login: Fri Nov 30 05:29:32 2012 from 10.0.2.2
 devcloud@devcloud:~$ ls /opt/cloudstack/
 apache-tomcat-6.0.32  apache-tomcat-6.0.32.zip  incubator-cloudstack
 startdevcloud.sh

 and now you have an clean devcloud vagrant install.  If you ever screw
 up the system,
 you simply:
 vagrant destroy
 vagrant up

 to start fresh

 I have all of that completed.  I just want to be able to install a
 build to this blank vm.  It seems like I should follow these steps:

 https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+devcloud+environment+setup

 but I receive an error here:

 mvn -P developer -pl developer,tools/devcloud -Ddeploydb
 [INFO] Scanning for projects...
 [INFO] 
 
 [INFO] Reactor Build Order:
 [INFO]
 [INFO] Apache CloudStack Developer Tools
 [INFO] Apache CloudStack Developer Tools
 [INFO]
 [INFO] 
 
 [INFO] Building Apache CloudStack Developer Tools 4.1.0-SNAPSHOT
 [INFO] 
 
 [INFO]
 [INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties
 (default) @ cloud-developer ---
 [WARNING] Ignoring missing properties file:
 /Users/jmartin/work/code/basho-cloudstack/utils/conf/db.properties.override
 [INFO]
 [INFO] --- maven-remote-resources-plugin:1.3:process (default) @
 cloud-developer ---
 [INFO]
 [INFO] --- maven-antrun-plugin:1.7:run (default) @ cloud-developer ---
 [INFO] Executing tasks

 main:
  [copy] Copying 60 files to
 /Users/jmartin/work/code/basho-cloudstack/developer/target/db
  [copy] Copying 9 files to
 /Users/jmartin/work/code/basho-cloudstack/developer/target/db
 [INFO] Executed tasks
 [INFO]
 [INFO] --- sql-maven-plugin:1.5:execute (drop-database) @ cloud-developer ---
 [INFO] 
 
 [INFO] Reactor Summary:
 [INFO]
 [INFO] Apache CloudStack Developer Tools . FAILURE [2.025s]
 [INFO] Apache CloudStack Developer Tools . SKIPPED
 [INFO] 
 
 [INFO] BUILD FAILURE
 [INFO] 
 
 [INFO] Total time: 2.947s
 [INFO] Finished at: Fri Nov 30 02:15:39 EST 2012
 [INFO] Final Memory: 12M/81M
 [INFO] 
 
 [ERROR] Failed to execute goal
 org.codehaus.mojo:sql-maven-plugin:1.5:execute (drop-database) on
 project cloud-developer: Communications link

Re: back in the game, deploying to devcloud

There is a wiki page here :
https://cwiki.apache.org/CLOUDSTACK/building-devcloud.html


On Fri, Nov 30, 2012 at 3:16 PM, James Martin jmar...@basho.com wrote:

 Rohit,

 I've spent quite a bit of time fixing all the veewee and vagrant
 configs in tools devcloud, and also re-rewirting the puppet stuff.  I
 understand that you create the image yourself because it's a hassle to
 do so yourself.  My work has alleviated that problem.

 RIght now the fruit of my labor is a fully ready configured vm, I just
 need instructions on how to deploy the build to it.  There is nothing
 on http://rohityadav.in/logs/devcloud that mentnions how to do so.

 - James

 On Fri, Nov 30, 2012 at 2:51 AM, Rohit Yadav rohit.ya...@citrix.com
 wrote:
  James, I see your point, this will probably be fixed later on. We need
 to fix the veewee and vagrant configs in tools/devcloud.
  Right now I created only the image as most people would not want to
 create their own. If you're looking to create your own, checkout diy
 section of http://rohityadav.in/logs/devcloud
  The problem is I've used Debian Wheezy, configuring the vagrant box was
 tricky also some packages like mkisofs and maven3 will have to fetched as
 they are not on distro's repos.
  Any help in fixing these scripts would be great.
 
  Regards.
 
  
  From: James Martin [jmar...@basho.com]
  Sent: Friday, November 30, 2012 1:10 PM
  To: cloudstack-dev@incubator.apache.org
  Subject: Re: back in the game, deploying to devcloud
 
  Just to clear things up -- I'm not using an image at all.  I'm working
  on the stuff that builds devcloud.  I'd like devcloud to be part of
  the source tree, not something external that you download.  I feel
  this makes for a cleaner development experience and forces the
  creation of the devcloud image to remain in the core codebase.
 
  The goal is to be able, from the cloudstack project root:
 
  cd tools/devcloud
  vagrant up
  vagrant ssh
 
  In order for this to work it requires a vagrant basebox, and a vagrant
  xenbox.  Currently in my fork these are built cleanly with veewee,
  vagrant, and puppet via a shell script by simply:
 
  cd tools/devcloud/deps
  ./boxer.sh -b all
 
  And you end up with:
 
  vagrant box list
  devcloudbase (virtualbox)
  devcloudbase-xen (virtualbox)
 
  Once those vagrant boxes are completed you'd run,
 
  cd ../
  vagrant up
  vagrant ssh
 
  vagrant ssh
  Welcome to Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-29-generic-pae i686)
 
   * Documentation:  https://help.ubuntu.com/
  Last login: Fri Nov 30 05:29:32 2012 from 10.0.2.2
  devcloud@devcloud:~$ ls /opt/cloudstack/
  apache-tomcat-6.0.32  apache-tomcat-6.0.32.zip  incubator-cloudstack
  startdevcloud.sh
 
  and now you have an clean devcloud vagrant install.  If you ever screw
  up the system,
  you simply:
  vagrant destroy
  vagrant up
 
  to start fresh
 
  I have all of that completed.  I just want to be able to install a
  build to this blank vm.  It seems like I should follow these steps:
 
 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+devcloud+environment+setup
 
  but I receive an error here:
 
  mvn -P developer -pl developer,tools/devcloud -Ddeploydb
  [INFO] Scanning for projects...
  [INFO]
 
  [INFO] Reactor Build Order:
  [INFO]
  [INFO] Apache CloudStack Developer Tools
  [INFO] Apache CloudStack Developer Tools
  [INFO]
  [INFO]
 
  [INFO] Building Apache CloudStack Developer Tools 4.1.0-SNAPSHOT
  [INFO]
 
  [INFO]
  [INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties
  (default) @ cloud-developer ---
  [WARNING] Ignoring missing properties file:
 
 /Users/jmartin/work/code/basho-cloudstack/utils/conf/db.properties.override
  [INFO]
  [INFO] --- maven-remote-resources-plugin:1.3:process (default) @
  cloud-developer ---
  [INFO]
  [INFO] --- maven-antrun-plugin:1.7:run (default) @ cloud-developer ---
  [INFO] Executing tasks
 
  main:
   [copy] Copying 60 files to
  /Users/jmartin/work/code/basho-cloudstack/developer/target/db
   [copy] Copying 9 files to
  /Users/jmartin/work/code/basho-cloudstack/developer/target/db
  [INFO] Executed tasks
  [INFO]
  [INFO] --- sql-maven-plugin:1.5:execute (drop-database) @
 cloud-developer ---
  [INFO]
 
  [INFO] Reactor Summary:
  [INFO]
  [INFO] Apache CloudStack Developer Tools . FAILURE
 [2.025s]
  [INFO] Apache CloudStack Developer Tools . SKIPPED
  [INFO]
 
  [INFO] BUILD FAILURE
  [INFO]
 
  [INFO] Total time: 2.947s
  [INFO] Finished at: Fri Nov 30

Re: back in the game, deploying to devcloud

Charles,

I checked out the link, it doesn't make a mention of how to get the
build to the vm.

- James

On Fri, Nov 30, 2012 at 9:31 AM, Charles Moulliard ch0...@gmail.com wrote:
 There is a wiki page here :
 https://cwiki.apache.org/CLOUDSTACK/building-devcloud.html


 On Fri, Nov 30, 2012 at 3:16 PM, James Martin jmar...@basho.com wrote:

 Rohit,

 I've spent quite a bit of time fixing all the veewee and vagrant
 configs in tools devcloud, and also re-rewirting the puppet stuff.  I
 understand that you create the image yourself because it's a hassle to
 do so yourself.  My work has alleviated that problem.

 RIght now the fruit of my labor is a fully ready configured vm, I just
 need instructions on how to deploy the build to it.  There is nothing
 on http://rohityadav.in/logs/devcloud that mentnions how to do so.

 - James

 On Fri, Nov 30, 2012 at 2:51 AM, Rohit Yadav rohit.ya...@citrix.com
 wrote:
  James, I see your point, this will probably be fixed later on. We need
 to fix the veewee and vagrant configs in tools/devcloud.
  Right now I created only the image as most people would not want to
 create their own. If you're looking to create your own, checkout diy
 section of http://rohityadav.in/logs/devcloud
  The problem is I've used Debian Wheezy, configuring the vagrant box was
 tricky also some packages like mkisofs and maven3 will have to fetched as
 they are not on distro's repos.
  Any help in fixing these scripts would be great.
 
  Regards.
 
  
  From: James Martin [jmar...@basho.com]
  Sent: Friday, November 30, 2012 1:10 PM
  To: cloudstack-dev@incubator.apache.org
  Subject: Re: back in the game, deploying to devcloud
 
  Just to clear things up -- I'm not using an image at all.  I'm working
  on the stuff that builds devcloud.  I'd like devcloud to be part of
  the source tree, not something external that you download.  I feel
  this makes for a cleaner development experience and forces the
  creation of the devcloud image to remain in the core codebase.
 
  The goal is to be able, from the cloudstack project root:
 
  cd tools/devcloud
  vagrant up
  vagrant ssh
 
  In order for this to work it requires a vagrant basebox, and a vagrant
  xenbox.  Currently in my fork these are built cleanly with veewee,
  vagrant, and puppet via a shell script by simply:
 
  cd tools/devcloud/deps
  ./boxer.sh -b all
 
  And you end up with:
 
  vagrant box list
  devcloudbase (virtualbox)
  devcloudbase-xen (virtualbox)
 
  Once those vagrant boxes are completed you'd run,
 
  cd ../
  vagrant up
  vagrant ssh
 
  vagrant ssh
  Welcome to Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-29-generic-pae i686)
 
   * Documentation:  https://help.ubuntu.com/
  Last login: Fri Nov 30 05:29:32 2012 from 10.0.2.2
  devcloud@devcloud:~$ ls /opt/cloudstack/
  apache-tomcat-6.0.32  apache-tomcat-6.0.32.zip  incubator-cloudstack
  startdevcloud.sh
 
  and now you have an clean devcloud vagrant install.  If you ever screw
  up the system,
  you simply:
  vagrant destroy
  vagrant up
 
  to start fresh
 
  I have all of that completed.  I just want to be able to install a
  build to this blank vm.  It seems like I should follow these steps:
 
 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+devcloud+environment+setup
 
  but I receive an error here:
 
  mvn -P developer -pl developer,tools/devcloud -Ddeploydb
  [INFO] Scanning for projects...
  [INFO]
 
  [INFO] Reactor Build Order:
  [INFO]
  [INFO] Apache CloudStack Developer Tools
  [INFO] Apache CloudStack Developer Tools
  [INFO]
  [INFO]
 
  [INFO] Building Apache CloudStack Developer Tools 4.1.0-SNAPSHOT
  [INFO]
 
  [INFO]
  [INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties
  (default) @ cloud-developer ---
  [WARNING] Ignoring missing properties file:
 
 /Users/jmartin/work/code/basho-cloudstack/utils/conf/db.properties.override
  [INFO]
  [INFO] --- maven-remote-resources-plugin:1.3:process (default) @
  cloud-developer ---
  [INFO]
  [INFO] --- maven-antrun-plugin:1.7:run (default) @ cloud-developer ---
  [INFO] Executing tasks
 
  main:
   [copy] Copying 60 files to
  /Users/jmartin/work/code/basho-cloudstack/developer/target/db
   [copy] Copying 9 files to
  /Users/jmartin/work/code/basho-cloudstack/developer/target/db
  [INFO] Executed tasks
  [INFO]
  [INFO] --- sql-maven-plugin:1.5:execute (drop-database) @
 cloud-developer ---
  [INFO]
 
  [INFO] Reactor Summary:
  [INFO]
  [INFO] Apache CloudStack Developer Tools . FAILURE
 [2.025s]
  [INFO] Apache CloudStack Developer Tools . SKIPPED
  [INFO]

Re: back in the game, deploying to devcloud

Maybe I can help with a bit of context here,

After Edison released the first devcloud, Chip started to automate the building
of devcloud. He contributed some early code in /tools/devcloud which used
veewee/vagrant and puppet to build the image automatically. I tested it and
created the wiki page:

https://cwiki.apache.org/CLOUDSTACK/building-devcloud.html

but this was not finished and fully tested.

Time passed...

Then James started fixing this.

Time passed…

Then Rohit just released a new devcloud which solved problems a few of us where
having, especially with the host only interface.

The automation of building devcloud is still there.

What would be nice is for James and Rohit to sync, so that what Rohit did can
be automated by the work from James with vagrant and puppet.

The current problem James is having just seems to be a building issue with
maven that Rohit could help with ? However James may have to look at using
Wheezy per Rohit's work?

Maybe an IRC discussion can help ?

Hope that helps,

-Sebastien

On Nov 30, 2012, at 3:31 PM, Charles Moulliard ch0...@gmail.com wrote:

There is a wiki page here :
https://cwiki.apache.org/CLOUDSTACK/building-devcloud.html

On Fri, Nov 30, 2012 at 3:16 PM, James Martin jmar...@basho.com wrote:

Rohit,

I've spent quite a bit of time fixing all the veewee and vagrant
configs in tools devcloud, and also re-rewirting the puppet stuff. I
understand that you create the image yourself because it's a hassle to
do so yourself. My work has alleviated that problem.

RIght now the fruit of my labor is a fully ready configured vm, I just
need instructions on how to deploy the build to it. There is nothing
on http://rohityadav.in/logs/devcloud that mentnions how to do so.

- James

On Fri, Nov 30, 2012 at 2:51 AM, Rohit Yadav rohit.ya...@citrix.com
wrote:
James, I see your point, this will probably be fixed later on. We need
to fix the veewee and vagrant configs in tools/devcloud.
Right now I created only the image as most people would not want to
create their own. If you're looking to create your own, checkout diy
section of http://rohityadav.in/logs/devcloud
The problem is I've used Debian Wheezy, configuring the vagrant box was
tricky also some packages like mkisofs and maven3 will have to fetched as
they are not on distro's repos.
Any help in fixing these scripts would be great.

Regards.

From: James Martin [jmar...@basho.com]
Sent: Friday, November 30, 2012 1:10 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: back in the game, deploying to devcloud

Just to clear things up -- I'm not using an image at all. I'm working
on the stuff that builds devcloud. I'd like devcloud to be part of
the source tree, not something external that you download. I feel
this makes for a cleaner development experience and forces the
creation of the devcloud image to remain in the core codebase.

The goal is to be able, from the cloudstack project root:

cd tools/devcloud
vagrant up
vagrant ssh

In order for this to work it requires a vagrant basebox, and a vagrant
xenbox. Currently in my fork these are built cleanly with veewee,
vagrant, and puppet via a shell script by simply:

cd tools/devcloud/deps
./boxer.sh -b all

And you end up with:

vagrant box list
devcloudbase (virtualbox)
devcloudbase-xen (virtualbox)

Once those vagrant boxes are completed you'd run,

cd ../
vagrant up
vagrant ssh

vagrant ssh
Welcome to Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-29-generic-pae i686)

* Documentation: https://help.ubuntu.com/
Last login: Fri Nov 30 05:29:32 2012 from 10.0.2.2
devcloud@devcloud:~$ ls /opt/cloudstack/
apache-tomcat-6.0.32 apache-tomcat-6.0.32.zip incubator-cloudstack
startdevcloud.sh

and now you have an clean devcloud vagrant install. If you ever screw
up the system,
you simply:
vagrant destroy
vagrant up

to start fresh

I have all of that completed. I just want to be able to install a
build to this blank vm. It seems like I should follow these steps:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+devcloud+environment+setup

but I receive an error here:

mvn -P developer -pl developer,tools/devcloud -Ddeploydb
[INFO] Scanning for projects...
[INFO]

[INFO] Reactor Build Order:
[INFO]
[INFO] Apache CloudStack Developer Tools
[INFO] Apache CloudStack Developer Tools
[INFO]
[INFO]

[INFO] Building Apache CloudStack Developer Tools 4.1.0-SNAPSHOT
[INFO]

[INFO]
[INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties
(default) @ cloud-developer ---
[WARNING] Ignoring missing properties file:

RE: New DevCloud Appliance

Charles, this simply deploys a basic zone using configuration from 
tools/devcloud/devcloud.cfg
The problem I see is that it's unable to create a connection to mgmt server. 
You can start mgmt server and manually add a basic zone.

Checklist:
- Are you running your mgmt server on host os (192.168.56.1) or on devcloud 
(192.168.56.10)
- Where are you running your mysql server (56.1 or 56.10)
- Where are you running these commands, on host os or on devcloud?
- Is MySQL and mgmt server running at that time?

Note: You are required to run mgmt server, this command simply calls a bunch of 
APIs to mgmt server's API server to deploy a basic zone. I've added a section 
about it on my blog.

In background it call's marvin. You can try this:
run mgmt server: mvn -pl jetty:run (make sure mgmt server is running)
deploy datacenter/basic zone: cd tools/devcloud; python 
../marvin/marvin/deployDataCenter.py -i devcloud.cfg (change devcloud.cfg as 
per your needs)

Will update the devcloud2.ova image later today with mysql-connector-python, 
thanks for finding the issue.

Regards.


From: Charles Moulliard [ch0...@gmail.com]
Sent: Friday, November 30, 2012 5:37 PM
To: cloudstack-dev
Subject: Re: New DevCloud Appliance

Have installed the missing mysql python package but there is a mysql error
now :

mvn -P developer -pl tools/devcloud -Ddeploysvr
[INFO] Scanning for projects...
[INFO]

[INFO]

[INFO] Building Apache CloudStack Developer Tools 4.1.0-SNAPSHOT
[INFO]

[INFO]
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @
cloud-devcloud ---
[INFO]
[INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @
cloud-devcloud ---
[INFO]
[INFO] --- exec-maven-plugin:1.2.1:exec (default) @ cloud-devcloud ---
Traceback (most recent call last):
  File ../marvin/marvin/deployDataCenter.py, line 435, in module
deploy.deploy()
  File ../marvin/marvin/deployDataCenter.py, line 418, in deploy
self.loadCfg()
  File ../marvin/marvin/deployDataCenter.py, line 394, in loadCfg
apiKey, securityKey = self.registerApiKey()
  File ../marvin/marvin/deployDataCenter.py, line 334, in registerApiKey
listuserRes = self.testClient.getApiClient().listUsers(listuser)
  File
/opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackAPI/cloudstackAPIClient.py,
line 358, in listUsers
response = self.connection.make_request(command, response)
  File
/opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py,
line 177, in make_request
result = self.make_request_without_auth(commandName, requests)
  File
/opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py,
line 108, in make_request_without_auth
self.connection = urllib2.urlopen(%s://%s:%d%s?%s%(self.protocol,
self.mgtSvr, self.port, self.path, requestUrl))
  File /usr/lib/python2.7/urllib2.py, line 126, in urlopen
return _opener.open(url, data, timeout)
  File /usr/lib/python2.7/urllib2.py, line 400, in open
response = self._open(req, data)
  File /usr/lib/python2.7/urllib2.py, line 418, in _open
'_open', req)
  File /usr/lib/python2.7/urllib2.py, line 378, in _call_chain
result = func(*args)
  File /usr/lib/python2.7/urllib2.py, line 1207, in http_open
return self.do_open(httplib.HTTPConnection, req)
  File /usr/lib/python2.7/urllib2.py, line 1177, in do_open
raise URLError(err)
urllib2.URLError: urlopen error [Errno 111] Connection refused



On Fri, Nov 30, 2012 at 11:55 AM, Sebastien Goasguen run...@gmail.comwrote:

 Charles, looks to me like a missing dependency in Rohit's image, try:

 root@devcloud:~# easy_install mysql-connector-python
 Searching for mysql-connector-python
 Reading http://pypi.python.org/simple/mysql-connector-python/
 Reading http://dev.mysql.com/doc/connector-python/en/index.html
 Reading http://dev.mysql.com/usingmysql/python/
 Reading http://dev.mysql.com/downloads/connector/python/
 Best match: mysql-connector-python 1.0.7
 Downloading
 http://cdn.mysql.com/Downloads/Connector-Python/mysql-connector-python-1.0.7.zip
 Processing mysql-connector-python-1.0.7.zip
 Running mysql-connector-python-1.0.7/setup.py -q bdist_egg --dist-dir
 /tmp/easy_install-AaNj6M/mysql-connector-python-1.0.7/egg-dist-tmp-fFnbZX
 zip_safe flag not set; analyzing archive contents...
 Adding mysql-connector-python 1.0.7 to easy-install.pth file

 Installed
 /usr/local/lib/python2.7/dist-packages/mysql_connector_python-1.0.7-py2.7.egg
 Processing dependencies for mysql-connector-python
 Finished processing dependencies for mysql-connector-python
 root@devcloud:~# python
 Python 2.7.3rc2 (default, Apr 22 2012, 22:35:38)
 [GCC 4.6.3] on linux2
 Type help, copyright, credits or license for more information.
  import mysql
 



 On Nov 30, 2012, at 11:45 AM, Charles Moulliard ch0...@gmail.com

Re: back in the game, deploying to devcloud

Sebastien,

Thanks for the context. An IRC meetup would be great.

-James

On Fri, Nov 30, 2012 at 9:58 AM, Sebastien Goasguen run...@gmail.com wrote:
Maybe I can help with a bit of context here,

After Edison released the first devcloud, Chip started to automate the
building of devcloud. He contributed some early code in /tools/devcloud which
used veewee/vagrant and puppet to build the image automatically. I tested it
and created the wiki page:

https://cwiki.apache.org/CLOUDSTACK/building-devcloud.html

but this was not finished and fully tested.

Time passed...

Then James started fixing this.

Time passed…

Then Rohit just released a new devcloud which solved problems a few of us
where having, especially with the host only interface.

The automation of building devcloud is still there.

What would be nice is for James and Rohit to sync, so that what Rohit did can
be automated by the work from James with vagrant and puppet.

The current problem James is having just seems to be a building issue with
maven that Rohit could help with ? However James may have to look at using
Wheezy per Rohit's work?

Maybe an IRC discussion can help ?

Hope that helps,

-Sebastien

On Nov 30, 2012, at 3:31 PM, Charles Moulliard ch0...@gmail.com wrote:

There is a wiki page here :
https://cwiki.apache.org/CLOUDSTACK/building-devcloud.html

On Fri, Nov 30, 2012 at 3:16 PM, James Martin jmar...@basho.com wrote:

Rohit,

- James

Regards.

From: James Martin [jmar...@basho.com]
Sent: Friday, November 30, 2012 1:10 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: back in the game, deploying to devcloud

The goal is to be able, from the cloudstack project root:

cd tools/devcloud
vagrant up
vagrant ssh

In order for this to work it requires a vagrant basebox, and a vagrant
xenbox. Currently in my fork these are built cleanly with veewee,
vagrant, and puppet via a shell script by simply:

cd tools/devcloud/deps
./boxer.sh -b all

And you end up with:

vagrant box list
devcloudbase (virtualbox)
devcloudbase-xen (virtualbox)

Once those vagrant boxes are completed you'd run,

cd ../
vagrant up
vagrant ssh

vagrant ssh
Welcome to Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-29-generic-pae i686)

and now you have an clean devcloud vagrant install. If you ever screw
up the system,
you simply:
vagrant destroy
vagrant up

to start fresh

I have all of that completed. I just want to be able to install a
build to this blank vm. It seems like I should follow these steps:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+devcloud+environment+setup

but I receive an error here:

mvn -P developer -pl developer,tools/devcloud -Ddeploydb
[INFO] Scanning for projects...
[INFO]

[INFO] Reactor Build Order:
[INFO]
[INFO] Apache CloudStack Developer Tools
[INFO] Apache CloudStack Developer Tools
[INFO]
[INFO]

[INFO] Building Apache CloudStack Developer Tools 4.1.0-SNAPSHOT
[INFO]

[INFO]
[INFO] ---

Re: New DevCloud Appliance

Hi Rohit,

This is my fault. I always forget to start first the servers (mvn -pl
:cloud-client-ui jetty:run) and after this command to deploy / configure
the cloud (mvn -P developer -pl tools/devcloud -Ddeploysvr). This is in
order and works fine on 192.168.56.190.
Nevertheless, I cannot upload an ISO (CentOS). If using the web interface I
try to add an ISO file, then the status of Ready is equal to No and I see
this message in the log :

INFO  [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:)
Console proxy v-2-VM is started
INFO  [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:)
Secondary storage vm s-1-VM is started
INFO  [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:)
Primary secondary storage is not even started, wait until next turn
WARN  [storage.download.DownloadMonitorImpl] (4525736@qtp-28288134-4:)
There is no secondary storage VM for secondary storage host
nfs://192.168.56.10:/opt/storage/secondary

Remark : wget works fine locally so there is no internet issue this time.

Regards,

Charles


On Fri, Nov 30, 2012 at 4:01 PM, Rohit Yadav rohit.ya...@citrix.com wrote:

 Charles, this simply deploys a basic zone using configuration from
 tools/devcloud/devcloud.cfg
 The problem I see is that it's unable to create a connection to mgmt
 server. You can start mgmt server and manually add a basic zone.

 Checklist:
 - Are you running your mgmt server on host os (192.168.56.1) or on
 devcloud (192.168.56.10)
 - Where are you running your mysql server (56.1 or 56.10)
 - Where are you running these commands, on host os or on devcloud?
 - Is MySQL and mgmt server running at that time?

 Note: You are required to run mgmt server, this command simply calls a
 bunch of APIs to mgmt server's API server to deploy a basic zone. I've
 added a section about it on my blog.

 In background it call's marvin. You can try this:
 run mgmt server: mvn -pl jetty:run (make sure mgmt server is running)
 deploy datacenter/basic zone: cd tools/devcloud; python
 ../marvin/marvin/deployDataCenter.py -i devcloud.cfg (change devcloud.cfg
 as per your needs)

 Will update the devcloud2.ova image later today with
 mysql-connector-python, thanks for finding the issue.

 Regards.

 
 From: Charles Moulliard [ch0...@gmail.com]
 Sent: Friday, November 30, 2012 5:37 PM
 To: cloudstack-dev
 Subject: Re: New DevCloud Appliance

 Have installed the missing mysql python package but there is a mysql error
 now :

 mvn -P developer -pl tools/devcloud -Ddeploysvr
 [INFO] Scanning for projects...
 [INFO]

 [INFO]
 
 [INFO] Building Apache CloudStack Developer Tools 4.1.0-SNAPSHOT
 [INFO]
 
 [INFO]
 [INFO] --- maven-remote-resources-plugin:1.3:process (default) @
 cloud-devcloud ---
 [INFO]
 [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @
 cloud-devcloud ---
 [INFO]
 [INFO] --- exec-maven-plugin:1.2.1:exec (default) @ cloud-devcloud ---
 Traceback (most recent call last):
   File ../marvin/marvin/deployDataCenter.py, line 435, in module
 deploy.deploy()
   File ../marvin/marvin/deployDataCenter.py, line 418, in deploy
 self.loadCfg()
   File ../marvin/marvin/deployDataCenter.py, line 394, in loadCfg
 apiKey, securityKey = self.registerApiKey()
   File ../marvin/marvin/deployDataCenter.py, line 334, in registerApiKey
 listuserRes = self.testClient.getApiClient().listUsers(listuser)
   File

 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackAPI/cloudstackAPIClient.py,
 line 358, in listUsers
 response = self.connection.make_request(command, response)
   File

 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py,
 line 177, in make_request
 result = self.make_request_without_auth(commandName, requests)
   File

 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py,
 line 108, in make_request_without_auth
 self.connection = urllib2.urlopen(%s://%s:%d%s?%s%(self.protocol,
 self.mgtSvr, self.port, self.path, requestUrl))
   File /usr/lib/python2.7/urllib2.py, line 126, in urlopen
 return _opener.open(url, data, timeout)
   File /usr/lib/python2.7/urllib2.py, line 400, in open
 response = self._open(req, data)
   File /usr/lib/python2.7/urllib2.py, line 418, in _open
 '_open', req)
   File /usr/lib/python2.7/urllib2.py, line 378, in _call_chain
 result = func(*args)
   File /usr/lib/python2.7/urllib2.py, line 1207, in http_open
 return self.do_open(httplib.HTTPConnection, req)
   File /usr/lib/python2.7/urllib2.py, line 1177, in do_open
 raise URLError(err)
 urllib2.URLError: urlopen error [Errno 111] Connection refused



 On Fri, Nov 30, 2012 at 11:55 AM, Sebastien Goasguen run...@gmail.com
 wrote:

  Charles, looks to me like a missing dependency in Rohit's image, try:

Re: New DevCloud Appliance

Here is the result of what I get after running the command ssvm-check.sh on
devcloud2 machine running in VB (192.168.56.10)

 ./ssvm-check.sh
cat: /var/cache/cloud/cmdline: No such file or directory

First DNS server is  10.0.3.3
PING 10.0.3.3 (10.0.3.3) 56(84) bytes of data.

--- 10.0.3.3 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1008ms

WARNING: cannot ping DNS server
route follows
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
0.0.0.0 10.0.3.20.0.0.0 UG0  00
xenbr1
0.0.0.0 192.168.56.10.0.0.0 UG10000
xenbr0
10.0.3.00.0.0.0 255.255.255.0   U 0  00
xenbr1
169.254.0.0 0.0.0.0 255.255.0.0 U 0  00
xapi0
192.168.56.00.0.0.0 255.255.255.0   U 0  00
xenbr0

Good: DNS resolves download.cloud.com

NFS is currently mounted
Mount point is /var/lib/nfs/rpc_pipefs
touch: cannot touch `/var/lib/nfs/rpc_pipefs/foo': Permission denied
ERROR: Cannot write to mount point
You need to export with norootsquash
Mount point is /proc/fs/nfsd
touch: cannot touch `/proc/fs/nfsd/foo': Permission denied
ERROR: Cannot write to mount point
You need to export with norootsquash

Management server is . Checking connectivity.
ERROR: Cannot connect to  port 8250
./ssvm-check.sh: line 111: socat: command not found



On Fri, Nov 30, 2012 at 4:40 PM, Charles Moulliard ch0...@gmail.com wrote:

 Hi Rohit,

 This is my fault. I always forget to start first the servers (mvn -pl
 :cloud-client-ui jetty:run) and after this command to deploy / configure
 the cloud (mvn -P developer -pl tools/devcloud -Ddeploysvr). This is in
 order and works fine on 192.168.56.190.
 Nevertheless, I cannot upload an ISO (CentOS). If using the web interface
 I try to add an ISO file, then the status of Ready is equal to No and I
 see this message in the log :

 INFO  [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:)
 Console proxy v-2-VM is started
 INFO  [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:)
 Secondary storage vm s-1-VM is started
 INFO  [cloud.secstorage.PremiumSecondaryStorageManagerImpl]
 (secstorage-1:) Primary secondary storage is not even started, wait until
 next turn
 WARN  [storage.download.DownloadMonitorImpl] (4525736@qtp-28288134-4:)
 There is no secondary storage VM for secondary storage host
 nfs://192.168.56.10:/opt/storage/secondary

 Remark : wget works fine locally so there is no internet issue this time.

 Regards,

 Charles


 On Fri, Nov 30, 2012 at 4:01 PM, Rohit Yadav rohit.ya...@citrix.comwrote:

 Charles, this simply deploys a basic zone using configuration from
 tools/devcloud/devcloud.cfg
 The problem I see is that it's unable to create a connection to mgmt
 server. You can start mgmt server and manually add a basic zone.

 Checklist:
 - Are you running your mgmt server on host os (192.168.56.1) or on
 devcloud (192.168.56.10)
 - Where are you running your mysql server (56.1 or 56.10)
 - Where are you running these commands, on host os or on devcloud?
 - Is MySQL and mgmt server running at that time?

 Note: You are required to run mgmt server, this command simply calls a
 bunch of APIs to mgmt server's API server to deploy a basic zone. I've
 added a section about it on my blog.

 In background it call's marvin. You can try this:
 run mgmt server: mvn -pl jetty:run (make sure mgmt server is running)
 deploy datacenter/basic zone: cd tools/devcloud; python
 ../marvin/marvin/deployDataCenter.py -i devcloud.cfg (change devcloud.cfg
 as per your needs)

 Will update the devcloud2.ova image later today with
 mysql-connector-python, thanks for finding the issue.

 Regards.

 
 From: Charles Moulliard [ch0...@gmail.com]
 Sent: Friday, November 30, 2012 5:37 PM
 To: cloudstack-dev
 Subject: Re: New DevCloud Appliance

 Have installed the missing mysql python package but there is a mysql error
 now :

 mvn -P developer -pl tools/devcloud -Ddeploysvr
 [INFO] Scanning for projects...
 [INFO]

 [INFO]
 
 [INFO] Building Apache CloudStack Developer Tools 4.1.0-SNAPSHOT
 [INFO]
 
 [INFO]
 [INFO] --- maven-remote-resources-plugin:1.3:process (default) @
 cloud-devcloud ---
 [INFO]
 [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @
 cloud-devcloud ---
 [INFO]
 [INFO] --- exec-maven-plugin:1.2.1:exec (default) @ cloud-devcloud ---
 Traceback (most recent call last):
   File ../marvin/marvin/deployDataCenter.py, line 435, in module
 deploy.deploy()
   File

RE: [jira] [Comment Edited] (CLOUDSTACK-563) Unable to create guest network in UI for Advanced Zone

2012-11-30 Thread Musayev, Ilya

Hi Dave,

Yes I do have Virtual Providers enabled. I used the GUI for the most part to 
create the advanced zone. 

I checked on virtual providers, I have Virtual Router and VPC enabled. I 
disabled VPC because its not applicable shared network and is now disabled.

I also used CloudMonkey for part of the setup, specifically Networks - because 
GUI does not let me accomplish this task.  

My step by step install is documented here. If you were to follow this guide 
you should be able to reproduce this issue.

https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Advanced+Network+Tutorial+-+Step+by+Step

You can see I used CloudMokey at the very end..

Regards
ilya


-Original Message-
From: Dave Cahill (JIRA) [mailto:j...@apache.org] 
Sent: Friday, November 30, 2012 2:20 AM
To: cloudstack-dev@incubator.apache.org
Subject: [jira] [Comment Edited] (CLOUDSTACK-563) Unable to create guest 
network in UI for Advanced Zone


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13507156#comment-13507156
 ] 

Dave Cahill edited comment on CLOUDSTACK-563 at 11/30/12 7:19 AM:
--

Are relevant providers Enabled on the underlying Physical Network?

If you navigate to Infrastructure  Zones  YOURZONENAME  Physical Network  
YOURPHYSICALNETWORKNAME  Network Service Providers, are any of the providers 
marked as Enabled?

I experienced the same behaviour you mention, but it turned out to be because I 
set up my env using CloudMonkey CLI and hadn't enabled any of the providers 
(e.g. VirtualRouter).

  was (Author: davecahill):
Are relevant providers Enabled on the underlying Physical Network?

If you navigate to Infrastructure  Zones  YOURZONENAME  Physical Network  
YOURPHYSICALNETWORKNAME  Network Service Providers, are any of the providers 
marked as Enabled?

I exeprienced the saem behaviour you mention, but it turned out to be because I 
set up my env using CloudMonkey CLI and hadn't enabled any of the providers 
(e.g. VirtualRouter).
  
 Unable to create guest network in UI for Advanced Zone
 --

 Key: CLOUDSTACK-563
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-563
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.0.0
 Environment: CS 4.0 on CentOS 6.3 vSphere 5.0 clusters with 
 Advanced networks
Reporter: ilya musayev
  Labels: Bug, UI

 The UI would not allow for creation of guest Network.  - Please look at the 
 attached image.
 Screenshot - http://i50.tinypic.com/33zfmvs.jpg
 The drop down for NetworkOfferings is blank There is a dropdown for 
 VPC - which is also blank (not needed for shared networks) We also 
 need the ability to pick the proper Physical Network Name - which is 
 not available/ This feature is also broken in the Add A Zone wizard, i will 
 open a separate bug request for that.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators 
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-563) Unable to create guest network in UI for Advanced Zone

2012-11-30 Thread Musayev, Ilya (JIRA)

[
https://issues.apache.org/jira/browse/CLOUDSTACK-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13507426#comment-13507426
]

Musayev, Ilya commented on CLOUDSTACK-563:
--

Hi Dave,

Yes I do have Virtual Providers enabled. I used the GUI for the most part to
create the advanced zone.

I checked on virtual providers, I have Virtual Router and VPC enabled. I
disabled VPC because its not applicable shared network and is now disabled.

I also used CloudMonkey for part of the setup, specifically Networks - because
GUI does not let me accomplish this task.

My step by step install is documented here. If you were to follow this guide
you should be able to reproduce this issue.

https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Advanced+Network+Tutorial+-+Step+by+Step

You can see I used CloudMokey at the very end..

Regards
ilya

Unable to create guest network in UI for Advanced Zone
--

Key: CLOUDSTACK-563
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-563
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: UI
Affects Versions: 4.0.0
Environment: CS 4.0 on CentOS 6.3
vSphere 5.0 clusters with Advanced networks
Reporter: ilya musayev
Labels: Bug, UI

The UI would not allow for creation of guest Network. - Please look at the
attached image.
Screenshot - http://i50.tinypic.com/33zfmvs.jpg
The drop down for NetworkOfferings is blank
There is a dropdown for VPC - which is also blank (not needed for shared
networks)
We also need the ability to pick the proper Physical Network Name - which is
not available/
This feature is also broken in the Add A Zone wizard, i will open a separate
bug request for that.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

RE: back in the game, deploying to devcloud

Hi Sebastien, you're right the work on automation of building the DevCloud 
appliance is still pending as per new network and developer workflow scheme 
described in the blog: http://rohityadav.in/logs/devcloud/
I would suggest James goes ahead and fixes the automation of appliance 
building. If he faces any issues we can help contribute patches. The problem 
for me was the Ubuntu (vagrant) box, it does not work for some reason with two 
nics, Wheezy did and am not sure how one can create boxes using Wheezy.

I think the last emails should help all of you with maven building issues. Let 
know anyone faces any issues, we'll work on it.

Regards.

From: Sebastien Goasguen [run...@gmail.com]
Sent: Friday, November 30, 2012 8:28 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: back in the game, deploying to devcloud

Maybe I can help with a bit of context here,

After Edison released the first devcloud, Chip started to automate the building 
of devcloud. He contributed some early code in /tools/devcloud which used 
veewee/vagrant and puppet to build the image automatically. I tested it and 
created the wiki page:

 https://cwiki.apache.org/CLOUDSTACK/building-devcloud.html

but this was not finished and fully tested.

Time passed...

Then James started fixing this.

Time passed…

Then Rohit just released a new devcloud which solved problems a few of us where 
having, especially with the host only interface.

The automation of building devcloud is still there.

What would be nice is for James and Rohit to sync, so that what Rohit did can 
be automated by the work from James with vagrant and puppet.

The current problem James is having just seems to be a building issue with 
maven that Rohit could help with ? However James may have to look at using 
Wheezy per Rohit's work?

Maybe an IRC discussion can help ?

Hope that helps,

-Sebastien


On Nov 30, 2012, at 3:31 PM, Charles Moulliard ch0...@gmail.com wrote:

 There is a wiki page here :
 https://cwiki.apache.org/CLOUDSTACK/building-devcloud.html


 On Fri, Nov 30, 2012 at 3:16 PM, James Martin jmar...@basho.com wrote:

 Rohit,

 I've spent quite a bit of time fixing all the veewee and vagrant
 configs in tools devcloud, and also re-rewirting the puppet stuff.  I
 understand that you create the image yourself because it's a hassle to
 do so yourself.  My work has alleviated that problem.

 RIght now the fruit of my labor is a fully ready configured vm, I just
 need instructions on how to deploy the build to it.  There is nothing
 on http://rohityadav.in/logs/devcloud that mentnions how to do so.

 - James

 On Fri, Nov 30, 2012 at 2:51 AM, Rohit Yadav rohit.ya...@citrix.com
 wrote:
 James, I see your point, this will probably be fixed later on. We need
 to fix the veewee and vagrant configs in tools/devcloud.
 Right now I created only the image as most people would not want to
 create their own. If you're looking to create your own, checkout diy
 section of http://rohityadav.in/logs/devcloud
 The problem is I've used Debian Wheezy, configuring the vagrant box was
 tricky also some packages like mkisofs and maven3 will have to fetched as
 they are not on distro's repos.
 Any help in fixing these scripts would be great.

 Regards.

 
 From: James Martin [jmar...@basho.com]
 Sent: Friday, November 30, 2012 1:10 PM
 To: cloudstack-dev@incubator.apache.org
 Subject: Re: back in the game, deploying to devcloud

 Just to clear things up -- I'm not using an image at all.  I'm working
 on the stuff that builds devcloud.  I'd like devcloud to be part of
 the source tree, not something external that you download.  I feel
 this makes for a cleaner development experience and forces the
 creation of the devcloud image to remain in the core codebase.

 The goal is to be able, from the cloudstack project root:

 cd tools/devcloud
 vagrant up
 vagrant ssh

 In order for this to work it requires a vagrant basebox, and a vagrant
 xenbox.  Currently in my fork these are built cleanly with veewee,
 vagrant, and puppet via a shell script by simply:

 cd tools/devcloud/deps
 ./boxer.sh -b all

 And you end up with:

 vagrant box list
 devcloudbase (virtualbox)
 devcloudbase-xen (virtualbox)

 Once those vagrant boxes are completed you'd run,

 cd ../
 vagrant up
 vagrant ssh

 vagrant ssh
 Welcome to Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-29-generic-pae i686)

 * Documentation:  https://help.ubuntu.com/
 Last login: Fri Nov 30 05:29:32 2012 from 10.0.2.2
 devcloud@devcloud:~$ ls /opt/cloudstack/
 apache-tomcat-6.0.32  apache-tomcat-6.0.32.zip  incubator-cloudstack
 startdevcloud.sh

 and now you have an clean devcloud vagrant install.  If you ever screw
 up the system,
 you simply:
 vagrant destroy
 vagrant up

 to start fresh

 I have all of that completed.  I just want to be able to install a
 build to this blank vm.  It seems like I should follow these steps:

RE: New DevCloud Appliance

There can be multiple issues here, make sure your mgmt host is correct in 
global settings. Next, check that following are appropriate (may be some 
different values for your case) in global settings too:
management.network.cidr is 192.168.56.0/24
secstorage.allowed.internal.sites is 192.168.56.0/8

There is one issue, Internet won't be available to any VM, ssvm, cpvm etc. It's 
because the default bridge xenbr0 is host-only and is what is used by these vms 
for communication.
Since DevCloud itself is not supposed to support all the operations and the 
assumption is that developer should be able to work in an offline environment, 
xenbr0 was configured as host-only. For your setup, what you can do is setup a 
http server on your host 56.1 or devcloud 56.10 itself and host these isos 
there, and they would be reachable from your ssvm and upload using some url 
like 192.168.56.1/myiso.iso

Regards.


From: Charles Moulliard [ch0...@gmail.com]
Sent: Friday, November 30, 2012 9:10 PM
To: cloudstack-dev
Subject: Re: New DevCloud Appliance

Hi Rohit,

This is my fault. I always forget to start first the servers (mvn -pl
:cloud-client-ui jetty:run) and after this command to deploy / configure
the cloud (mvn -P developer -pl tools/devcloud -Ddeploysvr). This is in
order and works fine on 192.168.56.190.
Nevertheless, I cannot upload an ISO (CentOS). If using the web interface I
try to add an ISO file, then the status of Ready is equal to No and I see
this message in the log :

INFO  [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:)
Console proxy v-2-VM is started
INFO  [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:)
Secondary storage vm s-1-VM is started
INFO  [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:)
Primary secondary storage is not even started, wait until next turn
WARN  [storage.download.DownloadMonitorImpl] (4525736@qtp-28288134-4:)
There is no secondary storage VM for secondary storage host
nfs://192.168.56.10:/opt/storage/secondary

Remark : wget works fine locally so there is no internet issue this time.

Regards,

Charles


On Fri, Nov 30, 2012 at 4:01 PM, Rohit Yadav rohit.ya...@citrix.com wrote:

 Charles, this simply deploys a basic zone using configuration from
 tools/devcloud/devcloud.cfg
 The problem I see is that it's unable to create a connection to mgmt
 server. You can start mgmt server and manually add a basic zone.

 Checklist:
 - Are you running your mgmt server on host os (192.168.56.1) or on
 devcloud (192.168.56.10)
 - Where are you running your mysql server (56.1 or 56.10)
 - Where are you running these commands, on host os or on devcloud?
 - Is MySQL and mgmt server running at that time?

 Note: You are required to run mgmt server, this command simply calls a
 bunch of APIs to mgmt server's API server to deploy a basic zone. I've
 added a section about it on my blog.

 In background it call's marvin. You can try this:
 run mgmt server: mvn -pl jetty:run (make sure mgmt server is running)
 deploy datacenter/basic zone: cd tools/devcloud; python
 ../marvin/marvin/deployDataCenter.py -i devcloud.cfg (change devcloud.cfg
 as per your needs)

 Will update the devcloud2.ova image later today with
 mysql-connector-python, thanks for finding the issue.

 Regards.

 
 From: Charles Moulliard [ch0...@gmail.com]
 Sent: Friday, November 30, 2012 5:37 PM
 To: cloudstack-dev
 Subject: Re: New DevCloud Appliance

 Have installed the missing mysql python package but there is a mysql error
 now :

 mvn -P developer -pl tools/devcloud -Ddeploysvr
 [INFO] Scanning for projects...
 [INFO]

 [INFO]
 
 [INFO] Building Apache CloudStack Developer Tools 4.1.0-SNAPSHOT
 [INFO]
 
 [INFO]
 [INFO] --- maven-remote-resources-plugin:1.3:process (default) @
 cloud-devcloud ---
 [INFO]
 [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @
 cloud-devcloud ---
 [INFO]
 [INFO] --- exec-maven-plugin:1.2.1:exec (default) @ cloud-devcloud ---
 Traceback (most recent call last):
   File ../marvin/marvin/deployDataCenter.py, line 435, in module
 deploy.deploy()
   File ../marvin/marvin/deployDataCenter.py, line 418, in deploy
 self.loadCfg()
   File ../marvin/marvin/deployDataCenter.py, line 394, in loadCfg
 apiKey, securityKey = self.registerApiKey()
   File ../marvin/marvin/deployDataCenter.py, line 334, in registerApiKey
 listuserRes = self.testClient.getApiClient().listUsers(listuser)
   File

 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackAPI/cloudstackAPIClient.py,
 line 358, in listUsers
 response = self.connection.make_request(command, response)
   File

 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py,
 line 177, in make_request
 result =

Re: New DevCloud Appliance


On 30/11/12 17:27, Rohit Yadav wrote:

management.network.cidr is 192.168.56.0/24
secstorage.allowed.internal.sites is 192.168.56.0/8

Rohit,

As I use same config as you, the following values are the same :

management.network.cidr is 192.168.56.0/24
secstorage.allowed.internal.sites is 192.168.56.0/8

It seems that Debian Wheezy already provide a HTTP Server. Do you know 
which server has been installed (does not seems to be Apache2 by 
default) and where is the root directory (to copy an image) ?


Regards,

Charles

Re: New DevCloud Appliance

Can we change the ports number accepted by CloudStack as only 80  443 are
allowed to upload an ISO image ?


On Fri, Nov 30, 2012 at 6:07 PM, Charles Moulliard ch0...@gmail.com wrote:

 On 30/11/12 17:27, Rohit Yadav wrote:

 management.network.cidr is 192.168.56.0/24
 secstorage.allowed.internal.**sites is 192.168.56.0/8

 Rohit,

 As I use same config as you, the following values are the same :


 management.network.cidr is 192.168.56.0/24
 secstorage.allowed.internal.**sites is 192.168.56.0/8

 It seems that Debian Wheezy already provide a HTTP Server. Do you know
 which server has been installed (does not seems to be Apache2 by default)
 and where is the root directory (to copy an image) ?

 Regards,

 Charles






-- 
Charles Moulliard
Apache Committer / Sr. Enterprise Architect (RedHat)
Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com

[jira] [Created] (CLOUDSTACK-571) cloudstack UI - network menu - guest network section - network detailView - edit action - network offering upgrade is not allowed in Shared network.

2012-11-30 Thread Jessica Wang (JIRA)

Jessica Wang created CLOUDSTACK-571:
---

 Summary: cloudstack UI - network menu - guest network section - 
network detailView - edit action - network offering upgrade is not allowed in 
Shared network.
 Key: CLOUDSTACK-571
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-571
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-571) cloudstack UI - network menu - guest network section - network detailView - edit action - network offering upgrade is not allowed in Shared network.

2012-11-30 Thread Jessica Wang (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang resolved CLOUDSTACK-571.
-

Resolution: Fixed

Author: Jessica Wang 
jessica.w...@citrix.com#mailto:jessica.w...@citrix.com
Date:   2 minutes ago (Fri Nov 30 09:35:38 2012)
Commit hash:8819ec6ea7c7214ceb252db3657cfa288bbafaa8

CLOUDSTACK-571: cloudstack UI - network menu - guest network section - network 
detailView - edit action - network offering upgrade is not allowed in Shared 
network.

Contained in branches: master
Contained in no tag

 cloudstack UI - network menu - guest network section - network detailView - 
 edit action - network offering upgrade is not allowed in Shared network.
 

 Key: CLOUDSTACK-571
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-571
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: New DevCloud Appliance

Rohit,

Even, If I use a local HTTP Server, there is still an issue with the
DevCloud2.ova image with NFS.

WARN  [cloud.resource.DiscovererBase] (ClusteredAgentManager Timer:) Unable
to configure resource due to Can not create slave connection to
192.168.56.10
WARN  [agent.manager.AgentManagerImpl] (ClusteredAgentManager Timer:)
Unable to load the resource: 1
WARN  [cloud.resource.DiscovererBase] (ClusteredAgentManager Timer:) Unable
to configure resource due to Can not create slave connection to
192.168.56.10
WARN  [agent.manager.AgentManagerImpl] (ClusteredAgentManager Timer:)
Unable to load the resource: 1
WARN  [storage.download.DownloadMonitorImpl] (23179452@qtp-3363479-0:)
There is no secondary storage VM for secondary storage host
nfs://192.168.56.10:/opt/storage/secondary

See my previous email regarding what the script ssvm-check.sh report please

Regards,

Charles



On Fri, Nov 30, 2012 at 6:32 PM, Charles Moulliard ch0...@gmail.com wrote:

 Can we change the ports number accepted by CloudStack as only 80  443 are
 allowed to upload an ISO image ?


 On Fri, Nov 30, 2012 at 6:07 PM, Charles Moulliard ch0...@gmail.comwrote:

 On 30/11/12 17:27, Rohit Yadav wrote:

 management.network.cidr is 192.168.56.0/24
 secstorage.allowed.internal.**sites is 192.168.56.0/8

 Rohit,

 As I use same config as you, the following values are the same :


 management.network.cidr is 192.168.56.0/24
 secstorage.allowed.internal.**sites is 192.168.56.0/8

 It seems that Debian Wheezy already provide a HTTP Server. Do you know
 which server has been installed (does not seems to be Apache2 by default)
 and where is the root directory (to copy an image) ?

 Regards,

 Charles






 --
 Charles Moulliard
 Apache Committer / Sr. Enterprise Architect (RedHat)
 Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com





-- 
Charles Moulliard
Apache Committer / Sr. Enterprise Architect (RedHat)
Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com

Re: New DevCloud Appliance

Charles,

The 10.0.0.3 address in your SSVM is suspect. Can you make sure you have the 
last version of /tools/devcloud/devcloud.cfg ?

I manage to upload a new image, running a web server on my local machine with:
sudo python -m SimpleHTTPServer 443

The SSVM should be able to ping the host on which you are running the http 
server.

-Sebastien

On Nov 30, 2012, at 6:43 PM, Charles Moulliard ch0...@gmail.com wrote:

 Rohit,
 
 Even, If I use a local HTTP Server, there is still an issue with the
 DevCloud2.ova image with NFS.
 
 WARN  [cloud.resource.DiscovererBase] (ClusteredAgentManager Timer:) Unable
 to configure resource due to Can not create slave connection to
 192.168.56.10
 WARN  [agent.manager.AgentManagerImpl] (ClusteredAgentManager Timer:)
 Unable to load the resource: 1
 WARN  [cloud.resource.DiscovererBase] (ClusteredAgentManager Timer:) Unable
 to configure resource due to Can not create slave connection to
 192.168.56.10
 WARN  [agent.manager.AgentManagerImpl] (ClusteredAgentManager Timer:)
 Unable to load the resource: 1
 WARN  [storage.download.DownloadMonitorImpl] (23179452@qtp-3363479-0:)
 There is no secondary storage VM for secondary storage host
 nfs://192.168.56.10:/opt/storage/secondary
 
 See my previous email regarding what the script ssvm-check.sh report please
 
 Regards,
 
 Charles
 
 
 
 On Fri, Nov 30, 2012 at 6:32 PM, Charles Moulliard ch0...@gmail.com wrote:
 
 Can we change the ports number accepted by CloudStack as only 80  443 are
 allowed to upload an ISO image ?
 
 
 On Fri, Nov 30, 2012 at 6:07 PM, Charles Moulliard ch0...@gmail.comwrote:
 
 On 30/11/12 17:27, Rohit Yadav wrote:
 
 management.network.cidr is 192.168.56.0/24
 secstorage.allowed.internal.**sites is 192.168.56.0/8
 
 Rohit,
 
 As I use same config as you, the following values are the same :
 
 
 management.network.cidr is 192.168.56.0/24
 secstorage.allowed.internal.**sites is 192.168.56.0/8
 
 It seems that Debian Wheezy already provide a HTTP Server. Do you know
 which server has been installed (does not seems to be Apache2 by default)
 and where is the root directory (to copy an image) ?
 
 Regards,
 
 Charles
 
 
 
 
 
 
 --
 Charles Moulliard
 Apache Committer / Sr. Enterprise Architect (RedHat)
 Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
 
 
 
 
 
 -- 
 Charles Moulliard
 Apache Committer / Sr. Enterprise Architect (RedHat)
 Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com

Re: New DevCloud Appliance

Charles, I just posted a screencast. The one thing different is that I am 
actually running cloudstack locally and using devcloud as a host.

http://sebgoa.blogspot.com/2012/11/testing-cloudstack-41-with-devcloud.html

On Nov 30, 2012, at 7:19 PM, Charles Moulliard ch0...@gmail.com wrote:

 Thx Sebastien. If I compile last version of the code on DevCloud VM
 (192.168.56.10) running in VB, I get this error now :
 
 mvn -P developer -pl tools/devcloud -Ddeploysvr
 [INFO] Scanning for projects...
 [INFO]
 
 [INFO]
 
 [INFO] Building Apache CloudStack Developer Tools 4.1.0-SNAPSHOT
 [INFO]
 
 [INFO]
 [INFO] --- maven-remote-resources-plugin:1.3:process (default) @
 cloud-devcloud ---
 [INFO]
 [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @
 cloud-devcloud ---
 [INFO]
 [INFO] --- exec-maven-plugin:1.2.1:exec (default) @ cloud-devcloud ---
 Traceback (most recent call last):
  File ../marvin/marvin/deployDataCenter.py, line 435, in module
deploy.deploy()
  File ../marvin/marvin/deployDataCenter.py, line 419, in deploy
self.createZones(self.config.zones)
  File ../marvin/marvin/deployDataCenter.py, line 286, in createZones
zoneresponse = self.apiClient.createZone(createzone)
  File
 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackAPI/cloudstackAPIClient.py,
 line 1013, in createZone
response = self.connection.make_request(command, response)
  File
 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py,
 line 175, in make_request
result = self.make_request_with_auth(commandName, requests)
  File
 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py,
 line 89, in make_request_with_auth
raise e
 urllib2.HTTPError: HTTP Error 431: 431
 
 INFO  [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:) We are
 good, no orphan management server msid in host table is found
 INFO  [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:) No inactive
 management server node found
 WARN  [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:)
 Notifying management server join event took 18 ms
 INFO  [cloud.resource.ResourceManagerImpl] (16113904@qtp-22625510-5:)
 Trying to add a new host at http://192.168.56.10/ in data center 1
 WARN  [cloud.resource.ResourceManagerImpl] (16113904@qtp-22625510-5:)
 Unable to find the server resources at http://192.168.56.10/
 WARN  [api.commands.AddHostCmd] (16113904@qtp-22625510-5:) Exception:
 com.cloud.exception.DiscoveryException: Unable to add the host
 at
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:737)
 at
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:544)
 at com.cloud.api.commands.AddHostCmd.execute(AddHostCmd.java:140)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:167)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:539)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:423)
 at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:311)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
 at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
 at
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
 at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
 at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
 at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
 at
 org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
 at
 org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
 at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
 at org.mortbay.jetty.Server.handle(Server.java:326)
 at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
 at
 org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
 at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
 at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
 at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
 at
 org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
 at
 org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
 WARN  [cloud.api.ApiDispatcher] (16113904@qtp-22625510-5:) class
 com.cloud.api.ServerApiException : Unable to add the host
 
 
 
 
 On Fri, Nov 30, 2012 at 7:01 PM, Sebastien Goasguen run...@gmail.comwrote:
 
 Charles,
 
 The 10.0.0.3 address in your SSVM is suspect. Can you make sure you have
 the last version

Re: New DevCloud Appliance

The link is wrong ...


On Fri, Nov 30, 2012 at 7:42 PM, Sebastien Goasguen run...@gmail.comwrote:

 Charles, I just posted a screencast. The one thing different is that I am
 actually running cloudstack locally and using devcloud as a host.

 http://sebgoa.blogspot.com/2012/11/testing-cloudstack-41-with-devcloud.html

 On Nov 30, 2012, at 7:19 PM, Charles Moulliard ch0...@gmail.com wrote:

  Thx Sebastien. If I compile last version of the code on DevCloud VM
  (192.168.56.10) running in VB, I get this error now :
 
  mvn -P developer -pl tools/devcloud -Ddeploysvr
  [INFO] Scanning for projects...
  [INFO]
 
  [INFO]
  
  [INFO] Building Apache CloudStack Developer Tools 4.1.0-SNAPSHOT
  [INFO]
  
  [INFO]
  [INFO] --- maven-remote-resources-plugin:1.3:process (default) @
  cloud-devcloud ---
  [INFO]
  [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @
  cloud-devcloud ---
  [INFO]
  [INFO] --- exec-maven-plugin:1.2.1:exec (default) @ cloud-devcloud ---
  Traceback (most recent call last):
   File ../marvin/marvin/deployDataCenter.py, line 435, in module
 deploy.deploy()
   File ../marvin/marvin/deployDataCenter.py, line 419, in deploy
 self.createZones(self.config.zones)
   File ../marvin/marvin/deployDataCenter.py, line 286, in createZones
 zoneresponse = self.apiClient.createZone(createzone)
   File
 
 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 1013, in createZone
 response = self.connection.make_request(command, response)
   File
 
 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py,
  line 175, in make_request
 result = self.make_request_with_auth(commandName, requests)
   File
 
 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py,
  line 89, in make_request_with_auth
 raise e
  urllib2.HTTPError: HTTP Error 431: 431
 
  INFO  [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:) We are
  good, no orphan management server msid in host table is found
  INFO  [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:) No
 inactive
  management server node found
  WARN  [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:)
  Notifying management server join event took 18 ms
  INFO  [cloud.resource.ResourceManagerImpl] (16113904@qtp-22625510-5:)
  Trying to add a new host at http://192.168.56.10/ in data center 1
  WARN  [cloud.resource.ResourceManagerImpl] (16113904@qtp-22625510-5:)
  Unable to find the server resources at http://192.168.56.10/
  WARN  [api.commands.AddHostCmd] (16113904@qtp-22625510-5:) Exception:
  com.cloud.exception.DiscoveryException: Unable to add the host
  at
 
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:737)
  at
 
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:544)
  at com.cloud.api.commands.AddHostCmd.execute(AddHostCmd.java:140)
  at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:167)
  at com.cloud.api.ApiServer.queueCommand(ApiServer.java:539)
  at com.cloud.api.ApiServer.handleRequest(ApiServer.java:423)
  at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:311)
  at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
  at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
  at
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
  at
 
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
  at
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
  at
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
  at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
  at
 
 org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
  at
 
 org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
  at
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
  at org.mortbay.jetty.Server.handle(Server.java:326)
  at
 org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
  at
 
 org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
  at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
  at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
  at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
  at
 
 org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
  at
 
 org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
  WARN  [cloud.api.ApiDispatcher] (16113904@qtp-22625510-5:) class
  com.cloud.api.ServerApiException : Unable

Re: New DevCloud Appliance

my bad, did not publish it, can you try again

On Nov 30, 2012, at 7:45 PM, Charles Moulliard ch0...@gmail.com wrote:

 The link is wrong ...
 
 
 On Fri, Nov 30, 2012 at 7:42 PM, Sebastien Goasguen run...@gmail.comwrote:
 
 Charles, I just posted a screencast. The one thing different is that I am
 actually running cloudstack locally and using devcloud as a host.
 
 http://sebgoa.blogspot.com/2012/11/testing-cloudstack-41-with-devcloud.html
 
 On Nov 30, 2012, at 7:19 PM, Charles Moulliard ch0...@gmail.com wrote:
 
 Thx Sebastien. If I compile last version of the code on DevCloud VM
 (192.168.56.10) running in VB, I get this error now :
 
 mvn -P developer -pl tools/devcloud -Ddeploysvr
 [INFO] Scanning for projects...
 [INFO]
 
 [INFO]
 
 [INFO] Building Apache CloudStack Developer Tools 4.1.0-SNAPSHOT
 [INFO]
 
 [INFO]
 [INFO] --- maven-remote-resources-plugin:1.3:process (default) @
 cloud-devcloud ---
 [INFO]
 [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @
 cloud-devcloud ---
 [INFO]
 [INFO] --- exec-maven-plugin:1.2.1:exec (default) @ cloud-devcloud ---
 Traceback (most recent call last):
 File ../marvin/marvin/deployDataCenter.py, line 435, in module
   deploy.deploy()
 File ../marvin/marvin/deployDataCenter.py, line 419, in deploy
   self.createZones(self.config.zones)
 File ../marvin/marvin/deployDataCenter.py, line 286, in createZones
   zoneresponse = self.apiClient.createZone(createzone)
 File
 
 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackAPI/cloudstackAPIClient.py,
 line 1013, in createZone
   response = self.connection.make_request(command, response)
 File
 
 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py,
 line 175, in make_request
   result = self.make_request_with_auth(commandName, requests)
 File
 
 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py,
 line 89, in make_request_with_auth
   raise e
 urllib2.HTTPError: HTTP Error 431: 431
 
 INFO  [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:) We are
 good, no orphan management server msid in host table is found
 INFO  [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:) No
 inactive
 management server node found
 WARN  [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:)
 Notifying management server join event took 18 ms
 INFO  [cloud.resource.ResourceManagerImpl] (16113904@qtp-22625510-5:)
 Trying to add a new host at http://192.168.56.10/ in data center 1
 WARN  [cloud.resource.ResourceManagerImpl] (16113904@qtp-22625510-5:)
 Unable to find the server resources at http://192.168.56.10/
 WARN  [api.commands.AddHostCmd] (16113904@qtp-22625510-5:) Exception:
 com.cloud.exception.DiscoveryException: Unable to add the host
 at
 
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:737)
 at
 
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:544)
 at com.cloud.api.commands.AddHostCmd.execute(AddHostCmd.java:140)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:167)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:539)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:423)
 at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:311)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
 at
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
 at
 
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
 at
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
 at
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
 at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
 at
 
 org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
 at
 
 org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
 at
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
 at org.mortbay.jetty.Server.handle(Server.java:326)
 at
 org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
 at
 
 org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
 at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
 at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
 at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
 at
 
 org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
 at
 
 org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
 WARN  [cloud.api.ApiDispatcher] (16113904@qtp-22625510-5:) class

Re: Review Request: S3-backed Secondary Storage


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/8123/#review13904
---


John, thanks for patch. Much better now. Can you check, why the code that 
configure db in the testclient is commented? 
tools/marvin/marvin/deployDataCenter.py
For the actual functional review, Edison can help on storage and Alena/Kishan 
on API/DB layers.

- Rohit Yadav


On Nov. 26, 2012, 9:44 p.m., John Burwell wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/8123/
 ---
 
 (Updated Nov. 26, 2012, 9:44 p.m.)
 
 
 Review request for cloudstack.
 
 
 Description
 ---
 
 Backs NFS-based secondary storage with an S3-compatible object store. 
 Periodically, a reaper thread synchronizes templates and ISOs stored on a NFS 
 secondary storage mount with a configured S3 object store. It also pushes 
 snapshots to the object store when they are created and downloads them in 
 other zones on-demand. In addition to permitting the use of commodity or IaaS 
 storage solutions for static assets, it provides a means of automatically 
 synchronizing template and ISO assets across multiple zones.
 
 For more information about the design of the patch, please see the design 
 document 
 (https://cwiki.apache.org/confluence/display/CLOUDSTACK/S3-backed+Secondary+Storage).
 
 
 This addresses bug CLOUDSTACK-509.
 
 
 Diffs
 -
 
   .gitignore 33f95c7 
   api/src/com/cloud/agent/api/BackupSnapshotCommand.java 9476d7d 
   api/src/com/cloud/agent/api/DeleteSnapshotBackupCommand.java 3fa8c2b 
   api/src/com/cloud/agent/api/DeleteTemplateFromS3Command.java PRE-CREATION 
   api/src/com/cloud/agent/api/DownloadSnapshotFromS3Command.java PRE-CREATION 
   
 api/src/com/cloud/agent/api/DownloadTemplateFromS3ToSecondaryStorageCommand.java
  PRE-CREATION 
   
 api/src/com/cloud/agent/api/UploadTemplateToS3FromSecondaryStorageCommand.java
  PRE-CREATION 
   api/src/com/cloud/agent/api/to/S3TO.java PRE-CREATION 
   api/src/com/cloud/api/ApiConstants.java 78a3ded 
   api/src/com/cloud/api/ResponseGenerator.java 4e8fbd8 
   api/src/com/cloud/api/commands/AddS3Cmd.java PRE-CREATION 
   api/src/com/cloud/api/commands/ListS3sCmd.java PRE-CREATION 
   api/src/com/cloud/api/response/S3Response.java PRE-CREATION 
   api/src/com/cloud/resource/ResourceService.java 1065453 
   api/src/com/cloud/storage/S3.java PRE-CREATION 
   build/package.xml 09ed939 
   client/WEB-INF/classes/resources/messages.properties 626e44a 
   client/tomcatconf/commands.properties.in 149547e 
   core/pom.xml 15f0f7b 
   core/src/com/cloud/storage/S3VO.java PRE-CREATION 
   core/src/com/cloud/storage/SnapshotVO.java 08dfafa 
   core/src/com/cloud/storage/VMTemplateS3VO.java PRE-CREATION 
   core/src/com/cloud/storage/resource/NfsSecondaryStorageResource.java 
 155210d 
   patches/systemvm/debian/config/etc/sysctl.conf 7f945b0 
   
 plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/CitrixResourceBase.java
  d2db85c 
   pom.xml 4a4276e 
   scripts/vm/hypervisor/xenserver/s3xen PRE-CREATION 
   scripts/vm/hypervisor/xenserver/xenserver56/patch d485414 
   scripts/vm/hypervisor/xenserver/xenserver56fp1/patch 9fe9740 
   scripts/vm/hypervisor/xenserver/xenserver60/patch f049109 
   server/pom.xml e3308d8 
   server/src/com/cloud/api/ApiDBUtils.java 3b5f634 
   server/src/com/cloud/api/ApiDispatcher.java dfe4a1f 
   server/src/com/cloud/api/ApiResponseHelper.java ebe8415 
   server/src/com/cloud/api/doc/ApiXmlDocWriter.java d31ef5a 
   server/src/com/cloud/configuration/Config.java 66ac276 
   server/src/com/cloud/configuration/ConfigurationManagerImpl.java ef940e8 
   server/src/com/cloud/configuration/DefaultComponentLibrary.java ef61044 
   server/src/com/cloud/resource/ResourceManagerImpl.java ced601b 
   server/src/com/cloud/storage/StorageManagerImpl.java e252633 
   server/src/com/cloud/storage/dao/S3Dao.java PRE-CREATION 
   server/src/com/cloud/storage/dao/S3DaoImpl.java PRE-CREATION 
   server/src/com/cloud/storage/dao/VMTemplateDao.java f5b6913 
   server/src/com/cloud/storage/dao/VMTemplateDaoImpl.java 2a0dfc8 
   server/src/com/cloud/storage/dao/VMTemplateS3Dao.java PRE-CREATION 
   server/src/com/cloud/storage/dao/VMTemplateS3DaoImpl.java PRE-CREATION 
   server/src/com/cloud/storage/s3/S3Manager.java PRE-CREATION 
   server/src/com/cloud/storage/s3/S3ManagerImpl.java PRE-CREATION 
   server/src/com/cloud/storage/snapshot/SnapshotManager.java a10298e 
   server/src/com/cloud/storage/snapshot/SnapshotManagerImpl.java 32e37e6 
   server/src/com/cloud/template/S3SyncTask.java PRE-CREATION 
   server/src/com/cloud/template/TemplateManagerImpl.java 1e87de2 
   setup/db/create-schema.sql fff084e 
   setup/db/db/schema-40to410.sql PRE-CREATION

RE: New DevCloud Appliance

Yes, check your host IP in global settings, change to appropriate IP and 
restart mgmt server. Next, delete SSVM (they are stateless, don't worry). New 
ssvms would be able to get the templates from any IP within the secstorage 
internal cidr, 192.168.56.0/8 or any other value in your global settings.

Regards.

From: Sebastien Goasguen [run...@gmail.com]
Sent: Friday, November 30, 2012 11:31 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: New DevCloud Appliance

Charles,

The 10.0.0.3 address in your SSVM is suspect. Can you make sure you have the 
last version of /tools/devcloud/devcloud.cfg ?

I manage to upload a new image, running a web server on my local machine with:
sudo python -m SimpleHTTPServer 443

The SSVM should be able to ping the host on which you are running the http 
server.

-Sebastien

On Nov 30, 2012, at 6:43 PM, Charles Moulliard ch0...@gmail.com wrote:

 Rohit,

 Even, If I use a local HTTP Server, there is still an issue with the
 DevCloud2.ova image with NFS.

 WARN  [cloud.resource.DiscovererBase] (ClusteredAgentManager Timer:) Unable
 to configure resource due to Can not create slave connection to
 192.168.56.10
 WARN  [agent.manager.AgentManagerImpl] (ClusteredAgentManager Timer:)
 Unable to load the resource: 1
 WARN  [cloud.resource.DiscovererBase] (ClusteredAgentManager Timer:) Unable
 to configure resource due to Can not create slave connection to
 192.168.56.10
 WARN  [agent.manager.AgentManagerImpl] (ClusteredAgentManager Timer:)
 Unable to load the resource: 1
 WARN  [storage.download.DownloadMonitorImpl] (23179452@qtp-3363479-0:)
 There is no secondary storage VM for secondary storage host
 nfs://192.168.56.10:/opt/storage/secondary

 See my previous email regarding what the script ssvm-check.sh report please

 Regards,

 Charles

 On Fri, Nov 30, 2012 at 6:32 PM, Charles Moulliard ch0...@gmail.com wrote:

 Can we change the ports number accepted by CloudStack as only 80  443 are
 allowed to upload an ISO image ?

 On Fri, Nov 30, 2012 at 6:07 PM, Charles Moulliard ch0...@gmail.comwrote:

 On 30/11/12 17:27, Rohit Yadav wrote:

 management.network.cidr is 192.168.56.0/24
 secstorage.allowed.internal.**sites is 192.168.56.0/8

 Rohit,

 As I use same config as you, the following values are the same :

 management.network.cidr is 192.168.56.0/24
 secstorage.allowed.internal.**sites is 192.168.56.0/8

 It seems that Debian Wheezy already provide a HTTP Server. Do you know
 which server has been installed (does not seems to be Apache2 by default)
 and where is the root directory (to copy an image) ?

 Regards,

 Charles

 --
 Charles Moulliard
 Apache Committer / Sr. Enterprise Architect (RedHat)
 Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com

 --
 Charles Moulliard
 Apache Committer / Sr. Enterprise Architect (RedHat)
 Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com

RE: New DevCloud Appliance

I would too recommend you to run mgmt server locally on your host os and use 
devcloud only as Xen host and NFS server. Though, if you're developing inside 
it should work too, but you won't be able to debug it using your IDE (actually 
you can if you install gnome or kde on it and install intellij ce or eclipse) 
and you're required to change host ips and other global settings. Make sure you 
do them before deploying the datacenter.

Regards.

From: Sebastien Goasguen [run...@gmail.com]
Sent: Saturday, December 01, 2012 12:12 AM
To: cloudstack-dev@incubator.apache.org
Subject: Re: New DevCloud Appliance

Charles, I just posted a screencast. The one thing different is that I am 
actually running cloudstack locally and using devcloud as a host.

http://sebgoa.blogspot.com/2012/11/testing-cloudstack-41-with-devcloud.html

On Nov 30, 2012, at 7:19 PM, Charles Moulliard ch0...@gmail.com wrote:

 Thx Sebastien. If I compile last version of the code on DevCloud VM
 (192.168.56.10) running in VB, I get this error now :

 mvn -P developer -pl tools/devcloud -Ddeploysvr
 [INFO] Scanning for projects...
 [INFO]

 [INFO]
 
 [INFO] Building Apache CloudStack Developer Tools 4.1.0-SNAPSHOT
 [INFO]
 
 [INFO]
 [INFO] --- maven-remote-resources-plugin:1.3:process (default) @
 cloud-devcloud ---
 [INFO]
 [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @
 cloud-devcloud ---
 [INFO]
 [INFO] --- exec-maven-plugin:1.2.1:exec (default) @ cloud-devcloud ---
 Traceback (most recent call last):
  File ../marvin/marvin/deployDataCenter.py, line 435, in module
deploy.deploy()
  File ../marvin/marvin/deployDataCenter.py, line 419, in deploy
self.createZones(self.config.zones)
  File ../marvin/marvin/deployDataCenter.py, line 286, in createZones
zoneresponse = self.apiClient.createZone(createzone)
  File
 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackAPI/cloudstackAPIClient.py,
 line 1013, in createZone
response = self.connection.make_request(command, response)
  File
 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py,
 line 175, in make_request
result = self.make_request_with_auth(commandName, requests)
  File
 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py,
 line 89, in make_request_with_auth
raise e
 urllib2.HTTPError: HTTP Error 431: 431

 INFO  [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:) We are
 good, no orphan management server msid in host table is found
 INFO  [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:) No inactive
 management server node found
 WARN  [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:)
 Notifying management server join event took 18 ms
 INFO  [cloud.resource.ResourceManagerImpl] (16113904@qtp-22625510-5:)
 Trying to add a new host at http://192.168.56.10/ in data center 1
 WARN  [cloud.resource.ResourceManagerImpl] (16113904@qtp-22625510-5:)
 Unable to find the server resources at http://192.168.56.10/
 WARN  [api.commands.AddHostCmd] (16113904@qtp-22625510-5:) Exception:
 com.cloud.exception.DiscoveryException: Unable to add the host
 at
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:737)
 at
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:544)
 at com.cloud.api.commands.AddHostCmd.execute(AddHostCmd.java:140)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:167)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:539)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:423)
 at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:311)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
 at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
 at
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
 at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
 at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
 at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
 at
 org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
 at
 org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
 at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
 at org.mortbay.jetty.Server.handle(Server.java:326)
 at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
 at
 org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
 at

RE: New DevCloud Appliance

works for me: 
http://sebgoa.blogspot.com/2012/11/testing-cloudstack-41-with-devcloud.html

From: Charles Moulliard [ch0...@gmail.com]
Sent: Saturday, December 01, 2012 12:15 AM
To: cloudstack-dev
Subject: Re: New DevCloud Appliance

The link is wrong ...


On Fri, Nov 30, 2012 at 7:42 PM, Sebastien Goasguen run...@gmail.comwrote:

 Charles, I just posted a screencast. The one thing different is that I am
 actually running cloudstack locally and using devcloud as a host.

 http://sebgoa.blogspot.com/2012/11/testing-cloudstack-41-with-devcloud.html

 On Nov 30, 2012, at 7:19 PM, Charles Moulliard ch0...@gmail.com wrote:

  Thx Sebastien. If I compile last version of the code on DevCloud VM
  (192.168.56.10) running in VB, I get this error now :
 
  mvn -P developer -pl tools/devcloud -Ddeploysvr
  [INFO] Scanning for projects...
  [INFO]
 
  [INFO]
  
  [INFO] Building Apache CloudStack Developer Tools 4.1.0-SNAPSHOT
  [INFO]
  
  [INFO]
  [INFO] --- maven-remote-resources-plugin:1.3:process (default) @
  cloud-devcloud ---
  [INFO]
  [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @
  cloud-devcloud ---
  [INFO]
  [INFO] --- exec-maven-plugin:1.2.1:exec (default) @ cloud-devcloud ---
  Traceback (most recent call last):
   File ../marvin/marvin/deployDataCenter.py, line 435, in module
 deploy.deploy()
   File ../marvin/marvin/deployDataCenter.py, line 419, in deploy
 self.createZones(self.config.zones)
   File ../marvin/marvin/deployDataCenter.py, line 286, in createZones
 zoneresponse = self.apiClient.createZone(createzone)
   File
 
 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 1013, in createZone
 response = self.connection.make_request(command, response)
   File
 
 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py,
  line 175, in make_request
 result = self.make_request_with_auth(commandName, requests)
   File
 
 /opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py,
  line 89, in make_request_with_auth
 raise e
  urllib2.HTTPError: HTTP Error 431: 431
 
  INFO  [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:) We are
  good, no orphan management server msid in host table is found
  INFO  [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:) No
 inactive
  management server node found
  WARN  [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:)
  Notifying management server join event took 18 ms
  INFO  [cloud.resource.ResourceManagerImpl] (16113904@qtp-22625510-5:)
  Trying to add a new host at http://192.168.56.10/ in data center 1
  WARN  [cloud.resource.ResourceManagerImpl] (16113904@qtp-22625510-5:)
  Unable to find the server resources at http://192.168.56.10/
  WARN  [api.commands.AddHostCmd] (16113904@qtp-22625510-5:) Exception:
  com.cloud.exception.DiscoveryException: Unable to add the host
  at
 
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:737)
  at
 
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:544)
  at com.cloud.api.commands.AddHostCmd.execute(AddHostCmd.java:140)
  at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:167)
  at com.cloud.api.ApiServer.queueCommand(ApiServer.java:539)
  at com.cloud.api.ApiServer.handleRequest(ApiServer.java:423)
  at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:311)
  at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
  at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
  at
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
  at
 
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
  at
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
  at
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
  at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
  at
 
 org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
  at
 
 org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
  at
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
  at org.mortbay.jetty.Server.handle(Server.java:326)
  at
 org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
  at
 
 org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
  at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
  at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
  at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
  at

Re: Review Request: S3-backed Secondary Storage

2012-11-30 Thread John Burwell



 On Nov. 30, 2012, 7:15 p.m., Rohit Yadav wrote:
  John, thanks for patch. Much better now. Can you check, why the code that 
  configure db in the testclient is commented? 
  tools/marvin/marvin/deployDataCenter.py
  For the actual functional review, Edison can help on storage and 
  Alena/Kishan on API/DB layers.

Rohit,

I removed the code (which I forgot to delete) because, as I understand it, 
Marvin no longer connects to the database during testing but uses the API.  If 
it is no longer necessary, removing the requirement for remote access to the 
database on development machines the tool much lighter weight.

Thanks,
-John


- John


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/8123/#review13904
---


On Nov. 26, 2012, 9:44 p.m., John Burwell wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/8123/
 ---
 
 (Updated Nov. 26, 2012, 9:44 p.m.)
 
 
 Review request for cloudstack.
 
 
 Description
 ---
 
 Backs NFS-based secondary storage with an S3-compatible object store. 
 Periodically, a reaper thread synchronizes templates and ISOs stored on a NFS 
 secondary storage mount with a configured S3 object store. It also pushes 
 snapshots to the object store when they are created and downloads them in 
 other zones on-demand. In addition to permitting the use of commodity or IaaS 
 storage solutions for static assets, it provides a means of automatically 
 synchronizing template and ISO assets across multiple zones.
 
 For more information about the design of the patch, please see the design 
 document 
 (https://cwiki.apache.org/confluence/display/CLOUDSTACK/S3-backed+Secondary+Storage).
 
 
 This addresses bug CLOUDSTACK-509.
 
 
 Diffs
 -
 
   .gitignore 33f95c7 
   api/src/com/cloud/agent/api/BackupSnapshotCommand.java 9476d7d 
   api/src/com/cloud/agent/api/DeleteSnapshotBackupCommand.java 3fa8c2b 
   api/src/com/cloud/agent/api/DeleteTemplateFromS3Command.java PRE-CREATION 
   api/src/com/cloud/agent/api/DownloadSnapshotFromS3Command.java PRE-CREATION 
   
 api/src/com/cloud/agent/api/DownloadTemplateFromS3ToSecondaryStorageCommand.java
  PRE-CREATION 
   
 api/src/com/cloud/agent/api/UploadTemplateToS3FromSecondaryStorageCommand.java
  PRE-CREATION 
   api/src/com/cloud/agent/api/to/S3TO.java PRE-CREATION 
   api/src/com/cloud/api/ApiConstants.java 78a3ded 
   api/src/com/cloud/api/ResponseGenerator.java 4e8fbd8 
   api/src/com/cloud/api/commands/AddS3Cmd.java PRE-CREATION 
   api/src/com/cloud/api/commands/ListS3sCmd.java PRE-CREATION 
   api/src/com/cloud/api/response/S3Response.java PRE-CREATION 
   api/src/com/cloud/resource/ResourceService.java 1065453 
   api/src/com/cloud/storage/S3.java PRE-CREATION 
   build/package.xml 09ed939 
   client/WEB-INF/classes/resources/messages.properties 626e44a 
   client/tomcatconf/commands.properties.in 149547e 
   core/pom.xml 15f0f7b 
   core/src/com/cloud/storage/S3VO.java PRE-CREATION 
   core/src/com/cloud/storage/SnapshotVO.java 08dfafa 
   core/src/com/cloud/storage/VMTemplateS3VO.java PRE-CREATION 
   core/src/com/cloud/storage/resource/NfsSecondaryStorageResource.java 
 155210d 
   patches/systemvm/debian/config/etc/sysctl.conf 7f945b0 
   
 plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/CitrixResourceBase.java
  d2db85c 
   pom.xml 4a4276e 
   scripts/vm/hypervisor/xenserver/s3xen PRE-CREATION 
   scripts/vm/hypervisor/xenserver/xenserver56/patch d485414 
   scripts/vm/hypervisor/xenserver/xenserver56fp1/patch 9fe9740 
   scripts/vm/hypervisor/xenserver/xenserver60/patch f049109 
   server/pom.xml e3308d8 
   server/src/com/cloud/api/ApiDBUtils.java 3b5f634 
   server/src/com/cloud/api/ApiDispatcher.java dfe4a1f 
   server/src/com/cloud/api/ApiResponseHelper.java ebe8415 
   server/src/com/cloud/api/doc/ApiXmlDocWriter.java d31ef5a 
   server/src/com/cloud/configuration/Config.java 66ac276 
   server/src/com/cloud/configuration/ConfigurationManagerImpl.java ef940e8 
   server/src/com/cloud/configuration/DefaultComponentLibrary.java ef61044 
   server/src/com/cloud/resource/ResourceManagerImpl.java ced601b 
   server/src/com/cloud/storage/StorageManagerImpl.java e252633 
   server/src/com/cloud/storage/dao/S3Dao.java PRE-CREATION 
   server/src/com/cloud/storage/dao/S3DaoImpl.java PRE-CREATION 
   server/src/com/cloud/storage/dao/VMTemplateDao.java f5b6913 
   server/src/com/cloud/storage/dao/VMTemplateDaoImpl.java 2a0dfc8 
   server/src/com/cloud/storage/dao/VMTemplateS3Dao.java PRE-CREATION 
   server/src/com/cloud/storage/dao/VMTemplateS3DaoImpl.java PRE-CREATION 
   server/src/com/cloud/storage/s3/S3Manager.java PRE-CREATION 
   server/src/com/cloud/storage/s3/S3ManagerImpl.java PRE-CREATION

[jira] [Created] (CLOUDSTACK-572) SG Enabled Advanced Zone - Not able to deploy a VM in an account specific shared network.

Alena Prokharchyk created CLOUDSTACK-572:


 Summary: SG Enabled Advanced Zone - Not able to deploy a VM in an 
account specific shared network.
 Key: CLOUDSTACK-572
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-572
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.0.0
Reporter: Alena Prokharchyk
Assignee: Alena Prokharchyk
 Fix For: 4.1.0


SG Enabled Advanced Zone - Not able to deploy a VM in an account specific 
shared network.

Tested with:
[root@centos62mgmt management]# cloud-sccs
Git Revision: 7ff2f872debb5446c1f1ee844791b76a4352818e
Git URL: ssh://r...@git-cpp.citrix.com/var/lib/git/cloudstack-oss

Set up:

Advanced zone set up with SG enabled.
Create an account.
As this account , Deploy few Vms in the Zone wide shared SG enabled network.
Create a account specific shared network for this account.

Deploy a Vm in this network using the folloiwng api call:

It fails.

GET 
command=deployVirtualMachinezoneId=80f6719f-8fcc-4c87-bf36-b955e9389353templateId=abd10db9-5903-469f-a509-ab41699c0160hypervisor=KVMserviceOfferingId=8178b836-4c8d-4dfe-9b19-e3931e7234a8networkIds=d8bf2c7c-7741-43bc-858f-085adbc4cca6displayname=testacctspecificname=testacctsepecificresponse=jsonsessionkey=Yc797M%2BFtASw4helMfW6gONcxw8%3D_=1354232543251
 431 Can specify only Direct Guest Account specific networks when deploy vm in 
Security Group enabled


mysql select acl_type , name,id,uuid,guest_type from networks;
+--+-+-+--++
| acl_type | name | id | uuid | guest_type |
+--+-+-+--++
| NULL | NULL | 200 | 2ddf7576-bda4-414d-adc3-f47df493fbee | NULL |
| NULL | NULL | 201 | 7c1af3f2-19d8-489a-a64b-b68a5af9b1bf | NULL |
| NULL | NULL | 202 | 9365f3d0-ac2f-44e1-bb10-4a4ad6b769c3 | NULL |
| Domain | defaultGuestNetwork | 203 | a8617a98-da48-41c5-b3fd-f985833b934d | 
Shared |
| Account | test | 204 | d8bf2c7c-7741-43bc-858f-085adbc4cca6 | Shared |
+--+-+-+--++
5 rows in set (0.00 sec) 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-573) NPE at com.cloud.network.NetworkManagerImpl.networkOfferingIsConfiguredForExternalNetworking(NetworkManagerImpl.java:4345) when create network from the network offe

Alena Prokharchyk created CLOUDSTACK-573:


 Summary: NPE at 
com.cloud.network.NetworkManagerImpl.networkOfferingIsConfiguredForExternalNetworking(NetworkManagerImpl.java:4345)
 when create network from the network offering having NULL provider for the 
service
 Key: CLOUDSTACK-573
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-573
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.0.0
Reporter: Alena Prokharchyk
Assignee: Alena Prokharchyk
Priority: Trivial
 Fix For: 4.1.0


Steps to reproduce:

1) Create network offering, pass service list, but don't pass the provider:

http://localhost:8096/?command=createNetworkOfferingname=alena11displayText=alenatrafficType=GuestguestIpType=IsolatedsupportedServices=UserData

We do allow having null provider in the network offering; later when network is
being created from this network offering, the default provider of the service
on the physical network is being set for the service.

2) Try to create the network from this network offering. It results in NPE, 
because check for external device use is being done before services/providers 
are finalized for the network:

ERROR [cloud.api.ApiDispatcher] (catalina-exec-7:) Exception while executing 
CreateNetworkCmd:
java.lang.NullPointerException
at 
com.cloud.network.NetworkManagerImpl.networkOfferingIsConfiguredForExternalNetworking(NetworkManagerImpl.java:4345)
at 
com.cloud.network.NetworkManagerImpl.createGuestNetwork(NetworkManagerImpl.java:2666)
at 
com.cloud.utils.component.ComponentLocator$InterceptorDispatcher.intercept(ComponentLocator.java:1185)
at 
com.cloud.api.commands.CreateNetworkCmd.execute(CreateNetworkCmd.java:220)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:235)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:540)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:419)
at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:300)
at com.cloud.api.ApiServlet.doGet(ApiServlet.java:59)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at 
org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
at 
org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2260)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679) 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: back in the game, deploying to devcloud

Ok, sounds good. I'll keep an eye out for next Weds.

On Fri, Nov 30, 2012 at 2:20 PM, Rohit Yadav rohit.ya...@citrix.com wrote:
James, we've weekly IRC meetings, maybe you can join us next Wednesday.
Watchout on the mailing list, the meeting schedule is announced prior to the
meeting on dev ml.
Regards.

From: James Martin [jmar...@basho.com]
Sent: Friday, November 30, 2012 8:48 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: back in the game, deploying to devcloud

Sebastien,

Thanks for the context. An IRC meetup would be great.

-James

On Fri, Nov 30, 2012 at 9:58 AM, Sebastien Goasguen run...@gmail.com wrote:
Maybe I can help with a bit of context here,

After Edison released the first devcloud, Chip started to automate the
building of devcloud. He contributed some early code in /tools/devcloud
which used veewee/vagrant and puppet to build the image automatically. I
tested it and created the wiki page:

https://cwiki.apache.org/CLOUDSTACK/building-devcloud.html

but this was not finished and fully tested.

Time passed...

Then James started fixing this.

Time passed…

Then Rohit just released a new devcloud which solved problems a few of us
where having, especially with the host only interface.

The automation of building devcloud is still there.

What would be nice is for James and Rohit to sync, so that what Rohit did
can be automated by the work from James with vagrant and puppet.

The current problem James is having just seems to be a building issue with
maven that Rohit could help with ? However James may have to look at using
Wheezy per Rohit's work?

Maybe an IRC discussion can help ?

Hope that helps,

-Sebastien

On Nov 30, 2012, at 3:31 PM, Charles Moulliard ch0...@gmail.com wrote:

There is a wiki page here :
https://cwiki.apache.org/CLOUDSTACK/building-devcloud.html

On Fri, Nov 30, 2012 at 3:16 PM, James Martin jmar...@basho.com wrote:

Rohit,

- James

Regards.

From: James Martin [jmar...@basho.com]
Sent: Friday, November 30, 2012 1:10 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: back in the game, deploying to devcloud

The goal is to be able, from the cloudstack project root:

cd tools/devcloud
vagrant up
vagrant ssh

In order for this to work it requires a vagrant basebox, and a vagrant
xenbox. Currently in my fork these are built cleanly with veewee,
vagrant, and puppet via a shell script by simply:

cd tools/devcloud/deps
./boxer.sh -b all

And you end up with:

vagrant box list
devcloudbase (virtualbox)
devcloudbase-xen (virtualbox)

Once those vagrant boxes are completed you'd run,

cd ../
vagrant up
vagrant ssh

vagrant ssh
Welcome to Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-29-generic-pae i686)

and now you have an clean devcloud vagrant install. If you ever screw
up the system,
you simply:
vagrant destroy
vagrant up

to start fresh

I have all of that completed. I just want to be able to install a
build to this blank vm. It seems like I should follow these steps:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+devcloud+environment+setup

but I receive an error here:

mvn -P developer -pl developer,tools/devcloud -Ddeploydb
[INFO]

[jira] [Resolved] (CLOUDSTACK-572) SG Enabled Advanced Zone - Not able to deploy a VM in an account specific shared network.


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alena Prokharchyk resolved CLOUDSTACK-572.
--

Resolution: Fixed

Fixed with 1aa4ad6a3c5c051ff6fcb68e0bf2bd58c9ddedcc


 SG Enabled Advanced Zone - Not able to deploy a VM in an account specific 
 shared network.
 -

 Key: CLOUDSTACK-572
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-572
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.0.0
Reporter: Alena Prokharchyk
Assignee: Alena Prokharchyk
 Fix For: 4.1.0


 SG Enabled Advanced Zone - Not able to deploy a VM in an account specific 
 shared network.
 Tested with:
 [root@centos62mgmt management]# cloud-sccs
 Git Revision: 7ff2f872debb5446c1f1ee844791b76a4352818e
 Git URL: ssh://r...@git-cpp.citrix.com/var/lib/git/cloudstack-oss
 Set up:
 Advanced zone set up with SG enabled.
 Create an account.
 As this account , Deploy few Vms in the Zone wide shared SG enabled network.
 Create a account specific shared network for this account.
 Deploy a Vm in this network using the folloiwng api call:
 It fails.
 GET 
 command=deployVirtualMachinezoneId=80f6719f-8fcc-4c87-bf36-b955e9389353templateId=abd10db9-5903-469f-a509-ab41699c0160hypervisor=KVMserviceOfferingId=8178b836-4c8d-4dfe-9b19-e3931e7234a8networkIds=d8bf2c7c-7741-43bc-858f-085adbc4cca6displayname=testacctspecificname=testacctsepecificresponse=jsonsessionkey=Yc797M%2BFtASw4helMfW6gONcxw8%3D_=1354232543251
  431 Can specify only Direct Guest Account specific networks when deploy vm 
 in Security Group enabled
 mysql select acl_type , name,id,uuid,guest_type from networks;
 +--+-+-+--++
 | acl_type | name | id | uuid | guest_type |
 +--+-+-+--++
 | NULL | NULL | 200 | 2ddf7576-bda4-414d-adc3-f47df493fbee | NULL |
 | NULL | NULL | 201 | 7c1af3f2-19d8-489a-a64b-b68a5af9b1bf | NULL |
 | NULL | NULL | 202 | 9365f3d0-ac2f-44e1-bb10-4a4ad6b769c3 | NULL |
 | Domain | defaultGuestNetwork | 203 | a8617a98-da48-41c5-b3fd-f985833b934d | 
 Shared |
 | Account | test | 204 | d8bf2c7c-7741-43bc-858f-085adbc4cca6 | Shared |
 +--+-+-+--++
 5 rows in set (0.00 sec) 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-573) NPE at com.cloud.network.NetworkManagerImpl.networkOfferingIsConfiguredForExternalNetworking(NetworkManagerImpl.java:4345) when create network from the network off


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alena Prokharchyk resolved CLOUDSTACK-573.
--

Resolution: Fixed

Fixed with 7857b1f62ab905790e4dd96f6b19d7d67255b56c

 NPE at 
 com.cloud.network.NetworkManagerImpl.networkOfferingIsConfiguredForExternalNetworking(NetworkManagerImpl.java:4345)
  when create network from the network offering having NULL provider for the 
 service
 ---

 Key: CLOUDSTACK-573
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-573
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.0.0
Reporter: Alena Prokharchyk
Assignee: Alena Prokharchyk
Priority: Trivial
 Fix For: 4.1.0


 Steps to reproduce:
 1) Create network offering, pass service list, but don't pass the provider:
 http://localhost:8096/?command=createNetworkOfferingname=alena11displayText=alenatrafficType=GuestguestIpType=IsolatedsupportedServices=UserData
 We do allow having null provider in the network offering; later when network 
 is
 being created from this network offering, the default provider of the service
 on the physical network is being set for the service.
 2) Try to create the network from this network offering. It results in NPE, 
 because check for external device use is being done before services/providers 
 are finalized for the network:
 ERROR [cloud.api.ApiDispatcher] (catalina-exec-7:) Exception while executing 
 CreateNetworkCmd:
 java.lang.NullPointerException
 at 
 com.cloud.network.NetworkManagerImpl.networkOfferingIsConfiguredForExternalNetworking(NetworkManagerImpl.java:4345)
 at 
 com.cloud.network.NetworkManagerImpl.createGuestNetwork(NetworkManagerImpl.java:2666)
 at 
 com.cloud.utils.component.ComponentLocator$InterceptorDispatcher.intercept(ComponentLocator.java:1185)
 at 
 com.cloud.api.commands.CreateNetworkCmd.execute(CreateNetworkCmd.java:220)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:235)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:540)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:419)
 at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:300)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:59)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
 at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
 at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
 at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
 at 
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
 at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
 at 
 org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
 at 
 org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
 at 
 org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2260)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679) 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Review Request: S3-backed Secondary Storage