date:20140320

url: https://wiki.eclipse.org/Jetty/Feature/GZIP_Compression#Static_Content


On Thu, Mar 20, 2014 at 11:19 PM, John Kinsella  wrote:

>  Laszlo, can you reference any other open source projects that have
> similar solutions to this issue? Anything I've read states dynamic
> compression in tomcat/httpd/nginx does not add significant CPU overhead.
>
>  On Mar 20, 2014, at 12:53 PM, Laszlo Hornyak 
> wrote:
>
>
> ---
>
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12228/
> ---
>
> (Updated March 20, 2014, 7:53 p.m.)
>
>
>
> Review request for cloudstack, Brian Federle, Darren Shepherd, and
> Prasanna Santhanam.
>
>
> Changes
> ---
>
> spaces
>
>
> Repository: cloudstack-git
>
>
> Description
> ---
>
>
> CloudStack at first use downloads some 3.5 MB of css and javascript to the
> client. With a weak internet connection, this might take a long time. With
> gzip compression content can be compressed to 850 KB.
>
> This version of the patch uses a custom plugin to compress static
> resources, so that no dynamic compression is needed at runtime. When the
> static resource servlet notices that there is gzipped version of the
> resource and the client accepts gzipped content, then it is going to send
> the gziped version, while still respects http caching.
>
>
> Diffs (updated)
> -
>
>  client/WEB-INF/web.xml 1af38e1
>  client/pom.xml d8dbde7
>  server/src/com/cloud/servlet/StaticResourceServlet.java PRE-CREATION
>  server/test/com/cloud/servlet/StaticResourceServletTest.java PRE-CREATION
>
> Diff: https://reviews.apache.org/r/12228/diff/
>
>
> Testing
> ---
>
>
> yes, tested with firefox and chrome
>
>
> Thanks,
>
> Laszlo Hornyak
>
>
>  Stratosec  - Compliance as a Service
> o: 415.315.9385
> @johnlkinsella 
>
>


-- 

EOF

Re: Review Request 12228: static resource compression

Hi John,

Jetty gives this functionality by default without a filter/servlet, simply
it is not available in tomcat. I used this functionality a lot in jetty and
that plus the massive size of the UI gave me the idea.
My approach to the problem was motivated by that I don't like to see
anything wasted, but let's make a measurement and see what the impact is.
This is what could be interesting in comparison with dynamic compression:
- request/sec and average delay for static resoures in different sizes
- time taken by full page reload




On Thu, Mar 20, 2014 at 11:19 PM, John Kinsella  wrote:

>  Laszlo, can you reference any other open source projects that have
> similar solutions to this issue? Anything I've read states dynamic
> compression in tomcat/httpd/nginx does not add significant CPU overhead.
>
>  On Mar 20, 2014, at 12:53 PM, Laszlo Hornyak 
> wrote:
>
>
> ---
>
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12228/
> ---
>
> (Updated March 20, 2014, 7:53 p.m.)
>
>
>
> Review request for cloudstack, Brian Federle, Darren Shepherd, and
> Prasanna Santhanam.
>
>
> Changes
> ---
>
> spaces
>
>
> Repository: cloudstack-git
>
>
> Description
> ---
>
>
> CloudStack at first use downloads some 3.5 MB of css and javascript to the
> client. With a weak internet connection, this might take a long time. With
> gzip compression content can be compressed to 850 KB.
>
> This version of the patch uses a custom plugin to compress static
> resources, so that no dynamic compression is needed at runtime. When the
> static resource servlet notices that there is gzipped version of the
> resource and the client accepts gzipped content, then it is going to send
> the gziped version, while still respects http caching.
>
>
> Diffs (updated)
> -
>
>  client/WEB-INF/web.xml 1af38e1
>  client/pom.xml d8dbde7
>  server/src/com/cloud/servlet/StaticResourceServlet.java PRE-CREATION
>  server/test/com/cloud/servlet/StaticResourceServletTest.java PRE-CREATION
>
> Diff: https://reviews.apache.org/r/12228/diff/
>
>
> Testing
> ---
>
>
> yes, tested with firefox and chrome
>
>
> Thanks,
>
> Laszlo Hornyak
>
>
>  Stratosec  - Compliance as a Service
> o: 415.315.9385
> @johnlkinsella 
>
>


-- 

EOF

Re: [GitHub] cloudstack-docs-admin pull request: fixed internal links, tables, ...

2014-03-20 Thread David Nalley

So originally 'concepts' appeared in almost every document. I didn't
personally like that, so it's now in the root docs repo:
http://docs.cloudstack.apache.org/en/latest/concepts.html

That may not be the right location, but duplication of content didn't
seem appropriate anymore.

--David


On Thu, Mar 20, 2014 at 9:56 PM, Pierre-Luc Dion  wrote:
> I've update pretty much all internal links in the admin guide, although I
> haven't found following sections:
> - section #2 Cloud Infrastructure concept is missing ?
> - appendixes
>
> Should I copy the old appendix in the admin guide ?
>
> Thanks,
>
>
> Pierre-Luc Dion
> Architecte de Solution Cloud | Cloud Solutions Architect
> 514-447-3456, 1101
> - - -
>
> *CloudOps*420 rue Guy
> Montréal QC  H3J 1S6
> www.cloudops.com
> @CloudOps_
>
>
> On Thu, Mar 20, 2014 at 9:43 PM, pdion891  wrote:
>
>> GitHub user pdion891 opened a pull request:
>>
>> https://github.com/apache/cloudstack-docs-admin/pull/3
>>
>> fixed internal links, tables, CLOUDSTACK-5954
>>
>> Fixed internal links, forgotten tables and  update-ssl.png file :
>> CLOUDSTACK-5954
>> add default OS in .gitignore file.
>>
>> ```
>> $ sphinx-build -b html source build
>> Running Sphinx v1.2.2
>> loading pickled environment... done
>> building [html]: targets for 19 source files that are out of date
>> updating environment: 0 added, 0 changed, 0 removed
>> looking for now-outdated files... none found
>> preparing documents... done
>> writing output... [100%] virtual_machines
>> writing additional files... genindex search
>> copying images... [100%] _static/images/egress-firewall-rule.png
>> copying static files... done
>> copying extra files... done
>> dumping search index... done
>> dumping object inventory... done
>> build succeeded.
>> ```
>>
>> You can merge this pull request into a Git repository by running:
>>
>> $ git pull https://github.com/cloudops/cloudstack-docs-admin master
>>
>> Alternatively you can review and apply these changes as the patch at:
>>
>> https://github.com/apache/cloudstack-docs-admin/pull/3.patch
>>
>> To close this pull request, make a commit to your master/trunk branch
>> with (at least) the following in the commit message:
>>
>> This closes #3
>>
>> 
>> commit 6b2c8268f67328eaf2088166631dcd4d059521b0
>> Author: Pierre-Luc Dion 
>> Date:   2014-03-20T01:29:33Z
>>
>> fixed images links, tables, toctree
>>
>> commit 08e60ee04b10be2437bfd701e002787ab8dafe97
>> Author: Pierre-Luc Dion 
>> Date:   2014-03-21T01:30:33Z
>>
>> fixed internal links, tables, CLOUDSTACK-5954
>>
>> commit 0647b9740a15faf51cbb81894927271b611023bf
>> Author: Pierre-Luc Dion 
>> Date:   2014-03-21T01:41:26Z
>>
>> replaced â EURO\" by :
>>
>> 
>>
>>
>> ---
>> If your project is set up for it, you can reply to this email and have your
>> reply appear on GitHub as well. If your project does not have this feature
>> enabled and wishes so, or if the feature is enabled but not working, please
>> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
>> with INFRA.
>> ---
>>

Re: [GitHub] cloudstack-docs-admin pull request: fixed internal links, tables, ...

2014-03-20 Thread Pierre-Luc Dion

I've update pretty much all internal links in the admin guide, although I
haven't found following sections:
- section #2 Cloud Infrastructure concept is missing ?
- appendixes

Should I copy the old appendix in the admin guide ?

Thanks,


Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Thu, Mar 20, 2014 at 9:43 PM, pdion891  wrote:

> GitHub user pdion891 opened a pull request:
>
> https://github.com/apache/cloudstack-docs-admin/pull/3
>
> fixed internal links, tables, CLOUDSTACK-5954
>
> Fixed internal links, forgotten tables and  update-ssl.png file :
> CLOUDSTACK-5954
> add default OS in .gitignore file.
>
> ```
> $ sphinx-build -b html source build
> Running Sphinx v1.2.2
> loading pickled environment... done
> building [html]: targets for 19 source files that are out of date
> updating environment: 0 added, 0 changed, 0 removed
> looking for now-outdated files... none found
> preparing documents... done
> writing output... [100%] virtual_machines
> writing additional files... genindex search
> copying images... [100%] _static/images/egress-firewall-rule.png
> copying static files... done
> copying extra files... done
> dumping search index... done
> dumping object inventory... done
> build succeeded.
> ```
>
> You can merge this pull request into a Git repository by running:
>
> $ git pull https://github.com/cloudops/cloudstack-docs-admin master
>
> Alternatively you can review and apply these changes as the patch at:
>
> https://github.com/apache/cloudstack-docs-admin/pull/3.patch
>
> To close this pull request, make a commit to your master/trunk branch
> with (at least) the following in the commit message:
>
> This closes #3
>
> 
> commit 6b2c8268f67328eaf2088166631dcd4d059521b0
> Author: Pierre-Luc Dion 
> Date:   2014-03-20T01:29:33Z
>
> fixed images links, tables, toctree
>
> commit 08e60ee04b10be2437bfd701e002787ab8dafe97
> Author: Pierre-Luc Dion 
> Date:   2014-03-21T01:30:33Z
>
> fixed internal links, tables, CLOUDSTACK-5954
>
> commit 0647b9740a15faf51cbb81894927271b611023bf
> Author: Pierre-Luc Dion 
> Date:   2014-03-21T01:41:26Z
>
> replaced â EURO\" by :
>
> 
>
>
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> with INFRA.
> ---
>

[GitHub] cloudstack-docs-admin pull request: fixed internal links, tables, ...

2014-03-20 Thread pdion891

GitHub user pdion891 opened a pull request:

https://github.com/apache/cloudstack-docs-admin/pull/3

fixed internal links, tables, CLOUDSTACK-5954

Fixed internal links, forgotten tables and  update-ssl.png file : 
CLOUDSTACK-5954
add default OS in .gitignore file.

```
$ sphinx-build -b html source build
Running Sphinx v1.2.2
loading pickled environment... done
building [html]: targets for 19 source files that are out of date
updating environment: 0 added, 0 changed, 0 removed
looking for now-outdated files... none found
preparing documents... done
writing output... [100%] virtual_machines   

 
writing additional files... genindex search
copying images... [100%] _static/images/egress-firewall-rule.png

 
copying static files... done
copying extra files... done
dumping search index... done
dumping object inventory... done
build succeeded.
```

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cloudops/cloudstack-docs-admin master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack-docs-admin/pull/3.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3


commit 6b2c8268f67328eaf2088166631dcd4d059521b0
Author: Pierre-Luc Dion 
Date:   2014-03-20T01:29:33Z

fixed images links, tables, toctree

commit 08e60ee04b10be2437bfd701e002787ab8dafe97
Author: Pierre-Luc Dion 
Date:   2014-03-21T01:30:33Z

fixed internal links, tables, CLOUDSTACK-5954

commit 0647b9740a15faf51cbb81894927271b611023bf
Author: Pierre-Luc Dion 
Date:   2014-03-21T01:41:26Z

replaced Ã¢â¬\â by :




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

RE: [VOTE] Apache CloudStack 4.3.0 (ninth round) - CLOUDSTACK-6266 Missing "Accounts" menu text as well as the entire menu itself

Tanner,

I attached two screenshots to this bug:
https://issues.apache.org/jira/i#browse/CLOUDSTACK-6266

Jessica

-Original Message-
From: Jessica Wang [mailto:jessica.w...@citrix.com] 
Sent: Thursday, March 20, 2014 5:04 PM
To: Animesh Chaturvedi; dev@cloudstack.apache.org; arkan...@gmail.com
Subject: RE: [VOTE] Apache CloudStack 4.3.0 (ninth round) - CLOUDSTACK-6266 
Missing "Accounts" menu text as well as the entire menu itself

Tanner,

I just got latest code from 4.3 branch and do not see this issue.
"Accounts" menu is not missing.

Could you please clear your browser cache and try again?

Jessica

-Original Message-
From: Animesh Chaturvedi 
Sent: Thursday, March 20, 2014 4:55 PM
To: dev@cloudstack.apache.org
Cc: Jessica Wang
Subject: RE: [VOTE] Apache CloudStack 4.3.0 (ninth round)

Can you clear up browser cache and try again?

> -Original Message-
> From: Animesh Chaturvedi
> Sent: Thursday, March 20, 2014 4:54 PM
> To: dev@cloudstack.apache.org
> Cc: Jessica Wang
> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (ninth round)
> 
> That's weird but I do not see the issue in my setup. Copying jessicaW
> 
> > -Original Message-
> > From: Tanner Danzey [mailto:arkan...@gmail.com]
> > Sent: Thursday, March 20, 2014 4:40 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Apache CloudStack 4.3.0 (ninth round)
> >
> > -1 see https://issues.apache.org/jira/browse/CLOUDSTACK-6266 (If it is
> > something easily fixed I will happily rescind my -1)
> >
> >
> > On Thu, Mar 20, 2014 at 4:32 PM, Edison Su  wrote:
> >
> > > +1(binding) After fixed the serious bugs in security group in the
> > > +last
> > > round.
> > >
> > > > -Original Message-
> > > > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > > > Sent: Tuesday, March 18, 2014 12:06 PM
> > > > To: dev@cloudstack.apache.org
> > > > Subject: [VOTE] Apache CloudStack 4.3.0 (ninth round)
> > > >
> > > >
> > > >
> > > >
> > > > Hi All,
> > > >
> > > >
> > > >
> > > > I've created a 4.3.0 release, with the following artifacts up for
> > > > a
> > > >
> > > > vote:
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Git Branch and Commit SH:
> > > >
> > > > https://git-wip-
> > > > us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4
> > > > .3
> > > > Commit:  0810029f274878eca8fd74b44ab1117054e929a5
> > > >
> > > >
> > > > List of changes:
> > > >
> > > > New Features in 4.3:
> > > https://issues.apache.org/jira/issues/?filter=12325248
> > > >
> > > > Improvement in 4.3:
> > > https://issues.apache.org/jira/issues/?filter=12325249
> > > >
> > > > Issues fixed in 4.3
> > > https://issues.apache.org/jira/issues/?filter=12326161
> > > >
> > > > Known Issues in 4.3:
> > > https://issues.apache.org/jira/issues/?filter=12326162
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Source release (checksums and signatures are available at the same
> > > >
> > > > location):
> > > >
> > > > https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
> > > >
> > > >
> > > >
> > > > PGP release keys (signed using 94BE0D7C):
> > > >
> > > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> > > >
> > > >
> > > >
> > > > Testing instructions are here:
> > > >
> > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+tes
> > > > t+
> > > > pr
> > > > ocedure
> > > >
> > > >
> > > >
> > > > Vote will be open for 72 hours (Friday 3/21 12:05 PM PST)
> > > >
> > > >
> > > >
> > > > For sanity in tallying the vote, can PMC members please be sure to
> > > indicate
> > > > "(binding)" with their vote?
> > > >
> > > >
> > > >
> > > > [ ] +1  approve
> > > >
> > > > [ ] +0  no opinion
> > > >
> > > > [ ] -1  disapprove (and reason why)
> > > >
> > > >
> > > >
> > > > Thanks
> > > >
> > > > Animesh
> > > >
> > >
> > >
> >
> >
> > --
> > *Tanner Danzey*
> > Systems Engineer
> > Northstar Technology Group
> > arkan...@gmail.com / tanner.dan...@northstar-tg.com
> > (701) 237-9096 x7122

RE: [VOTE] Apache CloudStack 4.3.0 (ninth round) - CLOUDSTACK-6266 Missing "Accounts" menu text as well as the entire menu itself

Tanner,

I just got latest code from 4.3 branch and do not see this issue.
"Accounts" menu is not missing.

Could you please clear your browser cache and try again?

Jessica

-Original Message-
From: Animesh Chaturvedi 
Sent: Thursday, March 20, 2014 4:55 PM
To: dev@cloudstack.apache.org
Cc: Jessica Wang
Subject: RE: [VOTE] Apache CloudStack 4.3.0 (ninth round)

Can you clear up browser cache and try again?

> -Original Message-
> From: Animesh Chaturvedi
> Sent: Thursday, March 20, 2014 4:54 PM
> To: dev@cloudstack.apache.org
> Cc: Jessica Wang
> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (ninth round)
> 
> That's weird but I do not see the issue in my setup. Copying jessicaW
> 
> > -Original Message-
> > From: Tanner Danzey [mailto:arkan...@gmail.com]
> > Sent: Thursday, March 20, 2014 4:40 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Apache CloudStack 4.3.0 (ninth round)
> >
> > -1 see https://issues.apache.org/jira/browse/CLOUDSTACK-6266 (If it is
> > something easily fixed I will happily rescind my -1)
> >
> >
> > On Thu, Mar 20, 2014 at 4:32 PM, Edison Su  wrote:
> >
> > > +1(binding) After fixed the serious bugs in security group in the
> > > +last
> > > round.
> > >
> > > > -Original Message-
> > > > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > > > Sent: Tuesday, March 18, 2014 12:06 PM
> > > > To: dev@cloudstack.apache.org
> > > > Subject: [VOTE] Apache CloudStack 4.3.0 (ninth round)
> > > >
> > > >
> > > >
> > > >
> > > > Hi All,
> > > >
> > > >
> > > >
> > > > I've created a 4.3.0 release, with the following artifacts up for
> > > > a
> > > >
> > > > vote:
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Git Branch and Commit SH:
> > > >
> > > > https://git-wip-
> > > > us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4
> > > > .3
> > > > Commit:  0810029f274878eca8fd74b44ab1117054e929a5
> > > >
> > > >
> > > > List of changes:
> > > >
> > > > New Features in 4.3:
> > > https://issues.apache.org/jira/issues/?filter=12325248
> > > >
> > > > Improvement in 4.3:
> > > https://issues.apache.org/jira/issues/?filter=12325249
> > > >
> > > > Issues fixed in 4.3
> > > https://issues.apache.org/jira/issues/?filter=12326161
> > > >
> > > > Known Issues in 4.3:
> > > https://issues.apache.org/jira/issues/?filter=12326162
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Source release (checksums and signatures are available at the same
> > > >
> > > > location):
> > > >
> > > > https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
> > > >
> > > >
> > > >
> > > > PGP release keys (signed using 94BE0D7C):
> > > >
> > > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> > > >
> > > >
> > > >
> > > > Testing instructions are here:
> > > >
> > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+tes
> > > > t+
> > > > pr
> > > > ocedure
> > > >
> > > >
> > > >
> > > > Vote will be open for 72 hours (Friday 3/21 12:05 PM PST)
> > > >
> > > >
> > > >
> > > > For sanity in tallying the vote, can PMC members please be sure to
> > > indicate
> > > > "(binding)" with their vote?
> > > >
> > > >
> > > >
> > > > [ ] +1  approve
> > > >
> > > > [ ] +0  no opinion
> > > >
> > > > [ ] -1  disapprove (and reason why)
> > > >
> > > >
> > > >
> > > > Thanks
> > > >
> > > > Animesh
> > > >
> > >
> > >
> >
> >
> > --
> > *Tanner Danzey*
> > Systems Engineer
> > Northstar Technology Group
> > arkan...@gmail.com / tanner.dan...@northstar-tg.com
> > (701) 237-9096 x7122

RE: [VOTE] Apache CloudStack 4.3.0 (ninth round)

Can you clear up browser cache and try again?

> -Original Message-
> From: Animesh Chaturvedi
> Sent: Thursday, March 20, 2014 4:54 PM
> To: dev@cloudstack.apache.org
> Cc: Jessica Wang
> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (ninth round)
> 
> That's weird but I do not see the issue in my setup. Copying jessicaW
> 
> > -Original Message-
> > From: Tanner Danzey [mailto:arkan...@gmail.com]
> > Sent: Thursday, March 20, 2014 4:40 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Apache CloudStack 4.3.0 (ninth round)
> >
> > -1 see https://issues.apache.org/jira/browse/CLOUDSTACK-6266 (If it is
> > something easily fixed I will happily rescind my -1)
> >
> >
> > On Thu, Mar 20, 2014 at 4:32 PM, Edison Su  wrote:
> >
> > > +1(binding) After fixed the serious bugs in security group in the
> > > +last
> > > round.
> > >
> > > > -Original Message-
> > > > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > > > Sent: Tuesday, March 18, 2014 12:06 PM
> > > > To: dev@cloudstack.apache.org
> > > > Subject: [VOTE] Apache CloudStack 4.3.0 (ninth round)
> > > >
> > > >
> > > >
> > > >
> > > > Hi All,
> > > >
> > > >
> > > >
> > > > I've created a 4.3.0 release, with the following artifacts up for
> > > > a
> > > >
> > > > vote:
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Git Branch and Commit SH:
> > > >
> > > > https://git-wip-
> > > > us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4
> > > > .3
> > > > Commit:  0810029f274878eca8fd74b44ab1117054e929a5
> > > >
> > > >
> > > > List of changes:
> > > >
> > > > New Features in 4.3:
> > > https://issues.apache.org/jira/issues/?filter=12325248
> > > >
> > > > Improvement in 4.3:
> > > https://issues.apache.org/jira/issues/?filter=12325249
> > > >
> > > > Issues fixed in 4.3
> > > https://issues.apache.org/jira/issues/?filter=12326161
> > > >
> > > > Known Issues in 4.3:
> > > https://issues.apache.org/jira/issues/?filter=12326162
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Source release (checksums and signatures are available at the same
> > > >
> > > > location):
> > > >
> > > > https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
> > > >
> > > >
> > > >
> > > > PGP release keys (signed using 94BE0D7C):
> > > >
> > > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> > > >
> > > >
> > > >
> > > > Testing instructions are here:
> > > >
> > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+tes
> > > > t+
> > > > pr
> > > > ocedure
> > > >
> > > >
> > > >
> > > > Vote will be open for 72 hours (Friday 3/21 12:05 PM PST)
> > > >
> > > >
> > > >
> > > > For sanity in tallying the vote, can PMC members please be sure to
> > > indicate
> > > > "(binding)" with their vote?
> > > >
> > > >
> > > >
> > > > [ ] +1  approve
> > > >
> > > > [ ] +0  no opinion
> > > >
> > > > [ ] -1  disapprove (and reason why)
> > > >
> > > >
> > > >
> > > > Thanks
> > > >
> > > > Animesh
> > > >
> > >
> > >
> >
> >
> > --
> > *Tanner Danzey*
> > Systems Engineer
> > Northstar Technology Group
> > arkan...@gmail.com / tanner.dan...@northstar-tg.com
> > (701) 237-9096 x7122

RE: [VOTE] Apache CloudStack 4.3.0 (ninth round)

That's weird but I do not see the issue in my setup. Copying jessicaW

> -Original Message-
> From: Tanner Danzey [mailto:arkan...@gmail.com]
> Sent: Thursday, March 20, 2014 4:40 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache CloudStack 4.3.0 (ninth round)
> 
> -1 see https://issues.apache.org/jira/browse/CLOUDSTACK-6266 (If it is
> something easily fixed I will happily rescind my -1)
> 
> 
> On Thu, Mar 20, 2014 at 4:32 PM, Edison Su  wrote:
> 
> > +1(binding) After fixed the serious bugs in security group in the last
> > round.
> >
> > > -Original Message-
> > > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > > Sent: Tuesday, March 18, 2014 12:06 PM
> > > To: dev@cloudstack.apache.org
> > > Subject: [VOTE] Apache CloudStack 4.3.0 (ninth round)
> > >
> > >
> > >
> > >
> > > Hi All,
> > >
> > >
> > >
> > > I've created a 4.3.0 release, with the following artifacts up for a
> > >
> > > vote:
> > >
> > >
> > >
> > >
> > >
> > > Git Branch and Commit SH:
> > >
> > > https://git-wip-
> > > us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
> > > Commit:  0810029f274878eca8fd74b44ab1117054e929a5
> > >
> > >
> > > List of changes:
> > >
> > > New Features in 4.3:
> > https://issues.apache.org/jira/issues/?filter=12325248
> > >
> > > Improvement in 4.3:
> > https://issues.apache.org/jira/issues/?filter=12325249
> > >
> > > Issues fixed in 4.3
> > https://issues.apache.org/jira/issues/?filter=12326161
> > >
> > > Known Issues in 4.3:
> > https://issues.apache.org/jira/issues/?filter=12326162
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Source release (checksums and signatures are available at the same
> > >
> > > location):
> > >
> > > https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
> > >
> > >
> > >
> > > PGP release keys (signed using 94BE0D7C):
> > >
> > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> > >
> > >
> > >
> > > Testing instructions are here:
> > >
> > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+
> > > pr
> > > ocedure
> > >
> > >
> > >
> > > Vote will be open for 72 hours (Friday 3/21 12:05 PM PST)
> > >
> > >
> > >
> > > For sanity in tallying the vote, can PMC members please be sure to
> > indicate
> > > "(binding)" with their vote?
> > >
> > >
> > >
> > > [ ] +1  approve
> > >
> > > [ ] +0  no opinion
> > >
> > > [ ] -1  disapprove (and reason why)
> > >
> > >
> > >
> > > Thanks
> > >
> > > Animesh
> > >
> >
> >
> 
> 
> --
> *Tanner Danzey*
> Systems Engineer
> Northstar Technology Group
> arkan...@gmail.com / tanner.dan...@northstar-tg.com
> (701) 237-9096 x7122

Re: [ACS4.4] Are tests still failing for people?

Thanks for reverting on master, too - I was just in the process of doing
that. :)


On Thu, Mar 20, 2014 at 5:39 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> OK - thanks! I'll look into those tests now.
>
>
> On Thu, Mar 20, 2014 at 5:38 PM, Min Chen  wrote:
>
>>  To revert a commit, you can just do:
>>  git revert 
>> git commit
>>
>>  Thanks
>> -min
>>
>>   From: Mike Tutkowski 
>> Date: Thursday, March 20, 2014 4:37 PM
>> To: "dev@cloudstack.apache.org" 
>> Cc: Min Chen 
>>
>> Subject: Re: [ACS4.4] Are tests still failing for people?
>>
>>   It looks like you just literally changed the code (as opposed to force
>> removed the commit). Is that accurate?
>>
>>
>> On Thu, Mar 20, 2014 at 5:35 PM, Jessica Wang wrote:
>>
>>> Min,
>>>
>>> Thanks a lot!!!
>>> (The testing failure is also blocking me)
>>>
>>> Jessica
>>>
>>> -Original Message-
>>> From: Min Chen [mailto:min.c...@citrix.com]
>>> Sent: Thursday, March 20, 2014 4:31 PM
>>> To: dev@cloudstack.apache.org
>>> Subject: Re: [ACS4.4] Are tests still failing for people?
>>>
>>> I am reverting it for you now along with my another fix to be checked in.
>>>
>>> Thanks
>>> -min
>>>
>>> On 3/20/14 4:25 PM, "Mike Tutkowski" 
>>> wrote:
>>>
>>> >For example, I can't seem to force the branch back to a previous commit.
>>> >
>>> >
>>> >On Thu, Mar 20, 2014 at 5:21 PM, Mike Tutkowski <
>>> >mike.tutkow...@solidfire.com> wrote:
>>> >
>>> >> Hey Min,
>>> >>
>>> >> What is our standard way of reverting a commit?
>>> >>
>>> >> I have ways of doing this locally, but have never done it on a remote
>>> >>repo.
>>> >>
>>> >> Thanks!
>>> >>
>>> >>
>>> >> On Thu, Mar 20, 2014 at 5:19 PM, Mike Tutkowski <
>>> >> mike.tutkow...@solidfire.com> wrote:
>>> >>
>>> >>> Sure, I'll look into that. Thanks
>>> >>>
>>> >>>
>>> >>> On Thu, Mar 20, 2014 at 5:16 PM, Min Chen 
>>> wrote:
>>> >>>
>>>  Mike, with your latest commit
>>> 7a7d9cff0d5bb40284506faa6e34138f97a12428 on
>>>  4.4, test failed in cloud-server:
>>> 
>>>  Tests in error:
>>>    testRestoreVMF2(com.cloud.vm.UserVmManagerTest)
>>>    testRestoreVMF3(com.cloud.vm.UserVmManagerTest)
>>>    testRestoreVMF4(com.cloud.vm.UserVmManagerTest)
>>>    testRestoreVMF5(com.cloud.vm.UserVmManagerTest)
>>> 
>>> 
>>>  Before getting your commit, I am able to build 4.4 successfully. Can
>>> you
>>>  revert your change and fix the failure then commit again?
>>> 
>>>  Thanks
>>>  -min
>>> 
>>> 
>>>  On 3/20/14 4:11 PM, "Mike Tutkowski" 
>>>  wrote:
>>> 
>>>  >Hi,
>>>  >
>>>  >I think there was a discussion earlier about this, but I was
>>> wondering
>>>  if
>>>  >others were seeing test failures in 4.4 when running mvn -P
>>>  >developer,systemvm clean install?
>>>  >
>>>  >I have to add -D skipTests=true to get the build to finish.
>>>  >
>>>  >Thanks,
>>>  >
>>>  >--
>>>  >*Mike Tutkowski*
>>>  >*Senior CloudStack Developer, SolidFire Inc.*
>>>  >e: mike.tutkow...@solidfire.com
>>>  >o: 303.746.7302
>>>  >Advancing the way the world uses the
>>>  >cloud
>>>  >*(tm)*
>>> 
>>> 
>>> >>>
>>> >>>
>>> >>> --
>>> >>> *Mike Tutkowski*
>>> >>>  *Senior CloudStack Developer, SolidFire Inc.*
>>> >>> e: mike.tutkow...@solidfire.com
>>> >>> o: 303.746.7302
>>> >>> Advancing the way the world uses the
>>> >>>cloud
>>> >>> *(tm)*
>>> >>>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> *Mike Tutkowski*
>>> >> *Senior CloudStack Developer, SolidFire Inc.*
>>> >> e: mike.tutkow...@solidfire.com
>>> >> o: 303.746.7302
>>> >> Advancing the way the world uses the
>>> >>cloud
>>> >> *(tm)*
>>> >>
>>> >
>>> >
>>> >
>>> >--
>>> >*Mike Tutkowski*
>>> >*Senior CloudStack Developer, SolidFire Inc.*
>>> >e: mike.tutkow...@solidfire.com
>>> >o: 303.746.7302
>>> >Advancing the way the world uses the
>>> >cloud
>>> >*(tm)*
>>>
>>>
>>
>>
>>  --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkow...@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the 
>> cloud
>> *(tm)*
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the 
> cloud
> *(tm)*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

Re: [VOTE] Apache CloudStack 4.3.0 (ninth round)

2014-03-20 Thread Tanner Danzey

-1 see https://issues.apache.org/jira/browse/CLOUDSTACK-6266 (If it is
something easily fixed I will happily rescind my -1)


On Thu, Mar 20, 2014 at 4:32 PM, Edison Su  wrote:

> +1(binding) After fixed the serious bugs in security group in the last
> round.
>
> > -Original Message-
> > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > Sent: Tuesday, March 18, 2014 12:06 PM
> > To: dev@cloudstack.apache.org
> > Subject: [VOTE] Apache CloudStack 4.3.0 (ninth round)
> >
> >
> >
> >
> > Hi All,
> >
> >
> >
> > I've created a 4.3.0 release, with the following artifacts up for a
> >
> > vote:
> >
> >
> >
> >
> >
> > Git Branch and Commit SH:
> >
> > https://git-wip-
> > us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
> > Commit:  0810029f274878eca8fd74b44ab1117054e929a5
> >
> >
> > List of changes:
> >
> > New Features in 4.3:
> https://issues.apache.org/jira/issues/?filter=12325248
> >
> > Improvement in 4.3:
> https://issues.apache.org/jira/issues/?filter=12325249
> >
> > Issues fixed in 4.3
> https://issues.apache.org/jira/issues/?filter=12326161
> >
> > Known Issues in 4.3:
> https://issues.apache.org/jira/issues/?filter=12326162
> >
> >
> >
> >
> >
> >
> >
> > Source release (checksums and signatures are available at the same
> >
> > location):
> >
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
> >
> >
> >
> > PGP release keys (signed using 94BE0D7C):
> >
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> >
> >
> > Testing instructions are here:
> >
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+pr
> > ocedure
> >
> >
> >
> > Vote will be open for 72 hours (Friday 3/21 12:05 PM PST)
> >
> >
> >
> > For sanity in tallying the vote, can PMC members please be sure to
> indicate
> > "(binding)" with their vote?
> >
> >
> >
> > [ ] +1  approve
> >
> > [ ] +0  no opinion
> >
> > [ ] -1  disapprove (and reason why)
> >
> >
> >
> > Thanks
> >
> > Animesh
> >
>
>


-- 
*Tanner Danzey*
Systems Engineer
Northstar Technology Group
arkan...@gmail.com / tanner.dan...@northstar-tg.com
(701) 237-9096 x7122

Re: [ACS4.4] Are tests still failing for people?

OK - thanks! I'll look into those tests now.


On Thu, Mar 20, 2014 at 5:38 PM, Min Chen  wrote:

>  To revert a commit, you can just do:
>  git revert 
> git commit
>
>  Thanks
> -min
>
>   From: Mike Tutkowski 
> Date: Thursday, March 20, 2014 4:37 PM
> To: "dev@cloudstack.apache.org" 
> Cc: Min Chen 
>
> Subject: Re: [ACS4.4] Are tests still failing for people?
>
>   It looks like you just literally changed the code (as opposed to force
> removed the commit). Is that accurate?
>
>
> On Thu, Mar 20, 2014 at 5:35 PM, Jessica Wang wrote:
>
>> Min,
>>
>> Thanks a lot!!!
>> (The testing failure is also blocking me)
>>
>> Jessica
>>
>> -Original Message-
>> From: Min Chen [mailto:min.c...@citrix.com]
>> Sent: Thursday, March 20, 2014 4:31 PM
>> To: dev@cloudstack.apache.org
>> Subject: Re: [ACS4.4] Are tests still failing for people?
>>
>> I am reverting it for you now along with my another fix to be checked in.
>>
>> Thanks
>> -min
>>
>> On 3/20/14 4:25 PM, "Mike Tutkowski" 
>> wrote:
>>
>> >For example, I can't seem to force the branch back to a previous commit.
>> >
>> >
>> >On Thu, Mar 20, 2014 at 5:21 PM, Mike Tutkowski <
>> >mike.tutkow...@solidfire.com> wrote:
>> >
>> >> Hey Min,
>> >>
>> >> What is our standard way of reverting a commit?
>> >>
>> >> I have ways of doing this locally, but have never done it on a remote
>> >>repo.
>> >>
>> >> Thanks!
>> >>
>> >>
>> >> On Thu, Mar 20, 2014 at 5:19 PM, Mike Tutkowski <
>> >> mike.tutkow...@solidfire.com> wrote:
>> >>
>> >>> Sure, I'll look into that. Thanks
>> >>>
>> >>>
>> >>> On Thu, Mar 20, 2014 at 5:16 PM, Min Chen 
>> wrote:
>> >>>
>>  Mike, with your latest commit
>> 7a7d9cff0d5bb40284506faa6e34138f97a12428 on
>>  4.4, test failed in cloud-server:
>> 
>>  Tests in error:
>>    testRestoreVMF2(com.cloud.vm.UserVmManagerTest)
>>    testRestoreVMF3(com.cloud.vm.UserVmManagerTest)
>>    testRestoreVMF4(com.cloud.vm.UserVmManagerTest)
>>    testRestoreVMF5(com.cloud.vm.UserVmManagerTest)
>> 
>> 
>>  Before getting your commit, I am able to build 4.4 successfully. Can
>> you
>>  revert your change and fix the failure then commit again?
>> 
>>  Thanks
>>  -min
>> 
>> 
>>  On 3/20/14 4:11 PM, "Mike Tutkowski" 
>>  wrote:
>> 
>>  >Hi,
>>  >
>>  >I think there was a discussion earlier about this, but I was
>> wondering
>>  if
>>  >others were seeing test failures in 4.4 when running mvn -P
>>  >developer,systemvm clean install?
>>  >
>>  >I have to add -D skipTests=true to get the build to finish.
>>  >
>>  >Thanks,
>>  >
>>  >--
>>  >*Mike Tutkowski*
>>  >*Senior CloudStack Developer, SolidFire Inc.*
>>  >e: mike.tutkow...@solidfire.com
>>  >o: 303.746.7302
>>  >Advancing the way the world uses the
>>  >cloud
>>  >*(tm)*
>> 
>> 
>> >>>
>> >>>
>> >>> --
>> >>> *Mike Tutkowski*
>> >>>  *Senior CloudStack Developer, SolidFire Inc.*
>> >>> e: mike.tutkow...@solidfire.com
>> >>> o: 303.746.7302
>> >>> Advancing the way the world uses the
>> >>>cloud
>> >>> *(tm)*
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> *Mike Tutkowski*
>> >> *Senior CloudStack Developer, SolidFire Inc.*
>> >> e: mike.tutkow...@solidfire.com
>> >> o: 303.746.7302
>> >> Advancing the way the world uses the
>> >>cloud
>> >> *(tm)*
>> >>
>> >
>> >
>> >
>> >--
>> >*Mike Tutkowski*
>> >*Senior CloudStack Developer, SolidFire Inc.*
>> >e: mike.tutkow...@solidfire.com
>> >o: 303.746.7302
>> >Advancing the way the world uses the
>> >cloud
>> >*(tm)*
>>
>>
>
>
>  --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the 
> cloud
> *(tm)*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

Re: [ACS4.4] Are tests still failing for people?

To revert a commit, you can just do:
git revert 
git commit

Thanks
-min

From: Mike Tutkowski 
mailto:mike.tutkow...@solidfire.com>>
Date: Thursday, March 20, 2014 4:37 PM
To: "dev@cloudstack.apache.org" 
mailto:dev@cloudstack.apache.org>>
Cc: Min Chen mailto:min.c...@citrix.com>>
Subject: Re: [ACS4.4] Are tests still failing for people?

It looks like you just literally changed the code (as opposed to force removed 
the commit). Is that accurate?


On Thu, Mar 20, 2014 at 5:35 PM, Jessica Wang 
mailto:jessica.w...@citrix.com>> wrote:
Min,

Thanks a lot!!!
(The testing failure is also blocking me)

Jessica

-Original Message-
From: Min Chen [mailto:min.c...@citrix.com]
Sent: Thursday, March 20, 2014 4:31 PM
To: dev@cloudstack.apache.org
Subject: Re: [ACS4.4] Are tests still failing for people?

I am reverting it for you now along with my another fix to be checked in.

Thanks
-min

On 3/20/14 4:25 PM, "Mike Tutkowski" 
mailto:mike.tutkow...@solidfire.com>> wrote:

>For example, I can't seem to force the branch back to a previous commit.
>
>
>On Thu, Mar 20, 2014 at 5:21 PM, Mike Tutkowski <
>mike.tutkow...@solidfire.com> wrote:
>
>> Hey Min,
>>
>> What is our standard way of reverting a commit?
>>
>> I have ways of doing this locally, but have never done it on a remote
>>repo.
>>
>> Thanks!
>>
>>
>> On Thu, Mar 20, 2014 at 5:19 PM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>>> Sure, I'll look into that. Thanks
>>>
>>>
>>> On Thu, Mar 20, 2014 at 5:16 PM, Min Chen 
>>> mailto:min.c...@citrix.com>> wrote:
>>>
 Mike, with your latest commit
7a7d9cff0d5bb40284506faa6e34138f97a12428 on
 4.4, test failed in cloud-server:

 Tests in error:
   testRestoreVMF2(com.cloud.vm.UserVmManagerTest)
   testRestoreVMF3(com.cloud.vm.UserVmManagerTest)
   testRestoreVMF4(com.cloud.vm.UserVmManagerTest)
   testRestoreVMF5(com.cloud.vm.UserVmManagerTest)


 Before getting your commit, I am able to build 4.4 successfully. Can
you
 revert your change and fix the failure then commit again?

 Thanks
 -min


 On 3/20/14 4:11 PM, "Mike Tutkowski" 
 mailto:mike.tutkow...@solidfire.com>>
 wrote:

 >Hi,
 >
 >I think there was a discussion earlier about this, but I was
wondering
 if
 >others were seeing test failures in 4.4 when running mvn -P
 >developer,systemvm clean install?
 >
 >I have to add -D skipTests=true to get the build to finish.
 >
 >Thanks,
 >
 >--
 >*Mike Tutkowski*
 >*Senior CloudStack Developer, SolidFire Inc.*
 >e: mike.tutkow...@solidfire.com
 >o: 303.746.7302
 >Advancing the way the world uses the
 >cloud
 >*(tm)*


>>>
>>>
>>> --
>>> *Mike Tutkowski*
>>>  *Senior CloudStack Developer, SolidFire Inc.*
>>> e: mike.tutkow...@solidfire.com
>>> o: 303.746.7302
>>> Advancing the way the world uses the
>>>cloud
>>> *(tm)*
>>>
>>
>>
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkow...@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the
>>cloud
>> *(tm)*
>>
>
>
>
>--
>*Mike Tutkowski*
>*Senior CloudStack Developer, SolidFire Inc.*
>e: mike.tutkow...@solidfire.com
>o: 303.746.7302
>Advancing the way the world uses the
>cloud
>*(tm)*




--
Mike Tutkowski
Senior CloudStack Developer, SolidFire Inc.
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the 
cloud™

Re: [ACS4.4] Are tests still failing for people?

I have reverted it on 4.4. To revert a commit, you can just do:
 
git revert 
git commit 

Thanks
-min

On 3/20/14 4:25 PM, "Mike Tutkowski"  wrote:

>For example, I can't seem to force the branch back to a previous commit.
>
>
>On Thu, Mar 20, 2014 at 5:21 PM, Mike Tutkowski <
>mike.tutkow...@solidfire.com> wrote:
>
>> Hey Min,
>>
>> What is our standard way of reverting a commit?
>>
>> I have ways of doing this locally, but have never done it on a remote
>>repo.
>>
>> Thanks!
>>
>>
>> On Thu, Mar 20, 2014 at 5:19 PM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>>> Sure, I'll look into that. Thanks
>>>
>>>
>>> On Thu, Mar 20, 2014 at 5:16 PM, Min Chen  wrote:
>>>
 Mike, with your latest commit
7a7d9cff0d5bb40284506faa6e34138f97a12428 on
 4.4, test failed in cloud-server:

 Tests in error:
   testRestoreVMF2(com.cloud.vm.UserVmManagerTest)
   testRestoreVMF3(com.cloud.vm.UserVmManagerTest)
   testRestoreVMF4(com.cloud.vm.UserVmManagerTest)
   testRestoreVMF5(com.cloud.vm.UserVmManagerTest)


 Before getting your commit, I am able to build 4.4 successfully. Can
you
 revert your change and fix the failure then commit again?

 Thanks
 -min


 On 3/20/14 4:11 PM, "Mike Tutkowski" 
 wrote:

 >Hi,
 >
 >I think there was a discussion earlier about this, but I was
wondering
 if
 >others were seeing test failures in 4.4 when running mvn -P
 >developer,systemvm clean install?
 >
 >I have to add -D skipTests=true to get the build to finish.
 >
 >Thanks,
 >
 >--
 >*Mike Tutkowski*
 >*Senior CloudStack Developer, SolidFire Inc.*
 >e: mike.tutkow...@solidfire.com
 >o: 303.746.7302
 >Advancing the way the world uses the
 >cloud
 >*(tm)*


>>>
>>>
>>> --
>>> *Mike Tutkowski*
>>>  *Senior CloudStack Developer, SolidFire Inc.*
>>> e: mike.tutkow...@solidfire.com
>>> o: 303.746.7302
>>> Advancing the way the world uses the
>>>cloud
>>> *(tm)*
>>>
>>
>>
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkow...@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the
>>cloud
>> *(tm)*
>>
>
>
>
>-- 
>*Mike Tutkowski*
>*Senior CloudStack Developer, SolidFire Inc.*
>e: mike.tutkow...@solidfire.com
>o: 303.746.7302
>Advancing the way the world uses the
>cloud
>*(tm)*

Re: [ACS4.4] Are tests still failing for people?

It looks like you just literally changed the code (as opposed to force
removed the commit). Is that accurate?


On Thu, Mar 20, 2014 at 5:35 PM, Jessica Wang wrote:

> Min,
>
> Thanks a lot!!!
> (The testing failure is also blocking me)
>
> Jessica
>
> -Original Message-
> From: Min Chen [mailto:min.c...@citrix.com]
> Sent: Thursday, March 20, 2014 4:31 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [ACS4.4] Are tests still failing for people?
>
> I am reverting it for you now along with my another fix to be checked in.
>
> Thanks
> -min
>
> On 3/20/14 4:25 PM, "Mike Tutkowski"  wrote:
>
> >For example, I can't seem to force the branch back to a previous commit.
> >
> >
> >On Thu, Mar 20, 2014 at 5:21 PM, Mike Tutkowski <
> >mike.tutkow...@solidfire.com> wrote:
> >
> >> Hey Min,
> >>
> >> What is our standard way of reverting a commit?
> >>
> >> I have ways of doing this locally, but have never done it on a remote
> >>repo.
> >>
> >> Thanks!
> >>
> >>
> >> On Thu, Mar 20, 2014 at 5:19 PM, Mike Tutkowski <
> >> mike.tutkow...@solidfire.com> wrote:
> >>
> >>> Sure, I'll look into that. Thanks
> >>>
> >>>
> >>> On Thu, Mar 20, 2014 at 5:16 PM, Min Chen  wrote:
> >>>
>  Mike, with your latest commit
> 7a7d9cff0d5bb40284506faa6e34138f97a12428 on
>  4.4, test failed in cloud-server:
> 
>  Tests in error:
>    testRestoreVMF2(com.cloud.vm.UserVmManagerTest)
>    testRestoreVMF3(com.cloud.vm.UserVmManagerTest)
>    testRestoreVMF4(com.cloud.vm.UserVmManagerTest)
>    testRestoreVMF5(com.cloud.vm.UserVmManagerTest)
> 
> 
>  Before getting your commit, I am able to build 4.4 successfully. Can
> you
>  revert your change and fix the failure then commit again?
> 
>  Thanks
>  -min
> 
> 
>  On 3/20/14 4:11 PM, "Mike Tutkowski" 
>  wrote:
> 
>  >Hi,
>  >
>  >I think there was a discussion earlier about this, but I was
> wondering
>  if
>  >others were seeing test failures in 4.4 when running mvn -P
>  >developer,systemvm clean install?
>  >
>  >I have to add -D skipTests=true to get the build to finish.
>  >
>  >Thanks,
>  >
>  >--
>  >*Mike Tutkowski*
>  >*Senior CloudStack Developer, SolidFire Inc.*
>  >e: mike.tutkow...@solidfire.com
>  >o: 303.746.7302
>  >Advancing the way the world uses the
>  >cloud
>  >*(tm)*
> 
> 
> >>>
> >>>
> >>> --
> >>> *Mike Tutkowski*
> >>>  *Senior CloudStack Developer, SolidFire Inc.*
> >>> e: mike.tutkow...@solidfire.com
> >>> o: 303.746.7302
> >>> Advancing the way the world uses the
> >>>cloud
> >>> *(tm)*
> >>>
> >>
> >>
> >>
> >> --
> >> *Mike Tutkowski*
> >> *Senior CloudStack Developer, SolidFire Inc.*
> >> e: mike.tutkow...@solidfire.com
> >> o: 303.746.7302
> >> Advancing the way the world uses the
> >>cloud
> >> *(tm)*
> >>
> >
> >
> >
> >--
> >*Mike Tutkowski*
> >*Senior CloudStack Developer, SolidFire Inc.*
> >e: mike.tutkow...@solidfire.com
> >o: 303.746.7302
> >Advancing the way the world uses the
> >cloud
> >*(tm)*
>
>


-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

Re: [ACS4.4] Are tests still failing for people?

Thanks, Min!

I remembered it incorrect. I was under the impression those tests were
failing before my code was changed.

Can you tell me how to revert on the remote repo just for future reference?


On Thu, Mar 20, 2014 at 5:30 PM, Min Chen  wrote:

> I am reverting it for you now along with my another fix to be checked in.
>
> Thanks
> -min
>
> On 3/20/14 4:25 PM, "Mike Tutkowski"  wrote:
>
> >For example, I can't seem to force the branch back to a previous commit.
> >
> >
> >On Thu, Mar 20, 2014 at 5:21 PM, Mike Tutkowski <
> >mike.tutkow...@solidfire.com> wrote:
> >
> >> Hey Min,
> >>
> >> What is our standard way of reverting a commit?
> >>
> >> I have ways of doing this locally, but have never done it on a remote
> >>repo.
> >>
> >> Thanks!
> >>
> >>
> >> On Thu, Mar 20, 2014 at 5:19 PM, Mike Tutkowski <
> >> mike.tutkow...@solidfire.com> wrote:
> >>
> >>> Sure, I'll look into that. Thanks
> >>>
> >>>
> >>> On Thu, Mar 20, 2014 at 5:16 PM, Min Chen  wrote:
> >>>
>  Mike, with your latest commit
> 7a7d9cff0d5bb40284506faa6e34138f97a12428 on
>  4.4, test failed in cloud-server:
> 
>  Tests in error:
>    testRestoreVMF2(com.cloud.vm.UserVmManagerTest)
>    testRestoreVMF3(com.cloud.vm.UserVmManagerTest)
>    testRestoreVMF4(com.cloud.vm.UserVmManagerTest)
>    testRestoreVMF5(com.cloud.vm.UserVmManagerTest)
> 
> 
>  Before getting your commit, I am able to build 4.4 successfully. Can
> you
>  revert your change and fix the failure then commit again?
> 
>  Thanks
>  -min
> 
> 
>  On 3/20/14 4:11 PM, "Mike Tutkowski" 
>  wrote:
> 
>  >Hi,
>  >
>  >I think there was a discussion earlier about this, but I was
> wondering
>  if
>  >others were seeing test failures in 4.4 when running mvn -P
>  >developer,systemvm clean install?
>  >
>  >I have to add -D skipTests=true to get the build to finish.
>  >
>  >Thanks,
>  >
>  >--
>  >*Mike Tutkowski*
>  >*Senior CloudStack Developer, SolidFire Inc.*
>  >e: mike.tutkow...@solidfire.com
>  >o: 303.746.7302
>  >Advancing the way the world uses the
>  >cloud
>  >*(tm)*
> 
> 
> >>>
> >>>
> >>> --
> >>> *Mike Tutkowski*
> >>>  *Senior CloudStack Developer, SolidFire Inc.*
> >>> e: mike.tutkow...@solidfire.com
> >>> o: 303.746.7302
> >>> Advancing the way the world uses the
> >>>cloud
> >>> *(tm)*
> >>>
> >>
> >>
> >>
> >> --
> >> *Mike Tutkowski*
> >> *Senior CloudStack Developer, SolidFire Inc.*
> >> e: mike.tutkow...@solidfire.com
> >> o: 303.746.7302
> >> Advancing the way the world uses the
> >>cloud
> >> *(tm)*
> >>
> >
> >
> >
> >--
> >*Mike Tutkowski*
> >*Senior CloudStack Developer, SolidFire Inc.*
> >e: mike.tutkow...@solidfire.com
> >o: 303.746.7302
> >Advancing the way the world uses the
> >cloud
> >*(tm)*
>
>


-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

RE: [ACS4.4] Are tests still failing for people?

Min,

Thanks a lot!!!
(The testing failure is also blocking me)

Jessica

-Original Message-
From: Min Chen [mailto:min.c...@citrix.com] 
Sent: Thursday, March 20, 2014 4:31 PM
To: dev@cloudstack.apache.org
Subject: Re: [ACS4.4] Are tests still failing for people?

I am reverting it for you now along with my another fix to be checked in.

Thanks
-min

On 3/20/14 4:25 PM, "Mike Tutkowski"  wrote:

>For example, I can't seem to force the branch back to a previous commit.
>
>
>On Thu, Mar 20, 2014 at 5:21 PM, Mike Tutkowski <
>mike.tutkow...@solidfire.com> wrote:
>
>> Hey Min,
>>
>> What is our standard way of reverting a commit?
>>
>> I have ways of doing this locally, but have never done it on a remote
>>repo.
>>
>> Thanks!
>>
>>
>> On Thu, Mar 20, 2014 at 5:19 PM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>>> Sure, I'll look into that. Thanks
>>>
>>>
>>> On Thu, Mar 20, 2014 at 5:16 PM, Min Chen  wrote:
>>>
 Mike, with your latest commit
7a7d9cff0d5bb40284506faa6e34138f97a12428 on
 4.4, test failed in cloud-server:

 Tests in error:
   testRestoreVMF2(com.cloud.vm.UserVmManagerTest)
   testRestoreVMF3(com.cloud.vm.UserVmManagerTest)
   testRestoreVMF4(com.cloud.vm.UserVmManagerTest)
   testRestoreVMF5(com.cloud.vm.UserVmManagerTest)


 Before getting your commit, I am able to build 4.4 successfully. Can
you
 revert your change and fix the failure then commit again?

 Thanks
 -min


 On 3/20/14 4:11 PM, "Mike Tutkowski" 
 wrote:

 >Hi,
 >
 >I think there was a discussion earlier about this, but I was
wondering
 if
 >others were seeing test failures in 4.4 when running mvn -P
 >developer,systemvm clean install?
 >
 >I have to add -D skipTests=true to get the build to finish.
 >
 >Thanks,
 >
 >--
 >*Mike Tutkowski*
 >*Senior CloudStack Developer, SolidFire Inc.*
 >e: mike.tutkow...@solidfire.com
 >o: 303.746.7302
 >Advancing the way the world uses the
 >cloud
 >*(tm)*


>>>
>>>
>>> --
>>> *Mike Tutkowski*
>>>  *Senior CloudStack Developer, SolidFire Inc.*
>>> e: mike.tutkow...@solidfire.com
>>> o: 303.746.7302
>>> Advancing the way the world uses the
>>>cloud
>>> *(tm)*
>>>
>>
>>
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkow...@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the
>>cloud
>> *(tm)*
>>
>
>
>
>-- 
>*Mike Tutkowski*
>*Senior CloudStack Developer, SolidFire Inc.*
>e: mike.tutkow...@solidfire.com
>o: 303.746.7302
>Advancing the way the world uses the
>cloud
>*(tm)*

Re: [ACS4.4] Are tests still failing for people?

I am reverting it for you now along with my another fix to be checked in.

Thanks
-min

On 3/20/14 4:25 PM, "Mike Tutkowski"  wrote:

>For example, I can't seem to force the branch back to a previous commit.
>
>
>On Thu, Mar 20, 2014 at 5:21 PM, Mike Tutkowski <
>mike.tutkow...@solidfire.com> wrote:
>
>> Hey Min,
>>
>> What is our standard way of reverting a commit?
>>
>> I have ways of doing this locally, but have never done it on a remote
>>repo.
>>
>> Thanks!
>>
>>
>> On Thu, Mar 20, 2014 at 5:19 PM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>>> Sure, I'll look into that. Thanks
>>>
>>>
>>> On Thu, Mar 20, 2014 at 5:16 PM, Min Chen  wrote:
>>>
 Mike, with your latest commit
7a7d9cff0d5bb40284506faa6e34138f97a12428 on
 4.4, test failed in cloud-server:

 Tests in error:
   testRestoreVMF2(com.cloud.vm.UserVmManagerTest)
   testRestoreVMF3(com.cloud.vm.UserVmManagerTest)
   testRestoreVMF4(com.cloud.vm.UserVmManagerTest)
   testRestoreVMF5(com.cloud.vm.UserVmManagerTest)


 Before getting your commit, I am able to build 4.4 successfully. Can
you
 revert your change and fix the failure then commit again?

 Thanks
 -min


 On 3/20/14 4:11 PM, "Mike Tutkowski" 
 wrote:

 >Hi,
 >
 >I think there was a discussion earlier about this, but I was
wondering
 if
 >others were seeing test failures in 4.4 when running mvn -P
 >developer,systemvm clean install?
 >
 >I have to add -D skipTests=true to get the build to finish.
 >
 >Thanks,
 >
 >--
 >*Mike Tutkowski*
 >*Senior CloudStack Developer, SolidFire Inc.*
 >e: mike.tutkow...@solidfire.com
 >o: 303.746.7302
 >Advancing the way the world uses the
 >cloud
 >*(tm)*


>>>
>>>
>>> --
>>> *Mike Tutkowski*
>>>  *Senior CloudStack Developer, SolidFire Inc.*
>>> e: mike.tutkow...@solidfire.com
>>> o: 303.746.7302
>>> Advancing the way the world uses the
>>>cloud
>>> *(tm)*
>>>
>>
>>
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkow...@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the
>>cloud
>> *(tm)*
>>
>
>
>
>-- 
>*Mike Tutkowski*
>*Senior CloudStack Developer, SolidFire Inc.*
>e: mike.tutkow...@solidfire.com
>o: 303.746.7302
>Advancing the way the world uses the
>cloud
>*(tm)*

Re: [ACS4.4] Are tests still failing for people?

For example, I can't seem to force the branch back to a previous commit.


On Thu, Mar 20, 2014 at 5:21 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Hey Min,
>
> What is our standard way of reverting a commit?
>
> I have ways of doing this locally, but have never done it on a remote repo.
>
> Thanks!
>
>
> On Thu, Mar 20, 2014 at 5:19 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> Sure, I'll look into that. Thanks
>>
>>
>> On Thu, Mar 20, 2014 at 5:16 PM, Min Chen  wrote:
>>
>>> Mike, with your latest commit 7a7d9cff0d5bb40284506faa6e34138f97a12428 on
>>> 4.4, test failed in cloud-server:
>>>
>>> Tests in error:
>>>   testRestoreVMF2(com.cloud.vm.UserVmManagerTest)
>>>   testRestoreVMF3(com.cloud.vm.UserVmManagerTest)
>>>   testRestoreVMF4(com.cloud.vm.UserVmManagerTest)
>>>   testRestoreVMF5(com.cloud.vm.UserVmManagerTest)
>>>
>>>
>>> Before getting your commit, I am able to build 4.4 successfully. Can you
>>> revert your change and fix the failure then commit again?
>>>
>>> Thanks
>>> -min
>>>
>>>
>>> On 3/20/14 4:11 PM, "Mike Tutkowski" 
>>> wrote:
>>>
>>> >Hi,
>>> >
>>> >I think there was a discussion earlier about this, but I was wondering
>>> if
>>> >others were seeing test failures in 4.4 when running mvn -P
>>> >developer,systemvm clean install?
>>> >
>>> >I have to add -D skipTests=true to get the build to finish.
>>> >
>>> >Thanks,
>>> >
>>> >--
>>> >*Mike Tutkowski*
>>> >*Senior CloudStack Developer, SolidFire Inc.*
>>> >e: mike.tutkow...@solidfire.com
>>> >o: 303.746.7302
>>> >Advancing the way the world uses the
>>> >cloud
>>> >*(tm)*
>>>
>>>
>>
>>
>> --
>> *Mike Tutkowski*
>>  *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkow...@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the 
>> cloud
>> *(tm)*
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the 
> cloud
> *(tm)*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

Re: [ACS4.4] Are tests still failing for people?

Hey Min,

What is our standard way of reverting a commit?

I have ways of doing this locally, but have never done it on a remote repo.

Thanks!


On Thu, Mar 20, 2014 at 5:19 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Sure, I'll look into that. Thanks
>
>
> On Thu, Mar 20, 2014 at 5:16 PM, Min Chen  wrote:
>
>> Mike, with your latest commit 7a7d9cff0d5bb40284506faa6e34138f97a12428 on
>> 4.4, test failed in cloud-server:
>>
>> Tests in error:
>>   testRestoreVMF2(com.cloud.vm.UserVmManagerTest)
>>   testRestoreVMF3(com.cloud.vm.UserVmManagerTest)
>>   testRestoreVMF4(com.cloud.vm.UserVmManagerTest)
>>   testRestoreVMF5(com.cloud.vm.UserVmManagerTest)
>>
>>
>> Before getting your commit, I am able to build 4.4 successfully. Can you
>> revert your change and fix the failure then commit again?
>>
>> Thanks
>> -min
>>
>>
>> On 3/20/14 4:11 PM, "Mike Tutkowski" 
>> wrote:
>>
>> >Hi,
>> >
>> >I think there was a discussion earlier about this, but I was wondering if
>> >others were seeing test failures in 4.4 when running mvn -P
>> >developer,systemvm clean install?
>> >
>> >I have to add -D skipTests=true to get the build to finish.
>> >
>> >Thanks,
>> >
>> >--
>> >*Mike Tutkowski*
>> >*Senior CloudStack Developer, SolidFire Inc.*
>> >e: mike.tutkow...@solidfire.com
>> >o: 303.746.7302
>> >Advancing the way the world uses the
>> >cloud
>> >*(tm)*
>>
>>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the 
> cloud
> *(tm)*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

Re: [ACS4.4] Are tests still failing for people?

Sure, I'll look into that. Thanks


On Thu, Mar 20, 2014 at 5:16 PM, Min Chen  wrote:

> Mike, with your latest commit 7a7d9cff0d5bb40284506faa6e34138f97a12428 on
> 4.4, test failed in cloud-server:
>
> Tests in error:
>   testRestoreVMF2(com.cloud.vm.UserVmManagerTest)
>   testRestoreVMF3(com.cloud.vm.UserVmManagerTest)
>   testRestoreVMF4(com.cloud.vm.UserVmManagerTest)
>   testRestoreVMF5(com.cloud.vm.UserVmManagerTest)
>
>
> Before getting your commit, I am able to build 4.4 successfully. Can you
> revert your change and fix the failure then commit again?
>
> Thanks
> -min
>
>
> On 3/20/14 4:11 PM, "Mike Tutkowski"  wrote:
>
> >Hi,
> >
> >I think there was a discussion earlier about this, but I was wondering if
> >others were seeing test failures in 4.4 when running mvn -P
> >developer,systemvm clean install?
> >
> >I have to add -D skipTests=true to get the build to finish.
> >
> >Thanks,
> >
> >--
> >*Mike Tutkowski*
> >*Senior CloudStack Developer, SolidFire Inc.*
> >e: mike.tutkow...@solidfire.com
> >o: 303.746.7302
> >Advancing the way the world uses the
> >cloud
> >*(tm)*
>
>


-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

Re: [ACS4.4] Are tests still failing for people?

Mike, with your latest commit 7a7d9cff0d5bb40284506faa6e34138f97a12428 on
4.4, test failed in cloud-server:

Tests in error: 
  testRestoreVMF2(com.cloud.vm.UserVmManagerTest)
  testRestoreVMF3(com.cloud.vm.UserVmManagerTest)
  testRestoreVMF4(com.cloud.vm.UserVmManagerTest)
  testRestoreVMF5(com.cloud.vm.UserVmManagerTest)


Before getting your commit, I am able to build 4.4 successfully. Can you
revert your change and fix the failure then commit again?

Thanks
-min


On 3/20/14 4:11 PM, "Mike Tutkowski"  wrote:

>Hi,
>
>I think there was a discussion earlier about this, but I was wondering if
>others were seeing test failures in 4.4 when running mvn -P
>developer,systemvm clean install?
>
>I have to add -D skipTests=true to get the build to finish.
>
>Thanks,
>
>-- 
>*Mike Tutkowski*
>*Senior CloudStack Developer, SolidFire Inc.*
>e: mike.tutkow...@solidfire.com
>o: 303.746.7302
>Advancing the way the world uses the
>cloud
>*(tm)*

Build failed in Jenkins: cloudstack-4.4-maven-build #27

2014-03-20 Thread jenkins

See 

Changes:

[mike.tutkowski] CLOUDSTACK-6170

--
[...truncated 1326 lines...]
[INFO] Executed tasks
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
cloud-server ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 30 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ cloud-server 
---
[INFO] Compiling 360 source files to 

[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-server ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 29 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
cloud-server ---
[INFO] Compiling 82 source files to 

[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ cloud-server ---
[INFO] Surefire report directory: 


---
 T E S T S
---
Running 
org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImplTest
log4j:WARN No appenders could be found for logger 
(org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImplTest).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.856 sec
Running org.apache.cloudstack.region.RegionManagerTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.127 sec
Running org.apache.cloudstack.service.ServiceOfferingVOTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.158 sec
Running org.apache.cloudstack.affinity.AffinityApiUnitTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.665 sec
Running org.apache.cloudstack.privategw.AclOnPrivateGwTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.929 sec
Running org.apache.cloudstack.network.lb.CertServiceTest
Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.08 sec
Running org.apache.cloudstack.network.lb.ApplicationLoadBalancerTest
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.375 sec
Running org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 28.683 sec
Running com.cloud.template.TemplateManagerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec
Running com.cloud.keystore.KeystoreTest
org.apache.cloudstack.api.response.UserVmResponse/null/{"id":"3","securitygroup":[],"nic":[],"tags":[],"affinitygroup":[]}
org.apache.cloudstack.api.response.AlertResponse/null/{"id":"100","description":"Hello"}
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.445 sec
Running com.cloud.server.ConfigurationServerImplTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.071 sec
Running com.cloud.event.EventControlsUnitTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.478 sec
Running com.cloud.resourcelimit.ResourceLimitManagerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec
Running com.cloud.api.dispatch.ParamGenericValidationWorkerTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.139 sec
Running com.cloud.api.dispatch.ParamProcessWorkerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.112 sec
Running com.cloud.api.dispatch.CommandCreationWorkerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.126 sec
Running com.cloud.api.dispatch.DispatchChainFactoryTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.018 sec
Running com.cloud.api.dispatch.SpecificCmdValidationWorkerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
Running com.cloud.alert.AlertControlsUnitTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.068 sec
Running com.cloud.ha.KVMFencerTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.453 sec
Running com.cloud.capacity.CapacityManagerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.214 sec
Running com.cloud.vm.snapshot.VMSnapshotManagerTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.379 sec
Running com.cloud.vm.UserVmManagerTest
Tests run: 9, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 1.831 sec <<< 
FAILURE!
Running com.cloud.vm.De

[ACS4.4] Are tests still failing for people?

Hi,

I think there was a discussion earlier about this, but I was wondering if
others were seeing test failures in 4.4 when running mvn -P
developer,systemvm clean install?

I have to add -D skipTests=true to get the build to finish.

Thanks,

-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

Re: concole proxy in 4.3RC9

2014-03-20 Thread Nitin Mehta

I also tried on XS setup and default case seems to be as expected.

 the console url is ::
VM-1f2d2061-07ca-4867-9f12-edc7b845247chttp://10.223.247.3/ajax?token=P3yRFP_NZaXFv0KoRrKD6U9Riz0Cp0-0mgeGCj7
hCD5BpKSBc9pKMl53c-1zjaKyk-NsJt4qh0L82PqTOmF6ahCdNE5TJytveKZPvO5Th2NI48beO9
0uIKD0y7zTwv1x4ONdCnkeOTyq53U5X9XdGkai62FGCZG-ve1Bc8sU2G62JnvqTsZpwruHS4V32
Jxiv8cw8eUtVcr0SGqNQRqQ-UqRwP8WITKerETW6GVVf7VI0N5A_CKGkqhqZx2P62CW2KxvAZWp
g5b8Hoiukzc7DtJc_jLsOaULfzNiGLki4yz07nT5phCrbOdht3D7r7kXBPik9TEU8lxZStaAhtJ
XPo0sVGqwCBRhoxmmP_tLGjgzDww34q24ENL3OuL20iA57IZmbO1rDerB2TSJUjedhuqW1x0wxG
FGTaC5w1TNYT-HY6XIr2WpXKRETEPMgu2PCAcu6pGUBKRcoRjAyjjlLSXfFwEWZel_tUDwTPJXc
P0">

Thanks,
-Nitin

On 20/03/14 1:10 PM, "Daan Hoogland"  wrote:

>Amogh, I am running the ms on windows but I did build a 4.3 systemvm
>on a differnt machine and copied it to the hypervisors. port 80 can go
>to the hypervisor which says that it does not have the page /console
>
>On Thu, Mar 20, 2014 at 7:45 PM, Amogh Vasekar 
>wrote:
>> Hi,
>>
>> Tried on XenServer set-up, and the defaults work fine for me. The
>>console
>> URL for me :
>> 2014-03-20 18:43:08,558 DEBUG [c.c.s.ConsoleProxyServlet]
>> (24565443@qtp-27436568-8:null) Compose console url:
>> 
>>http://192.168.56.139/ajax?token=tVsokSDt2PUASaa77NN_qBAZFJsma76qRT5Y1OLQ
>>FW
>> 
>>1zl82-vizkq36Fii1yLNvR1h7Ul3CL0L8yrtn2y7FkqLgZyXFc3bObM5U2H6n-3CO01d-zqJG
>>xq
>> 
>>hNom6i-oUEgQhp-QPJ0rKkEZErTeYF6YyMwHghWabLuAyDYYT9gA39VWAVHcySUtSjFcjRFWh
>>IA
>> 
>>vOs9RghpY9D6rvzgjeCvBOuy4aOD1kQlT_7lUIX3BIcLyipMR200o0y2ZjAfxwdfN-9oyMuuU
>>jr
>> 
>>YsObY9xb-BQxOb5p5cZogqqqiCnXGhr1mPwlN6Ba-BI-UQzgNjlHX95sp0x_hnHhdzMfZ0vfa
>>Ao
>> 
>>7SZLrfD1oGRxMOWFonu-WHSsu4OBcDSELFxd-2Yt_noZ6Mdz2kheMvGfYmFC2r1gjii0rxzuj
>>8L
>> 
>>w8p42DZAGLq8TqSWyBUGsQWhMveyHVJHbKJDrsOcJVMyUdDLKsVhGR9voti7TJUAAzQb75Aha
>>w
>>
>> Just to reconfirm - did you build using systemvm profile? Is port 80
>> blocked somewhere?
>>
>> Thanks,
>> Amogh
>>
>> On 3/20/14 10:15 AM, "Daan Hoogland"  wrote:
>>
>>>btw
>>>
>>>the last lines:
>>>
>>>2014-03-20 13:57:09,858 DEBUG [c.c.a.t.Request]
>>>(1372260265@qtp-1676921458-10:null) Seq 1-762183775: Sending  { Cmd ,
>>>MgmtId: 24062491136, via: 1(mccdxen2), Ver: v1, Flags: 100011,
>>>[{"com.cloud.agent.api.GetVncPortCommand":{"id":5,"name":"i-2-5-VM","wai
>>>t"
>>>:0}}]
>>>}
>>>2014-03-20 13:57:09,858 DEBUG [c.c.a.t.Request]
>>>(1372260265@qtp-1676921458-10:null) Seq 1-762183775: Executing:  { Cmd
>>>, MgmtId: 24062491136, via: 1(mccdxen2), Ver: v1, Flags: 100011,
>>>[{"com.cloud.agent.api.GetVncPortCommand":{"id":5,"name":"i-2-5-VM","wai
>>>t"
>>>:0}}]
>>>}
>>>2014-03-20 13:57:09,859 DEBUG [c.c.a.m.DirectAgentAttache]
>>>(DirectAgent-63:ctx-6c8a6687) Seq 1-762183775: Executing request
>>>2014-03-20 13:57:09,976 DEBUG [c.c.a.m.DirectAgentAttache]
>>>(DirectAgent-63:ctx-6c8a6687) Seq 1-762183775: Response Received:
>>>2014-03-20 13:57:09,976 DEBUG [c.c.a.t.Request]
>>>(DirectAgent-63:ctx-6c8a6687) Seq 1-762183775: Processing:  { Ans: ,
>>>MgmtId: 24062491136, via: 1, Ver: v1, Flags: 10,
>>>[{"com.cloud.agent.api.GetVncPortAnswer":{"address":"consoleurl=https://
>>>10
>>>.200.23.42/console?uuid=d539642a-7c78-622e-9c22-e6b3b0771122&sessionref=
>>>Op
>>>aqueRef:160e30d3-5f3e-255e-ef8a-596e69ad30d4","port":-1,"result":true,"w
>>>ai
>>>t":0}}]
>>>}
>>>2014-03-20 13:57:09,976 DEBUG [c.c.a.t.Request]
>>>(1372260265@qtp-1676921458-10:null) Seq 1-762183775: Received:  { Ans:
>>>, MgmtId: 24062491136, via: 1, Ver: v1, Flags: 10, { GetVncPortAnswer
>>>} }
>>>2014-03-20 13:57:09,976 DEBUG [c.c.s.ConsoleProxyServlet]
>>>(1372260265@qtp-1676921458-10:null) Port info
>>>consoleurl=https://10.200.23.42/console?uuid=d539642a-7c78-622e-9c22-e6b
>>>3b
>>>0771122&sessionref=OpaqueRef:160e30d3-5f3e-255e-ef8a-596e69ad30d4
>>>2014-03-20 13:57:09,976 INFO  [c.c.s.ConsoleProxyServlet]
>>>(1372260265@qtp-1676921458-10:null) Parse host info returned from
>>>executing GetVNCPortCommand. host info:
>>>consoleurl=https://10.200.23.42/console?uuid=d539642a-7c78-622e-9c22-e6b
>>>3b
>>>0771122&sessionref=OpaqueRef:160e30d3-5f3e-255e-ef8a-596e69ad30d4
>>>2014-03-20 13:57:09,979 DEBUG [c.c.s.ConsoleProxyServlet]
>>>(1372260265@qtp-1676921458-10:null) Compose console url:
>>>http://195.66.90.213/ajax?token=9Rrl0mjwUQd3Ym9mEb-ziydOD0YOSWJNi_QZFP7e
>>>fE
>>>r1mIalpz2Xg0UvR2eUUyqbgFqNXQJOlt0yJsfkH7CnubShCuEb82qKCD4zf50hyHxZufjglf
>>>9N
>>>efAuIXRJmmXe10afkEVYHARondjCtJ80RkovHVtQHkErX9s2wB2HT9Zx7kuKGdYmigVQ8_Aj
>>>qF
>>>yusOCQ6XTplJOlr4ZdvSZoafu0dowEYJysruLtBvY9qsi5eMXC4ozvodmRUfBN4jARisUjus
>>>BC
>>>DUSzQyrdXImCjLFT3cL1GVmdNPQz7L7s3PJrSyMdB9ZZshnzNYAYkCjUtjiLwAf3aJfZt3z3
>>>r9
>>>TuJg6k5kfhRbBsvpBVtrYcI1DXJfEANZD6g9f4hDRghnsXxrUpPrA973CiSUaKsKzUMqVWM4
>>>Vu
>>>iDtHkWIgk_p100K-ai9wzufJYAk9lZ_vhY9GWYkQhpBtZeupk3Gl5Gc_iudCMwP9kFvEA12i
>>>6j
>>>Nvtng
>>>2014-03-20 13:57:09,979 DEBUG [c.c.s.ConsoleProxyServlet]
>>>(1372260265@qtp-1676921458-10:null) the console url is ::
>>>g>>src="http://195.66.90.213/ajax?token=9Rrl0mjwUQd3Ym9mEb-ziydOD0YOSWJNi_Q
>>>ZF
>>>P7e

Re: Review Request 12228: static resource compression

2014-03-20 Thread John Kinsella

Laszlo, can you reference any other open source projects that have similar 
solutions to this issue? Anything I’ve read states dynamic compression in 
tomcat/httpd/nginx does not add significant CPU overhead.

On Mar 20, 2014, at 12:53 PM, Laszlo Hornyak 
mailto:laszlo.horn...@gmail.com>> wrote:


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

(Updated March 20, 2014, 7:53 p.m.)


Review request for cloudstack, Brian Federle, Darren Shepherd, and Prasanna 
Santhanam.


Changes
---

spaces


Repository: cloudstack-git


Description
---

CloudStack at first use downloads some 3.5 MB of css and javascript to the 
client. With a weak internet connection, this might take a long time. With gzip 
compression content can be compressed to 850 KB.

This version of the patch uses a custom plugin to compress static resources, so 
that no dynamic compression is needed at runtime. When the static resource 
servlet notices that there is gzipped version of the resource and the client 
accepts gzipped content, then it is going to send the gziped version, while 
still respects http caching.


Diffs (updated)
-

 client/WEB-INF/web.xml 1af38e1
 client/pom.xml d8dbde7
 server/src/com/cloud/servlet/StaticResourceServlet.java PRE-CREATION
 server/test/com/cloud/servlet/StaticResourceServletTest.java PRE-CREATION

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


Testing
---

yes, tested with firefox and chrome


Thanks,

Laszlo Hornyak


Stratosec - Compliance as a Service
o: 415.315.9385
@johnlkinsella

Re: concole proxy in 4.3RC9

2014-03-20 Thread Amogh Vasekar

Tried with a VPC on KVM and the console access went fine.
I had initially tested console access for all three different scenarios :
1. HTTP
2. HTTPS with realhostip domain
3. HTTPS with custom domain

The URL you see in the browser is for the MS, the console URL can be seen
in the log.

I am not sure about copying the systemvm iso to machine - there is a
change in the conf file for console proxy which needs the updated systemvm
iso.

Thanks,
Amogh

On 3/20/14 1:10 PM, "Daan Hoogland"  wrote:

>Amogh, I am running the ms on windows but I did build a 4.3 systemvm
>on a differnt machine and copied it to the hypervisors. port 80 can go
>to the hypervisor which says that it does not have the page /console
>
>On Thu, Mar 20, 2014 at 7:45 PM, Amogh Vasekar 
>wrote:
>> Hi,
>>
>> Tried on XenServer set-up, and the defaults work fine for me. The
>>console
>> URL for me :
>> 2014-03-20 18:43:08,558 DEBUG [c.c.s.ConsoleProxyServlet]
>> (24565443@qtp-27436568-8:null) Compose console url:
>> 
>>http://192.168.56.139/ajax?token=tVsokSDt2PUASaa77NN_qBAZFJsma76qRT5Y1OLQ
>>FW
>> 
>>1zl82-vizkq36Fii1yLNvR1h7Ul3CL0L8yrtn2y7FkqLgZyXFc3bObM5U2H6n-3CO01d-zqJG
>>xq
>> 
>>hNom6i-oUEgQhp-QPJ0rKkEZErTeYF6YyMwHghWabLuAyDYYT9gA39VWAVHcySUtSjFcjRFWh
>>IA
>> 
>>vOs9RghpY9D6rvzgjeCvBOuy4aOD1kQlT_7lUIX3BIcLyipMR200o0y2ZjAfxwdfN-9oyMuuU
>>jr
>> 
>>YsObY9xb-BQxOb5p5cZogqqqiCnXGhr1mPwlN6Ba-BI-UQzgNjlHX95sp0x_hnHhdzMfZ0vfa
>>Ao
>> 
>>7SZLrfD1oGRxMOWFonu-WHSsu4OBcDSELFxd-2Yt_noZ6Mdz2kheMvGfYmFC2r1gjii0rxzuj
>>8L
>> 
>>w8p42DZAGLq8TqSWyBUGsQWhMveyHVJHbKJDrsOcJVMyUdDLKsVhGR9voti7TJUAAzQb75Aha
>>w
>>
>> Just to reconfirm - did you build using systemvm profile? Is port 80
>> blocked somewhere?
>>
>> Thanks,
>> Amogh
>>
>> On 3/20/14 10:15 AM, "Daan Hoogland"  wrote:
>>
>>>btw
>>>
>>>the last lines:
>>>
>>>2014-03-20 13:57:09,858 DEBUG [c.c.a.t.Request]
>>>(1372260265@qtp-1676921458-10:null) Seq 1-762183775: Sending  { Cmd ,
>>>MgmtId: 24062491136, via: 1(mccdxen2), Ver: v1, Flags: 100011,
>>>[{"com.cloud.agent.api.GetVncPortCommand":{"id":5,"name":"i-2-5-VM","wai
>>>t"
>>>:0}}]
>>>}
>>>2014-03-20 13:57:09,858 DEBUG [c.c.a.t.Request]
>>>(1372260265@qtp-1676921458-10:null) Seq 1-762183775: Executing:  { Cmd
>>>, MgmtId: 24062491136, via: 1(mccdxen2), Ver: v1, Flags: 100011,
>>>[{"com.cloud.agent.api.GetVncPortCommand":{"id":5,"name":"i-2-5-VM","wai
>>>t"
>>>:0}}]
>>>}
>>>2014-03-20 13:57:09,859 DEBUG [c.c.a.m.DirectAgentAttache]
>>>(DirectAgent-63:ctx-6c8a6687) Seq 1-762183775: Executing request
>>>2014-03-20 13:57:09,976 DEBUG [c.c.a.m.DirectAgentAttache]
>>>(DirectAgent-63:ctx-6c8a6687) Seq 1-762183775: Response Received:
>>>2014-03-20 13:57:09,976 DEBUG [c.c.a.t.Request]
>>>(DirectAgent-63:ctx-6c8a6687) Seq 1-762183775: Processing:  { Ans: ,
>>>MgmtId: 24062491136, via: 1, Ver: v1, Flags: 10,
>>>[{"com.cloud.agent.api.GetVncPortAnswer":{"address":"consoleurl=https://
>>>10
>>>.200.23.42/console?uuid=d539642a-7c78-622e-9c22-e6b3b0771122&sessionref=
>>>Op
>>>aqueRef:160e30d3-5f3e-255e-ef8a-596e69ad30d4","port":-1,"result":true,"w
>>>ai
>>>t":0}}]
>>>}
>>>2014-03-20 13:57:09,976 DEBUG [c.c.a.t.Request]
>>>(1372260265@qtp-1676921458-10:null) Seq 1-762183775: Received:  { Ans:
>>>, MgmtId: 24062491136, via: 1, Ver: v1, Flags: 10, { GetVncPortAnswer
>>>} }
>>>2014-03-20 13:57:09,976 DEBUG [c.c.s.ConsoleProxyServlet]
>>>(1372260265@qtp-1676921458-10:null) Port info
>>>consoleurl=https://10.200.23.42/console?uuid=d539642a-7c78-622e-9c22-e6b
>>>3b
>>>0771122&sessionref=OpaqueRef:160e30d3-5f3e-255e-ef8a-596e69ad30d4
>>>2014-03-20 13:57:09,976 INFO  [c.c.s.ConsoleProxyServlet]
>>>(1372260265@qtp-1676921458-10:null) Parse host info returned from
>>>executing GetVNCPortCommand. host info:
>>>consoleurl=https://10.200.23.42/console?uuid=d539642a-7c78-622e-9c22-e6b
>>>3b
>>>0771122&sessionref=OpaqueRef:160e30d3-5f3e-255e-ef8a-596e69ad30d4
>>>2014-03-20 13:57:09,979 DEBUG [c.c.s.ConsoleProxyServlet]
>>>(1372260265@qtp-1676921458-10:null) Compose console url:
>>>http://195.66.90.213/ajax?token=9Rrl0mjwUQd3Ym9mEb-ziydOD0YOSWJNi_QZFP7e
>>>fE
>>>r1mIalpz2Xg0UvR2eUUyqbgFqNXQJOlt0yJsfkH7CnubShCuEb82qKCD4zf50hyHxZufjglf
>>>9N
>>>efAuIXRJmmXe10afkEVYHARondjCtJ80RkovHVtQHkErX9s2wB2HT9Zx7kuKGdYmigVQ8_Aj
>>>qF
>>>yusOCQ6XTplJOlr4ZdvSZoafu0dowEYJysruLtBvY9qsi5eMXC4ozvodmRUfBN4jARisUjus
>>>BC
>>>DUSzQyrdXImCjLFT3cL1GVmdNPQz7L7s3PJrSyMdB9ZZshnzNYAYkCjUtjiLwAf3aJfZt3z3
>>>r9
>>>TuJg6k5kfhRbBsvpBVtrYcI1DXJfEANZD6g9f4hDRghnsXxrUpPrA973CiSUaKsKzUMqVWM4
>>>Vu
>>>iDtHkWIgk_p100K-ai9wzufJYAk9lZ_vhY9GWYkQhpBtZeupk3Gl5Gc_iudCMwP9kFvEA12i
>>>6j
>>>Nvtng
>>>2014-03-20 13:57:09,979 DEBUG [c.c.s.ConsoleProxyServlet]
>>>(1372260265@qtp-1676921458-10:null) the console url is ::
>>>g>>src="http://195.66.90.213/ajax?token=9Rrl0mjwUQd3Ym9mEb-ziydOD0YOSWJNi_Q
>>>ZF
>>>P7efEr1mIalpz2Xg0UvR2eUUyqbgFqNXQJOlt0yJsfkH7CnubShCuEb82qKCD4zf50hyHxZu
>>>fj
>>>glf9NefAuIXRJmmXe10afkEVYHARondjCtJ80RkovHVtQHkErX9s2wB2HT9Zx7kuKGdYmigV
>>>Q8
>>>_AjqFyusOCQ6XTplJOlr4ZdvSZoafu0dowEYJysruLtBvY9qsi5eMXC4ozvodmRUfB

Re: Resetting a VM is broken?

Right...that would be great, as well.


On Thu, Mar 20, 2014 at 3:45 PM, Jessica Wang wrote:

>  Also:
>
> (3) Change Reinstall icon to use a 'recycle' symbol, to avoid confusion w/
> reboot VM
>
>
>
>
>
>
>
> *From:* Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> *Sent:* Thursday, March 20, 2014 2:43 PM
> *To:* Jessica Wang
> *Cc:* Brian Federle; n...@li.nux.ro; dev@cloudstack.apache.org;
> Harikrishna Patnala; Alena Prokharchyk; Stephen Turner
>
> *Subject:* Re: Resetting a VM is broken?
>
>
>
> Works for me. Thanks!
>
>
>
> On Thu, Mar 20, 2014 at 3:41 PM, Jessica Wang 
> wrote:
>
> So, we'll change UI to:
>
> (1) Label the action icon that fires recoverVirtualMachine API as
> "Recover".
> Label the action icon that fires restoreVirtualMachine API as
> "Reinstall".
>
> (2) change text in confirmation dialog of Reinstall action as:
> "The VM will be reinstalled from template, all current data will be lost,
> proceed with caution! Extra data volumes, if any, will not be touched."
>
>
>
>
> -Original Message-
> From: Nux! [mailto:n...@li.nux.ro]
> Sent: Thursday, March 20, 2014 2:04 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Resetting a VM is broken?
>
> On 20.03.2014 20:54, Mike Tutkowski wrote:
> > The only technicality is that data on data disks won't be lost (just
> > the
> > root disk).
>
> Yes, that is true, we can add something like: "Extra data volumes, if
> any, will not be touched."
>
> HTH
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
>
>
>
>
> --
> *Mike Tutkowski*
>
> *Senior CloudStack Developer, SolidFire Inc.*
>
> e: mike.tutkow...@solidfire.com
>
> o: 303.746.7302
>
> Advancing the way the world uses the 
> cloud
> *(tm)*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

RE: Resetting a VM is broken?

Also:
(3) Change Reinstall icon to use a 'recycle' symbol, to avoid confusion w/ 
reboot VM

From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Thursday, March 20, 2014 2:43 PM
To: Jessica Wang
Cc: Brian Federle; n...@li.nux.ro; dev@cloudstack.apache.org; Harikrishna 
Patnala; Alena Prokharchyk; Stephen Turner
Subject: Re: Resetting a VM is broken?

Works for me. Thanks!

On Thu, Mar 20, 2014 at 3:41 PM, Jessica Wang 
mailto:jessica.w...@citrix.com>> wrote:
So, we'll change UI to:

(1) Label the action icon that fires recoverVirtualMachine API as "Recover".
Label the action icon that fires restoreVirtualMachine API as "Reinstall".

(2) change text in confirmation dialog of Reinstall action as:
"The VM will be reinstalled from template, all current data will be lost, 
proceed with caution! Extra data volumes, if any, will not be touched."

-Original Message-
From: Nux! [mailto:n...@li.nux.ro]
Sent: Thursday, March 20, 2014 2:04 PM
To: dev@cloudstack.apache.org
Subject: Re: Resetting a VM is broken?
On 20.03.2014 20:54, Mike Tutkowski wrote:
> The only technicality is that data on data disks won't be lost (just
> the
> root disk).

Yes, that is true, we can add something like: "Extra data volumes, if
any, will not be touched."

HTH

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

--
Mike Tutkowski
Senior CloudStack Developer, SolidFire Inc.
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the 
cloud(tm)

Re: Resetting a VM is broken?

Works for me. Thanks!


On Thu, Mar 20, 2014 at 3:41 PM, Jessica Wang wrote:

> So, we'll change UI to:
>
> (1) Label the action icon that fires recoverVirtualMachine API as
> "Recover".
> Label the action icon that fires restoreVirtualMachine API as
> "Reinstall".
>
> (2) change text in confirmation dialog of Reinstall action as:
> "The VM will be reinstalled from template, all current data will be lost,
> proceed with caution! Extra data volumes, if any, will not be touched."
>
>
>
> -Original Message-
> From: Nux! [mailto:n...@li.nux.ro]
> Sent: Thursday, March 20, 2014 2:04 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Resetting a VM is broken?
>
> On 20.03.2014 20:54, Mike Tutkowski wrote:
> > The only technicality is that data on data disks won't be lost (just
> > the
> > root disk).
>
> Yes, that is true, we can add something like: "Extra data volumes, if
> any, will not be touched."
>
> HTH
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

RE: Resetting a VM is broken?

So, we'll change UI to:

(1) Label the action icon that fires recoverVirtualMachine API as "Recover". 
Label the action icon that fires restoreVirtualMachine API as "Reinstall". 

(2) change text in confirmation dialog of Reinstall action as: 
"The VM will be reinstalled from template, all current data will be lost, 
proceed with caution! Extra data volumes, if any, will not be touched."

-Original Message-
From: Nux! [mailto:n...@li.nux.ro] 
Sent: Thursday, March 20, 2014 2:04 PM
To: dev@cloudstack.apache.org
Subject: Re: Resetting a VM is broken?

On 20.03.2014 20:54, Mike Tutkowski wrote:
> The only technicality is that data on data disks won't be lost (just 
> the
> root disk).

Yes, that is true, we can add something like: "Extra data volumes, if 
any, will not be touched."

HTH

-- 
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

[REQUEST] Using prefixes for ML discussions

2014-03-20 Thread Sudha Ponnaganti

Hi,

We have been using release tags as prefixes i.e ACS43, ACS44 etc for mailing 
list discussions. These days these prefixes are missing for some of the 
discussions. If community can use those prefixes, it would be very helpful to 
follow relevant discussions.

Thanks
/Sudha

RE: [VOTE] Apache CloudStack 4.3.0 (ninth round)

2014-03-20 Thread Edison Su

+1(binding) After fixed the serious bugs in security group in the last round.

> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Tuesday, March 18, 2014 12:06 PM
> To: dev@cloudstack.apache.org
> Subject: [VOTE] Apache CloudStack 4.3.0 (ninth round)
> 
> 
> 
> 
> Hi All,
> 
> 
> 
> I've created a 4.3.0 release, with the following artifacts up for a
> 
> vote:
> 
> 
> 
> 
> 
> Git Branch and Commit SH:
> 
> https://git-wip-
> us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
> Commit:  0810029f274878eca8fd74b44ab1117054e929a5
> 
> 
> List of changes:
> 
> New Features in 4.3: https://issues.apache.org/jira/issues/?filter=12325248
> 
> Improvement in 4.3: https://issues.apache.org/jira/issues/?filter=12325249
> 
> Issues fixed in 4.3 https://issues.apache.org/jira/issues/?filter=12326161
> 
> Known Issues in 4.3: https://issues.apache.org/jira/issues/?filter=12326162
> 
> 
> 
> 
> 
> 
> 
> Source release (checksums and signatures are available at the same
> 
> location):
> 
> https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
> 
> 
> 
> PGP release keys (signed using 94BE0D7C):
> 
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> 
> 
> 
> Testing instructions are here:
> 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+pr
> ocedure
> 
> 
> 
> Vote will be open for 72 hours (Friday 3/21 12:05 PM PST)
> 
> 
> 
> For sanity in tallying the vote, can PMC members please be sure to indicate
> "(binding)" with their vote?
> 
> 
> 
> [ ] +1  approve
> 
> [ ] +0  no opinion
> 
> [ ] -1  disapprove (and reason why)
> 
> 
> 
> Thanks
> 
> Animesh
>

Re: [VOTE] Apache CloudStack 4.3.0 (ninth round)

Yet I see https in the url after a db clean and rebuild and reinstall
of a vpc with tier and guest vm.

On Thu, Mar 20, 2014 at 9:44 PM, Animesh Chaturvedi
 wrote:
>
>
>> -Original Message-
>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>> Sent: Thursday, March 20, 2014 10:25 AM
>> To: dev
>> Cc: Amogh Vasekar; Suresh Sadhu
>> Subject: Re: [VOTE] Apache CloudStack 4.3.0 (ninth round)
>>
>> On Thu, Mar 20, 2014 at 6:21 PM, Animesh Chaturvedi
>>  wrote:
>> > should work
>>
>>
>> You mean 'should work" after default installation, Animesh?
>> consoleproxy.url.domain is empty.
> [Animesh] Yes and that will default as http
>>
>> thanks,
>> --
>> Daan



-- 
Daan

Re: Resetting a VM is broken?


On 20.03.2014 20:54, Mike Tutkowski wrote:
The only technicality is that data on data disks won't be lost (just 
the

root disk).


Yes, that is true, we can add something like: "Extra data volumes, if 
any, will not be touched."


HTH

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

RE: Resetting a VM is broken?

Yes, "Reinstall VM" sounds clearer.


-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] 
Sent: Thursday, March 20, 2014 1:54 PM
To: dev@cloudstack.apache.org
Subject: Re: Resetting a VM is broken?

I also like Reinstall VM for the text (even if it doesn't match the API's
name).


On Thu, Mar 20, 2014 at 2:53 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> That sounds great. Let's go with your text. Thanks!
>
>
> On Thu, Mar 20, 2014 at 2:51 PM, Nux!  wrote:
>
>> On 20.03.2014 19:35, Mike Tutkowski wrote:
>>
>>> This action will restore the VM to a fresh root disk. After this action,
>>> the
>>> current root disk will be destroyed and un-recoverable.
>>>
>>> Just curious, Lucian - what is your recommended text?
>>>
>>
>> Your text is great, but it sounds like from a dev to a dev.
>>
>> I'd name the button "Reinstall VM" and say something like "The VM will be
>> reinstalled from template, all current data will be lost, proceed with
>> caution!"
>>
>> Sounds more end-user friendly. :)
>>
>>
>> Lucian
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the 
> cloud
> *(tm)*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

RE: Resetting a VM is broken?

+1

-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] 
Sent: Thursday, March 20, 2014 1:53 PM
To: dev@cloudstack.apache.org
Subject: Re: Resetting a VM is broken?

That sounds great. Let's go with your text. Thanks!


On Thu, Mar 20, 2014 at 2:51 PM, Nux!  wrote:

> On 20.03.2014 19:35, Mike Tutkowski wrote:
>
>> This action will restore the VM to a fresh root disk. After this action,
>> the
>> current root disk will be destroyed and un-recoverable.
>>
>> Just curious, Lucian - what is your recommended text?
>>
>
> Your text is great, but it sounds like from a dev to a dev.
>
> I'd name the button "Reinstall VM" and say something like "The VM will be
> reinstalled from template, all current data will be lost, proceed with
> caution!"
>
> Sounds more end-user friendly. :)
>
>
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

Re: Resetting a VM is broken?

The only technicality is that data on data disks won't be lost (just the
root disk).


On Thu, Mar 20, 2014 at 2:54 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> I also like Reinstall VM for the text (even if it doesn't match the API's
> name).
>
>
> On Thu, Mar 20, 2014 at 2:53 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> That sounds great. Let's go with your text. Thanks!
>>
>>
>> On Thu, Mar 20, 2014 at 2:51 PM, Nux!  wrote:
>>
>>> On 20.03.2014 19:35, Mike Tutkowski wrote:
>>>
 This action will restore the VM to a fresh root disk. After this
 action, the
 current root disk will be destroyed and un-recoverable.

 Just curious, Lucian - what is your recommended text?

>>>
>>> Your text is great, but it sounds like from a dev to a dev.
>>>
>>> I'd name the button "Reinstall VM" and say something like "The VM will
>>> be reinstalled from template, all current data will be lost, proceed with
>>> caution!"
>>>
>>> Sounds more end-user friendly. :)
>>>
>>>
>>> Lucian
>>>
>>> --
>>> Sent from the Delta quadrant using Borg technology!
>>>
>>> Nux!
>>> www.nux.ro
>>>
>>
>>
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkow...@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the 
>> cloud
>> *(tm)*
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the 
> cloud
> *(tm)*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

Re: Resetting a VM is broken?

I also like Reinstall VM for the text (even if it doesn't match the API's
name).


On Thu, Mar 20, 2014 at 2:53 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> That sounds great. Let's go with your text. Thanks!
>
>
> On Thu, Mar 20, 2014 at 2:51 PM, Nux!  wrote:
>
>> On 20.03.2014 19:35, Mike Tutkowski wrote:
>>
>>> This action will restore the VM to a fresh root disk. After this action,
>>> the
>>> current root disk will be destroyed and un-recoverable.
>>>
>>> Just curious, Lucian - what is your recommended text?
>>>
>>
>> Your text is great, but it sounds like from a dev to a dev.
>>
>> I'd name the button "Reinstall VM" and say something like "The VM will be
>> reinstalled from template, all current data will be lost, proceed with
>> caution!"
>>
>> Sounds more end-user friendly. :)
>>
>>
>> Lucian
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the 
> cloud
> *(tm)*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

Re: Resetting a VM is broken?

That sounds great. Let's go with your text. Thanks!


On Thu, Mar 20, 2014 at 2:51 PM, Nux!  wrote:

> On 20.03.2014 19:35, Mike Tutkowski wrote:
>
>> This action will restore the VM to a fresh root disk. After this action,
>> the
>> current root disk will be destroyed and un-recoverable.
>>
>> Just curious, Lucian - what is your recommended text?
>>
>
> Your text is great, but it sounds like from a dev to a dev.
>
> I'd name the button "Reinstall VM" and say something like "The VM will be
> reinstalled from template, all current data will be lost, proceed with
> caution!"
>
> Sounds more end-user friendly. :)
>
>
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

Re: Resetting a VM is broken?


On 20.03.2014 19:35, Mike Tutkowski wrote:
This action will restore the VM to a fresh root disk. After this 
action, the

current root disk will be destroyed and un-recoverable.

Just curious, Lucian - what is your recommended text?


Your text is great, but it sounds like from a dev to a dev.

I'd name the button "Reinstall VM" and say something like "The VM will 
be reinstalled from template, all current data will be lost, proceed 
with caution!"


Sounds more end-user friendly. :)

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

RE: concole proxy in 4.3RC9



> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Thursday, March 20, 2014 9:50 AM
> To: dev
> Subject: Re: concole proxy in 4.3RC9
> 
> meaning the console of the ssvm? or the cpvm?
> 
> I just confirmed myself that there is indeed a diff between 4.2.1 and 4.3RC9
[Animesh] Ofcourse there is that's the change in this commit 
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=ec4db7bbff60f0be96e39f51c0f17b12e0de440c

> 
> On Thu, Mar 20, 2014 at 5:32 PM, Nux!  wrote:
> > On 20.03.2014 16:29, Ove Ewerlid wrote:
> >>
> >> Console SSVM works in my 4.3 setup.
> >> Traffic does not use SSL and is on port 80.
> >
> >
> > Did you have to do anything in particular to disable SSL or is this
> > the new default?
> >
> > I was having problems with 4.4 where VC VM was in Alert mode and the
> VMs'
> > console was dead; will have to revisit this.
> >
> > Lucian
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
> 
> 
> 
> --
> Daan

RE: [VOTE] Apache CloudStack 4.3.0 (ninth round)



> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Thursday, March 20, 2014 10:25 AM
> To: dev
> Cc: Amogh Vasekar; Suresh Sadhu
> Subject: Re: [VOTE] Apache CloudStack 4.3.0 (ninth round)
> 
> On Thu, Mar 20, 2014 at 6:21 PM, Animesh Chaturvedi
>  wrote:
> > should work
> 
> 
> You mean 'should work" after default installation, Animesh?
> consoleproxy.url.domain is empty.
[Animesh] Yes and that will default as http
> 
> thanks,
> --
> Daan

Re: Errors building master

never mind, chris did it

On Thu, Mar 20, 2014 at 9:13 PM, Daan Hoogland  wrote:
> On Thu, Mar 20, 2014 at 7:11 PM, Alex Hitchins
>  wrote:
>> VolumeServiceImpl.java
>
>
> which one is that?
>
>
> --
> Daan



-- 
Daan

Re: Errors building master

On Thu, Mar 20, 2014 at 7:11 PM, Alex Hitchins
 wrote:
> VolumeServiceImpl.java


which one is that?


-- 
Daan

Re: concole proxy in 4.3RC9

Amogh, I am running the ms on windows but I did build a 4.3 systemvm
on a differnt machine and copied it to the hypervisors. port 80 can go
to the hypervisor which says that it does not have the page /console

On Thu, Mar 20, 2014 at 7:45 PM, Amogh Vasekar  wrote:
> Hi,
>
> Tried on XenServer set-up, and the defaults work fine for me. The console
> URL for me :
> 2014-03-20 18:43:08,558 DEBUG [c.c.s.ConsoleProxyServlet]
> (24565443@qtp-27436568-8:null) Compose console url:
> http://192.168.56.139/ajax?token=tVsokSDt2PUASaa77NN_qBAZFJsma76qRT5Y1OLQFW
> 1zl82-vizkq36Fii1yLNvR1h7Ul3CL0L8yrtn2y7FkqLgZyXFc3bObM5U2H6n-3CO01d-zqJGxq
> hNom6i-oUEgQhp-QPJ0rKkEZErTeYF6YyMwHghWabLuAyDYYT9gA39VWAVHcySUtSjFcjRFWhIA
> vOs9RghpY9D6rvzgjeCvBOuy4aOD1kQlT_7lUIX3BIcLyipMR200o0y2ZjAfxwdfN-9oyMuuUjr
> YsObY9xb-BQxOb5p5cZogqqqiCnXGhr1mPwlN6Ba-BI-UQzgNjlHX95sp0x_hnHhdzMfZ0vfaAo
> 7SZLrfD1oGRxMOWFonu-WHSsu4OBcDSELFxd-2Yt_noZ6Mdz2kheMvGfYmFC2r1gjii0rxzuj8L
> w8p42DZAGLq8TqSWyBUGsQWhMveyHVJHbKJDrsOcJVMyUdDLKsVhGR9voti7TJUAAzQb75Ahaw
>
> Just to reconfirm - did you build using systemvm profile? Is port 80
> blocked somewhere?
>
> Thanks,
> Amogh
>
> On 3/20/14 10:15 AM, "Daan Hoogland"  wrote:
>
>>btw
>>
>>the last lines:
>>
>>2014-03-20 13:57:09,858 DEBUG [c.c.a.t.Request]
>>(1372260265@qtp-1676921458-10:null) Seq 1-762183775: Sending  { Cmd ,
>>MgmtId: 24062491136, via: 1(mccdxen2), Ver: v1, Flags: 100011,
>>[{"com.cloud.agent.api.GetVncPortCommand":{"id":5,"name":"i-2-5-VM","wait"
>>:0}}]
>>}
>>2014-03-20 13:57:09,858 DEBUG [c.c.a.t.Request]
>>(1372260265@qtp-1676921458-10:null) Seq 1-762183775: Executing:  { Cmd
>>, MgmtId: 24062491136, via: 1(mccdxen2), Ver: v1, Flags: 100011,
>>[{"com.cloud.agent.api.GetVncPortCommand":{"id":5,"name":"i-2-5-VM","wait"
>>:0}}]
>>}
>>2014-03-20 13:57:09,859 DEBUG [c.c.a.m.DirectAgentAttache]
>>(DirectAgent-63:ctx-6c8a6687) Seq 1-762183775: Executing request
>>2014-03-20 13:57:09,976 DEBUG [c.c.a.m.DirectAgentAttache]
>>(DirectAgent-63:ctx-6c8a6687) Seq 1-762183775: Response Received:
>>2014-03-20 13:57:09,976 DEBUG [c.c.a.t.Request]
>>(DirectAgent-63:ctx-6c8a6687) Seq 1-762183775: Processing:  { Ans: ,
>>MgmtId: 24062491136, via: 1, Ver: v1, Flags: 10,
>>[{"com.cloud.agent.api.GetVncPortAnswer":{"address":"consoleurl=https://10
>>.200.23.42/console?uuid=d539642a-7c78-622e-9c22-e6b3b0771122&sessionref=Op
>>aqueRef:160e30d3-5f3e-255e-ef8a-596e69ad30d4","port":-1,"result":true,"wai
>>t":0}}]
>>}
>>2014-03-20 13:57:09,976 DEBUG [c.c.a.t.Request]
>>(1372260265@qtp-1676921458-10:null) Seq 1-762183775: Received:  { Ans:
>>, MgmtId: 24062491136, via: 1, Ver: v1, Flags: 10, { GetVncPortAnswer
>>} }
>>2014-03-20 13:57:09,976 DEBUG [c.c.s.ConsoleProxyServlet]
>>(1372260265@qtp-1676921458-10:null) Port info
>>consoleurl=https://10.200.23.42/console?uuid=d539642a-7c78-622e-9c22-e6b3b
>>0771122&sessionref=OpaqueRef:160e30d3-5f3e-255e-ef8a-596e69ad30d4
>>2014-03-20 13:57:09,976 INFO  [c.c.s.ConsoleProxyServlet]
>>(1372260265@qtp-1676921458-10:null) Parse host info returned from
>>executing GetVNCPortCommand. host info:
>>consoleurl=https://10.200.23.42/console?uuid=d539642a-7c78-622e-9c22-e6b3b
>>0771122&sessionref=OpaqueRef:160e30d3-5f3e-255e-ef8a-596e69ad30d4
>>2014-03-20 13:57:09,979 DEBUG [c.c.s.ConsoleProxyServlet]
>>(1372260265@qtp-1676921458-10:null) Compose console url:
>>http://195.66.90.213/ajax?token=9Rrl0mjwUQd3Ym9mEb-ziydOD0YOSWJNi_QZFP7efE
>>r1mIalpz2Xg0UvR2eUUyqbgFqNXQJOlt0yJsfkH7CnubShCuEb82qKCD4zf50hyHxZufjglf9N
>>efAuIXRJmmXe10afkEVYHARondjCtJ80RkovHVtQHkErX9s2wB2HT9Zx7kuKGdYmigVQ8_AjqF
>>yusOCQ6XTplJOlr4ZdvSZoafu0dowEYJysruLtBvY9qsi5eMXC4ozvodmRUfBN4jARisUjusBC
>>DUSzQyrdXImCjLFT3cL1GVmdNPQz7L7s3PJrSyMdB9ZZshnzNYAYkCjUtjiLwAf3aJfZt3z3r9
>>TuJg6k5kfhRbBsvpBVtrYcI1DXJfEANZD6g9f4hDRghnsXxrUpPrA973CiSUaKsKzUMqVWM4Vu
>>iDtHkWIgk_p100K-ai9wzufJYAk9lZ_vhY9GWYkQhpBtZeupk3Gl5Gc_iudCMwP9kFvEA12i6j
>>Nvtng
>>2014-03-20 13:57:09,979 DEBUG [c.c.s.ConsoleProxyServlet]
>>(1372260265@qtp-1676921458-10:null) the console url is ::
>>g>src="http://195.66.90.213/ajax?token=9Rrl0mjwUQd3Ym9mEb-ziydOD0YOSWJNi_QZF
>>P7efEr1mIalpz2Xg0UvR2eUUyqbgFqNXQJOlt0yJsfkH7CnubShCuEb82qKCD4zf50hyHxZufj
>>glf9NefAuIXRJmmXe10afkEVYHARondjCtJ80RkovHVtQHkErX9s2wB2HT9Zx7kuKGdYmigVQ8
>>_AjqFyusOCQ6XTplJOlr4ZdvSZoafu0dowEYJysruLtBvY9qsi5eMXC4ozvodmRUfBN4jARisU
>>jusBCDUSzQyrdXImCjLFT3cL1GVmdNPQz7L7s3PJrSyMdB9ZZshnzNYAYkCjUtjiLwAf3aJfZt
>>3z3r9TuJg6k5kfhRbBsvpBVtrYcI1DXJfEANZD6g9f4hDRghnsXxrUpPrA973CiSUaKsKzUMqV
>>WM4VuiDtHkWIgk_p100K-ai9wzufJYAk9lZ_vhY9GWYkQhpBtZeupk3Gl5Gc_iudCMwP9kFvEA
>>12i6jNvtng">
>>
>>and next nothing but the browser saying connection refused.
>>
>>So what changed? Where do I need to adjust my infra to make it work
>>again? Or is my setup not supported anymore?
>>
>>On Thu, Mar 20, 2014 at 5:49 PM, Daan Hoogland 
>>wrote:
>>> meaning the console of the ssvm? or the cpvm?
>>>
>>> I just confirmed myself that there is indeed a diff between 4.2.1 and
>>>4.3RC9
>>>
>>> On Thu, Mar 20, 2014 at 5:32 PM, Nux!  wrote:
>>

Re: Review Request 12228: static resource compression


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

(Updated March 20, 2014, 7:53 p.m.)


Review request for cloudstack, Brian Federle, Darren Shepherd, and Prasanna 
Santhanam.


Changes
---

spaces


Repository: cloudstack-git


Description
---

CloudStack at first use downloads some 3.5 MB of css and javascript to the 
client. With a weak internet connection, this might take a long time. With gzip 
compression content can be compressed to 850 KB.

This version of the patch uses a custom plugin to compress static resources, so 
that no dynamic compression is needed at runtime. When the static resource 
servlet notices that there is gzipped version of the resource and the client 
accepts gzipped content, then it is going to send the gziped version, while 
still respects http caching.


Diffs (updated)
-

  client/WEB-INF/web.xml 1af38e1 
  client/pom.xml d8dbde7 
  server/src/com/cloud/servlet/StaticResourceServlet.java PRE-CREATION 
  server/test/com/cloud/servlet/StaticResourceServletTest.java PRE-CREATION 

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


Testing
---

yes, tested with firefox and chrome


Thanks,

Laszlo Hornyak

Re: Commit Revert Request

2014-03-20 Thread SuichII, Christopher

I have reverted the commits on 4.4 and master.

Sorry about that, everyone. I thought I recompiled after applying the patch but 
I must have missed a step…

-Chris
-- 
Chris Suich
chris.su...@netapp.com
NetApp Software Engineer
Data Center Platforms – Cloud Solutions
Citrix, Cisco & Red Hat

On Mar 20, 2014, at 3:22 PM, Alex Hitchins  wrote:

> All,
> 
> Can someone with committer permission please revert this commit?
> 
> 9a615ee7b26547f0c439faf04e5fbf91dc2cbeb1
> 
> It's causing the master branch to fail on build. I attempted to upload a 
> patch to revert however the review board said the file didn't exist (which 
> confused me).
> 
> I'll go back to my original fix once this has been undone.
> 
> Regards
> 
> Alex Hitchins
> 
> D: +44 1892 523 587 | S: +44 2036 030 540 | M: +44 7788 423 969
> 
> alex.hitch...@shapeblue.com
> 
> -Original Message-
> From: Alex Hitchins [mailto:alex.hitch...@shapeblue.com]
> Sent: 20 March 2014 18:07
> To: dev@cloudstack.apache.org
> Subject: RE: Errors building master
> 
> Ah, yes - that's related to my last patch. I'll log it and raise a new 
> request.
> 
> Sorry everyone.
> 
> 
> Regards
> 
> Alex Hitchins
> 
> D: +44 1892 523 587 | S: +44 2036 030 540 | M: +44 7788 423 969
> 
> alex.hitch...@shapeblue.com
> 
> -Original Message-
> From: Laszlo Hornyak [mailto:laszlo.horn...@gmail.com]
> Sent: 20 March 2014 17:59
> To: dev@cloudstack.apache.org
> Subject: Re: Errors building master
> 
> Hi Alex,
> 
> It should be OK if you recompile, the required module is in the module tree.
> Btw I am getting a compile error:
> engine/storage/volume/src/org/apache/cloudstack/storage/volume/VolumeServiceImpl.java:[1502,12]
> error: unreported exception ResourceAllocationException; must be caught or 
> declared to be thrown
> 
> 
> 
> 
> On Thu, Mar 20, 2014 at 12:40 PM, Alex Hitchins > wrote:
> 
>> 
>> Anyone else seing this?
>> 
>> [ERROR] Failed to execute goal on project cloud-client-ui: Could not
>> resolve dependencies for project
>> org.apache.cloudstack:cloud-client-ui:war:4.5.0-SNAPSHOT:
>> Could not find artifact
>> org.apache.cloudstack:cloud-plugin-storage-volume-cloudbyte:jar:4.5.0-
>> SNAPSHOT in apache.snapshots (http://repository.apache.org/snapshots)
>> -> [Help 1]
>> 
>> Is there somewhere I can manually download the cloudbyte dependency?
>> 
>> Alex
>> 
>> .
>> Need Enterprise Grade Support for Apache CloudStack?
>> Our CloudStack Infrastructure Support<
>> http://shapeblue.com/cloudstack-infrastructure-support/> offers the
>> best
>> 24/7 SLA for CloudStack Environments.
>> 
>> Apache CloudStack Bootcamp training courses
>> 
>> **NEW!** CloudStack 4.2.1 training<
>> http://shapeblue.com/cloudstack-training/>
>> 18th-19th February 2014, Brazil. Classroom<
>> http://shapeblue.com/cloudstack-training/>
>> 17th-23rd March 2014, Region A. Instructor led, On-line<
>> http://shapeblue.com/cloudstack-training/>
>> 24th-28th March 2014, Region B. Instructor led, On-line<
>> http://shapeblue.com/cloudstack-training/>
>> 16th-20th June 2014, Region A. Instructor led, On-line<
>> http://shapeblue.com/cloudstack-training/>
>> 23rd-27th June 2014, Region B. Instructor led, On-line<
>> http://shapeblue.com/cloudstack-training/>
>> 
>> This email and any attachments to it may be confidential and are
>> intended solely for the use of the individual to whom it is addressed.
>> Any views or opinions expressed are solely those of the author and do
>> not necessarily represent those of Shape Blue Ltd or related
>> companies. If you are not the intended recipient of this email, you
>> must neither take any action based upon its contents, nor copy or show
>> it to anyone. Please contact the sender if you believe you have
>> received this email in error. Shape Blue Ltd is a company incorporated
>> in England & Wales. ShapeBlue Services India LLP is a company
>> incorporated in India and is operated under license from Shape Blue
>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
>> Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a 
>> registered trademark.
>> 
> 
> 
> 
> --
> 
> EOF
> This email and any attachments to it may be confidential and are intended 
> solely for the use of the individual to whom it is addressed. Any views or 
> opinions expressed are solely those of the author and do not necessarily 
> represent those of Shape Blue Ltd or related companies. If you are not the 
> intended recipient of this email, you must neither take any action based upon 
> its contents, nor copy or show it to anyone. Please contact the sender if you 
> believe you have received this email in error. Shape Blue Ltd is a company 
> incorporated in England & Wales. ShapeBlue Services India LLP is a company 
> incorporated in India and is operated under license from Shape Blue Ltd. 
> Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
> operated under license from Shape Blue Ltd. ShapeBlue is a registered 
> trad

Re: Resetting a VM is broken?

This action will restore the VM to a fresh root disk. After this action, the
current root disk will be destroyed and un-recoverable.

Just curious, Lucian - what is your recommended text?

Thanks


On Thu, Mar 20, 2014 at 1:33 PM, Nux!  wrote:

> On 20.03.2014 19:21, Mike Tutkowski wrote:
>
>> Personally I prefer something more along these lines:
>>
>> This action will restore the VM to a fresh root disk. After this action,
>> the current root disk will be destroyed.
>>
>
> I'm fine with either, I already know what it does. It depends how much you
> want to dumb down the message, to some non-technical users it might not be
> very clear.
>
>
> Just my 2 slips of gold-pressed latinum,
>
> Lucian
>
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

Re: Resetting a VM is broken?


On 20.03.2014 19:21, Mike Tutkowski wrote:

Personally I prefer something more along these lines:

This action will restore the VM to a fresh root disk. After this 
action,

the current root disk will be destroyed.


I'm fine with either, I already know what it does. It depends how much 
you want to dumb down the message, to some non-technical users it might 
not be very clear.



Just my 2 slips of gold-pressed latinum,

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Re: Resetting a VM is broken?

Great - thanks!


On Thu, Mar 20, 2014 at 1:30 PM, Brian Federle wrote:

> OK, sounds good :)
> On Mar 20, 2014, at 12:21 PM, Mike Tutkowski 
> wrote:
>
> > Personally I prefer something more along these lines:
> >
> > This action will restore the VM to a fresh root disk. After this action,
> > the current root disk will be destroyed.
> >
> >
> > On Thu, Mar 20, 2014 at 1:19 PM, Brian Federle  >wrote:
> >
> >> I was just using what was suggested earlier in the thread (I'm not
> really
> >> familiar with the feature); if that is incorrect then I can change it to
> >> say,
> >>
> >> "Warning: this action is irreversible. If you continue you may lose
> data.
> >> Please confirm that you would like to proceed."
> >>
> >> -Brian
> >>
> >> On Mar 20, 2014, at 12:08 PM, Nux!  wrote:
> >>
> >>> On 20.03.2014 18:55, Brian Federle wrote:
>  Those suggestions sound good. Here are the changes I will make in the
> >> UI:
>  - Change icon to use a 'recycle' symbol, to avoid confusion w/ reboot
> VM
>  - Rename action(s) to reflect the name of the API calls.
>  - Update the confirm dialog to say, "This action will restore the VM
>  to a fresh root disk. After this action, the current root disk will be
>  attached to the VM."
> >>>
> >>> "After this action, the current root disk will be attached to the VM."
> >> <- What does this mean? To me it sounds like the VM gets re-instantiated
> >> from template and the "current" root disk will be attached as a volume,
> in
> >> addition to a _new_ root disk. This is not what is happening.
> >>>
> >>> People need to be aware that this action is irreversible and THEY WILL
> >> LOSE DATA, the message should say this.
> >>>
> >>>
> >>> --
> >>> Sent from the Delta quadrant using Borg technology!
> >>>
> >>> Nux!
> >>> www.nux.ro
> >>
> >>
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud
> > *(tm)*
>
>


-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

Re: Resetting a VM is broken?

OK, sounds good :)
On Mar 20, 2014, at 12:21 PM, Mike Tutkowski  
wrote:

> Personally I prefer something more along these lines:
> 
> This action will restore the VM to a fresh root disk. After this action,
> the current root disk will be destroyed.
> 
> 
> On Thu, Mar 20, 2014 at 1:19 PM, Brian Federle 
> wrote:
> 
>> I was just using what was suggested earlier in the thread (I'm not really
>> familiar with the feature); if that is incorrect then I can change it to
>> say,
>> 
>> "Warning: this action is irreversible. If you continue you may lose data.
>> Please confirm that you would like to proceed."
>> 
>> -Brian
>> 
>> On Mar 20, 2014, at 12:08 PM, Nux!  wrote:
>> 
>>> On 20.03.2014 18:55, Brian Federle wrote:
 Those suggestions sound good. Here are the changes I will make in the
>> UI:
 - Change icon to use a 'recycle' symbol, to avoid confusion w/ reboot VM
 - Rename action(s) to reflect the name of the API calls.
 - Update the confirm dialog to say, "This action will restore the VM
 to a fresh root disk. After this action, the current root disk will be
 attached to the VM."
>>> 
>>> "After this action, the current root disk will be attached to the VM."
>> <- What does this mean? To me it sounds like the VM gets re-instantiated
>> from template and the "current" root disk will be attached as a volume, in
>> addition to a _new_ root disk. This is not what is happening.
>>> 
>>> People need to be aware that this action is irreversible and THEY WILL
>> LOSE DATA, the message should say this.
>>> 
>>> 
>>> --
>>> Sent from the Delta quadrant using Borg technology!
>>> 
>>> Nux!
>>> www.nux.ro
>> 
>> 
> 
> 
> -- 
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *(tm)*

Commit Revert Request

All,

Can someone with committer permission please revert this commit?

9a615ee7b26547f0c439faf04e5fbf91dc2cbeb1

It's causing the master branch to fail on build. I attempted to upload a patch 
to revert however the review board said the file didn't exist (which confused 
me).

I'll go back to my original fix once this has been undone.

Regards

Alex Hitchins

D: +44 1892 523 587 | S: +44 2036 030 540 | M: +44 7788 423 969

alex.hitch...@shapeblue.com

-Original Message-
From: Alex Hitchins [mailto:alex.hitch...@shapeblue.com]
Sent: 20 March 2014 18:07
To: dev@cloudstack.apache.org
Subject: RE: Errors building master

Ah, yes - that's related to my last patch. I'll log it and raise a new request.

Sorry everyone.

Regards

Alex Hitchins

D: +44 1892 523 587 | S: +44 2036 030 540 | M: +44 7788 423 969

alex.hitch...@shapeblue.com

-Original Message-
From: Laszlo Hornyak [mailto:laszlo.horn...@gmail.com]
Sent: 20 March 2014 17:59
To: dev@cloudstack.apache.org
Subject: Re: Errors building master

Hi Alex,

It should be OK if you recompile, the required module is in the module tree.
Btw I am getting a compile error:
engine/storage/volume/src/org/apache/cloudstack/storage/volume/VolumeServiceImpl.java:[1502,12]
error: unreported exception ResourceAllocationException; must be caught or 
declared to be thrown

On Thu, Mar 20, 2014 at 12:40 PM, Alex Hitchins  wrote:

>
> Anyone else seing this?
>
> [ERROR] Failed to execute goal on project cloud-client-ui: Could not
> resolve dependencies for project
> org.apache.cloudstack:cloud-client-ui:war:4.5.0-SNAPSHOT:
> Could not find artifact
> org.apache.cloudstack:cloud-plugin-storage-volume-cloudbyte:jar:4.5.0-
> SNAPSHOT in apache.snapshots (http://repository.apache.org/snapshots)
> -> [Help 1]
>
> Is there somewhere I can manually download the cloudbyte dependency?
>
> Alex
>
> .
> Need Enterprise Grade Support for Apache CloudStack?
> Our CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/> offers the
> best
> 24/7 SLA for CloudStack Environments.
>
> Apache CloudStack Bootcamp training courses
>
> **NEW!** CloudStack 4.2.1 training<
> http://shapeblue.com/cloudstack-training/>
> 18th-19th February 2014, Brazil. Classroom<
> http://shapeblue.com/cloudstack-training/>
> 17th-23rd March 2014, Region A. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
> 24th-28th March 2014, Region B. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
> 16th-20th June 2014, Region A. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
> 23rd-27th June 2014, Region B. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
>
> This email and any attachments to it may be confidential and are
> intended solely for the use of the individual to whom it is addressed.
> Any views or opinions expressed are solely those of the author and do
> not necessarily represent those of Shape Blue Ltd or related
> companies. If you are not the intended recipient of this email, you
> must neither take any action based upon its contents, nor copy or show
> it to anyone. Please contact the sender if you believe you have
> received this email in error. Shape Blue Ltd is a company incorporated
> in England & Wales. ShapeBlue Services India LLP is a company
> incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
> Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a 
> registered trademark.
>

--

EOF
This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in Engl

Re: Resetting a VM is broken?

Personally I prefer something more along these lines:

This action will restore the VM to a fresh root disk. After this action,
the current root disk will be destroyed.


On Thu, Mar 20, 2014 at 1:19 PM, Brian Federle wrote:

> I was just using what was suggested earlier in the thread (I'm not really
> familiar with the feature); if that is incorrect then I can change it to
> say,
>
> "Warning: this action is irreversible. If you continue you may lose data.
> Please confirm that you would like to proceed."
>
> -Brian
>
> On Mar 20, 2014, at 12:08 PM, Nux!  wrote:
>
> > On 20.03.2014 18:55, Brian Federle wrote:
> >> Those suggestions sound good. Here are the changes I will make in the
> UI:
> >> - Change icon to use a 'recycle' symbol, to avoid confusion w/ reboot VM
> >> - Rename action(s) to reflect the name of the API calls.
> >> - Update the confirm dialog to say, "This action will restore the VM
> >> to a fresh root disk. After this action, the current root disk will be
> >> attached to the VM."
> >
> > "After this action, the current root disk will be attached to the VM."
> <- What does this mean? To me it sounds like the VM gets re-instantiated
> from template and the "current" root disk will be attached as a volume, in
> addition to a _new_ root disk. This is not what is happening.
> >
> > People need to be aware that this action is irreversible and THEY WILL
> LOSE DATA, the message should say this.
> >
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
>
>


-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

Re: Resetting a VM is broken?

I was just using what was suggested earlier in the thread (I’m not really 
familiar with the feature); if that is incorrect then I can change it to say,

“Warning: this action is irreversible. If you continue you may lose data. 
Please confirm that you would like to proceed.”

-Brian

On Mar 20, 2014, at 12:08 PM, Nux!  wrote:

> On 20.03.2014 18:55, Brian Federle wrote:
>> Those suggestions sound good. Here are the changes I will make in the UI:
>> - Change icon to use a ‘recycle’ symbol, to avoid confusion w/ reboot VM
>> - Rename action(s) to reflect the name of the API calls.
>> - Update the confirm dialog to say, “This action will restore the VM
>> to a fresh root disk. After this action, the current root disk will be
>> attached to the VM.”
> 
> "After this action, the current root disk will be attached to the VM." <- 
> What does this mean? To me it sounds like the VM gets re-instantiated from 
> template and the "current" root disk will be attached as a volume, in 
> addition to a _new_ root disk. This is not what is happening.
> 
> People need to be aware that this action is irreversible and THEY WILL LOSE 
> DATA, the message should say this.
> 
> 
> -- 
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro

RE: [RFC]Bypass Libvirt storage pool for NFS

2014-03-20 Thread Edison Su



> -Original Message-
> From: Nux! [mailto:n...@li.nux.ro]
> Sent: Thursday, March 20, 2014 11:51 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [RFC]Bypass Libvirt storage pool for NFS
> 
> On 20.03.2014 18:48, Wido den Hollander wrote:
> >
> > And it just went upstream! How great is that?
> 
> Pretty great. That's how open source works. :)
Thanks guys to push it:)  
But fundamentally, I don't think Libvirt doing a right thing here, libvirt 
should not need to care about integrity of storage pool, as the storage pool is 
shared by multiple hypervisor hosts, one libvirt is only one of them, so it's 
useless and error-prone, to check the files on the storage pool.
If the integrity of storage pool is broken, then user should complain to 
CloudStack or other upper layer of cloud orchestration software.

> 
> >
> >> Quick question: there is no problem if instead of using NFS directly
> >> we use the "shared mount point" option, is it?
> >>
> >
> > Probably not, since we would then be mounting the filesystem manually
> > instead of having libvirt do it.
> 
> Ok, so worst case scenario people can just fall-back on this option.
> 
> >
> > I'd say get this patch down into EL6 and I'll try to get it into
> > Ubuntu 14.04.
> 
> Yeah, fingers crossed on that!
> 
> Lucian
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro

Re: Resetting a VM is broken?


On 20.03.2014 18:55, Brian Federle wrote:
Those suggestions sound good. Here are the changes I will make in the 
UI:


- Change icon to use a ‘recycle’ symbol, to avoid confusion w/ reboot 
VM

- Rename action(s) to reflect the name of the API calls.
- Update the confirm dialog to say, “This action will restore the VM
to a fresh root disk. After this action, the current root disk will be
attached to the VM.”


"After this action, the current root disk will be attached to the VM." 
<- What does this mean? To me it sounds like the VM gets re-instantiated 
from template and the "current" root disk will be attached as a volume, 
in addition to a _new_ root disk. This is not what is happening.


People need to be aware that this action is irreversible and THEY WILL 
LOSE DATA, the message should say this.



--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Re: Resetting a VM is broken?

Quick question: The current root disk will be attached to the VM.

I interpret that statement (along with the line before it) to mean the old
root disk is replaced by a new root disk and the old root disk will be
attached to the VM as a data disk, which is not the behavior.

The behavior I see could be summarized as follows:

This action will restore the VM to a fresh root disk. After this action,
the current root disk will be destroyed.


On Thu, Mar 20, 2014 at 12:56 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Perfect
>
>
> On Thu, Mar 20, 2014 at 12:55 PM, Brian Federle 
> wrote:
>
>> Those suggestions sound good. Here are the changes I will make in the UI:
>>
>> - Change icon to use a 'recycle' symbol, to avoid confusion w/ reboot VM
>> - Rename action(s) to reflect the name of the API calls.
>> - Update the confirm dialog to say, "This action will restore the VM to a
>> fresh root disk. After this action, the current root disk will be attached
>> to the VM."
>>
>> -Brian
>>
>> On Mar 20, 2014, at 11:46 AM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>> > I think with the addition of detailed confirmation info that that is a
>> good
>> > solution.
>> >
>> > Thanks!
>> >
>> >
>> > On Thu, Mar 20, 2014 at 12:44 PM, Jessica Wang > >wrote:
>> >
>> >> And also provide detailed info in confirmation dialog when clicking the
>> >> icon that fires restoreVirtualMachine API.
>> >>
>> >> e.g. "This action will restore the VM to a fresh new root disk.
>> >> After this action, the current root disk wll be destroyed and a new
>> root
>> >> disk will be attached to the VM."
>> >>
>> >>
>> >> Harikrishna,
>> >> do you any suggestion for the text in confirmation dialog?
>> >>
>> >>
>> >> -Original Message-
>> >> From: Jessica Wang [mailto:jessica.w...@citrix.com]
>> >> Sent: Thursday, March 20, 2014 11:32 AM
>> >> To: Mike Tutkowski
>> >> Cc: Brian Federle; Harikrishna Patnala; Alena Prokharchyk;
>> >> dev@cloudstack.apache.org; Stephen Turner
>> >> Subject: RE: Resetting a VM is broken?
>> >>
>> >> How about we just match text with API name?
>> >>
>> >> i. Label the icon that fires recoverVirtualMachine API as "Recover".
>> >> ii. Label the icon that fires restoreVirtualMachine API as "Restore".
>> >>
>> >>
>> >> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> >> Sent: Thursday, March 20, 2014 11:29 AM
>> >> To: Jessica Wang
>> >> Cc: Brian Federle; Harikrishna Patnala; Alena Prokharchyk;
>> >> dev@cloudstack.apache.org; Stephen Turner
>> >> Subject: Re: Resetting a VM is broken?
>> >>
>> >> OK, thanks for the history there.
>> >>
>> >> What about the text we're using? Are we OK with Reset VM, for example?
>> >>
>> >> Thanks!
>> >>
>> >> On Thu, Mar 20, 2014 at 12:26 PM, Jessica Wang <
>> jessica.w...@citrix.com
>> >> > wrote:
>> >> Mike,
>> >>
>> >> Right.
>> >>
>> >> The history is recoverVirtualMachine API was created several years ago,
>> >> restoreVirtualMachine didn't exist yet at that time.
>> >> So, the icon that fires recoverVirtualMachine API was labeled as
>> "Restore"
>> >> at that time.
>> >>
>> >> restoreVirtualMachine API came along several years later.
>> >> Then, since label "Restore" has already taken, the icon that fires
>> >> restoreVirtualMachine API was therefore labeled as "Reset".
>> >>
>> >> The result is indeed weird.
>> >> We'll fix the label to match API name.
>> >>
>> >> Jessica
>> >>
>> >> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com> >> mike.tutkow...@solidfire.com>]
>> >> Sent: Thursday, March 20, 2014 11:03 AM
>> >> To: Jessica Wang
>> >> Cc: Brian Federle; Harikrishna Patnala; Alena Prokharchyk;
>> >> dev@cloudstack.apache.org; Stephen
>> >> Turner
>> >>
>> >> Subject: Re: Resetting a VM is broken?
>> >>
>> >> Thanks, Jessica
>> >>
>> >> The even weirder part, though, is that the text Restore maps to the
>> >> recoverVirtualMachine API and the text Reset VM maps to the
>> >> restoreVirtualMachine.
>> >>
>> >> On Thu, Mar 20, 2014 at 11:58 AM, Jessica Wang <
>> jessica.w...@citrix.com
>> >> > wrote:
>> >>> [Mike Tutkowski] Unless I'm reading this incorrectly, it looks like
>> >>> label.action.restore.instance (Restore Instance) maps to
>> >> recoverVirtualMachine
>> >>> and
>> >>> label.resetVM (Reset VM) maps to restoreVirtualMachine
>> >> Yes, this is confusing.
>> >> I'll file an UI bug to match icon label with API name.
>> >> i.e. The icon that fires recoverVirtualMachine API will be labeled as
>> >> "Recover"
>> >> and the icon that fires restoreVirtualMachine API will be labeled as
>> >> "Restore"
>> >>
>> >>
>> >> -Original Message-
>> >> From: Brian Federle
>> >> Sent: Thursday, March 20, 2014 10:29 AM
>> >> To: Alena Prokharchyk
>> >> Cc: dev@cloudstack.apache.org; Brian
>> >> Federle; Jessica Wang; Mike Tutkowski; Harikrishna Patnala
>> >> Subject: Re: Resetting a VM is b

Re: Resetting a VM is broken?

Perfect


On Thu, Mar 20, 2014 at 12:55 PM, Brian Federle wrote:

> Those suggestions sound good. Here are the changes I will make in the UI:
>
> - Change icon to use a 'recycle' symbol, to avoid confusion w/ reboot VM
> - Rename action(s) to reflect the name of the API calls.
> - Update the confirm dialog to say, "This action will restore the VM to a
> fresh root disk. After this action, the current root disk will be attached
> to the VM."
>
> -Brian
>
> On Mar 20, 2014, at 11:46 AM, Mike Tutkowski 
> wrote:
>
> > I think with the addition of detailed confirmation info that that is a
> good
> > solution.
> >
> > Thanks!
> >
> >
> > On Thu, Mar 20, 2014 at 12:44 PM, Jessica Wang  >wrote:
> >
> >> And also provide detailed info in confirmation dialog when clicking the
> >> icon that fires restoreVirtualMachine API.
> >>
> >> e.g. "This action will restore the VM to a fresh new root disk.
> >> After this action, the current root disk wll be destroyed and a new root
> >> disk will be attached to the VM."
> >>
> >>
> >> Harikrishna,
> >> do you any suggestion for the text in confirmation dialog?
> >>
> >>
> >> -Original Message-
> >> From: Jessica Wang [mailto:jessica.w...@citrix.com]
> >> Sent: Thursday, March 20, 2014 11:32 AM
> >> To: Mike Tutkowski
> >> Cc: Brian Federle; Harikrishna Patnala; Alena Prokharchyk;
> >> dev@cloudstack.apache.org; Stephen Turner
> >> Subject: RE: Resetting a VM is broken?
> >>
> >> How about we just match text with API name?
> >>
> >> i. Label the icon that fires recoverVirtualMachine API as "Recover".
> >> ii. Label the icon that fires restoreVirtualMachine API as "Restore".
> >>
> >>
> >> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> >> Sent: Thursday, March 20, 2014 11:29 AM
> >> To: Jessica Wang
> >> Cc: Brian Federle; Harikrishna Patnala; Alena Prokharchyk;
> >> dev@cloudstack.apache.org; Stephen Turner
> >> Subject: Re: Resetting a VM is broken?
> >>
> >> OK, thanks for the history there.
> >>
> >> What about the text we're using? Are we OK with Reset VM, for example?
> >>
> >> Thanks!
> >>
> >> On Thu, Mar 20, 2014 at 12:26 PM, Jessica Wang  >> > wrote:
> >> Mike,
> >>
> >> Right.
> >>
> >> The history is recoverVirtualMachine API was created several years ago,
> >> restoreVirtualMachine didn't exist yet at that time.
> >> So, the icon that fires recoverVirtualMachine API was labeled as
> "Restore"
> >> at that time.
> >>
> >> restoreVirtualMachine API came along several years later.
> >> Then, since label "Restore" has already taken, the icon that fires
> >> restoreVirtualMachine API was therefore labeled as "Reset".
> >>
> >> The result is indeed weird.
> >> We'll fix the label to match API name.
> >>
> >> Jessica
> >>
> >> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com >> mike.tutkow...@solidfire.com>]
> >> Sent: Thursday, March 20, 2014 11:03 AM
> >> To: Jessica Wang
> >> Cc: Brian Federle; Harikrishna Patnala; Alena Prokharchyk;
> >> dev@cloudstack.apache.org; Stephen
> >> Turner
> >>
> >> Subject: Re: Resetting a VM is broken?
> >>
> >> Thanks, Jessica
> >>
> >> The even weirder part, though, is that the text Restore maps to the
> >> recoverVirtualMachine API and the text Reset VM maps to the
> >> restoreVirtualMachine.
> >>
> >> On Thu, Mar 20, 2014 at 11:58 AM, Jessica Wang  >> > wrote:
> >>> [Mike Tutkowski] Unless I'm reading this incorrectly, it looks like
> >>> label.action.restore.instance (Restore Instance) maps to
> >> recoverVirtualMachine
> >>> and
> >>> label.resetVM (Reset VM) maps to restoreVirtualMachine
> >> Yes, this is confusing.
> >> I'll file an UI bug to match icon label with API name.
> >> i.e. The icon that fires recoverVirtualMachine API will be labeled as
> >> "Recover"
> >> and the icon that fires restoreVirtualMachine API will be labeled as
> >> "Restore"
> >>
> >>
> >> -Original Message-
> >> From: Brian Federle
> >> Sent: Thursday, March 20, 2014 10:29 AM
> >> To: Alena Prokharchyk
> >> Cc: dev@cloudstack.apache.org; Brian
> >> Federle; Jessica Wang; Mike Tutkowski; Harikrishna Patnala
> >> Subject: Re: Resetting a VM is broken?
>  the Reset Vm option is presented as a button unlike the icons
> >> I think this was because all the other icons we tried to represent this
> >> with were too confusing to users - they were clicking on 'reset VM'
> >> thinking it was 'reboot VM' - then as a last minute fix the decision
> was to
> >> just to show a text label.
> >>
> >> Any ideas from anyone on what would be a good icon representation?
> >>
> >> -Brian
> >>
> >> On Mar 19, 2014, at 3:02 PM, Alena Prokharchyk <
> >> alena.prokharc...@citrix.com>
> wrote:
> >>
> >>> 1) Didn't notice "the elephant" - that the Reset Vm option is presented
> >> as
> >>> a button unlike the icons for other options. UI folks - Brian/Jessica-
> >> why
> >>>

Re: Resetting a VM is broken?

Those suggestions sound good. Here are the changes I will make in the UI:

- Change icon to use a ‘recycle’ symbol, to avoid confusion w/ reboot VM
- Rename action(s) to reflect the name of the API calls.
- Update the confirm dialog to say, “This action will restore the VM to a fresh 
root disk. After this action, the current root disk will be attached to the VM.”

-Brian
 
On Mar 20, 2014, at 11:46 AM, Mike Tutkowski  
wrote:

> I think with the addition of detailed confirmation info that that is a good
> solution.
> 
> Thanks!
> 
> 
> On Thu, Mar 20, 2014 at 12:44 PM, Jessica Wang wrote:
> 
>> And also provide detailed info in confirmation dialog when clicking the
>> icon that fires restoreVirtualMachine API.
>> 
>> e.g. "This action will restore the VM to a fresh new root disk.
>> After this action, the current root disk wll be destroyed and a new root
>> disk will be attached to the VM."
>> 
>> 
>> Harikrishna,
>> do you any suggestion for the text in confirmation dialog?
>> 
>> 
>> -Original Message-
>> From: Jessica Wang [mailto:jessica.w...@citrix.com]
>> Sent: Thursday, March 20, 2014 11:32 AM
>> To: Mike Tutkowski
>> Cc: Brian Federle; Harikrishna Patnala; Alena Prokharchyk;
>> dev@cloudstack.apache.org; Stephen Turner
>> Subject: RE: Resetting a VM is broken?
>> 
>> How about we just match text with API name?
>> 
>> i. Label the icon that fires recoverVirtualMachine API as "Recover".
>> ii. Label the icon that fires restoreVirtualMachine API as "Restore".
>> 
>> 
>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> Sent: Thursday, March 20, 2014 11:29 AM
>> To: Jessica Wang
>> Cc: Brian Federle; Harikrishna Patnala; Alena Prokharchyk;
>> dev@cloudstack.apache.org; Stephen Turner
>> Subject: Re: Resetting a VM is broken?
>> 
>> OK, thanks for the history there.
>> 
>> What about the text we're using? Are we OK with Reset VM, for example?
>> 
>> Thanks!
>> 
>> On Thu, Mar 20, 2014 at 12:26 PM, Jessica Wang > > wrote:
>> Mike,
>> 
>> Right.
>> 
>> The history is recoverVirtualMachine API was created several years ago,
>> restoreVirtualMachine didn't exist yet at that time.
>> So, the icon that fires recoverVirtualMachine API was labeled as "Restore"
>> at that time.
>> 
>> restoreVirtualMachine API came along several years later.
>> Then, since label "Restore" has already taken, the icon that fires
>> restoreVirtualMachine API was therefore labeled as "Reset".
>> 
>> The result is indeed weird.
>> We'll fix the label to match API name.
>> 
>> Jessica
>> 
>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com> mike.tutkow...@solidfire.com>]
>> Sent: Thursday, March 20, 2014 11:03 AM
>> To: Jessica Wang
>> Cc: Brian Federle; Harikrishna Patnala; Alena Prokharchyk;
>> dev@cloudstack.apache.org; Stephen
>> Turner
>> 
>> Subject: Re: Resetting a VM is broken?
>> 
>> Thanks, Jessica
>> 
>> The even weirder part, though, is that the text Restore maps to the
>> recoverVirtualMachine API and the text Reset VM maps to the
>> restoreVirtualMachine.
>> 
>> On Thu, Mar 20, 2014 at 11:58 AM, Jessica Wang > > wrote:
>>> [Mike Tutkowski] Unless I'm reading this incorrectly, it looks like
>>> label.action.restore.instance (Restore Instance) maps to
>> recoverVirtualMachine
>>> and
>>> label.resetVM (Reset VM) maps to restoreVirtualMachine
>> Yes, this is confusing.
>> I'll file an UI bug to match icon label with API name.
>> i.e. The icon that fires recoverVirtualMachine API will be labeled as
>> "Recover"
>> and the icon that fires restoreVirtualMachine API will be labeled as
>> "Restore"
>> 
>> 
>> -Original Message-
>> From: Brian Federle
>> Sent: Thursday, March 20, 2014 10:29 AM
>> To: Alena Prokharchyk
>> Cc: dev@cloudstack.apache.org; Brian
>> Federle; Jessica Wang; Mike Tutkowski; Harikrishna Patnala
>> Subject: Re: Resetting a VM is broken?
 the Reset Vm option is presented as a button unlike the icons
>> I think this was because all the other icons we tried to represent this
>> with were too confusing to users - they were clicking on 'reset VM'
>> thinking it was 'reboot VM' - then as a last minute fix the decision was to
>> just to show a text label.
>> 
>> Any ideas from anyone on what would be a good icon representation?
>> 
>> -Brian
>> 
>> On Mar 19, 2014, at 3:02 PM, Alena Prokharchyk <
>> alena.prokharc...@citrix.com> wrote:
>> 
>>> 1) Didn't notice "the elephant" - that the Reset Vm option is presented
>> as
>>> a button unlike the icons for other options. UI folks - Brian/Jessica-
>> why
>>> we decided to represent this option differently in the UI?
>>> 
>>> 2) Mike, I've looked at the code and the history. We've always allocated
>> a
>>> new volume during the vm restore call. Hari, can you please confirm that
>>> this feature you wrote, was designed to work this way
>>> 
>>> 
>>> -Alena.
>>>

Re: [RFC]Bypass Libvirt storage pool for NFS


On 20.03.2014 18:48, Wido den Hollander wrote:


And it just went upstream! How great is that?


Pretty great. That's how open source works. :)



Quick question: there is no problem if instead of using NFS directly 
we

use the "shared mount point" option, is it?



Probably not, since we would then be mounting the filesystem manually
instead of having libvirt do it.


Ok, so worst case scenario people can just fall-back on this option.



I'd say get this patch down into EL6 and I'll try to get it into 
Ubuntu 14.04.


Yeah, fingers crossed on that!

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Re: [RFC]Bypass Libvirt storage pool for NFS

2014-03-20 Thread Wido den Hollander




On 03/20/2014 05:38 PM, Nux! wrote:

On 19.03.2014 22:48, Edison Su wrote:

-Original Message-
From: Nux! [mailto:n...@li.nux.ro]
Sent: Wednesday, March 19, 2014 3:34 PM
To: dev@cloudstack.apache.org
Subject: RE: [RFC]Bypass Libvirt storage pool for NFS

On 19.03.2014 22:28, Edison Su wrote:

Edison, if - with the workarounds in place now - the current version
of KVM works OK, then why wouldn't a newer version work just as fine?
Just trying to understand this.


That's a long story, there is a bug in Libvirt, which is introduced in
a newer version(>0.9.10), which can make the storage pool disappear.


Edison, that I understand, but what is the technical reason that
prevents
using newer KVM?
It looks like current KVM works fine on CentOS 6.5 for example which has
libvirt 0.10.2.


Yes, at first glance, the newer version libvirt(> 0.9.10) just works
fine. But under stress test, it will complain NFS storage pool
missing, and can't add the storage pool back, unless you shut down all
the VMs which using the storage pool. That's the
bug(https://bugzilla.redhat.com/show_bug.cgi?id=977706) all about.

In ACS 4.2/4.3 release, we only recommend to use libvirt <=0.9.10, if
primary storage is NFS.


Ok, I'm trying to make some noise in that bz entry, hopefully someone
gets annoyed enough to do something about it.



And it just went upstream! How great is that?


Quick question: there is no problem if instead of using NFS directly we
use the "shared mount point" option, is it?



Probably not, since we would then be mounting the filesystem manually 
instead of having libvirt do it.


I'd say get this patch down into EL6 and I'll try to get it into Ubuntu 
14.04.


Wido


Lucian

Re: Resetting a VM is broken?

I think with the addition of detailed confirmation info that that is a good
solution.

Thanks!


On Thu, Mar 20, 2014 at 12:44 PM, Jessica Wang wrote:

> And also provide detailed info in confirmation dialog when clicking the
> icon that fires restoreVirtualMachine API.
>
> e.g. "This action will restore the VM to a fresh new root disk.
> After this action, the current root disk wll be destroyed and a new root
> disk will be attached to the VM."
>
>
> Harikrishna,
> do you any suggestion for the text in confirmation dialog?
>
>
> -Original Message-
> From: Jessica Wang [mailto:jessica.w...@citrix.com]
> Sent: Thursday, March 20, 2014 11:32 AM
> To: Mike Tutkowski
> Cc: Brian Federle; Harikrishna Patnala; Alena Prokharchyk;
> dev@cloudstack.apache.org; Stephen Turner
> Subject: RE: Resetting a VM is broken?
>
> How about we just match text with API name?
>
> i. Label the icon that fires recoverVirtualMachine API as "Recover".
> ii. Label the icon that fires restoreVirtualMachine API as "Restore".
>
>
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Thursday, March 20, 2014 11:29 AM
> To: Jessica Wang
> Cc: Brian Federle; Harikrishna Patnala; Alena Prokharchyk;
> dev@cloudstack.apache.org; Stephen Turner
> Subject: Re: Resetting a VM is broken?
>
> OK, thanks for the history there.
>
> What about the text we're using? Are we OK with Reset VM, for example?
>
> Thanks!
>
> On Thu, Mar 20, 2014 at 12:26 PM, Jessica Wang  > wrote:
> Mike,
>
> Right.
>
> The history is recoverVirtualMachine API was created several years ago,
> restoreVirtualMachine didn't exist yet at that time.
> So, the icon that fires recoverVirtualMachine API was labeled as "Restore"
> at that time.
>
> restoreVirtualMachine API came along several years later.
> Then, since label "Restore" has already taken, the icon that fires
> restoreVirtualMachine API was therefore labeled as "Reset".
>
> The result is indeed weird.
> We'll fix the label to match API name.
>
> Jessica
>
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com mike.tutkow...@solidfire.com>]
> Sent: Thursday, March 20, 2014 11:03 AM
> To: Jessica Wang
> Cc: Brian Federle; Harikrishna Patnala; Alena Prokharchyk;
> dev@cloudstack.apache.org; Stephen
> Turner
>
> Subject: Re: Resetting a VM is broken?
>
> Thanks, Jessica
>
> The even weirder part, though, is that the text Restore maps to the
> recoverVirtualMachine API and the text Reset VM maps to the
> restoreVirtualMachine.
>
> On Thu, Mar 20, 2014 at 11:58 AM, Jessica Wang  > wrote:
> > [Mike Tutkowski] Unless I'm reading this incorrectly, it looks like
> > label.action.restore.instance (Restore Instance) maps to
> recoverVirtualMachine
> > and
> > label.resetVM (Reset VM) maps to restoreVirtualMachine
> Yes, this is confusing.
> I'll file an UI bug to match icon label with API name.
> i.e. The icon that fires recoverVirtualMachine API will be labeled as
> "Recover"
> and the icon that fires restoreVirtualMachine API will be labeled as
> "Restore"
>
>
> -Original Message-
> From: Brian Federle
> Sent: Thursday, March 20, 2014 10:29 AM
> To: Alena Prokharchyk
> Cc: dev@cloudstack.apache.org; Brian
> Federle; Jessica Wang; Mike Tutkowski; Harikrishna Patnala
> Subject: Re: Resetting a VM is broken?
> >> the Reset Vm option is presented as a button unlike the icons
> I think this was because all the other icons we tried to represent this
> with were too confusing to users - they were clicking on 'reset VM'
> thinking it was 'reboot VM' - then as a last minute fix the decision was to
> just to show a text label.
>
> Any ideas from anyone on what would be a good icon representation?
>
> -Brian
>
> On Mar 19, 2014, at 3:02 PM, Alena Prokharchyk <
> alena.prokharc...@citrix.com> wrote:
>
> > 1) Didn't notice "the elephant" - that the Reset Vm option is presented
> as
> > a button unlike the icons for other options. UI folks - Brian/Jessica-
> why
> > we decided to represent this option differently in the UI?
> >
> > 2) Mike, I've looked at the code and the history. We've always allocated
> a
> > new volume during the vm restore call. Hari, can you please confirm that
> > this feature you wrote, was designed to work this way
> >
> >
> > -Alena.
> >
> >
> > On 3/19/14, 2:41 PM, "Mike Tutkowski"  > wrote:
> >
> >> To clarify: Reboot VM seemed to keep the VM running and just reboot the
> >> OS.
> >>
> >> Reset VM seemed to shut the VM down and then re-start it (with the same
> >> root disk for the OS).
> >>
> >>
> >> On Wed, Mar 19, 2014 at 3:40 PM, Mike Tutkowski <
> >> mike.tutkow...@solidfire.com>
> wrote:
> >>
> >>> I could be wrong, but I thought as recently as 4.3 that Reset VM
> >>> essentially stopped and then re-started the VM with the same root di

Re: concole proxy in 4.3RC9

2014-03-20 Thread Amogh Vasekar

Hi,

Tried on XenServer set-up, and the defaults work fine for me. The console
URL for me :
2014-03-20 18:43:08,558 DEBUG [c.c.s.ConsoleProxyServlet]
(24565443@qtp-27436568-8:null) Compose console url:
http://192.168.56.139/ajax?token=tVsokSDt2PUASaa77NN_qBAZFJsma76qRT5Y1OLQFW
1zl82-vizkq36Fii1yLNvR1h7Ul3CL0L8yrtn2y7FkqLgZyXFc3bObM5U2H6n-3CO01d-zqJGxq
hNom6i-oUEgQhp-QPJ0rKkEZErTeYF6YyMwHghWabLuAyDYYT9gA39VWAVHcySUtSjFcjRFWhIA
vOs9RghpY9D6rvzgjeCvBOuy4aOD1kQlT_7lUIX3BIcLyipMR200o0y2ZjAfxwdfN-9oyMuuUjr
YsObY9xb-BQxOb5p5cZogqqqiCnXGhr1mPwlN6Ba-BI-UQzgNjlHX95sp0x_hnHhdzMfZ0vfaAo
7SZLrfD1oGRxMOWFonu-WHSsu4OBcDSELFxd-2Yt_noZ6Mdz2kheMvGfYmFC2r1gjii0rxzuj8L
w8p42DZAGLq8TqSWyBUGsQWhMveyHVJHbKJDrsOcJVMyUdDLKsVhGR9voti7TJUAAzQb75Ahaw

Just to reconfirm - did you build using systemvm profile? Is port 80
blocked somewhere?

Thanks,
Amogh

On 3/20/14 10:15 AM, "Daan Hoogland"  wrote:

>btw
>
>the last lines:
>
>2014-03-20 13:57:09,858 DEBUG [c.c.a.t.Request]
>(1372260265@qtp-1676921458-10:null) Seq 1-762183775: Sending  { Cmd ,
>MgmtId: 24062491136, via: 1(mccdxen2), Ver: v1, Flags: 100011,
>[{"com.cloud.agent.api.GetVncPortCommand":{"id":5,"name":"i-2-5-VM","wait"
>:0}}]
>}
>2014-03-20 13:57:09,858 DEBUG [c.c.a.t.Request]
>(1372260265@qtp-1676921458-10:null) Seq 1-762183775: Executing:  { Cmd
>, MgmtId: 24062491136, via: 1(mccdxen2), Ver: v1, Flags: 100011,
>[{"com.cloud.agent.api.GetVncPortCommand":{"id":5,"name":"i-2-5-VM","wait"
>:0}}]
>}
>2014-03-20 13:57:09,859 DEBUG [c.c.a.m.DirectAgentAttache]
>(DirectAgent-63:ctx-6c8a6687) Seq 1-762183775: Executing request
>2014-03-20 13:57:09,976 DEBUG [c.c.a.m.DirectAgentAttache]
>(DirectAgent-63:ctx-6c8a6687) Seq 1-762183775: Response Received:
>2014-03-20 13:57:09,976 DEBUG [c.c.a.t.Request]
>(DirectAgent-63:ctx-6c8a6687) Seq 1-762183775: Processing:  { Ans: ,
>MgmtId: 24062491136, via: 1, Ver: v1, Flags: 10,
>[{"com.cloud.agent.api.GetVncPortAnswer":{"address":"consoleurl=https://10
>.200.23.42/console?uuid=d539642a-7c78-622e-9c22-e6b3b0771122&sessionref=Op
>aqueRef:160e30d3-5f3e-255e-ef8a-596e69ad30d4","port":-1,"result":true,"wai
>t":0}}]
>}
>2014-03-20 13:57:09,976 DEBUG [c.c.a.t.Request]
>(1372260265@qtp-1676921458-10:null) Seq 1-762183775: Received:  { Ans:
>, MgmtId: 24062491136, via: 1, Ver: v1, Flags: 10, { GetVncPortAnswer
>} }
>2014-03-20 13:57:09,976 DEBUG [c.c.s.ConsoleProxyServlet]
>(1372260265@qtp-1676921458-10:null) Port info
>consoleurl=https://10.200.23.42/console?uuid=d539642a-7c78-622e-9c22-e6b3b
>0771122&sessionref=OpaqueRef:160e30d3-5f3e-255e-ef8a-596e69ad30d4
>2014-03-20 13:57:09,976 INFO  [c.c.s.ConsoleProxyServlet]
>(1372260265@qtp-1676921458-10:null) Parse host info returned from
>executing GetVNCPortCommand. host info:
>consoleurl=https://10.200.23.42/console?uuid=d539642a-7c78-622e-9c22-e6b3b
>0771122&sessionref=OpaqueRef:160e30d3-5f3e-255e-ef8a-596e69ad30d4
>2014-03-20 13:57:09,979 DEBUG [c.c.s.ConsoleProxyServlet]
>(1372260265@qtp-1676921458-10:null) Compose console url:
>http://195.66.90.213/ajax?token=9Rrl0mjwUQd3Ym9mEb-ziydOD0YOSWJNi_QZFP7efE
>r1mIalpz2Xg0UvR2eUUyqbgFqNXQJOlt0yJsfkH7CnubShCuEb82qKCD4zf50hyHxZufjglf9N
>efAuIXRJmmXe10afkEVYHARondjCtJ80RkovHVtQHkErX9s2wB2HT9Zx7kuKGdYmigVQ8_AjqF
>yusOCQ6XTplJOlr4ZdvSZoafu0dowEYJysruLtBvY9qsi5eMXC4ozvodmRUfBN4jARisUjusBC
>DUSzQyrdXImCjLFT3cL1GVmdNPQz7L7s3PJrSyMdB9ZZshnzNYAYkCjUtjiLwAf3aJfZt3z3r9
>TuJg6k5kfhRbBsvpBVtrYcI1DXJfEANZD6g9f4hDRghnsXxrUpPrA973CiSUaKsKzUMqVWM4Vu
>iDtHkWIgk_p100K-ai9wzufJYAk9lZ_vhY9GWYkQhpBtZeupk3Gl5Gc_iudCMwP9kFvEA12i6j
>Nvtng
>2014-03-20 13:57:09,979 DEBUG [c.c.s.ConsoleProxyServlet]
>(1372260265@qtp-1676921458-10:null) the console url is ::
>gsrc="http://195.66.90.213/ajax?token=9Rrl0mjwUQd3Ym9mEb-ziydOD0YOSWJNi_QZF
>P7efEr1mIalpz2Xg0UvR2eUUyqbgFqNXQJOlt0yJsfkH7CnubShCuEb82qKCD4zf50hyHxZufj
>glf9NefAuIXRJmmXe10afkEVYHARondjCtJ80RkovHVtQHkErX9s2wB2HT9Zx7kuKGdYmigVQ8
>_AjqFyusOCQ6XTplJOlr4ZdvSZoafu0dowEYJysruLtBvY9qsi5eMXC4ozvodmRUfBN4jARisU
>jusBCDUSzQyrdXImCjLFT3cL1GVmdNPQz7L7s3PJrSyMdB9ZZshnzNYAYkCjUtjiLwAf3aJfZt
>3z3r9TuJg6k5kfhRbBsvpBVtrYcI1DXJfEANZD6g9f4hDRghnsXxrUpPrA973CiSUaKsKzUMqV
>WM4VuiDtHkWIgk_p100K-ai9wzufJYAk9lZ_vhY9GWYkQhpBtZeupk3Gl5Gc_iudCMwP9kFvEA
>12i6jNvtng">
>
>and next nothing but the browser saying connection refused.
>
>So what changed? Where do I need to adjust my infra to make it work
>again? Or is my setup not supported anymore?
>
>On Thu, Mar 20, 2014 at 5:49 PM, Daan Hoogland 
>wrote:
>> meaning the console of the ssvm? or the cpvm?
>>
>> I just confirmed myself that there is indeed a diff between 4.2.1 and
>>4.3RC9
>>
>> On Thu, Mar 20, 2014 at 5:32 PM, Nux!  wrote:
>>> On 20.03.2014 16:29, Ove Ewerlid wrote:

 Console SSVM works in my 4.3 setup.
 Traffic does not use SSL and is on port 80.
>>>
>>>
>>> Did you have to do anything in particular to disable SSL or is this
>>>the new
>>> default?
>>>
>>> I was having problems with 4.4 where VC VM was in Alert mode and the
>>>VMs'
>>> console was dead; will have to revisit this.
>>>
>

RE: Resetting a VM is broken?

And also provide detailed info in confirmation dialog when clicking the icon 
that fires restoreVirtualMachine API.

e.g. "This action will restore the VM to a fresh new root disk. 
After this action, the current root disk wll be destroyed and a new root disk 
will be attached to the VM."

Harikrishna, 
do you any suggestion for the text in confirmation dialog?

-Original Message-
From: Jessica Wang [mailto:jessica.w...@citrix.com] 
Sent: Thursday, March 20, 2014 11:32 AM
To: Mike Tutkowski
Cc: Brian Federle; Harikrishna Patnala; Alena Prokharchyk; 
dev@cloudstack.apache.org; Stephen Turner
Subject: RE: Resetting a VM is broken?

How about we just match text with API name?

i. Label the icon that fires recoverVirtualMachine API as "Recover".
ii. Label the icon that fires restoreVirtualMachine API as "Restore".

From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Thursday, March 20, 2014 11:29 AM
To: Jessica Wang
Cc: Brian Federle; Harikrishna Patnala; Alena Prokharchyk; 
dev@cloudstack.apache.org; Stephen Turner
Subject: Re: Resetting a VM is broken?

OK, thanks for the history there.

What about the text we're using? Are we OK with Reset VM, for example?

Thanks!

On Thu, Mar 20, 2014 at 12:26 PM, Jessica Wang 
mailto:jessica.w...@citrix.com>> wrote:
Mike,

Right.

The history is recoverVirtualMachine API was created several years ago, 
restoreVirtualMachine didn't exist yet at that time.
So, the icon that fires recoverVirtualMachine API was labeled as "Restore" at 
that time.

restoreVirtualMachine API came along several years later.
Then, since label "Restore" has already taken, the icon that fires 
restoreVirtualMachine API was therefore labeled as "Reset".

The result is indeed weird.
We'll fix the label to match API name.

Jessica

From: Mike Tutkowski 
[mailto:mike.tutkow...@solidfire.com]
Sent: Thursday, March 20, 2014 11:03 AM
To: Jessica Wang
Cc: Brian Federle; Harikrishna Patnala; Alena Prokharchyk; 
dev@cloudstack.apache.org; Stephen Turner

Subject: Re: Resetting a VM is broken?

Thanks, Jessica

The even weirder part, though, is that the text Restore maps to the 
recoverVirtualMachine API and the text Reset VM maps to the 
restoreVirtualMachine.

On Thu, Mar 20, 2014 at 11:58 AM, Jessica Wang 
mailto:jessica.w...@citrix.com>> wrote:
> [Mike Tutkowski] Unless I'm reading this incorrectly, it looks like
> label.action.restore.instance (Restore Instance) maps to recoverVirtualMachine
> and
> label.resetVM (Reset VM) maps to restoreVirtualMachine
Yes, this is confusing.
I'll file an UI bug to match icon label with API name.
i.e. The icon that fires recoverVirtualMachine API will be labeled as "Recover"
and the icon that fires restoreVirtualMachine API will be labeled as "Restore"

-Original Message-
From: Brian Federle
Sent: Thursday, March 20, 2014 10:29 AM
To: Alena Prokharchyk
Cc: dev@cloudstack.apache.org; Brian Federle; 
Jessica Wang; Mike Tutkowski; Harikrishna Patnala
Subject: Re: Resetting a VM is broken?
>> the Reset Vm option is presented as a button unlike the icons
I think this was because all the other icons we tried to represent this with 
were too confusing to users - they were clicking on 'reset VM' thinking it was 
'reboot VM' - then as a last minute fix the decision was to just to show a text 
label.

Any ideas from anyone on what would be a good icon representation?

-Brian

On Mar 19, 2014, at 3:02 PM, Alena Prokharchyk 
mailto:alena.prokharc...@citrix.com>> wrote:

> 1) Didn't notice "the elephant" - that the Reset Vm option is presented as
> a button unlike the icons for other options. UI folks - Brian/Jessica- why
> we decided to represent this option differently in the UI?
>
> 2) Mike, I've looked at the code and the history. We've always allocated a
> new volume during the vm restore call. Hari, can you please confirm that
> this feature you wrote, was designed to work this way
>
>
> -Alena.
>
>
> On 3/19/14, 2:41 PM, "Mike Tutkowski" 
> mailto:mike.tutkow...@solidfire.com>> wrote:
>
>> To clarify: Reboot VM seemed to keep the VM running and just reboot the
>> OS.
>>
>> Reset VM seemed to shut the VM down and then re-start it (with the same
>> root disk for the OS).
>>
>>
>> On Wed, Mar 19, 2014 at 3:40 PM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>>> I could be wrong, but I thought as recently as 4.3 that Reset VM
>>> essentially stopped and then re-started the VM with the same root disk.
>>>
>>> It seemed to differ from Reboot VM only in the sense that the VM was
>>> never
>>> technically stopped (the OS inside the VM was just rebooted).
>>>
>>>
>>> On Wed, Mar 19, 2014 at 3:38 PM, Mike Tutkowski <
>>> mike.tutkow...@solidfire.com> wrote:
>>>
 I'm using XenServer 6.1 hosts (two of them) in this case.

 On Wed, Mar 19, 2014 at

Re: cloudstack talent

2014-03-20 Thread Marcus

Normally I'm looking to hire, but its also nice to survey the opportunities
out there.
On Mar 20, 2014 9:06 AM, "ilya musayev" 
wrote:

> Marcus,
>
> Not the best place, but CloudStack LinkedIn group has job posting section.
>
> btw, are you looking for a change or  need to hire?
>
> Thanks
> ilya
> On 3/20/14, 10:41 AM, Marcus wrote:
>
>>  Is there a jobs board/list where people can post or investigate
>> CloudStack related jobs? Or is that taboo due to the Apache model of
>> separation between an individual's employment and community roles?
>>
>
>

Re: [VOTE] Apache CloudStack 4.3.0 (ninth round)

2014-03-20 Thread ilya musayev

Sorry i missed this email, will update later tonight. Actually doing 
more work with ACS 4.3 - so test cases are growing.


On 3/20/14, 12:58 PM, Daan Hoogland wrote:

again I am seriously considering -1 (binding) and (sigh) and. Is there
any doc I missed on getting the console proxy working in 4.3, that
will make me hit me on the head and retract this thread?

On Tue, Mar 18, 2014 at 9:38 PM, Wilder Rodrigues
 wrote:

Hi there Ilya,

Could you please provide which tests cases you have covered? I would like to 
add them to my tests round as well.

Currently I'm testing multiple zones, networks, instances, ACLs, Port 
Forwarding and will add security groups. If you have more points, I would be 
glad to test them as well.

Thanks in advance.

Cheers,
Wilder

-Original Message-
From: ilya musayev [mailto:ilya.mailing.li...@gmail.com]
Sent: Tuesday, March 18, 2014 9:11 PM
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (ninth round)

+1 binding
On 3/18/14, 3:05 PM, Animesh Chaturvedi wrote:


Hi All,



I've created a 4.3.0 release, with the following artifacts up for a

vote:





Git Branch and Commit SH:

https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
Commit:  0810029f274878eca8fd74b44ab1117054e929a5


List of changes:

New Features in 4.3: https://issues.apache.org/jira/issues/?filter=12325248

Improvement in 4.3: https://issues.apache.org/jira/issues/?filter=12325249

Issues fixed in 4.3 https://issues.apache.org/jira/issues/?filter=12326161

Known Issues in 4.3: https://issues.apache.org/jira/issues/?filter=12326162







Source release (checksums and signatures are available at the same

location):

https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/



PGP release keys (signed using 94BE0D7C):

https://dist.apache.org/repos/dist/release/cloudstack/KEYS



Testing instructions are here:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure



Vote will be open for 72 hours (Friday 3/21 12:05 PM PST)



For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?



[ ] +1  approve

[ ] +0  no opinion

[ ] -1  disapprove (and reason why)



Thanks

Animesh

RE: Resetting a VM is broken?

How about we just match text with API name?

i. Label the icon that fires recoverVirtualMachine API as "Recover".
ii. Label the icon that fires restoreVirtualMachine API as "Restore".


From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Thursday, March 20, 2014 11:29 AM
To: Jessica Wang
Cc: Brian Federle; Harikrishna Patnala; Alena Prokharchyk; 
dev@cloudstack.apache.org; Stephen Turner
Subject: Re: Resetting a VM is broken?

OK, thanks for the history there.

What about the text we're using? Are we OK with Reset VM, for example?

Thanks!

On Thu, Mar 20, 2014 at 12:26 PM, Jessica Wang 
mailto:jessica.w...@citrix.com>> wrote:
Mike,

Right.

The history is recoverVirtualMachine API was created several years ago, 
restoreVirtualMachine didn't exist yet at that time.
So, the icon that fires recoverVirtualMachine API was labeled as "Restore" at 
that time.

restoreVirtualMachine API came along several years later.
Then, since label "Restore" has already taken, the icon that fires 
restoreVirtualMachine API was therefore labeled as "Reset".

The result is indeed weird.
We'll fix the label to match API name.

Jessica

From: Mike Tutkowski 
[mailto:mike.tutkow...@solidfire.com]
Sent: Thursday, March 20, 2014 11:03 AM
To: Jessica Wang
Cc: Brian Federle; Harikrishna Patnala; Alena Prokharchyk; 
dev@cloudstack.apache.org; Stephen Turner

Subject: Re: Resetting a VM is broken?

Thanks, Jessica

The even weirder part, though, is that the text Restore maps to the 
recoverVirtualMachine API and the text Reset VM maps to the 
restoreVirtualMachine.

On Thu, Mar 20, 2014 at 11:58 AM, Jessica Wang 
mailto:jessica.w...@citrix.com>> wrote:
> [Mike Tutkowski] Unless I'm reading this incorrectly, it looks like
> label.action.restore.instance (Restore Instance) maps to recoverVirtualMachine
> and
> label.resetVM (Reset VM) maps to restoreVirtualMachine
Yes, this is confusing.
I'll file an UI bug to match icon label with API name.
i.e. The icon that fires recoverVirtualMachine API will be labeled as "Recover"
and the icon that fires restoreVirtualMachine API will be labeled as "Restore"


-Original Message-
From: Brian Federle
Sent: Thursday, March 20, 2014 10:29 AM
To: Alena Prokharchyk
Cc: dev@cloudstack.apache.org; Brian Federle; 
Jessica Wang; Mike Tutkowski; Harikrishna Patnala
Subject: Re: Resetting a VM is broken?
>> the Reset Vm option is presented as a button unlike the icons
I think this was because all the other icons we tried to represent this with 
were too confusing to users - they were clicking on 'reset VM' thinking it was 
'reboot VM' - then as a last minute fix the decision was to just to show a text 
label.

Any ideas from anyone on what would be a good icon representation?

-Brian

On Mar 19, 2014, at 3:02 PM, Alena Prokharchyk 
mailto:alena.prokharc...@citrix.com>> wrote:

> 1) Didn't notice "the elephant" - that the Reset Vm option is presented as
> a button unlike the icons for other options. UI folks - Brian/Jessica- why
> we decided to represent this option differently in the UI?
>
> 2) Mike, I've looked at the code and the history. We've always allocated a
> new volume during the vm restore call. Hari, can you please confirm that
> this feature you wrote, was designed to work this way
>
>
> -Alena.
>
>
> On 3/19/14, 2:41 PM, "Mike Tutkowski" 
> mailto:mike.tutkow...@solidfire.com>> wrote:
>
>> To clarify: Reboot VM seemed to keep the VM running and just reboot the
>> OS.
>>
>> Reset VM seemed to shut the VM down and then re-start it (with the same
>> root disk for the OS).
>>
>>
>> On Wed, Mar 19, 2014 at 3:40 PM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>>> I could be wrong, but I thought as recently as 4.3 that Reset VM
>>> essentially stopped and then re-started the VM with the same root disk.
>>>
>>> It seemed to differ from Reboot VM only in the sense that the VM was
>>> never
>>> technically stopped (the OS inside the VM was just rebooted).
>>>
>>>
>>> On Wed, Mar 19, 2014 at 3:38 PM, Mike Tutkowski <
>>> mike.tutkow...@solidfire.com> wrote:
>>>
 I'm using XenServer 6.1 hosts (two of them) in this case.


 On Wed, Mar 19, 2014 at 3:37 PM, Mike Tutkowski <
 mike.tutkow...@solidfire.com> wrote:

> Yeah, stopping and restarting works fine...as does, I believe,
> rebooting
> the VM.
>
> Right below Reboot VM, there is a Reset VM option.
>
> If that means "re-install," then we probably should clean up the old
> root disk.
>
>
> On Wed, Mar 19, 2014 at 3:30 PM, Alena Prokharchyk <
> alena.prokharc...@citrix.com> wrote:
>
>> don¹t see ³Reset Vm² option in UI; do you mean ³Reboot instance²?
>> I¹ve
>> just tried that, as well as c

Re: Resetting a VM is broken?

OK, thanks for the history there.

What about the text we're using? Are we OK with Reset VM, for example?

Thanks!


On Thu, Mar 20, 2014 at 12:26 PM, Jessica Wang wrote:

>  Mike,
>
>
>
> Right.
>
>
>
> The history is recoverVirtualMachine API was created several years ago,
> restoreVirtualMachine didn't exist yet at that time.
>
> So, the icon that fires recoverVirtualMachine API was labeled as "Restore"
> at that time.
>
>
>
> restoreVirtualMachine API came along several years later.
>
> Then, since label "Restore" has already taken, the icon that fires
> restoreVirtualMachine API was therefore labeled as "Reset".
>
>
>
> The result is indeed weird.
>
> We'll fix the label to match API name.
>
>
>
> Jessica
>
>
>
> *From:* Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> *Sent:* Thursday, March 20, 2014 11:03 AM
> *To:* Jessica Wang
> *Cc:* Brian Federle; Harikrishna Patnala; Alena Prokharchyk;
> dev@cloudstack.apache.org; Stephen Turner
>
> *Subject:* Re: Resetting a VM is broken?
>
>
>
> Thanks, Jessica
>
>
>
> The even weirder part, though, is that the text Restore maps to the
> recoverVirtualMachine API and the text Reset VM maps to the
> restoreVirtualMachine.
>
>
>
> On Thu, Mar 20, 2014 at 11:58 AM, Jessica Wang 
> wrote:
>
> > [Mike Tutkowski] Unless I'm reading this incorrectly, it looks like
>
> > label.action.restore.instance (Restore Instance) maps to
> recoverVirtualMachine
> > and
> > label.resetVM (Reset VM) maps to restoreVirtualMachine
>
>  Yes, this is confusing.
> I'll file an UI bug to match icon label with API name.
> i.e. The icon that fires recoverVirtualMachine API will be labeled as
> "Recover"
> and the icon that fires restoreVirtualMachine API will be labeled as
> "Restore"
>
>
>
> -Original Message-
> From: Brian Federle
> Sent: Thursday, March 20, 2014 10:29 AM
> To: Alena Prokharchyk
> Cc: dev@cloudstack.apache.org; Brian Federle; Jessica Wang; Mike
> Tutkowski; Harikrishna Patnala
> Subject: Re: Resetting a VM is broken?
>
> >> the Reset Vm option is presented as a button unlike the icons
>
> I think this was because all the other icons we tried to represent this
> with were too confusing to users - they were clicking on 'reset VM'
> thinking it was 'reboot VM' - then as a last minute fix the decision was to
> just to show a text label.
>
>
> Any ideas from anyone on what would be a good icon representation?
>
> -Brian
>
> On Mar 19, 2014, at 3:02 PM, Alena Prokharchyk <
> alena.prokharc...@citrix.com> wrote:
>
> > 1) Didn't notice "the elephant" - that the Reset Vm option is presented
> as
> > a button unlike the icons for other options. UI folks - Brian/Jessica-
> why
> > we decided to represent this option differently in the UI?
> >
> > 2) Mike, I've looked at the code and the history. We've always allocated
> a
> > new volume during the vm restore call. Hari, can you please confirm that
> > this feature you wrote, was designed to work this way
> >
> >
> > -Alena.
> >
> >
> > On 3/19/14, 2:41 PM, "Mike Tutkowski" 
> wrote:
> >
> >> To clarify: Reboot VM seemed to keep the VM running and just reboot the
> >> OS.
> >>
> >> Reset VM seemed to shut the VM down and then re-start it (with the same
> >> root disk for the OS).
> >>
> >>
> >> On Wed, Mar 19, 2014 at 3:40 PM, Mike Tutkowski <
> >> mike.tutkow...@solidfire.com> wrote:
> >>
> >>> I could be wrong, but I thought as recently as 4.3 that Reset VM
> >>> essentially stopped and then re-started the VM with the same root disk.
> >>>
> >>> It seemed to differ from Reboot VM only in the sense that the VM was
> >>> never
> >>> technically stopped (the OS inside the VM was just rebooted).
> >>>
> >>>
> >>> On Wed, Mar 19, 2014 at 3:38 PM, Mike Tutkowski <
> >>> mike.tutkow...@solidfire.com> wrote:
> >>>
>  I'm using XenServer 6.1 hosts (two of them) in this case.
> 
> 
>  On Wed, Mar 19, 2014 at 3:37 PM, Mike Tutkowski <
>  mike.tutkow...@solidfire.com> wrote:
> 
> > Yeah, stopping and restarting works fine...as does, I believe,
> > rebooting
> > the VM.
> >
> > Right below Reboot VM, there is a Reset VM option.
> >
> > If that means "re-install," then we probably should clean up the old
> > root disk.
> >
> >
> > On Wed, Mar 19, 2014 at 3:30 PM, Alena Prokharchyk <
> > alena.prokharc...@citrix.com> wrote:
> >
> >> don¹t see ³Reset Vm² option in UI; do you mean ³Reboot instance²?
> >> I¹ve
> >> just tried that, as well as calling stop/startVM from the UI. The Vm
> >> boots
> >> up with its original disk.
> >>
> >> I¹m having Xen/Nfs, not sure it matters
> >>
> >> -Alena.
> >>
> >> On 3/19/14, 2:19 PM, "Mike Tutkowski"  >
> >> wrote:
> >>
> >>> I didn't look into what the GUI calls, but I invoked the Reset VM
> >> option
> >>> in
> >>> the GUI.
> >>>
> >>> Thanks
> >>>
> >>>
> >>> On Wed, Mar 19, 2014 at 3:17 PM, Alena Prokharchyk <
> >>> alena.pro

RE: Resetting a VM is broken?

Mike,

Right.

The history is recoverVirtualMachine API was created several years ago, 
restoreVirtualMachine didn't exist yet at that time.
So, the icon that fires recoverVirtualMachine API was labeled as "Restore" at 
that time.

restoreVirtualMachine API came along several years later.
Then, since label "Restore" has already taken, the icon that fires 
restoreVirtualMachine API was therefore labeled as "Reset".

The result is indeed weird.
We'll fix the label to match API name.

Jessica

From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Thursday, March 20, 2014 11:03 AM
To: Jessica Wang
Cc: Brian Federle; Harikrishna Patnala; Alena Prokharchyk; 
dev@cloudstack.apache.org; Stephen Turner
Subject: Re: Resetting a VM is broken?

Thanks, Jessica

The even weirder part, though, is that the text Restore maps to the 
recoverVirtualMachine API and the text Reset VM maps to the 
restoreVirtualMachine.

On Thu, Mar 20, 2014 at 11:58 AM, Jessica Wang 
mailto:jessica.w...@citrix.com>> wrote:
> [Mike Tutkowski] Unless I'm reading this incorrectly, it looks like
> label.action.restore.instance (Restore Instance) maps to recoverVirtualMachine
> and
> label.resetVM (Reset VM) maps to restoreVirtualMachine

Yes, this is confusing.
I'll file an UI bug to match icon label with API name.
i.e. The icon that fires recoverVirtualMachine API will be labeled as "Recover"
and the icon that fires restoreVirtualMachine API will be labeled as "Restore"


-Original Message-
From: Brian Federle
Sent: Thursday, March 20, 2014 10:29 AM
To: Alena Prokharchyk
Cc: dev@cloudstack.apache.org; Brian Federle; 
Jessica Wang; Mike Tutkowski; Harikrishna Patnala
Subject: Re: Resetting a VM is broken?
>> the Reset Vm option is presented as a button unlike the icons
I think this was because all the other icons we tried to represent this with 
were too confusing to users - they were clicking on 'reset VM' thinking it was 
'reboot VM' - then as a last minute fix the decision was to just to show a text 
label.

Any ideas from anyone on what would be a good icon representation?

-Brian

On Mar 19, 2014, at 3:02 PM, Alena Prokharchyk 
mailto:alena.prokharc...@citrix.com>> wrote:

> 1) Didn't notice "the elephant" - that the Reset Vm option is presented as
> a button unlike the icons for other options. UI folks - Brian/Jessica- why
> we decided to represent this option differently in the UI?
>
> 2) Mike, I've looked at the code and the history. We've always allocated a
> new volume during the vm restore call. Hari, can you please confirm that
> this feature you wrote, was designed to work this way
>
>
> -Alena.
>
>
> On 3/19/14, 2:41 PM, "Mike Tutkowski" 
> mailto:mike.tutkow...@solidfire.com>> wrote:
>
>> To clarify: Reboot VM seemed to keep the VM running and just reboot the
>> OS.
>>
>> Reset VM seemed to shut the VM down and then re-start it (with the same
>> root disk for the OS).
>>
>>
>> On Wed, Mar 19, 2014 at 3:40 PM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>>> I could be wrong, but I thought as recently as 4.3 that Reset VM
>>> essentially stopped and then re-started the VM with the same root disk.
>>>
>>> It seemed to differ from Reboot VM only in the sense that the VM was
>>> never
>>> technically stopped (the OS inside the VM was just rebooted).
>>>
>>>
>>> On Wed, Mar 19, 2014 at 3:38 PM, Mike Tutkowski <
>>> mike.tutkow...@solidfire.com> wrote:
>>>
 I'm using XenServer 6.1 hosts (two of them) in this case.


 On Wed, Mar 19, 2014 at 3:37 PM, Mike Tutkowski <
 mike.tutkow...@solidfire.com> wrote:

> Yeah, stopping and restarting works fine...as does, I believe,
> rebooting
> the VM.
>
> Right below Reboot VM, there is a Reset VM option.
>
> If that means "re-install," then we probably should clean up the old
> root disk.
>
>
> On Wed, Mar 19, 2014 at 3:30 PM, Alena Prokharchyk <
> alena.prokharc...@citrix.com> wrote:
>
>> don¹t see ³Reset Vm² option in UI; do you mean ³Reboot instance²?
>> I¹ve
>> just tried that, as well as calling stop/startVM from the UI. The Vm
>> boots
>> up with its original disk.
>>
>> I¹m having Xen/Nfs, not sure it matters
>>
>> -Alena.
>>
>> On 3/19/14, 2:19 PM, "Mike Tutkowski" 
>> mailto:mike.tutkow...@solidfire.com>>
>> wrote:
>>
>>> I didn't look into what the GUI calls, but I invoked the Reset VM
>> option
>>> in
>>> the GUI.
>>>
>>> Thanks
>>>
>>>
>>> On Wed, Mar 19, 2014 at 3:17 PM, Alena Prokharchyk <
>>> alena.prokharc...@citrix.com> 
>>> wrote:
>>>
 Mike, just to confirm - did you call
 stopVirtualMachine/startVirtualMachine apis?

 -alen

RE: Errors building master

Hugo/Daan,

Could you roll back the commit related to the 'VolumeServiceImpl.java' file 
commit. I'm working on a fix however the build is now no longer working so I 
need to resolve that issue first.

Regards

Alex Hitchins

D: +44 1892 523 587 | S: +44 2036 030 540 | M: +44 7788 423 969

alex.hitch...@shapeblue.com

-Original Message-
From: Alex Hitchins [mailto:alex.hitch...@shapeblue.com]
Sent: 20 March 2014 18:07
To: dev@cloudstack.apache.org
Subject: RE: Errors building master

Ah, yes - that's related to my last patch. I'll log it and raise a new request.

Sorry everyone.

Regards

Alex Hitchins

D: +44 1892 523 587 | S: +44 2036 030 540 | M: +44 7788 423 969

alex.hitch...@shapeblue.com

-Original Message-
From: Laszlo Hornyak [mailto:laszlo.horn...@gmail.com]
Sent: 20 March 2014 17:59
To: dev@cloudstack.apache.org
Subject: Re: Errors building master

Hi Alex,

It should be OK if you recompile, the required module is in the module tree.
Btw I am getting a compile error:
engine/storage/volume/src/org/apache/cloudstack/storage/volume/VolumeServiceImpl.java:[1502,12]
error: unreported exception ResourceAllocationException; must be caught or 
declared to be thrown

On Thu, Mar 20, 2014 at 12:40 PM, Alex Hitchins  wrote:

>
> Anyone else seing this?
>
> [ERROR] Failed to execute goal on project cloud-client-ui: Could not
> resolve dependencies for project
> org.apache.cloudstack:cloud-client-ui:war:4.5.0-SNAPSHOT:
> Could not find artifact
> org.apache.cloudstack:cloud-plugin-storage-volume-cloudbyte:jar:4.5.0-
> SNAPSHOT in apache.snapshots (http://repository.apache.org/snapshots)
> -> [Help 1]
>
> Is there somewhere I can manually download the cloudbyte dependency?
>
> Alex
>
> .
> Need Enterprise Grade Support for Apache CloudStack?
> Our CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/> offers the
> best
> 24/7 SLA for CloudStack Environments.
>
> Apache CloudStack Bootcamp training courses
>
> **NEW!** CloudStack 4.2.1 training<
> http://shapeblue.com/cloudstack-training/>
> 18th-19th February 2014, Brazil. Classroom<
> http://shapeblue.com/cloudstack-training/>
> 17th-23rd March 2014, Region A. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
> 24th-28th March 2014, Region B. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
> 16th-20th June 2014, Region A. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
> 23rd-27th June 2014, Region B. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
>
> This email and any attachments to it may be confidential and are
> intended solely for the use of the individual to whom it is addressed.
> Any views or opinions expressed are solely those of the author and do
> not necessarily represent those of Shape Blue Ltd or related
> companies. If you are not the intended recipient of this email, you
> must neither take any action based upon its contents, nor copy or show
> it to anyone. Please contact the sender if you believe you have
> received this email in error. Shape Blue Ltd is a company incorporated
> in England & Wales. ShapeBlue Services India LLP is a company
> incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
> Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a 
> registered trademark.
>

--

EOF
This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
B

RE: Errors building master

Ah, yes - that's related to my last patch. I'll log it and raise a new request.

Sorry everyone.

Regards

Alex Hitchins

D: +44 1892 523 587 | S: +44 2036 030 540 | M: +44 7788 423 969

alex.hitch...@shapeblue.com

-Original Message-
From: Laszlo Hornyak [mailto:laszlo.horn...@gmail.com]
Sent: 20 March 2014 17:59
To: dev@cloudstack.apache.org
Subject: Re: Errors building master

Hi Alex,

It should be OK if you recompile, the required module is in the module tree.
Btw I am getting a compile error:
engine/storage/volume/src/org/apache/cloudstack/storage/volume/VolumeServiceImpl.java:[1502,12]
error: unreported exception ResourceAllocationException; must be caught or 
declared to be thrown

On Thu, Mar 20, 2014 at 12:40 PM, Alex Hitchins  wrote:

>
> Anyone else seing this?
>
> [ERROR] Failed to execute goal on project cloud-client-ui: Could not
> resolve dependencies for project
> org.apache.cloudstack:cloud-client-ui:war:4.5.0-SNAPSHOT:
> Could not find artifact
> org.apache.cloudstack:cloud-plugin-storage-volume-cloudbyte:jar:4.5.0-
> SNAPSHOT in apache.snapshots (http://repository.apache.org/snapshots)
> -> [Help 1]
>
> Is there somewhere I can manually download the cloudbyte dependency?
>
> Alex
>
> .
> Need Enterprise Grade Support for Apache CloudStack?
> Our CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/> offers the
> best
> 24/7 SLA for CloudStack Environments.
>
> Apache CloudStack Bootcamp training courses
>
> **NEW!** CloudStack 4.2.1 training<
> http://shapeblue.com/cloudstack-training/>
> 18th-19th February 2014, Brazil. Classroom<
> http://shapeblue.com/cloudstack-training/>
> 17th-23rd March 2014, Region A. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
> 24th-28th March 2014, Region B. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
> 16th-20th June 2014, Region A. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
> 23rd-27th June 2014, Region B. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
>
> This email and any attachments to it may be confidential and are
> intended solely for the use of the individual to whom it is addressed.
> Any views or opinions expressed are solely those of the author and do
> not necessarily represent those of Shape Blue Ltd or related
> companies. If you are not the intended recipient of this email, you
> must neither take any action based upon its contents, nor copy or show
> it to anyone. Please contact the sender if you believe you have
> received this email in error. Shape Blue Ltd is a company incorporated
> in England & Wales. ShapeBlue Services India LLP is a company
> incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
> Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a 
> registered trademark.
>

--

EOF
This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.

Build failed in Jenkins: cloudstack-4.4-maven-build #25

2014-03-20 Thread jenkins

See 

Changes:

[chris.suich] Issue CS-5825 Part Resolution

--
[...truncated 1589 lines...]
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloudstack-services ---
[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Secondary Storage 4.4.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
cloudstack-service-secondary-storage ---
[INFO] Deleting 

 (includes = [**/*], excludes = [])
[INFO] Deleting 

 (includes = [target, dist], excludes = [])
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloudstack-service-secondary-storage ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloudstack-service-secondary-storage ---
[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Secondary Storage Service 4.4.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
cloud-secondary-storage ---
[INFO] Deleting 

 (includes = [**/*], excludes = [])
[INFO] Deleting 

 (includes = [target, dist], excludes = [])
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-secondary-storage ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-secondary-storage ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
cloud-secondary-storage ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
cloud-secondary-storage ---
[INFO] Compiling 10 source files to 

[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-secondary-storage ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
cloud-secondary-storage ---
[INFO] Compiling 2 source files to 

[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ 
cloud-secondary-storage ---
[INFO] Tests are skipped.
[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Engine Storage Component 4.4.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ cloud-engine-storage 
---
[INFO] Deleting 

 (includes = [**/*], excludes = [])
[INFO] Deleting 

 (includes = [target, dist], excludes = [])
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-engine-storage ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-engine-storage ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
cloud-engine-storage ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
cloud-engine-storage ---
[INFO] Compiling 60 source files to 

[INFO] 
[I

Re: Review Request 19463: UI: Applied localization function to labels on Zone Chart page


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

Ship it!


Ship It!

- Brian Federle


On March 20, 2014, 2:11 p.m., Mihaela Stoica wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19463/
> ---
> 
> (Updated March 20, 2014, 2:11 p.m.)
> 
> 
> Review request for cloudstack, Brian Federle and Jessica Wang.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> This fixes the following issue: 
> Some labels on the Zone Chart page display the wrong text, e.g. 
> 'label.view.all' instead of 'View all', 'label.pods' instead of 'Pods'.
> 
> 
> Diffs
> -
> 
>   ui/scripts/ui-custom/zoneChart.js bc30d51 
> 
> Diff: https://reviews.apache.org/r/19463/diff/
> 
> 
> Testing
> ---
> 
> Yes
> 
> 
> Thanks,
> 
> Mihaela Stoica
> 
>

RE: Resetting a VM is broken?

> [Mike Tutkowski] Unless I'm reading this incorrectly, it looks like  
> label.action.restore.instance (Restore Instance) maps to 
> recoverVirtualMachine  
> and  
> label.resetVM (Reset VM) maps to restoreVirtualMachine  


Yes, this is confusing.
I'll file an UI bug to match icon label with API name.
i.e. The icon that fires recoverVirtualMachine API will be labeled as "Recover" 
and the icon that fires restoreVirtualMachine API will be labeled as "Restore" 


-Original Message-
From: Brian Federle 
Sent: Thursday, March 20, 2014 10:29 AM
To: Alena Prokharchyk
Cc: dev@cloudstack.apache.org; Brian Federle; Jessica Wang; Mike Tutkowski; 
Harikrishna Patnala
Subject: Re: Resetting a VM is broken?

>> the Reset Vm option is presented as a button unlike the icons 

I think this was because all the other icons we tried to represent this with 
were too confusing to users - they were clicking on 'reset VM' thinking it was 
'reboot VM' - then as a last minute fix the decision was to just to show a text 
label.

Any ideas from anyone on what would be a good icon representation?

-Brian

On Mar 19, 2014, at 3:02 PM, Alena Prokharchyk  
wrote:

> 1) Didn't notice "the elephant" - that the Reset Vm option is presented as
> a button unlike the icons for other options. UI folks - Brian/Jessica- why
> we decided to represent this option differently in the UI?
> 
> 2) Mike, I've looked at the code and the history. We've always allocated a
> new volume during the vm restore call. Hari, can you please confirm that
> this feature you wrote, was designed to work this way
> 
> 
> -Alena.
> 
> 
> On 3/19/14, 2:41 PM, "Mike Tutkowski"  wrote:
> 
>> To clarify: Reboot VM seemed to keep the VM running and just reboot the
>> OS.
>> 
>> Reset VM seemed to shut the VM down and then re-start it (with the same
>> root disk for the OS).
>> 
>> 
>> On Wed, Mar 19, 2014 at 3:40 PM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>> 
>>> I could be wrong, but I thought as recently as 4.3 that Reset VM
>>> essentially stopped and then re-started the VM with the same root disk.
>>> 
>>> It seemed to differ from Reboot VM only in the sense that the VM was
>>> never
>>> technically stopped (the OS inside the VM was just rebooted).
>>> 
>>> 
>>> On Wed, Mar 19, 2014 at 3:38 PM, Mike Tutkowski <
>>> mike.tutkow...@solidfire.com> wrote:
>>> 
 I'm using XenServer 6.1 hosts (two of them) in this case.
 
 
 On Wed, Mar 19, 2014 at 3:37 PM, Mike Tutkowski <
 mike.tutkow...@solidfire.com> wrote:
 
> Yeah, stopping and restarting works fine...as does, I believe,
> rebooting
> the VM.
> 
> Right below Reboot VM, there is a Reset VM option.
> 
> If that means "re-install," then we probably should clean up the old
> root disk.
> 
> 
> On Wed, Mar 19, 2014 at 3:30 PM, Alena Prokharchyk <
> alena.prokharc...@citrix.com> wrote:
> 
>> don¹t see ³Reset Vm² option in UI; do you mean ³Reboot instance²?
>> I¹ve
>> just tried that, as well as calling stop/startVM from the UI. The Vm
>> boots
>> up with its original disk.
>> 
>> I¹m having Xen/Nfs, not sure it matters
>> 
>> -Alena.
>> 
>> On 3/19/14, 2:19 PM, "Mike Tutkowski" 
>> wrote:
>> 
>>> I didn't look into what the GUI calls, but I invoked the Reset VM
>> option
>>> in
>>> the GUI.
>>> 
>>> Thanks
>>> 
>>> 
>>> On Wed, Mar 19, 2014 at 3:17 PM, Alena Prokharchyk <
>>> alena.prokharc...@citrix.com> wrote:
>>> 
 Mike, just to confirm - did you call
 stopVirtualMachine/startVirtualMachine apis?
 
 -alena.
 
 On 3/19/14, 1:55 PM, "Mike Tutkowski"
>> 
 wrote:
 
> Hi,
> 
> I noticed today while running through some test cases for 4.4
>> that
> resetting a VM does not work as expected.
> 
> Instead of the typical stop and re-start behavior where the VM is
 booted
> back up using the same root disk, the VM gets a new root disk
>> when
>> it
 is
> booted back up.
> 
> Can anyone confirm this finding for me with his or her setup?
> 
> Thanks!
> 
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *(tm)*
 
 
>>> 
>>> 
>>> --
>>> *Mike Tutkowski*
>>> *Senior CloudStack Developer, SolidFire Inc.*
>>> e: mike.tutkow...@solidfire.com
>>> o: 303.746.7302
>>> Advancing the way the world uses the
>>> cloud
>>> *(tm)*
>> 
>> 
> 
> 
> --
> *Mike Tutkowski*
> *Senior CloudStack

Re: Errors building master

Hi Alex,

It should be OK if you recompile, the required module is in the module tree.
Btw I am getting a compile error:
engine/storage/volume/src/org/apache/cloudstack/storage/volume/VolumeServiceImpl.java:[1502,12]
error: unreported exception ResourceAllocationException; must be caught or
declared to be thrown




On Thu, Mar 20, 2014 at 12:40 PM, Alex Hitchins  wrote:

>
> Anyone else seing this?
>
> [ERROR] Failed to execute goal on project cloud-client-ui: Could not
> resolve dependencies for project
> org.apache.cloudstack:cloud-client-ui:war:4.5.0-SNAPSHOT:
> Could not find artifact
> org.apache.cloudstack:cloud-plugin-storage-volume-cloudbyte:jar:4.5.0-SNAPSHOT
> in apache.snapshots (http://repository.apache.org/snapshots) -> [Help 1]
>
> Is there somewhere I can manually download the cloudbyte dependency?
>
> Alex
>
> .
> Need Enterprise Grade Support for Apache CloudStack?
> Our CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/> offers the best
> 24/7 SLA for CloudStack Environments.
>
> Apache CloudStack Bootcamp training courses
>
> **NEW!** CloudStack 4.2.1 training<
> http://shapeblue.com/cloudstack-training/>
> 18th-19th February 2014, Brazil. Classroom<
> http://shapeblue.com/cloudstack-training/>
> 17th-23rd March 2014, Region A. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
> 24th-28th March 2014, Region B. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
> 16th-20th June 2014, Region A. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
> 23rd-27th June 2014, Region B. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
>
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error. Shape Blue Ltd is a
> company incorporated in England & Wales. ShapeBlue Services India LLP is a
> company incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
> and is operated under license from Shape Blue Ltd. ShapeBlue is a
> registered trademark.
>



-- 

EOF

RE: Resetting a VM is broken?

Perhaps a recycle icon would be better? To me it makes more sense.

I do like the idea of making sure via dialogs that the user knows what they are 
doing. Perhaps configurable so for private clouds where sysadmins know their 
stuff they don't get prompted.


Regards

Alex Hitchins

D: +44 1892 523 587 | S: +44 2036 030 540 | M: +44 7788 423 969

alex.hitch...@shapeblue.com

-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: 20 March 2014 17:38
To: Brian Federle
Cc: Alena Prokharchyk; dev@cloudstack.apache.org; Jessica Wang; Harikrishna 
Patnala
Subject: Re: Resetting a VM is broken?

I don't really have an opinion regarding icons, but maybe another idea here 
would be to provide a detailed explanation in the confirmation dialog of what's 
about to happen since it could lead to data loss (unless you follow John's 
solution of the management server having to be stopped, which seems like a lot 
of work in a multi-management server environment).


On Thu, Mar 20, 2014 at 11:29 AM, Brian Federle wrote:

> >> the Reset Vm option is presented as a button unlike the icons
>
> I think this was because all the other icons we tried to represent
> this with were too confusing to users -- they were clicking on 'reset VM'
> thinking it was 'reboot VM' -- then as a last minute fix the decision
> was to just to show a text label.
>
> Any ideas from anyone on what would be a good icon representation?
>
> -Brian
>
> On Mar 19, 2014, at 3:02 PM, Alena Prokharchyk <
> alena.prokharc...@citrix.com> wrote:
>
> > 1) Didn't notice "the elephant" - that the Reset Vm option is
> > presented
> as
> > a button unlike the icons for other options. UI folks -
> > Brian/Jessica-
> why
> > we decided to represent this option differently in the UI?
> >
> > 2) Mike, I've looked at the code and the history. We've always
> > allocated
> a
> > new volume during the vm restore call. Hari, can you please confirm
> > that this feature you wrote, was designed to work this way
> >
> >
> > -Alena.
> >
> >
> > On 3/19/14, 2:41 PM, "Mike Tutkowski" 
> wrote:
> >
> >> To clarify: Reboot VM seemed to keep the VM running and just reboot
> >> the OS.
> >>
> >> Reset VM seemed to shut the VM down and then re-start it (with the
> >> same root disk for the OS).
> >>
> >>
> >> On Wed, Mar 19, 2014 at 3:40 PM, Mike Tutkowski <
> >> mike.tutkow...@solidfire.com> wrote:
> >>
> >>> I could be wrong, but I thought as recently as 4.3 that Reset VM
> >>> essentially stopped and then re-started the VM with the same root disk.
> >>>
> >>> It seemed to differ from Reboot VM only in the sense that the VM
> >>> was never technically stopped (the OS inside the VM was just
> >>> rebooted).
> >>>
> >>>
> >>> On Wed, Mar 19, 2014 at 3:38 PM, Mike Tutkowski <
> >>> mike.tutkow...@solidfire.com> wrote:
> >>>
>  I'm using XenServer 6.1 hosts (two of them) in this case.
> 
> 
>  On Wed, Mar 19, 2014 at 3:37 PM, Mike Tutkowski <
>  mike.tutkow...@solidfire.com> wrote:
> 
> > Yeah, stopping and restarting works fine...as does, I believe,
> > rebooting the VM.
> >
> > Right below Reboot VM, there is a Reset VM option.
> >
> > If that means "re-install," then we probably should clean up the
> > old root disk.
> >
> >
> > On Wed, Mar 19, 2014 at 3:30 PM, Alena Prokharchyk <
> > alena.prokharc...@citrix.com> wrote:
> >
> >> don¹t see ³Reset Vm² option in UI; do you mean ³Reboot instance²?
> >> I¹ve
> >> just tried that, as well as calling stop/startVM from the UI.
> >> The Vm boots up with its original disk.
> >>
> >> I¹m having Xen/Nfs, not sure it matters
> >>
> >> -Alena.
> >>
> >> On 3/19/14, 2:19 PM, "Mike Tutkowski"
> >>  >
> >> wrote:
> >>
> >>> I didn't look into what the GUI calls, but I invoked the Reset
> >>> VM
> >> option
> >>> in
> >>> the GUI.
> >>>
> >>> Thanks
> >>>
> >>>
> >>> On Wed, Mar 19, 2014 at 3:17 PM, Alena Prokharchyk <
> >>> alena.prokharc...@citrix.com> wrote:
> >>>
>  Mike, just to confirm - did you call
>  stopVirtualMachine/startVirtualMachine apis?
> 
>  -alena.
> 
>  On 3/19/14, 1:55 PM, "Mike Tutkowski"
> >> 
>  wrote:
> 
> > Hi,
> >
> > I noticed today while running through some test cases for
> > 4.4
> >> that
> > resetting a VM does not work as expected.
> >
> > Instead of the typical stop and re-start behavior where the
> > VM is
>  booted
> > back up using the same root disk, the VM gets a new root
> > disk
> >> when
> >> it
>  is
> > booted back up.
> >
> > Can anyone confirm this finding for me with his or her setup?
> >
> > Thanks!
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Dev

Re: Resetting a VM is broken?

Thanks, Jessica

The even weirder part, though, is that the text Restore maps to the
recoverVirtualMachine API and the text Reset VM maps to the
restoreVirtualMachine.


On Thu, Mar 20, 2014 at 11:58 AM, Jessica Wang wrote:

> > [Mike Tutkowski] Unless I'm reading this incorrectly, it looks like
> > label.action.restore.instance (Restore Instance) maps to
> recoverVirtualMachine
> > and
> > label.resetVM (Reset VM) maps to restoreVirtualMachine
>
>
> Yes, this is confusing.
> I'll file an UI bug to match icon label with API name.
> i.e. The icon that fires recoverVirtualMachine API will be labeled as
> "Recover"
> and the icon that fires restoreVirtualMachine API will be labeled as
> "Restore"
>
>
> -Original Message-
> From: Brian Federle
> Sent: Thursday, March 20, 2014 10:29 AM
> To: Alena Prokharchyk
> Cc: dev@cloudstack.apache.org; Brian Federle; Jessica Wang; Mike
> Tutkowski; Harikrishna Patnala
> Subject: Re: Resetting a VM is broken?
>
> >> the Reset Vm option is presented as a button unlike the icons
>
> I think this was because all the other icons we tried to represent this
> with were too confusing to users - they were clicking on 'reset VM'
> thinking it was 'reboot VM' - then as a last minute fix the decision was to
> just to show a text label.
>
> Any ideas from anyone on what would be a good icon representation?
>
> -Brian
>
> On Mar 19, 2014, at 3:02 PM, Alena Prokharchyk <
> alena.prokharc...@citrix.com> wrote:
>
> > 1) Didn't notice "the elephant" - that the Reset Vm option is presented
> as
> > a button unlike the icons for other options. UI folks - Brian/Jessica-
> why
> > we decided to represent this option differently in the UI?
> >
> > 2) Mike, I've looked at the code and the history. We've always allocated
> a
> > new volume during the vm restore call. Hari, can you please confirm that
> > this feature you wrote, was designed to work this way
> >
> >
> > -Alena.
> >
> >
> > On 3/19/14, 2:41 PM, "Mike Tutkowski" 
> wrote:
> >
> >> To clarify: Reboot VM seemed to keep the VM running and just reboot the
> >> OS.
> >>
> >> Reset VM seemed to shut the VM down and then re-start it (with the same
> >> root disk for the OS).
> >>
> >>
> >> On Wed, Mar 19, 2014 at 3:40 PM, Mike Tutkowski <
> >> mike.tutkow...@solidfire.com> wrote:
> >>
> >>> I could be wrong, but I thought as recently as 4.3 that Reset VM
> >>> essentially stopped and then re-started the VM with the same root disk.
> >>>
> >>> It seemed to differ from Reboot VM only in the sense that the VM was
> >>> never
> >>> technically stopped (the OS inside the VM was just rebooted).
> >>>
> >>>
> >>> On Wed, Mar 19, 2014 at 3:38 PM, Mike Tutkowski <
> >>> mike.tutkow...@solidfire.com> wrote:
> >>>
>  I'm using XenServer 6.1 hosts (two of them) in this case.
> 
> 
>  On Wed, Mar 19, 2014 at 3:37 PM, Mike Tutkowski <
>  mike.tutkow...@solidfire.com> wrote:
> 
> > Yeah, stopping and restarting works fine...as does, I believe,
> > rebooting
> > the VM.
> >
> > Right below Reboot VM, there is a Reset VM option.
> >
> > If that means "re-install," then we probably should clean up the old
> > root disk.
> >
> >
> > On Wed, Mar 19, 2014 at 3:30 PM, Alena Prokharchyk <
> > alena.prokharc...@citrix.com> wrote:
> >
> >> don¹t see ³Reset Vm² option in UI; do you mean ³Reboot instance²?
> >> I¹ve
> >> just tried that, as well as calling stop/startVM from the UI. The Vm
> >> boots
> >> up with its original disk.
> >>
> >> I¹m having Xen/Nfs, not sure it matters
> >>
> >> -Alena.
> >>
> >> On 3/19/14, 2:19 PM, "Mike Tutkowski"  >
> >> wrote:
> >>
> >>> I didn't look into what the GUI calls, but I invoked the Reset VM
> >> option
> >>> in
> >>> the GUI.
> >>>
> >>> Thanks
> >>>
> >>>
> >>> On Wed, Mar 19, 2014 at 3:17 PM, Alena Prokharchyk <
> >>> alena.prokharc...@citrix.com> wrote:
> >>>
>  Mike, just to confirm - did you call
>  stopVirtualMachine/startVirtualMachine apis?
> 
>  -alena.
> 
>  On 3/19/14, 1:55 PM, "Mike Tutkowski"
> >> 
>  wrote:
> 
> > Hi,
> >
> > I noticed today while running through some test cases for 4.4
> >> that
> > resetting a VM does not work as expected.
> >
> > Instead of the typical stop and re-start behavior where the VM is
>  booted
> > back up using the same root disk, the VM gets a new root disk
> >> when
> >> it
>  is
> > booted back up.
> >
> > Can anyone confirm this finding for me with his or her setup?
> >
> > Thanks!
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses

Re: Review Request 18964: Windowsfication of CloudStack Management Server - Changes to support windows OS

2014-03-20 Thread Damodar Reddy Talakanti

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

(Updated March 20, 2014, 5:47 p.m.)

Review request for cloudstack, Abhinandan Prateek, Chiradeep Vittal, daan
Hoogland, and Donal Lafferty.

Changes
---

Fixed extra spaces

Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-6105

https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/CLOUDSTACK-6105

Repository: cloudstack-git

Description
---

Windowsfication of CloudStack Management Server

Diffs (updated)
-

scripts/installer/windows/acs.wxs PRE-CREATION
scripts/installer/windows/client.wxs PRE-CREATION
scripts/installer/windows/start.bat PRE-CREATION
scripts/vm/systemvm/injectkeys.py PRE-CREATION
server/src/com/cloud/server/ConfigurationServerImpl.java 4781010
server/test/com/cloud/server/ConfigurationServerImplTest.java 08a2097

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

Testing
---

Tested in Linux environment after changes
Also tested in Windows environment(For now tested on windows-8) to make sure it
is getting installed and management service is running.

Able to add zones, able to register templates, able to launch a VM when it is
running on windows.

Currently though it is getting added as a windows service, not able to start
the service through windows service control manager which I am looking into
currently. When run .exe file which is installed then server is getting up and
able to access cloud stack UI.

For now The following assumptions are made:
1. SSH keys are already installed
2. JAVA is already installed
3. tomcat is already installed

This patch contains the following new files related to WiX tool (To compile and
run we need this tool)
1. acs.wxs
The following command will be used to compile
"\bin\candle.exe" acs.wxs
2. client.wxs
The following command will be used to generate the above file
"\bin\heat" dir client -gg -cg Test -ke -sfrag
-template fragment -out client.wxs -var wix.SourceClient -dr WEBAPPS
The following command will be used to compile the above generated file
"\bin\candle.exe" client.wxs
3. The following command will be used to generate .msi file
"\bin\light.exe" acs.wixobj client.wixobj -out acs.msi
-ext "C:\Program Files (x86)\WiX Toolset v3.8\bin\WixUIExtension.dll"
-dSourceClient=SourceDir\client

Thanks,

Damodar Reddy Talakanti

Re: Resetting a VM is broken?

I don't really have an opinion regarding icons, but maybe another idea here
would be to provide a detailed explanation in the confirmation dialog of
what's about to happen since it could lead to data loss (unless you follow
John's solution of the management server having to be stopped, which seems
like a lot of work in a multi-management server environment).


On Thu, Mar 20, 2014 at 11:29 AM, Brian Federle wrote:

> >> the Reset Vm option is presented as a button unlike the icons
>
> I think this was because all the other icons we tried to represent this
> with were too confusing to users -- they were clicking on 'reset VM'
> thinking it was 'reboot VM' -- then as a last minute fix the decision was to
> just to show a text label.
>
> Any ideas from anyone on what would be a good icon representation?
>
> -Brian
>
> On Mar 19, 2014, at 3:02 PM, Alena Prokharchyk <
> alena.prokharc...@citrix.com> wrote:
>
> > 1) Didn't notice "the elephant" - that the Reset Vm option is presented
> as
> > a button unlike the icons for other options. UI folks - Brian/Jessica-
> why
> > we decided to represent this option differently in the UI?
> >
> > 2) Mike, I've looked at the code and the history. We've always allocated
> a
> > new volume during the vm restore call. Hari, can you please confirm that
> > this feature you wrote, was designed to work this way
> >
> >
> > -Alena.
> >
> >
> > On 3/19/14, 2:41 PM, "Mike Tutkowski" 
> wrote:
> >
> >> To clarify: Reboot VM seemed to keep the VM running and just reboot the
> >> OS.
> >>
> >> Reset VM seemed to shut the VM down and then re-start it (with the same
> >> root disk for the OS).
> >>
> >>
> >> On Wed, Mar 19, 2014 at 3:40 PM, Mike Tutkowski <
> >> mike.tutkow...@solidfire.com> wrote:
> >>
> >>> I could be wrong, but I thought as recently as 4.3 that Reset VM
> >>> essentially stopped and then re-started the VM with the same root disk.
> >>>
> >>> It seemed to differ from Reboot VM only in the sense that the VM was
> >>> never
> >>> technically stopped (the OS inside the VM was just rebooted).
> >>>
> >>>
> >>> On Wed, Mar 19, 2014 at 3:38 PM, Mike Tutkowski <
> >>> mike.tutkow...@solidfire.com> wrote:
> >>>
>  I'm using XenServer 6.1 hosts (two of them) in this case.
> 
> 
>  On Wed, Mar 19, 2014 at 3:37 PM, Mike Tutkowski <
>  mike.tutkow...@solidfire.com> wrote:
> 
> > Yeah, stopping and restarting works fine...as does, I believe,
> > rebooting
> > the VM.
> >
> > Right below Reboot VM, there is a Reset VM option.
> >
> > If that means "re-install," then we probably should clean up the old
> > root disk.
> >
> >
> > On Wed, Mar 19, 2014 at 3:30 PM, Alena Prokharchyk <
> > alena.prokharc...@citrix.com> wrote:
> >
> >> don¹t see ³Reset Vm² option in UI; do you mean ³Reboot instance²?
> >> I¹ve
> >> just tried that, as well as calling stop/startVM from the UI. The Vm
> >> boots
> >> up with its original disk.
> >>
> >> I¹m having Xen/Nfs, not sure it matters
> >>
> >> -Alena.
> >>
> >> On 3/19/14, 2:19 PM, "Mike Tutkowski"  >
> >> wrote:
> >>
> >>> I didn't look into what the GUI calls, but I invoked the Reset VM
> >> option
> >>> in
> >>> the GUI.
> >>>
> >>> Thanks
> >>>
> >>>
> >>> On Wed, Mar 19, 2014 at 3:17 PM, Alena Prokharchyk <
> >>> alena.prokharc...@citrix.com> wrote:
> >>>
>  Mike, just to confirm - did you call
>  stopVirtualMachine/startVirtualMachine apis?
> 
>  -alena.
> 
>  On 3/19/14, 1:55 PM, "Mike Tutkowski"
> >> 
>  wrote:
> 
> > Hi,
> >
> > I noticed today while running through some test cases for 4.4
> >> that
> > resetting a VM does not work as expected.
> >
> > Instead of the typical stop and re-start behavior where the VM is
>  booted
> > back up using the same root disk, the VM gets a new root disk
> >> when
> >> it
>  is
> > booted back up.
> >
> > Can anyone confirm this finding for me with his or her setup?
> >
> > Thanks!
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud
> > *(tm)*
> 
> 
> >>>
> >>>
> >>> --
> >>> *Mike Tutkowski*
> >>> *Senior CloudStack Developer, SolidFire Inc.*
> >>> e: mike.tutkow...@solidfire.com
> >>> o: 303.746.7302
> >>> Advancing the way the world uses the
> >>> cloud
> >>> *(tm)*
> >>
> >>
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFi

Re: [PROPOSAL] Support pure Xen as a hypervisor

2014-03-20 Thread Marco Sinhoreli

+1

Marco Sinhoreli

Consultant Manager

Phone: +55 21 2586 6390 | Fax: +55 21 2586 6002 | Mobile: +55 21 98276
3636

Praia de Botafogo 501, bloco 1 - sala 101, Botafogo, Rio de Janeiro, RJ -
Brazil - CEP 22250-040

marco.sinhor...@shapeblue.com| www.shapeblue.com
 | Twitter: @shapeblue

Apache CloudStack Bootcamp training courses:

**NEW!** CloudStack 4.2 training

This email and any attachments to it may be confidential and are intended
solely for the use of the individual to whom it is addressed. Any views or
opinions expressed are solely those of the author and do not necessarily
represent those of Shape Blue Ltd or related companies. If you are not the
intended recipient of this email, you must neither take any action based
upon its contents, nor copy or show it to anyone. Please contact the
sender if you believe you have received this email in error. Shape Blue
Ltd is a company incorporated in England & Wales. ShapeBlue Services India
LLP and ShapeBlue Brasil Consultoria LTDA are operated under license from
Shape Blue Ltd. ShapeBlue is a registered trademark.

On 18/03/14 12:40, "Tim Mackey"  wrote:

>Historically CloudStack has used Xen and XenServer interchangeably to
>refer
>to any XenAPI based implementation.  With the recent release of Xen
>Project
>4.4 (http://blog.xen.org/index.php/2014/03/10/xen-4-4-released/), and
>interest in alternate architectures like ARM, the loose definition of our
>Xen support could be confusing.  In this two part effort I propose that
>CloudStack 4.4 be cleansed to ensure that all Xen references become
>XenServer references, and second that an alternate hypervisor type of
>"XenProject" be introduced for pure Xen which could either support libvirt
>or  libxl (preference for libvirt given the 4.4 work to improve the
>interface and broader support for libvirt in general).
>
>Cross posted to users to for broader comment.
>
>-tim

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: concole proxy in 4.3RC9

please note that 10.200.23.42 is a xenhost hosting the consoleproxy
and 195.66.90.213 is the cpvm
the ms is localhost with ui on port 8080

On Thu, Mar 20, 2014 at 6:15 PM, Daan Hoogland  wrote:
> btw
>
> the last lines:
>
> 2014-03-20 13:57:09,858 DEBUG [c.c.a.t.Request]
> (1372260265@qtp-1676921458-10:null) Seq 1-762183775: Sending  { Cmd ,
> MgmtId: 24062491136, via: 1(mccdxen2), Ver: v1, Flags: 100011,
> [{"com.cloud.agent.api.GetVncPortCommand":{"id":5,"name":"i-2-5-VM","wait":0}}]
> }
> 2014-03-20 13:57:09,858 DEBUG [c.c.a.t.Request]
> (1372260265@qtp-1676921458-10:null) Seq 1-762183775: Executing:  { Cmd
> , MgmtId: 24062491136, via: 1(mccdxen2), Ver: v1, Flags: 100011,
> [{"com.cloud.agent.api.GetVncPortCommand":{"id":5,"name":"i-2-5-VM","wait":0}}]
> }
> 2014-03-20 13:57:09,859 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-63:ctx-6c8a6687) Seq 1-762183775: Executing request
> 2014-03-20 13:57:09,976 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-63:ctx-6c8a6687) Seq 1-762183775: Response Received:
> 2014-03-20 13:57:09,976 DEBUG [c.c.a.t.Request]
> (DirectAgent-63:ctx-6c8a6687) Seq 1-762183775: Processing:  { Ans: ,
> MgmtId: 24062491136, via: 1, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.GetVncPortAnswer":{"address":"consoleurl=https://10.200.23.42/console?uuid=d539642a-7c78-622e-9c22-e6b3b0771122&sessionref=OpaqueRef:160e30d3-5f3e-255e-ef8a-596e69ad30d4","port":-1,"result":true,"wait":0}}]
> }
> 2014-03-20 13:57:09,976 DEBUG [c.c.a.t.Request]
> (1372260265@qtp-1676921458-10:null) Seq 1-762183775: Received:  { Ans:
> , MgmtId: 24062491136, via: 1, Ver: v1, Flags: 10, { GetVncPortAnswer
> } }
> 2014-03-20 13:57:09,976 DEBUG [c.c.s.ConsoleProxyServlet]
> (1372260265@qtp-1676921458-10:null) Port info
> consoleurl=https://10.200.23.42/console?uuid=d539642a-7c78-622e-9c22-e6b3b0771122&sessionref=OpaqueRef:160e30d3-5f3e-255e-ef8a-596e69ad30d4
> 2014-03-20 13:57:09,976 INFO  [c.c.s.ConsoleProxyServlet]
> (1372260265@qtp-1676921458-10:null) Parse host info returned from
> executing GetVNCPortCommand. host info:
> consoleurl=https://10.200.23.42/console?uuid=d539642a-7c78-622e-9c22-e6b3b0771122&sessionref=OpaqueRef:160e30d3-5f3e-255e-ef8a-596e69ad30d4
> 2014-03-20 13:57:09,979 DEBUG [c.c.s.ConsoleProxyServlet]
> (1372260265@qtp-1676921458-10:null) Compose console url:
> http://195.66.90.213/ajax?token=9Rrl0mjwUQd3Ym9mEb-ziydOD0YOSWJNi_QZFP7efEr1mIalpz2Xg0UvR2eUUyqbgFqNXQJOlt0yJsfkH7CnubShCuEb82qKCD4zf50hyHxZufjglf9NefAuIXRJmmXe10afkEVYHARondjCtJ80RkovHVtQHkErX9s2wB2HT9Zx7kuKGdYmigVQ8_AjqFyusOCQ6XTplJOlr4ZdvSZoafu0dowEYJysruLtBvY9qsi5eMXC4ozvodmRUfBN4jARisUjusBCDUSzQyrdXImCjLFT3cL1GVmdNPQz7L7s3PJrSyMdB9ZZshnzNYAYkCjUtjiLwAf3aJfZt3z3r9TuJg6k5kfhRbBsvpBVtrYcI1DXJfEANZD6g9f4hDRghnsXxrUpPrA973CiSUaKsKzUMqVWM4VuiDtHkWIgk_p100K-ai9wzufJYAk9lZ_vhY9GWYkQhpBtZeupk3Gl5Gc_iudCMwP9kFvEA12i6jNvtng
> 2014-03-20 13:57:09,979 DEBUG [c.c.s.ConsoleProxyServlet]
> (1372260265@qtp-1676921458-10:null) the console url is ::
> g src="http://195.66.90.213/ajax?token=9Rrl0mjwUQd3Ym9mEb-ziydOD0YOSWJNi_QZFP7efEr1mIalpz2Xg0UvR2eUUyqbgFqNXQJOlt0yJsfkH7CnubShCuEb82qKCD4zf50hyHxZufjglf9NefAuIXRJmmXe10afkEVYHARondjCtJ80RkovHVtQHkErX9s2wB2HT9Zx7kuKGdYmigVQ8_AjqFyusOCQ6XTplJOlr4ZdvSZoafu0dowEYJysruLtBvY9qsi5eMXC4ozvodmRUfBN4jARisUjusBCDUSzQyrdXImCjLFT3cL1GVmdNPQz7L7s3PJrSyMdB9ZZshnzNYAYkCjUtjiLwAf3aJfZt3z3r9TuJg6k5kfhRbBsvpBVtrYcI1DXJfEANZD6g9f4hDRghnsXxrUpPrA973CiSUaKsKzUMqVWM4VuiDtHkWIgk_p100K-ai9wzufJYAk9lZ_vhY9GWYkQhpBtZeupk3Gl5Gc_iudCMwP9kFvEA12i6jNvtng";>
>
> and next nothing but the browser saying connection refused.
>
> So what changed? Where do I need to adjust my infra to make it work
> again? Or is my setup not supported anymore?
>
> On Thu, Mar 20, 2014 at 5:49 PM, Daan Hoogland  
> wrote:
>> meaning the console of the ssvm? or the cpvm?
>>
>> I just confirmed myself that there is indeed a diff between 4.2.1 and 4.3RC9
>>
>> On Thu, Mar 20, 2014 at 5:32 PM, Nux!  wrote:
>>> On 20.03.2014 16:29, Ove Ewerlid wrote:

 Console SSVM works in my 4.3 setup.
 Traffic does not use SSL and is on port 80.
>>>
>>>
>>> Did you have to do anything in particular to disable SSL or is this the new
>>> default?
>>>
>>> I was having problems with 4.4 where VC VM was in Alert mode and the VMs'
>>> console was dead; will have to revisit this.
>>>
>>> Lucian
>>>
>>> --
>>> Sent from the Delta quadrant using Borg technology!
>>>
>>> Nux!
>>> www.nux.ro
>>
>>
>>
>> --
>> Daan
>
>
>
> --
> Daan



-- 
Daan

Re: 4.4 and master failing due to missing license header

as long as nothing in git is in it, no

On Thu, Mar 20, 2014 at 6:17 PM, SuichII, Christopher
 wrote:
> Maybe I should add **/target-eclipse/** to the list of excludes for the 
> license checking? Anyone have an objection?
>
> -Chris
> --
> Chris Suich
> chris.su...@netapp.com
> NetApp Software Engineer
> Data Center Platforms - Cloud Solutions
> Citrix, Cisco & Red Hat
>
> On Mar 20, 2014, at 1:08 PM, SuichII, Christopher  
> wrote:
>
>> I tried running the command with -X. There is quite a bit of output, but 
>> this is what I was able to find:
>>
>> ...
>> [WARNING] Missing header in: 
>> /Users/csuich/CloudStack/cloudstack/utils/target-eclipse/test-classes/com/cloud/utils/db/transactionContextBuilderTest.xml
>> ...
>> [WARNING] Missing header in: 
>> /Users/csuich/CloudStack/cloudstack/utils/target-eclipse/test-classes/testContext.xml
>> ...
>> [WARNING] Missing header in: 
>> /Users/csuich/CloudStack/cloudstack/utils/target-eclipse/test-classes/log4j.xml
>> ...
>> [WARNING] Missing header in: 
>> /Users/csuich/CloudStack/cloudstack/utils/target-eclipse/test-classes/com/cloud/utils/QualifierTestContext.xml
>> ...
>>
>> So, it looks like the check license plugin is going after some xml that 
>> Eclipse generates. Should I be telling maven to ignore these somehow? When I 
>> run 'git status', it says my working directory is clean as the .gitignore is 
>> setup to ignore that stuff.
>>
>> -Chris
>> --
>> Chris Suich
>> chris.su...@netapp.com
>> NetApp Software Engineer
>> Data Center Platforms - Cloud Solutions
>> Citrix, Cisco & Red Hat
>>
>> On Mar 20, 2014, at 12:54 PM, Daan Hoogland  wrote:
>>
>>> So the offending file is in utils. Doesn't it give info above the BUIL
>>> FAILURE line?
>>>
>>> On Thu, Mar 20, 2014 at 5:52 PM, SuichII, Christopher
>>>  wrote:
 Hey all,

 I'm unable to build on 4.4 and master with no changes made in either 
 branch. It appears that there are some files which don't meet the license 
 header requirement. I don't see one, but is there a profile for ignoring 
 the check license plugin? Alternatively, does anyone know what files are 
 offending or how to easily fix this?

 [INFO] 
 
 [INFO] BUILD FAILURE
 [INFO] 
 
 [INFO] Total time: 14.076s
 [INFO] Finished at: Thu Mar 20 12:48:27 EDT 2014
 [INFO] Final Memory: 40M/96M
 [INFO] 
 
 [ERROR] Failed to execute goal com.mycila:license-maven-plugin:2.5:check 
 (cloudstack-checklicence) on project cloud-utils: Some files do not have 
 the expected license header -> [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the 
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions, 
 please read the following articles:
 [ERROR] [Help 1] 
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with the 
 command
 [ERROR]   mvn  -rf :cloud-utils

 Thanks,
 Chris
 --
 Chris Suich
 chris.su...@netapp.com
 NetApp Software Engineer
 Data Center Platforms - Cloud Solutions
 Citrix, Cisco & Red Hat

>>>
>>>
>>>
>>> --
>>> Daan
>>
>



-- 
Daan

Re: [VOTE] Apache CloudStack 4.3.0 (ninth round)

please see the thread 'concole proxy in 4.3RC9' about this

On Thu, Mar 20, 2014 at 6:25 PM, Daan Hoogland  wrote:
> On Thu, Mar 20, 2014 at 6:21 PM, Animesh Chaturvedi
>  wrote:
>> should work
>
>
> You mean 'should work" after default installation, Animesh?
> consoleproxy.url.domain is empty.
>
> thanks,
> --
> Daan



-- 
Daan

Re: Review Request 19039: CLOUDSTACK-2266: Adding automation tests for IP reservation feature

2014-03-20 Thread Ashutosh Kelkar


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

(Updated March 20, 2014, 5:31 p.m.)


Review request for cloudstack, Santhosh Edukulla and SrikanteswaraRao Talluri.


Changes
---

Review changes.


Bugs: CLOUDSTACK-2266
https://issues.apache.org/jira/browse/CLOUDSTACK-2266


Repository: cloudstack-git


Description
---

Adding first set of automation tests for IP reservation feature.


Diffs (updated)
-

  test/integration/component/test_ip_reservation.py 224212f 
  tools/marvin/marvin/codes.py e4a0f6a 
  tools/marvin/marvin/config/config.cfg 356a291 
  tools/marvin/marvin/integration/lib/common.py 3b292bf 
  tools/marvin/marvin/integration/lib/utils.py 709fdde 

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


Testing
---

Yes. Log below.

test_RVR_network (test_ip_reservation.TestIpReservation) ... SKIP: Skip - WIP
test_ip_reservation_in_multiple_networks_same_account 
(test_ip_reservation.TestIpReservation) ... ok
test_nat_rules_nat rule (test_ip_reservation.TestIpReservation) ... ok
test_nat_rules_static nat rule (test_ip_reservation.TestIpReservation) ... ok
test_update_cidr_multiple_vms_not_all_inclusive 
(test_ip_reservation.TestIpReservation) ... ok
test_update_cidr_single_vm_not_inclusive 
(test_ip_reservation.TestIpReservation) ... ok
test_user_defined_cidr (test_ip_reservation.TestIpReservation) ... ok
test_vm_create_after_reservation_LB-NS (test_ip_reservation.TestIpReservation) 
... SKIP: Skipping - this test required netscaler configured in the network
test_vm_create_after_reservation_LB-VR (test_ip_reservation.TestIpReservation) 
... ok
test_vm_create_outside_cidr_after_reservation_LB-NS 
(test_ip_reservation.TestIpReservation) ... SKIP: Skipping - this test required 
netscaler configured in the network
test_vm_create_outside_cidr_after_reservation_LB-VR 
(test_ip_reservation.TestIpReservation) ... ok
--
Ran 11 tests in 3753.613s

OK

Two tests which require Netscaler configured are skipped due to netscaler was 
not available on setup.


Thanks,

Ashutosh Kelkar

Re: Review Request 19039: CLOUDSTACK-2266: Adding automation tests for IP reservation feature

2014-03-20 Thread Ashutosh Kelkar



> On March 18, 2014, 6:57 a.m., Santhosh Edukulla wrote:
> > test/integration/component/test_ip_reservation.py, line 258
> > 
> >
> > Move this to a utility function i believe. Also, do we have a class in 
> > base.py for Router to verify state. If not update or use that.

We are just listing the routers here and matching the state. There is no API 
for matching router state as such. I have moved this function to utility.


> On March 18, 2014, 6:57 a.m., Santhosh Edukulla wrote:
> > test/integration/component/test_ip_reservation.py, line 296
> > 
> >
> > The validation comment at step2 mentions about to verify that the guest 
> > vm ip is not changed. I believe we are just listing the vms, should that 
> > satisfy to verify ip as well, i mean is listing vms is equal to verify that 
> > ip is not changed?

IPs have been matched in step below it to verify it is not changed.


> On March 18, 2014, 6:57 a.m., Santhosh Edukulla wrote:
> > test/integration/component/test_ip_reservation.py, line 318
> > 
> >
> > Step1 is not validated it seems?

It is verified in the function called on line 246


> On March 18, 2014, 6:57 a.m., Santhosh Edukulla wrote:
> > test/integration/component/test_ip_reservation.py, line 328
> > 
> >
> > is 10.1.1.9 outside of 10.1.1.0/29?

10.1.1.0/29 translates to 10.1.1.0 to 10.1.1.7


> On March 18, 2014, 6:57 a.m., Santhosh Edukulla wrote:
> > test/integration/component/test_ip_reservation.py, line 1021
> > 
> >
> > Change this to one single assert?

The utility function you have suggested checks if the element is present in 
list. But here we have to check particular attributes of object, I think it 
won't be possible to combine two alerts with using utility function.


> On March 18, 2014, 6:57 a.m., Santhosh Edukulla wrote:
> > test/integration/component/test_ip_reservation.py, line 265
> > 
> >
> > We have a utility function under utils.py "verifyElementInList", this 
> > can help remove two asserts in to one i believe, please check.

The utility function you have suggested checks if the element is present in 
list. But here we have to check particular attributes of object, I think it 
won't be possible to combine two alerts with using utility function.


> On March 18, 2014, 6:57 a.m., Santhosh Edukulla wrote:
> > test/integration/component/test_ip_reservation.py, line 483
> > 
> >
> > Will it be possible to check the update state of router rather sleep? 
> > It will help other test cases as well.

I have used "router.check.interval" instead of sleeping for any random time, 
and we are using verifyRouterState function to check the router state is 
changed or not. This is a validation part of test case.


> On March 18, 2014, 6:57 a.m., Santhosh Edukulla wrote:
> > test/integration/component/test_ip_reservation.py, line 1271
> > 
> >
> > This function seems to be used in many classes, so if possible move it 
> > as a util\library function for better usage.

This is used only in this class and very specific to the test cases in this 
suite.


> On March 18, 2014, 6:57 a.m., Santhosh Edukulla wrote:
> > test/integration/component/test_ip_reservation.py, line 1277
> > 
> >
> > Will this be cleaned automatically?

It will be cleaned up as part of account cleanup.


> On March 18, 2014, 6:57 a.m., Santhosh Edukulla wrote:
> > test/integration/component/test_ip_reservation.py, line 1317
> > 
> >
> > Is this ok to hardcode these values? instead put it in one place, this 
> > way, the values can be altered at one place and effect takes place at all 
> > rather changing all test cases in future.

Removed hard-coded value, now subnet is taken randomly.


- Ashutosh


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


On March 14, 2014, 4:44 p.m., Ashutosh Kelkar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19039/
> ---
> 
> (Updated March 14, 2014, 4:44 p.m.)
> 
> 
> Rev

Re: Resetting a VM is broken?

>> the Reset Vm option is presented as a button unlike the icons 

I think this was because all the other icons we tried to represent this with 
were too confusing to users — they were clicking on 'reset VM' thinking it was 
‘reboot VM’ — then as a last minute fix the decision was to just to show a text 
label.

Any ideas from anyone on what would be a good icon representation?

-Brian

On Mar 19, 2014, at 3:02 PM, Alena Prokharchyk  
wrote:

> 1) Didn’t notice “the elephant” - that the Reset Vm option is presented as
> a button unlike the icons for other options. UI folks - Brian/Jessica- why
> we decided to represent this option differently in the UI?
> 
> 2) Mike, I’ve looked at the code and the history. We've always allocated a
> new volume during the vm restore call. Hari, can you please confirm that
> this feature you wrote, was designed to work this way
> 
> 
> -Alena.
> 
> 
> On 3/19/14, 2:41 PM, "Mike Tutkowski"  wrote:
> 
>> To clarify: Reboot VM seemed to keep the VM running and just reboot the
>> OS.
>> 
>> Reset VM seemed to shut the VM down and then re-start it (with the same
>> root disk for the OS).
>> 
>> 
>> On Wed, Mar 19, 2014 at 3:40 PM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>> 
>>> I could be wrong, but I thought as recently as 4.3 that Reset VM
>>> essentially stopped and then re-started the VM with the same root disk.
>>> 
>>> It seemed to differ from Reboot VM only in the sense that the VM was
>>> never
>>> technically stopped (the OS inside the VM was just rebooted).
>>> 
>>> 
>>> On Wed, Mar 19, 2014 at 3:38 PM, Mike Tutkowski <
>>> mike.tutkow...@solidfire.com> wrote:
>>> 
 I'm using XenServer 6.1 hosts (two of them) in this case.
 
 
 On Wed, Mar 19, 2014 at 3:37 PM, Mike Tutkowski <
 mike.tutkow...@solidfire.com> wrote:
 
> Yeah, stopping and restarting works fine...as does, I believe,
> rebooting
> the VM.
> 
> Right below Reboot VM, there is a Reset VM option.
> 
> If that means "re-install," then we probably should clean up the old
> root disk.
> 
> 
> On Wed, Mar 19, 2014 at 3:30 PM, Alena Prokharchyk <
> alena.prokharc...@citrix.com> wrote:
> 
>> don¹t see ³Reset Vm² option in UI; do you mean ³Reboot instance²?
>> I¹ve
>> just tried that, as well as calling stop/startVM from the UI. The Vm
>> boots
>> up with its original disk.
>> 
>> I¹m having Xen/Nfs, not sure it matters
>> 
>> -Alena.
>> 
>> On 3/19/14, 2:19 PM, "Mike Tutkowski" 
>> wrote:
>> 
>>> I didn't look into what the GUI calls, but I invoked the Reset VM
>> option
>>> in
>>> the GUI.
>>> 
>>> Thanks
>>> 
>>> 
>>> On Wed, Mar 19, 2014 at 3:17 PM, Alena Prokharchyk <
>>> alena.prokharc...@citrix.com> wrote:
>>> 
 Mike, just to confirm - did you call
 stopVirtualMachine/startVirtualMachine apis?
 
 -alena.
 
 On 3/19/14, 1:55 PM, "Mike Tutkowski"
>> 
 wrote:
 
> Hi,
> 
> I noticed today while running through some test cases for 4.4
>> that
> resetting a VM does not work as expected.
> 
> Instead of the typical stop and re-start behavior where the VM is
 booted
> back up using the same root disk, the VM gets a new root disk
>> when
>> it
 is
> booted back up.
> 
> Can anyone confirm this finding for me with his or her setup?
> 
> Thanks!
> 
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *(tm)*
 
 
>>> 
>>> 
>>> --
>>> *Mike Tutkowski*
>>> *Senior CloudStack Developer, SolidFire Inc.*
>>> e: mike.tutkow...@solidfire.com
>>> o: 303.746.7302
>>> Advancing the way the world uses the
>>> cloud
>>> *(tm)*
>> 
>> 
> 
> 
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *(tm)*
> 
 
 
 
 --
 *Mike Tutkowski*
 *Senior CloudStack Developer, SolidFire Inc.*
 e: mike.tutkow...@solidfire.com
 o: 303.746.7302
 Advancing the way the world uses the
 cloud
 *(tm)*
 
>>> 
>>> 
>>> 
>>> --
>>> *Mike Tutkowski*
>>> *Senior CloudStack Developer, SolidFire Inc.*
>>> e: mike.tutkow...@solidfire.com
>>> o: 303.746.7302
>>> Advancing the way the world uses the
>>> cloud

Re: [VOTE] Apache CloudStack 4.3.0 (ninth round)

On Thu, Mar 20, 2014 at 6:21 PM, Animesh Chaturvedi
 wrote:
> should work


You mean 'should work" after default installation, Animesh?
consoleproxy.url.domain is empty.

thanks,
-- 
Daan

RE: [VOTE] Apache CloudStack 4.3.0 (ninth round)

It should work and has been tested, adding Amogh and Sadhu

> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Thursday, March 20, 2014 10:19 AM
> To: dev
> Subject: Re: [VOTE] Apache CloudStack 4.3.0 (ninth round)
> 
> Thanks Ove,
> 
> It looks like the info I want. I will give it a try. (almost hitting myself)
> 
> On Thu, Mar 20, 2014 at 6:05 PM, Ove Ewerlid 
> wrote:
> > On 03/20/2014 05:58 PM, Daan Hoogland wrote:
> >>
> >> again I am seriously considering -1 (binding) and (sigh) and. Is
> >> there any doc I missed on getting the console proxy working in 4.3,
> >> that will make me hit me on the head and retract this thread?
> >
> >
> > A pointer to this will fit nicely in the 4.3 release notes;
> >
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Realhost+IP+cha
> > nges#RealhostIPchanges-Upgrade
> >
> > just checked, did not fine any note about this.
> > There have been email threads where this link has been noted on the
> > dev list.
> >
> > /Ove
> >
> >
> >
> >
> >> On Tue, Mar 18, 2014 at 9:38 PM, Wilder Rodrigues
> >>  wrote:
> >>>
> >>> Hi there Ilya,
> >>>
> >>> Could you please provide which tests cases you have covered? I would
> >>> like to add them to my tests round as well.
> >>>
> >>> Currently I'm testing multiple zones, networks, instances, ACLs,
> >>> Port Forwarding and will add security groups. If you have more
> >>> points, I would be glad to test them as well.
> >>>
> >>> Thanks in advance.
> >>>
> >>> Cheers,
> >>> Wilder
> >>>
> >>> -Original Message-
> >>> From: ilya musayev [mailto:ilya.mailing.li...@gmail.com]
> >>> Sent: Tuesday, March 18, 2014 9:11 PM
> >>> To: dev@cloudstack.apache.org
> >>> Subject: Re: [VOTE] Apache CloudStack 4.3.0 (ninth round)
> >>>
> >>> +1 binding
> >>> On 3/18/14, 3:05 PM, Animesh Chaturvedi wrote:
> 
> 
> 
>  Hi All,
> 
> 
> 
>  I've created a 4.3.0 release, with the following artifacts up for a
> 
>  vote:
> 
> 
> 
> 
> 
>  Git Branch and Commit SH:
> 
> 
>  https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog
>  ;h=refs/heads/4.3
>  Commit:  0810029f274878eca8fd74b44ab1117054e929a5
> 
> 
>  List of changes:
> 
>  New Features in 4.3:
>  https://issues.apache.org/jira/issues/?filter=12325248
> 
>  Improvement in 4.3:
>  https://issues.apache.org/jira/issues/?filter=12325249
> 
>  Issues fixed in 4.3
>  https://issues.apache.org/jira/issues/?filter=12326161
> 
>  Known Issues in 4.3:
>  https://issues.apache.org/jira/issues/?filter=12326162
> 
> 
> 
> 
> 
> 
> 
>  Source release (checksums and signatures are available at the same
> 
>  location):
> 
>  https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
> 
> 
> 
>  PGP release keys (signed using 94BE0D7C):
> 
>  https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> 
> 
> 
>  Testing instructions are here:
> 
> 
>  https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test
>  +procedure
> 
> 
> 
>  Vote will be open for 72 hours (Friday 3/21 12:05 PM PST)
> 
> 
> 
>  For sanity in tallying the vote, can PMC members please be sure to
>  indicate "(binding)" with their vote?
> 
> 
> 
>  [ ] +1  approve
> 
>  [ ] +0  no opinion
> 
>  [ ] -1  disapprove (and reason why)
> 
> 
> 
>  Thanks
> 
>  Animesh
> 
> 
> 
> >>>
> >>
> >>
> >>
> >
> >
> > --
> > Ove Everlid
> > System Administrator / Architect / SDN- & Automation- & Linux-hacker
> > Mobile: +46706662363 (dedicated work mobile)
> > Country: Sweden, timezone; Middle Europan Time (MET or GMT+1)
> 
> 
> 
> --
> Daan

Re: Resetting a VM is broken?

Thanks, John

I am mainly curious about this use case because of work I did on 4.4 to
support root disks for managed storage (just on XenServer for 4.4.).

It appears I need to make a small tweak to 4.4 code in the managed-storage
area for this cleanup to completely work (the SR that was auto created for
the volume that's deleted needs to be removed from the applicable XenServer
cluster).


On Thu, Mar 20, 2014 at 9:36 AM, John Kinsella  wrote:

> Mike - There is a way to restore disks in destroyed state before they are
> expunged. It requires shutting down management server, modifying database
> directly, and keeping a good stock of potential offerings near your data
> recovery shrine.
>
> I'm going to be covering this in my CCC Denver talk.
>
> John
>
> On Mar 19, 2014, at 9:59 PM, Mike Tutkowski  > wrote:
>
> Please correct me if I'm wrong, but there does not appear to be a way to
> "save" the old root disk once it has gone into the Destroy state in this
> situation, is there?
>
> In other words, the new root disk is created, the old is put into the
> Destroy state, and the old will get deleted at the next clean-up cycle...no
> chance to restore that volume (even for use as a data disk).
>
>
> On Wed, Mar 19, 2014 at 10:33 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
> OK, I went back an re-ran my test.
>
> I see how this works now.
>
> I was aware that volumes in the Destroy state get expunged by a background
> thread at some point; however, what tricked me here is that my "old" root
> disk no longer showed up in the Storage tab of the GUI.
>
> When I looked in the volumes table, though, I saw that that disk was in
> the Destroy state.
>
> I speed up the frequency of the clean-up background thread to run once
> every minute and I saw the old root disk got put into the Expunged state
> (as you'd expect, it was no longer present in the SR).
>
>
> On Wed, Mar 19, 2014 at 7:06 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
> Yeah, usually "reset" (for hypervisors) means "shut down the VM and
> re-start it."
>
>
> On Wed, Mar 19, 2014 at 6:22 PM, Marcus  shadow...@gmail.com>> wrote:
>
> +1 to reset being a bad verb for this. It's too late now, however.
>
> On Wed, Mar 19, 2014 at 6:22 PM, Marcus  shadow...@gmail.com>> wrote:
> The storage gets marked as 'Destroy' state. Then it goes to
> 'Expunging' when the storage cleanup interval occurs. I've actually
> thought about leveraging that for data disks, the current delete data
> disk immediately cleans up the disk, when we could create an api call
> that just moves the data disk to destroy state. Then there'd actually
> be room for an 'undo' operation where the state could be moved back to
> Ready, so long as the cleanup hasn't occurred.
>
> On Wed, Mar 19, 2014 at 4:43 PM, Nitin Mehta  >
> wrote:
> Please feel free to open a documentation bug on JIRA if the info
> doesn't
> exist.
>
> On 19/03/14 3:16 PM, "Mike Tutkowski"  >
> wrote:
>
> Thanks for that background-cleanup info. I was not aware of that.
>
> I'll probably take a look into it and see how that works.
>
>
> On Wed, Mar 19, 2014 at 4:13 PM, Alena Prokharchyk <
> alena.prokharc...@citrix.com> wrote:
>
> CS destroys the Root volume in CS DB, then its up to the storage
> pool
> cleanup task to clean it up on the backend. This is a background
> task
> running every storage.cleanup.interval seconds.
>
> For how long do you see the volume being present on the SR?
>
> On 3/19/14, 3:03 PM, "Mike Tutkowski"  
>
> wrote:
>
> OK, sounds good; however, if this is desired behavior, does anyone
> know
> why
> we abandon the old root disk in the XenServer SR? It seems that
> CloudStack
> "forgets" about it and it just stays in the SR taking up space.
>
> Do people think it should be deleted?
>
>
> On Wed, Mar 19, 2014 at 3:49 PM, Nitin Mehta <
> nitin.me...@citrix.com>
> wrote:
>
> I think that's what it is supposed to do. It discards the old
> root
> disk
> and creates a fresh root disk for the vm and in case an optional
> field
> template id is passed in the root disk is created from this new
> template
> id.
> The api name is restoreVirtualMachine. Please check that the UI
> is
> internally invoking this api
>
> Thanks,
> -Nitin
>
> On 19/03/14 1:55 PM, "Mike Tutkowski" <
> mike.tutkow...@solidfire.com>
> wrote:
>
> Hi,
>
> I noticed today while running through some test cases for 4.4
> that
> resetting a VM does not work as expected.
>
> Instead of the typical stop and re-start behavior where the VM
> is
> booted
> back up using the same root disk, the VM gets a new root disk
> when
> it
> is
> booted back up.
>
> Can anyone confirm this finding for me with his

Re: [VOTE] Apache CloudStack 4.3.0 (ninth round)

Thanks Ove,

It looks like the info I want. I will give it a try. (almost hitting myself)

On Thu, Mar 20, 2014 at 6:05 PM, Ove Ewerlid  wrote:
> On 03/20/2014 05:58 PM, Daan Hoogland wrote:
>>
>> again I am seriously considering -1 (binding) and (sigh) and. Is there
>> any doc I missed on getting the console proxy working in 4.3, that
>> will make me hit me on the head and retract this thread?
>
>
> A pointer to this will fit nicely in the 4.3 release notes;
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Realhost+IP+changes#RealhostIPchanges-Upgrade
>
> just checked, did not fine any note about this.
> There have been email threads where this link has been noted on the dev
> list.
>
> /Ove
>
>
>
>
>> On Tue, Mar 18, 2014 at 9:38 PM, Wilder Rodrigues
>>  wrote:
>>>
>>> Hi there Ilya,
>>>
>>> Could you please provide which tests cases you have covered? I would like
>>> to add them to my tests round as well.
>>>
>>> Currently I'm testing multiple zones, networks, instances, ACLs, Port
>>> Forwarding and will add security groups. If you have more points, I would be
>>> glad to test them as well.
>>>
>>> Thanks in advance.
>>>
>>> Cheers,
>>> Wilder
>>>
>>> -Original Message-
>>> From: ilya musayev [mailto:ilya.mailing.li...@gmail.com]
>>> Sent: Tuesday, March 18, 2014 9:11 PM
>>> To: dev@cloudstack.apache.org
>>> Subject: Re: [VOTE] Apache CloudStack 4.3.0 (ninth round)
>>>
>>> +1 binding
>>> On 3/18/14, 3:05 PM, Animesh Chaturvedi wrote:



 Hi All,



 I've created a 4.3.0 release, with the following artifacts up for a

 vote:





 Git Branch and Commit SH:


 https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
 Commit:  0810029f274878eca8fd74b44ab1117054e929a5


 List of changes:

 New Features in 4.3:
 https://issues.apache.org/jira/issues/?filter=12325248

 Improvement in 4.3:
 https://issues.apache.org/jira/issues/?filter=12325249

 Issues fixed in 4.3
 https://issues.apache.org/jira/issues/?filter=12326161

 Known Issues in 4.3:
 https://issues.apache.org/jira/issues/?filter=12326162







 Source release (checksums and signatures are available at the same

 location):

 https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/



 PGP release keys (signed using 94BE0D7C):

 https://dist.apache.org/repos/dist/release/cloudstack/KEYS



 Testing instructions are here:


 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure



 Vote will be open for 72 hours (Friday 3/21 12:05 PM PST)



 For sanity in tallying the vote, can PMC members please be sure to
 indicate "(binding)" with their vote?



 [ ] +1  approve

 [ ] +0  no opinion

 [ ] -1  disapprove (and reason why)



 Thanks

 Animesh



>>>
>>
>>
>>
>
>
> --
> Ove Everlid
> System Administrator / Architect / SDN- & Automation- & Linux-hacker
> Mobile: +46706662363 (dedicated work mobile)
> Country: Sweden, timezone; Middle Europan Time (MET or GMT+1)



-- 
Daan

Re: 4.4 and master failing due to missing license header

2014-03-20 Thread SuichII, Christopher

Maybe I should add **/target-eclipse/** to the list of excludes for the license 
checking? Anyone have an objection?

-Chris
-- 
Chris Suich
chris.su...@netapp.com
NetApp Software Engineer
Data Center Platforms – Cloud Solutions
Citrix, Cisco & Red Hat

On Mar 20, 2014, at 1:08 PM, SuichII, Christopher  
wrote:

> I tried running the command with -X. There is quite a bit of output, but this 
> is what I was able to find:
> 
> ...
> [WARNING] Missing header in: 
> /Users/csuich/CloudStack/cloudstack/utils/target-eclipse/test-classes/com/cloud/utils/db/transactionContextBuilderTest.xml
> ...
> [WARNING] Missing header in: 
> /Users/csuich/CloudStack/cloudstack/utils/target-eclipse/test-classes/testContext.xml
> ...
> [WARNING] Missing header in: 
> /Users/csuich/CloudStack/cloudstack/utils/target-eclipse/test-classes/log4j.xml
> ...
> [WARNING] Missing header in: 
> /Users/csuich/CloudStack/cloudstack/utils/target-eclipse/test-classes/com/cloud/utils/QualifierTestContext.xml
> …
> 
> So, it looks like the check license plugin is going after some xml that 
> Eclipse generates. Should I be telling maven to ignore these somehow? When I 
> run ‘git status’, it says my working directory is clean as the .gitignore is 
> setup to ignore that stuff.
> 
> -Chris
> -- 
> Chris Suich
> chris.su...@netapp.com
> NetApp Software Engineer
> Data Center Platforms – Cloud Solutions
> Citrix, Cisco & Red Hat
> 
> On Mar 20, 2014, at 12:54 PM, Daan Hoogland  wrote:
> 
>> So the offending file is in utils. Doesn't it give info above the BUIL
>> FAILURE line?
>> 
>> On Thu, Mar 20, 2014 at 5:52 PM, SuichII, Christopher
>>  wrote:
>>> Hey all,
>>> 
>>> I'm unable to build on 4.4 and master with no changes made in either 
>>> branch. It appears that there are some files which don't meet the license 
>>> header requirement. I don't see one, but is there a profile for ignoring 
>>> the check license plugin? Alternatively, does anyone know what files are 
>>> offending or how to easily fix this?
>>> 
>>> [INFO] 
>>> 
>>> [INFO] BUILD FAILURE
>>> [INFO] 
>>> 
>>> [INFO] Total time: 14.076s
>>> [INFO] Finished at: Thu Mar 20 12:48:27 EDT 2014
>>> [INFO] Final Memory: 40M/96M
>>> [INFO] 
>>> 
>>> [ERROR] Failed to execute goal com.mycila:license-maven-plugin:2.5:check 
>>> (cloudstack-checklicence) on project cloud-utils: Some files do not have 
>>> the expected license header -> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
>>> switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> [ERROR]
>>> [ERROR] For more information about the errors and possible solutions, 
>>> please read the following articles:
>>> [ERROR] [Help 1] 
>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>>> [ERROR]
>>> [ERROR] After correcting the problems, you can resume the build with the 
>>> command
>>> [ERROR]   mvn  -rf :cloud-utils
>>> 
>>> Thanks,
>>> Chris
>>> --
>>> Chris Suich
>>> chris.su...@netapp.com
>>> NetApp Software Engineer
>>> Data Center Platforms - Cloud Solutions
>>> Citrix, Cisco & Red Hat
>>> 
>> 
>> 
>> 
>> -- 
>> Daan
>

Re: concole proxy in 4.3RC9