date:20140711

Re: How to recreate ssvm & cpvm

2014-07-11 Thread Tejas Gadaria

Thanks Suresh,

It worked perfectly fine.

Regards,
Tejas


On Fri, Jul 11, 2014 at 12:06 PM, Suresh Sadhu 
wrote:

> Before destroying the cpvm and ssvm ,please analyse the logs. May be agent
> is not up.
> Also check below
>
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM%2C+templates%2C+Secondary+storage+troubleshooting
>
> regards
> sadhu
>
>
> -Original Message-
> From: Suresh Sadhu
> Sent: 11 July 2014 11:59
> To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> Subject: RE: How to recreate ssvm & cpvm
>
> NO it won't impact guet vms .destroy the  ssvm and cpvm , it will recreate
> again and  during that  time you can't create new guest vms.
>
> --sadhu
>
> -Original Message-
> From: Tejas Gadaria [mailto:refond.g...@gmail.com]
> Sent: 11 July 2014 11:53
> To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> Subject: How to recreate ssvm & cpvm
>
> If i recreate ssvm & cpvm, guest vm will be affected?
>
>
> On Fri, Jul 11, 2014 at 11:50 AM, Tejas Gadaria 
> wrote:
>
> > Hi,
> >
> > Due to power blackout i have to recreate ssvm & cpvm, i am able to
> > deploy new vms also create new template but on System Capacity, &
> > General  Alerts area, latest alerts are not populating.
> >
> > Also ssvm & cpvm status is 'running' but Agent state is not displayed
> > in Cloudstack UI.
> >
> > I have production VMs running on ACS. how can i recreate ssvm & cpvm. ?
> >
> > I am using ACS 4.3 & Xenserver 6.2 SP1
> >
> > Regards,
> > Tejas
> >
> >
> > On Thu, Jul 10, 2014 at 6:30 PM, Tejas Gadaria 
> > wrote:
> >
> >> Hi,
> >>
> >> I am getting below logs on CS 4.3 on Xenserver 6.2 SP1 i m getting
> >> huge amount of of memory allocated to vms, where it is not actully..
> >>
> >> 2014-07-10 16:43:16,643 DEBUG [c.c.a.AlertManagerImpl]
> >> (CapacityChecker:ctx-d205d3de) Done executing storage capacity update
> >> 2014-07-10 16:43:16,643 DEBUG [c.c.a.AlertManagerImpl]
> >> (CapacityChecker:ctx-d205d3de) Executing capacity updates for public
> >> ip and Vlans
> >> 2014-07-10 16:43:16,686 DEBUG [c.c.a.AlertManagerImpl]
> >> (CapacityChecker:ctx-d205d3de) Done capacity updates for public ip
> >> and Vlans
> >> 2014-07-10 16:43:16,686 DEBUG [c.c.a.AlertManagerImpl]
> >> (CapacityChecker:ctx-d205d3de) Executing capacity updates for private
> >> ip
> >> 2014-07-10 16:43:16,701 DEBUG [c.c.a.AlertManagerImpl]
> >> (CapacityChecker:ctx-d205d3de) Done executing capacity updates for
> >> private ip
> >> 2014-07-10 16:43:16,701 DEBUG [c.c.a.AlertManagerImpl]
> >> (CapacityChecker:ctx-d205d3de) Done recalculating system capacity
> >> 2014-07-10 16:43:16,705 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> >> (HostReservationReleaseChecker:ctx-0828f975) Checking if any host
> >> reservation can be released ...
> >> 2014-07-10 16:43:16,720 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> >> (HostReservationReleaseChecker:ctx-0828f975) Cannot release
> >> reservation, Found 4 VMs Running on
> >>
> >> host 1
> >> 2014-07-10 16:43:16,727 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> >> (HostReservationReleaseChecker:ctx-0828f975) Cannot release
> >> reservation, Found 4 VMs Running on
> >>
> >> host 5
> >> 2014-07-10 16:43:16,732 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> >> (HostReservationReleaseChecker:ctx-0828f975) Cannot release
> >> reservation, Found 1 VMs Running on
> >>
> >> host 6
> >> 2014-07-10 16:43:16,732 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> >> (HostReservationReleaseChecker:ctx-0828f975) Done running
> >> HostReservationReleaseChecker ...
> >>
> >
> >
>

customize systemVM

2014-07-11 Thread Tomasz Zięba

Where can I find a tutorial to modify systemVM image or create my own
systemVM template ?

-- 
Regards,
Tomasz Zięba
Twitter: @TZieba
LinkedIn: pl.linkedin.com/pub/tomasz-zięba-ph-d/3b/7a8/ab6/

Re: customize systemVM

2014-07-11 Thread Abhinandan Prateek

Rohit has put up a how-to here http://bhaisaab.org/logs/building-systemvms/

-abhi

On 11/07/14 2:27 pm, "Tomasz Zięba"  wrote:

>Where can I find a tutorial to modify systemVM image or create my own
>systemVM template ?
>
>-- 
>Regards,
>Tomasz Zięba
>Twitter: @TZieba
>LinkedIn: pl.linkedin.com/pub/tomasz-zięba-ph-d/3b/7a8/ab6/
>

Review Request 23395: CLOUDSTACK-5663 :- Handled the NULL check for network's cidr field to avoid NPE for createNetwork and listNetwork

2014-07-11 Thread Girish Chaudhari


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

Review request for cloudstack and Parth Jagirdar.


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


Repository: cloudstack-git


Description
---

CLOUDSTACK-5663 - API:MS: Network with NULL CIDR raises NPE for createNetwork 
and listNetwork

Root Cause:
In the listNetworks and createNetworks API execution flow, existing networks 
analysed to check whether they can be used for deploy. In this step, all the 
available IPs are calculated using the Network CIDR. In case the CIDR is NULL 
it results into the NPE. 

Solution:
Added the NULL check to avoid NPE, in case of NULL CIDR, API populate the 
"canusefordeploy" attribute as false.


Diffs
-

  server/src/com/cloud/network/NetworkModelImpl.java 0ef5cb9 

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


Testing
---

Tested on master for listNetworks and createNetwork command with NULL network 
cidr. 


Thanks,

Girish Chaudhari

Re: Cannot release reservation

2014-07-11 Thread Tejas Gadaria

Hi Punith,

I have recreated systemvms & now its in normal state now.
Thanks for replay

Regards,
Tejas


On Fri, Jul 11, 2014 at 11:57 AM, Punith S  wrote:

> hi,
>
> try restarting the MS and see whether agent and MS are in sync.
> also check the ssvm by running the health script by logging into to the
> ssvm.
> for more troubleshooting refer this link
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM%2C+templates%2C+Secondary+storage+troubleshooting
>
> thanks
>
>
> On Fri, Jul 11, 2014 at 11:50 AM, Tejas Gadaria 
> wrote:
>
> > Hi,
> >
> > Due to power blackout i have to recreate ssvm & cpvm, i am able to deploy
> > new vms also create new template but on System Capacity, & General
>  Alerts
> > area, latest alerts are not populating.
> >
> > Also ssvm & cpvm status is 'running' but Agent state is not displayed in
> > Cloudstack UI.
> >
> > I have production VMs running on ACS. how can i recreate ssvm & cpvm. ?
> >
> > I am using ACS 4.3 & Xenserver 6.2 SP1
> >
> > Regards,
> > Tejas
> >
> >
> > On Thu, Jul 10, 2014 at 6:30 PM, Tejas Gadaria 
> > wrote:
> >
> > > Hi,
> > >
> > > I am getting below logs on CS 4.3 on Xenserver 6.2 SP1
> > > i m getting huge amount of of memory allocated to vms, where it is not
> > > actully..
> > >
> > > 2014-07-10 16:43:16,643 DEBUG [c.c.a.AlertManagerImpl]
> > > (CapacityChecker:ctx-d205d3de) Done executing storage capacity update
> > > 2014-07-10 16:43:16,643 DEBUG [c.c.a.AlertManagerImpl]
> > > (CapacityChecker:ctx-d205d3de) Executing capacity updates for public ip
> > and
> > > Vlans
> > > 2014-07-10 16:43:16,686 DEBUG [c.c.a.AlertManagerImpl]
> > > (CapacityChecker:ctx-d205d3de) Done capacity updates for public ip and
> > Vlans
> > > 2014-07-10 16:43:16,686 DEBUG [c.c.a.AlertManagerImpl]
> > > (CapacityChecker:ctx-d205d3de) Executing capacity updates for private
> ip
> > > 2014-07-10 16:43:16,701 DEBUG [c.c.a.AlertManagerImpl]
> > > (CapacityChecker:ctx-d205d3de) Done executing capacity updates for
> > private
> > > ip
> > > 2014-07-10 16:43:16,701 DEBUG [c.c.a.AlertManagerImpl]
> > > (CapacityChecker:ctx-d205d3de) Done recalculating system capacity
> > > 2014-07-10 16:43:16,705 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (HostReservationReleaseChecker:ctx-0828f975) Checking if any host
> > > reservation can be released ...
> > > 2014-07-10 16:43:16,720 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (HostReservationReleaseChecker:ctx-0828f975) Cannot release
> reservation,
> > > Found 4 VMs Running on
> > >
> > > host 1
> > > 2014-07-10 16:43:16,727 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (HostReservationReleaseChecker:ctx-0828f975) Cannot release
> reservation,
> > > Found 4 VMs Running on
> > >
> > > host 5
> > > 2014-07-10 16:43:16,732 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (HostReservationReleaseChecker:ctx-0828f975) Cannot release
> reservation,
> > > Found 1 VMs Running on
> > >
> > > host 6
> > > 2014-07-10 16:43:16,732 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (HostReservationReleaseChecker:ctx-0828f975) Done running
> > > HostReservationReleaseChecker ...
> > >
> >
>
>
>
> --
> regards,
>
> punith s
> cloudbyte.com
>

Autostart vms on Xenserver 6.2 With HA

2014-07-11 Thread Tejas Gadaria

I have all vms HA enabled on ACS 4.3 on xenserver 6.2 .

I also want to enable auto start functionality in xen 6.2 for all vms.
but i found this

http://support.citrix.com/article/CTX133910

So will it be safe to enable auto start on xen6.2 with command line?

Regards,
Tejas

RE: "Bug" introduced by part of commit a600d8408ea86782318139c17cf346c8497943d0

2014-07-11 Thread Funs Kessen

Hi Santhosh,

Yep looks good!

In the meantime I've stumbled across another one that seems to originate either 
from the NetworksDaoImp.java upon update or allocateVnet, still looking into 
it, but here's the message:
2014-07-11 11:58:01,646 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Work-Job-Executor-4:ctx-3e9098c6 job-67/job-68 ctx-afb3767f) Lock is acquired 
for network id 205 as a part of network implement
2014-07-11 11:58:01,647 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Work-Job-Executor-4:ctx-3e9098c6 job-67/job-68 ctx-afb3767f) Asking 
ExternalGuestNetworkGuru to implement Ntwk[205|Guest|8]
2014-07-11 11:58:01,673 DEBUG [c.c.u.d.T.Transaction] 
(Work-Job-Executor-4:ctx-3e9098c6 job-67/job-68 ctx-afb3767f) Rolling back the 
transaction: Time = 1 Name =  Work-Job-Executor-4; called by 
-TransactionLegacy.rollback:902-Transac
tionLegacy.removeUpTo:845-TransactionLegacy.close:669-TransactionContextInterceptor.invoke:36-ReflectiveMethodInvocation.proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172-JdkDynamicAopProxy.invo
ke:204-$Proxy45.take:-1-DataCenterDaoImpl.allocateVnet:215-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:57
2014-07-11 11:58:01,675 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Work-Job-Executor-4:ctx-3e9098c6 job-67/job-68 ctx-afb3767f) Cleaning up 
because we're unable to implement the network Ntwk[205|Guest|8]
2014-07-11 11:58:01,689 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Work-Job-Executor-4:ctx-3e9098c6 job-67/job-68 ctx-afb3767f) Lock is acquired 
for network Ntwk[205|Guest|8] as a part of network shutdown

Cheers,

Funs

> -Original Message-
> From: Santhosh Edukulla [mailto:santhosh.eduku...@citrix.com]
> Sent: Thursday, July 10, 2014 8:13 PM
> To: dev@cloudstack.apache.org
> Subject: RE: "Bug" introduced by part of commit
> a600d8408ea86782318139c17cf346c8497943d0
> 
> I just reverted the changes done to this specific file, then
> 
> built the management server, stopped and started again twice, issue is not
> reproducible deployed a data center post the revert on simulator, it worked.
> 
> Please check. It seems,  TransactionLegacy now implements Closeable, new
> change under master, will check the reported issues for coverity to this file
> separately post the analysis.
> 
> Regards,
> Santhosh
> 
> From: Funs Kessen [fkes...@schubergphilis.com]
> Sent: Thursday, July 10, 2014 12:18 PM
> To: dev@cloudstack.apache.org
> Subject: RE: "Bug" introduced by part of commit
> a600d8408ea86782318139c17cf346c8497943d0
> 
> Hi Likitha,
> 
> You are absolutely spot on! This is the error message I found:
> INFO  [c.c.c.ClusterManagerImpl] (main:null) Management server
> 90520734207775 is being started WARN  [c.c.u.d.T.Transaction] (main:null)
> txn: Commit called when it is not a transaction: -Transaction.execute:38-
> Transaction.execute:46-ClusterManagerImpl.start:940-
> CloudStackExtendedLifeCycle$1.with:75-
> CloudStackExtendedLifeCycle.with:153-
> CloudStackExtendedLifeCycle.startBeans:72-
> CloudStackExtendedLifeCycleStart.run:46-
> DefaultModuleDefinitionSet$1.with:105-
> DefaultModuleDefinitionSet.withModule:245-
> DefaultModuleDefinitionSet.withModule:250-
> DefaultModuleDefinitionSet.withModule:250-
> DefaultModuleDefinitionSet.withModule:233
> INFO  [c.c.c.ClusterManagerImpl] (main:null) Management server (host id : 1)
> is being started at 127.0.0.1:9090
> 
> Cheers,
> 
> Funs
> 
> > -Original Message-
> > From: Likitha Shetty [mailto:likitha.she...@citrix.com]
> > Sent: Thursday, July 10, 2014 5:35 PM
> > To: dev@cloudstack.apache.org
> > Subject: RE: "Bug" introduced by part of commit
> > a600d8408ea86782318139c17cf346c8497943d0
> >
> > Are you guys are referring to the update method that is throwing the
> > error, 'update(long id, long runid, Date lastUpdate) ?. Agreed that
> > this is just a symptom.
> >
> > But I was referring to the first update method in the file which is
> > 'update(long id, long runid, String name, String version, String
> > serviceIP, int servicePort, Date lastUpdate)'.
> > From what I understand this is the method that updates the MS runId
> > when it is started. And the problem is that the transaction commit
> > made in this update is getting rolled back, which is why we have a
> > wrong runId in the DB for the MS. Since the second update method is
> > based on the right runId it throws an exception.
> > And I suspect the original transaction is getting rolled back because
> > we are trying to close a transaction that is already closed.
> >
> > Thanks,
> > Likitha
> >
> > -Original Message-
> > From: Funs Kessen [mailto:fkes...@schubergphilis.com]
> > Sent: Thursday, July 10, 2014 5:10 PM
> > To: dev@cloudstack.apache.org
> > Subject: RE: "Bug" introduced by part of commit
> > a600d8408ea86782318139c17cf346c8497943d0
> >
> > Hi Santhosh,
> >
> > You're right indeed, it's the update statement in the update itself
> > that adds the runid in

Review Request 23410: Improvised CloudByte Storage Plugin for 4.5 and above. jira id : CLOUDSTACK-7098

2014-07-11 Thread punith s


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

Review request for cloudstack, amit kumar das, edison su, and Mike Tutkowski.


Repository: cloudstack-git


Description
---

The new improvised cloudbyte plugin for cloudstack supports the following 
features

* support for managed storage, where each vm disk has the guaranteed QoS.

* supports resize of the volume.

* supports both iscsi and nfs protocols in XEN server, and iscsi protocol for 
KVM and vmware ESX with respect to managed storage.

* supports storage level snapshot capabilites as well as hypervisor level 
snapshot feature.

* also exposing the custom api's for better ui integration.

* support for unlimited storage nodes across the sites.

* account integration in cloudbyte with respect to domains in cloudstack.


Diffs
-

  
plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/spring-storage-volume-cloudbyte-context.xml
 87c5f51 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/driver/ElastistorPrimaryDataStoreDriver.java
 99d1e2a 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java
 33004e3 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorHostListener.java
 de4711a 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorPrimaryDataStoreProvider.java
 e591082 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorUtil.java
 b75d12a 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorVolumeApiService.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorVolumeApiServiceImpl.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorInterfaceCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorInterfaceResponse.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorPoolCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorPoolResponse.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorVolumeCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorVolumeResponse.java
 PRE-CREATION 
  server/src/com/cloud/configuration/Config.java fbcb1f4 

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


Testing
---

system testing done.


Thanks,

punith s

Re: Review Request 23258: CLOUDSTACK-7062: Tagging test case with BugId

2014-07-11 Thread ASF Subversion and Git Services


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


Commit ba389819338a9be23f1cb604b9d586afb5598795 in cloudstack's branch 
refs/heads/master from Koushik Das
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ba38981 ]

CLOUDSTACK-7062: Enabled back the test as not able to repro


- ASF Subversion and Git Services


On July 3, 2014, 12:19 p.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/23258/
> ---
> 
> (Updated July 3, 2014, 12:19 p.m.)
> 
> 
> Review request for cloudstack and Girish Shilamkar.
> 
> 
> Bugs: CLOUDSTACK-7062
> https://issues.apache.org/jira/browse/CLOUDSTACK-7062
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Tagging test_01_primary_storage_iscsi with BugId
> 
> 
> Diffs
> -
> 
>   test/integration/smoke/test_primary_storage.py 66aec59 
> 
> Diff: https://reviews.apache.org/r/23258/diff/
> 
> 
> Testing
> ---
> 
> 
> File Attachments
> 
> 
> Patch for master
>   
> https://reviews.apache.org/media/uploaded/files/2014/07/03/172621ab-42ad-4d11-91b9-1f43f5d290b1__0001-CLOUDSTACK-7062-Tagging-test-case-with-bug-Id.patch
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Review Request 23258: CLOUDSTACK-7062: Tagging test case with BugId

2014-07-11 Thread ASF Subversion and Git Services


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


Commit 5e181acbdb0865c0d26307c4e5359ec9c615f615 in cloudstack's branch 
refs/heads/4.4-forward from Koushik Das
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5e181ac ]

CLOUDSTACK-7062: Enabled back the test as not able to repro


- ASF Subversion and Git Services


On July 3, 2014, 12:19 p.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/23258/
> ---
> 
> (Updated July 3, 2014, 12:19 p.m.)
> 
> 
> Review request for cloudstack and Girish Shilamkar.
> 
> 
> Bugs: CLOUDSTACK-7062
> https://issues.apache.org/jira/browse/CLOUDSTACK-7062
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Tagging test_01_primary_storage_iscsi with BugId
> 
> 
> Diffs
> -
> 
>   test/integration/smoke/test_primary_storage.py 66aec59 
> 
> Diff: https://reviews.apache.org/r/23258/diff/
> 
> 
> Testing
> ---
> 
> 
> File Attachments
> 
> 
> Patch for master
>   
> https://reviews.apache.org/media/uploaded/files/2014/07/03/172621ab-42ad-4d11-91b9-1f43f5d290b1__0001-CLOUDSTACK-7062-Tagging-test-case-with-bug-Id.patch
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: [VOTE] Apache Cloudstack 4.4.0

2014-07-11 Thread Daan Hoogland

Our beloved VP pointed out that there has not come a vote conclusion yet:

The 4.4.0 vote has resulted in a rejection of the present release
candidate due to -1 of Marcus and no active voting since.

there are three issues pending from this vote thread:
- CLOUDSTACK-6036 (Tomasz)
- unable to add a KVM host (Marcus)
- top level pom.xml still contains a -SNAPSHOT suffix (Ove, question
outstanding to Tim)

Can I have some reporting on the status of those issues by the
reporters, please?

regards,
your friendly release manager


On Wed, Jul 2, 2014 at 10:18 PM, Daan Hoogland  wrote:
> Hi All,
>
> I've created a 4.4.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.4-RC20140702T2107
> Commit: 379387961bd05d1f84fe2e9a1997e9ecdceef91a
>
> List of changes:
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.4.0/
>
> PGP release keys (signed using 4096R/AA4736F3):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> Vote will be open for 72 hours.
>
> 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)
>
>
> I will ad my key to the mentioned KEYS file as soon as possible,
> --
> Daan



-- 
Daan

VM HA on xenserver 6.2

2014-07-11 Thread Tejas Gadaria

Hi,

I want to provide HA to VMs, currently i have created service offering with
'HA enable'
option. Hence VM is showing 'HA Enable'. but Host is hot HA enable.

Also for host If I change global setting 'ha.tag' = 'label' & apply 'label'
to host tag it shows 'HA Enable'.

but while deploying vm that host with host tag='label' doesn't allow to
create vms.
It act as dedicated HA host.

I don't want to create Dedicated HA for now. I want VM HA on cluster level
so if one host goes down vm will be migrated to another host.

Regards,
Tejas

Re: Review Request 23410: Improvised CloudByte Storage Plugin for 4.5 and above. jira id : CLOUDSTACK-7098

2014-07-11 Thread punith s


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

(Updated July 11, 2014, 6:12 p.m.)


Review request for cloudstack, amit kumar das, edison su, and Mike Tutkowski.


Changes
---

fixed a glitch in updating the used bytes.


Repository: cloudstack-git


Description
---

The new improvised cloudbyte plugin for cloudstack supports the following 
features

* support for managed storage, where each vm disk has the guaranteed QoS.

* supports resize of the volume.

* supports both iscsi and nfs protocols in XEN server, and iscsi protocol for 
KVM and vmware ESX with respect to managed storage.

* supports storage level snapshot capabilites as well as hypervisor level 
snapshot feature.

* also exposing the custom api's for better ui integration.

* support for unlimited storage nodes across the sites.

* account integration in cloudbyte with respect to domains in cloudstack.


Diffs (updated)
-

  
plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/spring-storage-volume-cloudbyte-context.xml
 87c5f51 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/driver/ElastistorPrimaryDataStoreDriver.java
 99d1e2a 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java
 33004e3 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorHostListener.java
 de4711a 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorPrimaryDataStoreProvider.java
 e591082 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorUtil.java
 b75d12a 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorVolumeApiService.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorVolumeApiServiceImpl.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorInterfaceCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorInterfaceResponse.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorPoolCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorPoolResponse.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorVolumeCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorVolumeResponse.java
 PRE-CREATION 
  server/src/com/cloud/configuration/Config.java fbcb1f4 

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


Testing
---

system testing done.


Thanks,

punith s

Re: [VOTE] Apache Cloudstack 4.4.0

2014-07-11 Thread Tomasz Zięba

Hello,

We are waiting for the patch with longingly.

Error associated with self-closing of machines causes very serious
complications, both from the technical (users need to wait for 10 minutes
and check if the machine is not closed automatically) as well as the
business side (this problem does not look very professional from the user
side)

Given that:
- An error has been detected in February so 5 months ago,
- in earlier versions  (3.0.2) error does not exists,
- there is a procedure to reproduce this error,

we would be very grateful if this issue will be resolved in ACS4.4.

-- 
Regards,
Tomasz Zięba
Twitter: @TZieba
LinkedIn: pl.linkedin.com/pub/tomasz-zięba-ph-d/3b/7a8/ab6/


2014-07-11 13:48 GMT+02:00 Daan Hoogland :

> Our beloved VP pointed out that there has not come a vote conclusion yet:
>
> The 4.4.0 vote has resulted in a rejection of the present release
> candidate due to -1 of Marcus and no active voting since.
>
> there are three issues pending from this vote thread:
> - CLOUDSTACK-6036 (Tomasz)
> - unable to add a KVM host (Marcus)
> - top level pom.xml still contains a -SNAPSHOT suffix (Ove, question
> outstanding to Tim)
>
> Can I have some reporting on the status of those issues by the
> reporters, please?
>
> regards,
> your friendly release manager
>
>
> On Wed, Jul 2, 2014 at 10:18 PM, Daan Hoogland 
> wrote:
> > Hi All,
> >
> > I've created a 4.4.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.4-RC20140702T2107
> > Commit: 379387961bd05d1f84fe2e9a1997e9ecdceef91a
> >
> > List of changes:
> >
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/
> >
> > Source release (checksums and signatures are available at the same
> > location):
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.4.0/
> >
> > PGP release keys (signed using 4096R/AA4736F3):
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> > Vote will be open for 72 hours.
> >
> > 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)
> >
> >
> > I will ad my key to the mentioned KEYS file as soon as possible,
> > --
> > Daan
>
>
>
> --
> Daan
>

Re: Review Request 23410: Improvised CloudByte Storage Plugin for 4.5 and above. jira id : CLOUDSTACK-7098

2014-07-11 Thread Mike Tutkowski


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



server/src/com/cloud/configuration/Config.java


Perhaps Edison knows the answer to this:

Do we typically allow vendor-specific config values in Global Settings?


- Mike Tutkowski


On July 11, 2014, 6:42 a.m., punith s wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/23410/
> ---
> 
> (Updated July 11, 2014, 6:42 a.m.)
> 
> 
> Review request for cloudstack, amit kumar das, edison su, and Mike Tutkowski.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> The new improvised cloudbyte plugin for cloudstack supports the following 
> features
> 
> * support for managed storage, where each vm disk has the guaranteed QoS.
> 
> * supports resize of the volume.
> 
> * supports both iscsi and nfs protocols in XEN server, and iscsi protocol for 
> KVM and vmware ESX with respect to managed storage.
> 
> * supports storage level snapshot capabilites as well as hypervisor level 
> snapshot feature.
> 
> * also exposing the custom api's for better ui integration.
> 
> * support for unlimited storage nodes across the sites.
> 
> * account integration in cloudbyte with respect to domains in cloudstack.
> 
> 
> Diffs
> -
> 
>   
> plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/spring-storage-volume-cloudbyte-context.xml
>  87c5f51 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/driver/ElastistorPrimaryDataStoreDriver.java
>  99d1e2a 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java
>  33004e3 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorHostListener.java
>  de4711a 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorPrimaryDataStoreProvider.java
>  e591082 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorUtil.java
>  b75d12a 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorVolumeApiService.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorVolumeApiServiceImpl.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorInterfaceCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorInterfaceResponse.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorPoolCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorPoolResponse.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorVolumeCmd.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorVolumeResponse.java
>  PRE-CREATION 
>   server/src/com/cloud/configuration/Config.java fbcb1f4 
> 
> Diff: https://reviews.apache.org/r/23410/diff/
> 
> 
> Testing
> ---
> 
> system testing done.
> 
> 
> Thanks,
> 
> punith s
> 
>

Re: Review Request 21685: Fixed Regression Issues for CLOUDSTACK-6708

2014-07-11 Thread ASF Subversion and Git Services


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


Commit aab6e1222fc75a37f8015ba1d2c7bc923c1cf614 in cloudstack's branch 
refs/heads/master from santhosh
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=aab6e12 ]

Fixed Regression issues mentioned under CLOUDSTACK-6708

Signed-off-by: santhosh 

Conflicts:

test/integration/smoke/test_deploy_vm.py
test/integration/smoke/test_network.py
test/integration/smoke/test_routers.py
test/integration/smoke/test_vm_life_cycle.py


- ASF Subversion and Git Services


On May 20, 2014, 11:50 a.m., Santhosh Edukulla wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/21685/
> ---
> 
> (Updated May 20, 2014, 11:50 a.m.)
> 
> 
> Review request for cloudstack, daan Hoogland and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-6708
> https://issues.apache.org/jira/browse/CLOUDSTACK-6708
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> There were few failures observed under regression. Fixed them.
> Added Bugids to few  test cases so that they will not run till bugs are fixed.
> 
> 
> Diffs
> -
> 
>   test/integration/smoke/test_deploy_vm.py 473b020 
>   test/integration/smoke/test_hosts.py 52827aa 
>   test/integration/smoke/test_network.py 85b417c 
>   test/integration/smoke/test_routers.py 2aa83c3 
>   test/integration/smoke/test_vm_life_cycle.py 62a807d 
> 
> Diff: https://reviews.apache.org/r/21685/diff/
> 
> 
> Testing
> ---
> 
> Yes, ran on simulator and they works fine.
> 
> 
> Thanks,
> 
> Santhosh Edukulla
> 
>

Coverity Scan Report: July 11 2014

2014-07-11 Thread Santhosh Edukulla

Hi All,

FYI, 
Current Defect Density :3.58
Newly Detected: 7, below are new defects reported by coverity scan service. 

A small note, we should not allow adding new defects  to the existing reported 
count, otherwise, current technical debt will never come down. 
Few of these issues can be equally, found by running findbugs or other static 
analysis tools, using IDE locally. Some of these, reported below could be fp as 
well.

How to use findbugs @link below:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Using+FindBugs 

I believe review submissions, can be made little stringent, if we can 
enforce\atleast inquire for findbugs reports from users for submitted reviews.

Regards
Santhosh


Defect(s) Reported-by: Coverity Scan
Showing 7 of 7 defect(s)


** CID 1225198:  Explicit null dereferenced  (FORWARD_NULL)
/engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java: 1055 in 
com.cloud.upgrade.dao.Upgrade410to420.updateNonLegacyZones(java.sql.Connection, 
java.util.List)()

** CID 1225199:  Resource leak  (RESOURCE_LEAK)
/engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java: 1031 in 
com.cloud.upgrade.dao.Upgrade410to420.updateNonLegacyZones(java.sql.Connection, 
java.util.List)()
/engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java: 1041 in 
com.cloud.upgrade.dao.Upgrade410to420.updateNonLegacyZones(java.sql.Connection, 
java.util.List)()
/engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java: 1109 in 
com.cloud.upgrade.dao.Upgrade410to420.updateNonLegacyZones(java.sql.Connection, 
java.util.List)()
/engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java: 1069 in 
com.cloud.upgrade.dao.Upgrade410to420.updateNonLegacyZones(java.sql.Connection, 
java.util.List)()
/engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java: 1077 in 
com.cloud.upgrade.dao.Upgrade410to420.updateNonLegacyZones(java.sql.Connection, 
java.util.List)()
/engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java: 1109 in 
com.cloud.upgrade.dao.Upgrade410to420.updateNonLegacyZones(java.sql.Connection, 
java.util.List)()

** CID 1225204:  REC: RuntimeException capture  (FB.REC_CATCH_EXCEPTION)
/plugins/hypervisors/baremetal/src/com/cloud/baremetal/networkservice/SecurityGroupHttpClient.java:
 144 in 
com.cloud.baremetal.networkservice.SecurityGroupHttpClient.echo(java.lang.String,
 long, long)()

** CID 1225203:  WMI: Inefficient Map Iterator  (FB.WMI_WRONG_MAP_ITERATOR)
/engine/schema/src/com/cloud/upgrade/dao/Upgrade440to450.java: 84 in 
com.cloud.upgrade.dao.Upgrade440to450.dropInvalidKeyFromStoragePoolTable(java.sql.Connection)()

** CID 1225202:  REC: RuntimeException capture  (FB.REC_CATCH_EXCEPTION)
/engine/schema/src/com/cloud/usage/dao/UsageSecurityGroupDaoImpl.java: 145 in 
com.cloud.usage.dao.UsageSecurityGroupDaoImpl.getUsageRecords(java.lang.Long, 
java.lang.Long, java.util.Date, java.util.Date, boolean, int)()

** CID 1225201:  REC: RuntimeException capture  (FB.REC_CATCH_EXCEPTION)
/engine/schema/src/com/cloud/usage/dao/UsageStorageDaoImpl.java: 211 in 
com.cloud.usage.dao.UsageStorageDaoImpl.getUsageRecords(java.lang.Long, 
java.lang.Long, java.util.Date, java.util.Date, boolean, int)()

** CID 1225200:  SIC: Inner class could be made static  
(FB.SIC_INNER_SHOULD_BE_STATIC)
/plugins/storage/volume/solidfire/src/org/apache/cloudstack/storage/datastore/lifecycle/SolidFireSharedPrimaryDataStoreLifeCycle.java:
 296 in ()



*** CID 1225198:  Explicit null dereferenced  (FORWARD_NULL)
/engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java: 1055 in 
com.cloud.upgrade.dao.Upgrade410to420.updateNonLegacyZones(java.sql.Connection, 
java.util.List)()
1049 } else if (key.equalsIgnoreCase("password")) {
1050 password = value;
1051 } else if (key.equalsIgnoreCase("url")) {
1052 url = value;
1053 }
1054 }
>>> CID 1225198:  Explicit null dereferenced  (FORWARD_NULL)
>>> Calling a method on null object "url".
1055 String[] tokens = url.split("/"); // url format - 
http://vcenter/dc/cluster
1056 String vc = tokens[2];
1057 String dcName = tokens[3];
1058 String guid = dcName + "@" + vc;
1059
1060 pstmt = conn.prepareStatement("INSERT INTO 
`cloud`.`vmware_data_center` (uuid, name, guid, vcenter_host, username, 
password) values(?, ?, ?, ?, ?, ?)");


*** CID 1225199:  Resource leak  (RESOURCE_LEAK)
/engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java: 1031 in 
com.cloud.upgrade.dao.Upgrade410to420.updateNonLegacyZones(java.sql.Connection, 
java.util.List)(

Re: feature : changing volume properties dynamically in 4.5

2014-07-11 Thread Mike Tutkowski

Just an FYI that I was busy the past week working on building integration
tests for SolidFire-related functionality that's executed in CloudStack,
but I plan to get back to this resizeVolume API work today.


On Wed, Jun 25, 2014 at 10:27 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Hi Punith,
>
> Yes, that is exactly the approach I was planning on taking: enhance the
> resizeVolume API to allow for IOPS control and to extend what it can do
> with volume sizes.
>
> Talk to you later!
> Mike
>
>
> On Wed, Jun 25, 2014 at 7:44 AM, Punith S  wrote:
>
>> hi mike,
>>
>> now this updateStoragePool API would be really helpful to update the
>> backend storagepool and other third party features.
>>
>> question on individual CloudStack volumes
>>  is it feasible to associate resize volume and changing IOPS into one API
>> ?
>>
>> if so we might need to add more intelligence in the design to make sure
>> disk is not detached if only IOPS is being modified in the select new disk
>> offering
>> else disk shall be detached if both size and IOPS vary in the selected
>> new disk offering.
>>
>> thanks.
>>
>>
>> On Wed, Jun 25, 2014 at 2:25 AM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>>> OK, I've completed work on enabling a storage plug-in to be notified
>>> when the size and/or IOPS of the primary storage that it represents is
>>> changed:
>>>
>>>
>>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=c344693e48d80313270d1a972b0a3badf315567d
>>>
>>> This is related to the updateStoragePool API.
>>>
>>> I plan to switch my focus now to the resizeVolume API so that individual
>>> CloudStack volumes (as opposed to the entire storage pool they are from)
>>> can have not only their size, but their IOPS updated.
>>>
>>>
>>> On Fri, Jun 20, 2014 at 12:31 AM, Mike Tutkowski <
>>> mike.tutkow...@solidfire.com> wrote:
>>>
 I'll define constants for the keys in PrimaryDataStoreLifeCycle.


 On Friday, June 20, 2014, Mike Tutkowski 
 wrote:

> In fact, we do use a hash-map approach for some KVM storage code, too.
>
> Let's do that here, as well.
>
> I'll make that change.
>
> Thanks
>
> On Friday, June 20, 2014, Mike Tutkowski 
> wrote:
>
>> We do - in some places in the code - use a hash map...like what you
>> describe.
>>
>> I guess the trade off there would be that the values that contain our
>> numbers would end up being high-level objects instead of numbers (because
>> we don't really know what future values might be).
>>
>> I'm OK with either approach.
>>
>> On Friday, June 20, 2014, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>>> Unfortunately, at the time being, the updateStoragePool API (from
>>> the public-facing API) only takes in bytes, IOPS, and storage tags...not
>>> details (createStoragePool takes in a lot more parameters...including
>>> details).
>>>
>>> So - for now at least - we're a little limited in what the new
>>> interface method can tell storage providers about (unless we wanted to
>>> spend time adding to the parameter list of updateStoragePool).
>>>
>>> On Friday, June 20, 2014, Amit Das  wrote:
>>>
 Hi Mike,

 Is there any use case to have a more generic signature for
 updateStoragePool API ?

 e.g
 void updateStoragePool(StoragePool storagePool, Map
 updateDetails);
 // not too sure of what should be E & V as of now. To start with E
 & V can be String types or Enums for better static checks.

 instead of below
 void updateCapacity(StoragePool storagePool, Long capacityBytes, L
 ong capacityIops);

 

 Regards,
 Amit
 *CloudByte Inc.* 


 On Fri, Jun 20, 2014 at 10:37 AM, Mike Tutkowski <
 mike.tutkow...@solidfire.com> wrote:

> I just wanted to update those who are interested in this thread
> about work I've done on this over the past couple days.
>
> This gist is that I've added a new method to the
> PrimaryDataStoreLifeCycle interface that has the following signature 
> (this
> code is not yet checked in):
>
> void updateCapacity(StoragePool storagePool, Long capacityBytes, L
> ong capacityIops);
>
> This method can be invoked from StorageManagerImpl when the
> updateStoragePool API is called.
>
> This gives the storage plug-in that backs the primary storage in
> question an opportunity to update the backend storage it represents, 
> if
> that makes sense to do in your particular case (for example, changing 
> the
> size and/or IOPS of a volume).
>
> There is a related enhancement

Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)

2014-07-11 Thread David Nalley

I tend to agree with Erik, flexibility solves the problem for more
people, while solution 1 is likely the easiest to implement. I am not
sure that it makes sense for most people though - and would really
only work for greenfield deployments or clouds that had all of the DNS
entries relating to instances in the cloud.

First question; how are you intending on using it? Which of those
solutions works for you?

--David



On Thu, Jul 3, 2014 at 3:49 PM, Erik Weber  wrote:
> To push that choice over to the operator you could add it as a
> global/zone/network option.
>
> As an operator i would prefer to have my own logic to handle cleanup, but
> this varies for everyone hence the option :-)
>
> Erik
> 3. juli 2014 21:45 skrev "Silvano Nogueira Buback" 
> følgende:
>
>> Hi guys,
>>
>> I think you are busy because 4.4 release tasks, but I'm worried about
>> the time to 4.5 feature freeze. I put the documentation of feature in wiki
>> as requested and I hoped people read there and make some comments here.
>>
>> To help, I will put design issues that are in document, one by one, and we
>> can discuss in this thread. After each discussion I will change the
>> document.
>>
>>I have one question about removing DNS domain when network has been
>> deleted. In my current implementation I remove DNS domain when network is
>> removed. But if the DNS domain is shared with another network or maybe is a
>> dns domain used outside ACS this can be a problem. What I can do with DNS
>> domain when network is removed:
>>
>>1. Keep the current implementation. Always deleted DNS domain when
>>network is removed (works well if the ACS is the only manager for the
>> DNS
>>(one network domain per network).
>>2. Remove DNS domain only if the domain was created by ACS. This can be
>>a problem if someone put records after ACS creation.
>>3. Remove DNS domain only if there is no more records there. Maybe DNS
>>domain can stay forever there because an inconsistency that keep only
>> one
>>record.
>>
>>
>> Which one is the best?
>>
>> []'s,
>>
>> Silvano Buback
>>
>>
>>
>> On Thu, Jun 26, 2014 at 11:34 AM, Silvano Nogueira Buback <
>> silv...@corp.globo.com> wrote:
>>
>> > Thank you David.
>> >
>> > I put design documents on wiki:
>> >
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Bind+and+PowerDNS+integration+by+Globo+DNSAPI
>> .
>> > I create an issue https://issues.apache.org/jira/browse/CLOUDSTACK-6998
>> > too.
>> >
>> > I look forward to hearing your feedbacks.
>> >
>> > []'s,
>> >
>> > Silvano Buback
>> >
>> >
>> > On Wed, Jun 25, 2014 at 5:50 PM, David Nalley  wrote:
>> >
>> >> On Wed, Jun 25, 2014 at 4:38 PM, Silvano Nogueira Buback
>> >>  wrote:
>> >> > Hi guys,
>> >> >
>> >> >I finish the first version of design document:
>> >> >
>> >>
>> https://docs.google.com/document/d/1kbPQJrBC87ZtR-t7LwHFDzAmT436ShtjwKE84FVfByM/pub
>> >> > .
>> >> >
>> >> >Someone could give me access to put design documents in wiki?
>> Bellow
>> >> the
>> >> > username of people work with Cloudstack in Globo.com and need access.
>> >> >
>> >> > snbuback silv...@corp.globo.com
>> >> > daniel.simoes daniel.sim...@corp.globo.com
>> >> > lokama - lok...@gmail.com
>> >> >
>> >> > Regards,
>> >> >
>> >> > Silvano Buback
>> >> >
>> >> >
>> >> >
>> >> > On Thu, Jun 19, 2014 at 11:29 AM, Silvano Buback 
>> >> wrote:
>> >> >
>> >> >> Of course, I forgotten my account info:
>> >> >> snbuback / silv...@corp.globo.com
>> >> >>
>> >>
>> >>
>> >> Done.
>> >>
>> >> --David
>> >>
>> >
>> >
>>

Resize Volume Question

2014-07-11 Thread Mike Tutkowski

Hi,

In the resize-volume command, I see this logic:

if (diskOffering.isCustomized() ||
volume.getVolumeType().equals(Volume.Type.ROOT)) {

newSize = cmd.getSize();


if (newSize != null) {

newSize = (newSize << 30);

}

}

Any thoughts on why we are shifting bits 30 places to the left?

I don't recall us doing this in other places for long values?

This is in VolumeApiServiceImpl.resizeVolume.

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
*™*

[DISCUSS]CLOUDSTACK-6191

2014-07-11 Thread Edison Su

Move the discussion to the list about CloudStack-6191:
Automation test is blocked by this bug, we need to find a solution. My 
suggestion is sort-of-revert-the-patch, but still give admin the opportunity to 
specify the way to optimize KVM volume creation. The reasons:

1.   End user shouldn't care about how the volume is created, is it 
sparse,flat/thin-provisoned or whatever technology used by hypervisor. So we'd 
better not expose this option in disk offering.

2.It's true that admin does care about how the volume is created, so we 
can add a global configuration just for the kvm volume creation. For vmware, 
the option is already there(vmware.create.full.clone to control whether link 
clone or full clone is used to create volume). We can add an option, something 
like kvm.qcow2.volume.create.options.
Comments?

Re: Resize Volume Question

2014-07-11 Thread Nitin Mehta

Probably converting from GB to bytes ? I recall doing that for creating
volumes from custom disk offering.

On 11/07/14 2:07 PM, "Mike Tutkowski"  wrote:

>Hi,
>
>In the resize-volume command, I see this logic:
>
>if (diskOffering.isCustomized() ||
>volume.getVolumeType().equals(Volume.Type.ROOT)) {
>
>newSize = cmd.getSize();
>
>
>if (newSize != null) {
>
>newSize = (newSize << 30);
>
>}
>
>}
>
>Any thoughts on why we are shifting bits 30 places to the left?
>
>I don't recall us doing this in other places for long values?
>
>This is in VolumeApiServiceImpl.resizeVolume.
>
>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
>**

Re: Review Request 22863: CLOUDSTACK-6823 : First code drop for Brocade Network plugin to orchestrate Brocade VDX switches for L2 connectivity.

2014-07-11 Thread Ritu Sabharwal

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

(Updated July 11, 2014, 10:10 p.m.)

Review request for cloudstack and Hugo Trippaers.

Changes
---

Updated the diff.

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

Repository: cloudstack-git

Description
---

First code drop for Brocade Network plugin to orchestrate Brocade VDX switches
for L2 connectivity. Please create a new branch for Brocade plugin.

Diffs (updated)
-

api/src/com/cloud/network/Network.java 885bffe
api/src/com/cloud/network/Networks.java 1e4d229
api/src/com/cloud/network/PhysicalNetwork.java 8cc214e
client/pom.xml 29fef4f
plugins/pom.xml b5e6a61
setup/db/db/schema-440to450.sql 77445a9
ui/scripts/system.js 9a98a5c
ui/scripts/ui-custom/zoneWizard.js 4091c03

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

Testing
---

• Create an isolated network; verify that the port-profile is created on
the Brocade switch.
• Attach a VM to the network; verify that the VMs MAC address is
associated with the port profile of the network on the Brocade switch.
• Delete VMs for an isolated network; verify that the VMs MAC address is
disassociated with the port profile of the network on the Brocade switch.
• Delete the isolated network; verify that the port-profile is deleted
from the Brocade switch.

File Attachments

Diff for the existing cloudstack code

https://reviews.apache.org/media/uploaded/files/2014/06/23/8fc3cfb1-7a21-4714-98f3-6514cf54ba84__diff
Patch file for Brocade functionality code

https://reviews.apache.org/media/uploaded/files/2014/06/26/92bb0014-a7b7-4f0b-97c9-018d615b658a__brocade-vcs.patch

Thanks,

Ritu Sabharwal

RE: VM HA on xenserver 6.2

2014-07-11 Thread Prachi Damle

If you set the global setting 'ha.tag' and tag the hosts then those hosts 
become dedicated HA hosts as you observed.
If you want to use all your hosts for regular VM deployments, then you should 
not ha tag them.

Just using 'ha.enabled' service offering while deploying the VMs should be 
sufficient for you.

Thanks,
Prachi

-Original Message-
From: Tejas Gadaria [mailto:refond.g...@gmail.com] 
Sent: Friday, July 11, 2014 4:56 AM
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: VM HA on xenserver 6.2

Hi,

I want to provide HA to VMs, currently i have created service offering with 'HA 
enable'
option. Hence VM is showing 'HA Enable'. but Host is hot HA enable.

Also for host If I change global setting 'ha.tag' = 'label' & apply 'label'
to host tag it shows 'HA Enable'.

but while deploying vm that host with host tag='label' doesn't allow to create 
vms.
It act as dedicated HA host.

I don't want to create Dedicated HA for now. I want VM HA on cluster level so 
if one host goes down vm will be migrated to another host.

Regards,
Tejas

RE: [DISCUSS]CLOUDSTACK-6191

2014-07-11 Thread Rayees Namathponnan

+1 Revert now and enable after complete full test in KVM

KVM automation blocked more than 7 days due to this defect 

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

Regards,
Rayees

-Original Message-
From: Edison Su [mailto:edison...@citrix.com] 
Sent: Friday, July 11, 2014 2:49 PM
To: dev@cloudstack.apache.org
Subject: [DISCUSS]CLOUDSTACK-6191

Move the discussion to the list about CloudStack-6191:
Automation test is blocked by this bug, we need to find a solution. My 
suggestion is sort-of-revert-the-patch, but still give admin the opportunity to 
specify the way to optimize KVM volume creation. The reasons:

1.   End user shouldn't care about how the volume is created, is it 
sparse,flat/thin-provisoned or whatever technology used by hypervisor. So we'd 
better not expose this option in disk offering.

2.It's true that admin does care about how the volume is created, so we 
can add a global configuration just for the kvm volume creation. For vmware, 
the option is already there(vmware.create.full.clone to control whether link 
clone or full clone is used to create volume). We can add an option, something 
like kvm.qcow2.volume.create.options.
Comments?

Re: Review Request 23314: Plugin specific code for the Brocade Network Plugin

2014-07-11 Thread Ritu Sabharwal


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

(Updated July 11, 2014, 11:44 p.m.)


Review request for cloudstack.


Changes
---

Unit tests added.


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


Repository: cloudstack-git


Description
---

Plugin specific code.


Diffs (updated)
-

  plugins/network-elements/brocade-vcs/pom.xml PRE-CREATION 
  plugins/network-elements/brocade-vcs/resources/BrocadeInterfaceSchema.xsd 
PRE-CREATION 
  plugins/network-elements/brocade-vcs/resources/BrocadePortProfileSchema.xsd 
PRE-CREATION 
  plugins/network-elements/brocade-vcs/resources/BrocadeShowVcsSchema.xsd 
PRE-CREATION 
  
plugins/network-elements/brocade-vcs/resources/META-INF/cloudstack/vcs/module.properties
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/resources/META-INF/cloudstack/vcs/spring-vcs-context.xml
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/AssociateMacToNetworkAnswer.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/AssociateMacToNetworkCommand.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/CreateNetworkAnswer.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/CreateNetworkCommand.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/DeleteNetworkAnswer.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/DeleteNetworkCommand.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/DisassociateMacFromNetworkAnswer.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/DisassociateMacFromNetworkCommand.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/StartupBrocadeVcsCommand.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/BrocadeVcsNetworkHostMappingVO.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/BrocadeVcsApi.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/BrocadeVcsApiException.java
 PRE-CREATION 
  plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/Cache.java 
PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/CacheManager.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/Constants.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/Switch.java 
PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/dao/BrocadeVcsNetworkHostMappingDao.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/dao/BrocadeVcsNetworkHostMappingDaoImpl.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/element/BrocadeVcsElement.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/guru/BrocadeVcsGuestNetworkGuru.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/resource/BrocadeVcsResource.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/test/com/cloud/network/brocade/BrocadeVcsApiTest.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/test/com/cloud/network/guru/BrocadeVcsGuestNetworkGuruTest.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/test/com/cloud/network/resource/BrocadeVcsResourceTest.java
 PRE-CREATION 

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


Testing
---


Thanks,

Ritu  Sabharwal

Re: Review Request 23314: Plugin specific code for the Brocade Network Plugin

2014-07-11 Thread Ritu Sabharwal



> On July 8, 2014, 9:29 a.m., Hugo Trippaers wrote:
> > Thanks for make this a separate review, much easier to read.
> > 
> > The licenses are not added to all files and in some files they appear not 
> > to be complete. A good trick to solve this is to include the 
> > license-maven-plugin in the build section. See 
> > plugins/network-elements/nicira-nvp/pom.xml for an example.
> > 
> > Also the plugin doesn't contain any tests. We need unit tests or functional 
> > tests (and preferably both) to validate that this plugin works and keeps on 
> > working in future versions of CloudStack. It would be great if you could 
> > supply unit tests to validate this inner workings of this module and marvin 
> > based integration tests that we can run to see if this work with the 
> > intended hardware.
> > 
> > The last general point is that we would also need documentation on this 
> > plugin so administrators will know how to use this.
> 
> Ritu  Sabharwal wrote:
> Thanks for reviewing the code.
> 
> I have fixed the license in all the files.
> 
> I am working on writing the unit tests for the plugin.
> 
> I am working on providing the documentation on using the plugin.
> 
> I have tested the plugin with the simulator and see the configurations on 
> Brocade switches happening. Currently, I am setting up a real hardware setup 
> with Vmware hypervisor and Brocade switches so test the connectivity between 
> spawned VMs.
> 
> Can I continue writing the unit tests and marvin integration tests and 
> documentation after the July 19 date so that this plugin makes to 4.5 feature 
> freeze date.
> 
> I have updated the diffs with the changes for the license and other 
> comments.
> 
> Ritu  Sabharwal wrote:
> I am planning to include the following in the documentation:
>  - Brocade switch setup
>  - Connections to the Hypervisor hosts
>  - the flow to use the plugin from UI
> 
> Hugo Trippaers wrote:
> Thanks for fixing the open issues.
> 
> I think it's ok to work on the documentation while a release is being 
> tested (eventhough it is far better to have it ready for the testers). 
> However unittests and functional testcases need to be there before we can 
> merge the plugin. Without it we can not properly test the plugin to see if it 
> is fit to be part of the release. 
> 
> I'd rather have a completely done plugin in the 4.6 release than 
> something that is not complete in 4.5. So currently the blockers for a merge 
> into master are the two property files and we need unit and integration tests.
> 
> Ritu  Sabharwal wrote:
> Hi Hugo,
> 
> Thanks for reviewing the plugin.
> 
> Few points:
> 
> 1. The configuration using properties file was part of the Design 
> document 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Brocade+Network+Plugin+to+Orchestrate+Brocade+VDX+Switches
>  and was not raised as a concern earlier and the implementation is based on 
> that.  
> 
> Changing the implementation right now would involve some work. Can this 
> be done as an enhancement as part of bug fix during testing?
> 
> 2. For functional testcases, we are doing functional testing but how will 
> functional testcases be run by the community without the Brocade hardware? 
> 
> We are working on writing the unit and functional testcases.
>

Hi Hugo,

I have added the unit tests, working on the the marvin integration tests.

Please reply back for the properties file change if that can be treated an an 
enhancement bug fix during testing phase.

Thanks for reviewing and supporting the plugin.

Thanks & Regards,
Ritu S.


- Ritu


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


On July 11, 2014, 11:44 p.m., Ritu  Sabharwal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/23314/
> ---
> 
> (Updated July 11, 2014, 11:44 p.m.)
> 
> 
> Review request for cloudstack.
> 
> 
> Bugs: CLOUDSTACK-6823
> https://issues.apache.org/jira/browse/CLOUDSTACK-6823
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Plugin specific code.
> 
> 
> Diffs
> -
> 
>   plugins/network-elements/brocade-vcs/pom.xml PRE-CREATION 
>   plugins/network-elements/brocade-vcs/resources/BrocadeInterfaceSchema.xsd 
> PRE-CREATION 
>   plugins/network-elements/brocade-vcs/resources/BrocadePortProfileSchema.xsd 
> PRE-CREATION 
>   plugins/network-elements/brocade-vcs/resources/BrocadeShowVcsSchema.xsd 
> PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/resources/META-INF/cloudstack/vcs/module.properties
>  PRE-CREATION 
>   
> plugins/netw

Re: Resize Volume Question

2014-07-11 Thread Mike Tutkowski

Sure, that makes sense - thanks.

It's too bad we don't really have a standard for our API in terms of how
volume sizes are referenced. It seems sometimes we use bytes while other
times we use GB. I was thinking the units were bytes here, but they are GB.


On Fri, Jul 11, 2014 at 3:55 PM, Nitin Mehta  wrote:

> Probably converting from GB to bytes ? I recall doing that for creating
> volumes from custom disk offering.
>
> On 11/07/14 2:07 PM, "Mike Tutkowski" 
> wrote:
>
> >Hi,
> >
> >In the resize-volume command, I see this logic:
> >
> >if (diskOffering.isCustomized() ||
> >volume.getVolumeType().equals(Volume.Type.ROOT)) {
> >
> >newSize = cmd.getSize();
> >
> >
> >if (newSize != null) {
> >
> >newSize = (newSize << 30);
> >
> >}
> >
> >}
> >
> >Any thoughts on why we are shifting bits 30 places to the left?
> >
> >I don't recall us doing this in other places for long values?
> >
> >This is in VolumeApiServiceImpl.resizeVolume.
> >
> >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
> >* *
>
>


-- 
*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: Resize Volume Question

2014-07-11 Thread Nitin Mehta

Mike - Would you mind creating a bug for it or better still adding a
comment in the code as a //TODO - standardize it if you can't fix it ?
I guess currently dev writing new code doesn't have a good reference
whether to take it as bytes or in GB. That¹s why you are seeing both
varieties.

Thanks,
-Nitin

On 11/07/14 6:33 PM, "Mike Tutkowski"  wrote:

>Sure, that makes sense - thanks.
>
>It's too bad we don't really have a standard for our API in terms of how
>volume sizes are referenced. It seems sometimes we use bytes while other
>times we use GB. I was thinking the units were bytes here, but they are
>GB.
>
>
>On Fri, Jul 11, 2014 at 3:55 PM, Nitin Mehta 
>wrote:
>
>> Probably converting from GB to bytes ? I recall doing that for creating
>> volumes from custom disk offering.
>>
>> On 11/07/14 2:07 PM, "Mike Tutkowski" 
>> wrote:
>>
>> >Hi,
>> >
>> >In the resize-volume command, I see this logic:
>> >
>> >if (diskOffering.isCustomized() ||
>> >volume.getVolumeType().equals(Volume.Type.ROOT)) {
>> >
>> >newSize = cmd.getSize();
>> >
>> >
>> >if (newSize != null) {
>> >
>> >newSize = (newSize << 30);
>> >
>> >}
>> >
>> >}
>> >
>> >Any thoughts on why we are shifting bits 30 places to the left?
>> >
>> >I don't recall us doing this in other places for long values?
>> >
>> >This is in VolumeApiServiceImpl.resizeVolume.
>> >
>> >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
>> >* *
>>
>>
>
>
>-- 
>*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: Resize Volume Question

2014-07-11 Thread Mike Tutkowski

OK, so, I did a couple things:

1) I documented the code in the resize-volume area (there were two places
that I saw) where we bit shift to convert from GB to bytes.

2) I created: https://issues.apache.org/jira/browse/CLOUDSTACK-7101

The ticket will probably have to wait until a major release because
changing the meaning of that parameter is essentially breaking backward
compatibility.


On Fri, Jul 11, 2014 at 8:47 PM, Nitin Mehta  wrote:

> Mike - Would you mind creating a bug for it or better still adding a
> comment in the code as a //TODO - standardize it if you can't fix it ?
> I guess currently dev writing new code doesn't have a good reference
> whether to take it as bytes or in GB. That¹s why you are seeing both
> varieties.
>
> Thanks,
> -Nitin
>
> On 11/07/14 6:33 PM, "Mike Tutkowski" 
> wrote:
>
> >Sure, that makes sense - thanks.
> >
> >It's too bad we don't really have a standard for our API in terms of how
> >volume sizes are referenced. It seems sometimes we use bytes while other
> >times we use GB. I was thinking the units were bytes here, but they are
> >GB.
> >
> >
> >On Fri, Jul 11, 2014 at 3:55 PM, Nitin Mehta 
> >wrote:
> >
> >> Probably converting from GB to bytes ? I recall doing that for creating
> >> volumes from custom disk offering.
> >>
> >> On 11/07/14 2:07 PM, "Mike Tutkowski" 
> >> wrote:
> >>
> >> >Hi,
> >> >
> >> >In the resize-volume command, I see this logic:
> >> >
> >> >if (diskOffering.isCustomized() ||
> >> >volume.getVolumeType().equals(Volume.Type.ROOT)) {
> >> >
> >> >newSize = cmd.getSize();
> >> >
> >> >
> >> >if (newSize != null) {
> >> >
> >> >newSize = (newSize << 30);
> >> >
> >> >}
> >> >
> >> >}
> >> >
> >> >Any thoughts on why we are shifting bits 30 places to the left?
> >> >
> >> >I don't recall us doing this in other places for long values?
> >> >
> >> >This is in VolumeApiServiceImpl.resizeVolume.
> >> >
> >> >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
> >> >* *
> >>
> >>
> >
> >
> >--
> >*Mike Tutkowski*
> >*Senior CloudStack Developer, SolidFire Inc.*
> >e: mike.tutkow...@solidfire.com
> >o: 303.746.7302
> >Advancing the way the world uses the cloud
> >* *
>
>


-- 
*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: Resize Volume Question

2014-07-11 Thread Mike Tutkowski

Oh, by the way, that code documentation is still in my sandbox (i.e. not
committed). I am working on updating the resize-volume logic for 4.5.
Hopefully I'll have it checked in sometime next week.


On Sat, Jul 12, 2014 at 12:09 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> OK, so, I did a couple things:
>
> 1) I documented the code in the resize-volume area (there were two places
> that I saw) where we bit shift to convert from GB to bytes.
>
> 2) I created: https://issues.apache.org/jira/browse/CLOUDSTACK-7101
>
> The ticket will probably have to wait until a major release because
> changing the meaning of that parameter is essentially breaking backward
> compatibility.
>
>
> On Fri, Jul 11, 2014 at 8:47 PM, Nitin Mehta 
> wrote:
>
>> Mike - Would you mind creating a bug for it or better still adding a
>> comment in the code as a //TODO - standardize it if you can't fix it ?
>> I guess currently dev writing new code doesn't have a good reference
>> whether to take it as bytes or in GB. That¹s why you are seeing both
>> varieties.
>>
>> Thanks,
>> -Nitin
>>
>> On 11/07/14 6:33 PM, "Mike Tutkowski" 
>> wrote:
>>
>> >Sure, that makes sense - thanks.
>> >
>> >It's too bad we don't really have a standard for our API in terms of how
>> >volume sizes are referenced. It seems sometimes we use bytes while other
>> >times we use GB. I was thinking the units were bytes here, but they are
>> >GB.
>> >
>> >
>> >On Fri, Jul 11, 2014 at 3:55 PM, Nitin Mehta 
>> >wrote:
>> >
>> >> Probably converting from GB to bytes ? I recall doing that for creating
>> >> volumes from custom disk offering.
>> >>
>> >> On 11/07/14 2:07 PM, "Mike Tutkowski" 
>> >> wrote:
>> >>
>> >> >Hi,
>> >> >
>> >> >In the resize-volume command, I see this logic:
>> >> >
>> >> >if (diskOffering.isCustomized() ||
>> >> >volume.getVolumeType().equals(Volume.Type.ROOT)) {
>> >> >
>> >> >newSize = cmd.getSize();
>> >> >
>> >> >
>> >> >if (newSize != null) {
>> >> >
>> >> >newSize = (newSize << 30);
>> >> >
>> >> >}
>> >> >
>> >> >}
>> >> >
>> >> >Any thoughts on why we are shifting bits 30 places to the left?
>> >> >
>> >> >I don't recall us doing this in other places for long values?
>> >> >
>> >> >This is in VolumeApiServiceImpl.resizeVolume.
>> >> >
>> >> >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
>> >> >* *
>> >>
>> >>
>> >
>> >
>> >--
>> >*Mike Tutkowski*
>> >*Senior CloudStack Developer, SolidFire Inc.*
>> >e: mike.tutkow...@solidfire.com
>> >o: 303.746.7302
>> >Advancing the way the world uses the cloud
>> >* *
>>
>>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> *™*
>



-- 
*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: End user portal

2014-07-11 Thread Giri Prasad

What if several features of the standard CloudStack GUI (user login) are not to 
be shown to the user?

Looking for a simple portal which allows end users to login, select a vm, 
spinoff that vm with its apps and data, and which allows end user logout. 

> What about just using the standard CloudStack GUI?

> http://xxx.xxx.xxx.xxx:8080/client/

On Sun, Jul 6, 2014 at 10:36 PM, Giri Prasad 
wrote:

> Hi All,
>
>  I am looking for a opensource end user portal to cloudstack 4.1. The CS
> is installed and working fine. I am looking at a simple end user portal,
> which will provide the users to ability to login and use the cloudstack
> infra installed. A portal which will provide simple facilities like
> selecting a vm, select a disk/compute offering, run an application on the
> vm, via the portal, etc etc.
>
>
> Any inputs.
>

Re: End user portal

2014-07-11 Thread Mike Tutkowski

Well, one of the GUI people might be able to answer this better, but I was
under the impression each tab on the left-hand side of the GUI is a
separate GUI plug-in and, as such, can be configured to be "in" or "out" of
the GUI fairly easily (kind of like how it works if you log in as an admin
and see more of those tabs than a user would).

I've CCed a couple GUI people.


On Sat, Jul 12, 2014 at 12:15 AM, Giri Prasad 
wrote:

> What if several features of the standard CloudStack GUI (user login) are
> not to be shown to the user?
>
> Looking for a simple portal which allows end users to login, select a vm,
> spinoff that vm with its apps and data, and which allows end user logout.
>
>
>
> > What about just using the standard CloudStack GUI?
>
> > http://xxx.xxx.xxx.xxx:8080/client/
>
>
> On Sun, Jul 6, 2014 at 10:36 PM, Giri Prasad 
> wrote:
>
> > Hi All,
> >
> >  I am looking for a opensource end user portal to cloudstack 4.1. The CS
> > is installed and working fine. I am looking at a simple end user portal,
> > which will provide the users to ability to login and use the cloudstack
> > infra installed. A portal which will provide simple facilities like
> > selecting a vm, select a disk/compute offering, run an application on the
> > vm, via the portal, etc etc.
> >
> >
> > Any inputs.
> >
>



-- 
*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: Resize Volume Question

2014-07-11 Thread Mike Tutkowski

I didn't put this in the ticket, but - historically - when one talks about
1 GB in the persistent-storage world, one means 1,000,000,000 bytes (as
opposed to memory, where 1 GB means 1,073,741,824 bytes).

Some systems try to clarify this by using, for example, GB versus GiB.


On Sat, Jul 12, 2014 at 12:11 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Oh, by the way, that code documentation is still in my sandbox (i.e. not
> committed). I am working on updating the resize-volume logic for 4.5.
> Hopefully I'll have it checked in sometime next week.
>
>
> On Sat, Jul 12, 2014 at 12:09 AM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> OK, so, I did a couple things:
>>
>> 1) I documented the code in the resize-volume area (there were two places
>> that I saw) where we bit shift to convert from GB to bytes.
>>
>> 2) I created: https://issues.apache.org/jira/browse/CLOUDSTACK-7101
>>
>> The ticket will probably have to wait until a major release because
>> changing the meaning of that parameter is essentially breaking backward
>> compatibility.
>>
>>
>> On Fri, Jul 11, 2014 at 8:47 PM, Nitin Mehta 
>> wrote:
>>
>>> Mike - Would you mind creating a bug for it or better still adding a
>>> comment in the code as a //TODO - standardize it if you can't fix it ?
>>> I guess currently dev writing new code doesn't have a good reference
>>> whether to take it as bytes or in GB. That¹s why you are seeing both
>>> varieties.
>>>
>>> Thanks,
>>> -Nitin
>>>
>>> On 11/07/14 6:33 PM, "Mike Tutkowski" 
>>> wrote:
>>>
>>> >Sure, that makes sense - thanks.
>>> >
>>> >It's too bad we don't really have a standard for our API in terms of how
>>> >volume sizes are referenced. It seems sometimes we use bytes while other
>>> >times we use GB. I was thinking the units were bytes here, but they are
>>> >GB.
>>> >
>>> >
>>> >On Fri, Jul 11, 2014 at 3:55 PM, Nitin Mehta 
>>> >wrote:
>>> >
>>> >> Probably converting from GB to bytes ? I recall doing that for
>>> creating
>>> >> volumes from custom disk offering.
>>> >>
>>> >> On 11/07/14 2:07 PM, "Mike Tutkowski" 
>>> >> wrote:
>>> >>
>>> >> >Hi,
>>> >> >
>>> >> >In the resize-volume command, I see this logic:
>>> >> >
>>> >> >if (diskOffering.isCustomized() ||
>>> >> >volume.getVolumeType().equals(Volume.Type.ROOT)) {
>>> >> >
>>> >> >newSize = cmd.getSize();
>>> >> >
>>> >> >
>>> >> >if (newSize != null) {
>>> >> >
>>> >> >newSize = (newSize << 30);
>>> >> >
>>> >> >}
>>> >> >
>>> >> >}
>>> >> >
>>> >> >Any thoughts on why we are shifting bits 30 places to the left?
>>> >> >
>>> >> >I don't recall us doing this in other places for long values?
>>> >> >
>>> >> >This is in VolumeApiServiceImpl.resizeVolume.
>>> >> >
>>> >> >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
>>> >> >* *
>>> >>
>>> >>
>>> >
>>> >
>>> >--
>>> >*Mike Tutkowski*
>>> >*Senior CloudStack Developer, SolidFire Inc.*
>>> >e: mike.tutkow...@solidfire.com
>>> >o: 303.746.7302
>>> >Advancing the way the world uses the cloud
>>> >* *
>>>
>>>
>>
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkow...@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the cloud
>> *™*
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> *™*
>



-- 
*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: How to recreate ssvm & cpvm

customize systemVM

Re: customize systemVM

Review Request 23395: CLOUDSTACK-5663 :- Handled the NULL check for network's cidr field to avoid NPE for createNetwork and listNetwork

Re: Cannot release reservation

Autostart vms on Xenserver 6.2 With HA

RE: "Bug" introduced by part of commit a600d8408ea86782318139c17cf346c8497943d0

Review Request 23410: Improvised CloudByte Storage Plugin for 4.5 and above. jira id : CLOUDSTACK-7098

Re: Review Request 23258: CLOUDSTACK-7062: Tagging test case with BugId

Re: Review Request 23258: CLOUDSTACK-7062: Tagging test case with BugId

Re: [VOTE] Apache Cloudstack 4.4.0

VM HA on xenserver 6.2

Re: Review Request 23410: Improvised CloudByte Storage Plugin for 4.5 and above. jira id : CLOUDSTACK-7098

Re: [VOTE] Apache Cloudstack 4.4.0

Re: Review Request 23410: Improvised CloudByte Storage Plugin for 4.5 and above. jira id : CLOUDSTACK-7098

Re: Review Request 21685: Fixed Regression Issues for CLOUDSTACK-6708

Coverity Scan Report: July 11 2014

Re: feature : changing volume properties dynamically in 4.5

Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)

Resize Volume Question

[DISCUSS]CLOUDSTACK-6191

Re: Resize Volume Question

Re: Review Request 22863: CLOUDSTACK-6823 : First code drop for Brocade Network plugin to orchestrate Brocade VDX switches for L2 connectivity.

RE: VM HA on xenserver 6.2

RE: [DISCUSS]CLOUDSTACK-6191

Re: Review Request 23314: Plugin specific code for the Brocade Network Plugin

Re: Review Request 23314: Plugin specific code for the Brocade Network Plugin

Re: Resize Volume Question

Re: Resize Volume Question

Re: Resize Volume Question

Re: Resize Volume Question

Re: End user portal

Re: End user portal

Re: Resize Volume Question

34 matches

Site Navigation

Mail list logo

Footer information