Questions about 4.2 RC - internal-load-balancing-between-vpc-tiers (2)

[Jessica Wang]

Marcus,

Internal load balancing is NOT supported in Basic zone.

Therefore, if you create a Basic zone through cloudstack UI, cloudstack UI will 
NOT do them automatically:

> list internalloadbalancerelements
> configure internalloadbalancerelement enabled=true 
> id=de5f3495-6a48-4451-bd2f-e9cb9a7f6fbf
> enable the InternalLbVM provider

Jessica

-Original Message-
From: Jessica Wang [mailto:jessica.w...@citrix.com] 
Sent: Thursday, September 05, 2013 2:49 PM
To: dev@cloudstack.apache.org
Cc: Animesh Chaturvedi; Brian Federle
Subject: RE: Questions about 4.2 RC - internal-load-balancing-between-vpc-tiers

Marcus,

> list internalloadbalancerelements
> configure internalloadbalancerelement enabled=true 
> id=de5f3495-6a48-4451-bd2f-e9cb9a7f6fbf
> enable the InternalLbVM provider,

If you create an Advanced zone through cloudStack UI, you don't need to do 
anything above.
cloudstack UI will do them automatically.

To create an Advanced zone through cloudStack UI:

Infrastructure menu > zones > click "Add zone" button > Add zone wizard pops up 
> click "Advanced" >  


Jessica


-Original Message-
From: Marcus Sorensen [mailto:shadow...@gmail.com] 
Sent: Thursday, September 05, 2013 2:15 PM
To: dev@cloudstack.apache.org
Cc: Animesh Chaturvedi
Subject: Re: Questions about 4.2 RC

More questions... I've been going down the rabbithole in figuring out
how to deploy VPCs. Part of this might be a missing marvin config in
my zone deploy, I still have no idea yet, but after reviewing
https://cwiki.apache.org/CLOUDSTACK/internal-load-balancing-between-vpc-tiers.html,
I found that I have to do this:

> list internalloadbalancerelements
> configure internalloadbalancerelement enabled=true 
> id=de5f3495-6a48-4451-bd2f-e9cb9a7f6fbf

Now I can go into the UI and enable the InternalLbVM provider, and
finally create a VPC. Is this how we expect users to do it, or is
there something I'm missing in the UI.

On Thu, Sep 5, 2013 at 2:37 PM, Edison Su  wrote:
>
>
>> -Original Message-
>> From: sebgoa [mailto:run...@gmail.com]
>> Sent: Thursday, September 05, 2013 1:22 AM
>> To: dev@cloudstack.apache.org; Animesh Chaturvedi
>> Subject: Questions about 4.2 RC
>>
>> Hi,
>>
>> I followed the testing procedure for the 4.2 RC, I am ready to vote +1 but I
>> have questions (hence the new thread, don't want to hijack the VOTE).
>>
>> 1. the CHANGES file points to the release notes, but where are the release
>> notes ? I know that no-one really stepped up on the RN but can't we at a
>> minimum do a JIRA query that lists the bugs fixed in 4.2 and the new
>> features ?
>>
>> 2. Under infrastructure when I view the DevCloud Zone, I get this in the log:
>> WARN  [cloud.api.ApiServer] (642225853@qtp-111037821-10:) Unknown API
>> command: listVmwareDcs This is not a deal breaker but why is our UI calling a
>> non-implemented API ? This sounds like introducing known issues. If it's not
>> implemented yet, remove it.
>
> The command is only available in non-oss build, but is still listed in 
> command.properties, as there is no separate file for commands non-oss build.
>
>>
>> 3. Under instances, the new tooltip shows a 'vm snapshot' icon. When you
>> use it, it snapshots but the snapshot is not shown under storage>view
>> snapshots ? Instead you see the snapshot under the instance view.
>> Proceeding to destroy the instance will destroy the snapshot, or at a
>> minimum we don't have access to it via the UI. It seems to be the difference
>> between listVMSnapshot and listSnapshots.
>
> It's by design, the vm snapshot is listed under vm->vm snapshot view, while 
> the volume snapshot listed under storage->snapshot view.
>
>>
>>
>> -Sebastien

RE: Questions about 4.2 RC - internal-load-balancing-between-vpc-tiers

[Jessica Wang]

Marcus,

> list internalloadbalancerelements
> configure internalloadbalancerelement enabled=true 
> id=de5f3495-6a48-4451-bd2f-e9cb9a7f6fbf
> enable the InternalLbVM provider,

If you create an Advanced zone through cloudStack UI, you don't need to do 
anything above.
cloudstack UI will do them automatically.

To create an Advanced zone through cloudStack UI:

Infrastructure menu > zones > click "Add zone" button > Add zone wizard pops up 
> click "Advanced" >  


Jessica


-Original Message-
From: Marcus Sorensen [mailto:shadow...@gmail.com] 
Sent: Thursday, September 05, 2013 2:15 PM
To: dev@cloudstack.apache.org
Cc: Animesh Chaturvedi
Subject: Re: Questions about 4.2 RC

More questions... I've been going down the rabbithole in figuring out
how to deploy VPCs. Part of this might be a missing marvin config in
my zone deploy, I still have no idea yet, but after reviewing
https://cwiki.apache.org/CLOUDSTACK/internal-load-balancing-between-vpc-tiers.html,
I found that I have to do this:

> list internalloadbalancerelements
> configure internalloadbalancerelement enabled=true 
> id=de5f3495-6a48-4451-bd2f-e9cb9a7f6fbf

Now I can go into the UI and enable the InternalLbVM provider, and
finally create a VPC. Is this how we expect users to do it, or is
there something I'm missing in the UI.

On Thu, Sep 5, 2013 at 2:37 PM, Edison Su  wrote:
>
>
>> -Original Message-
>> From: sebgoa [mailto:run...@gmail.com]
>> Sent: Thursday, September 05, 2013 1:22 AM
>> To: dev@cloudstack.apache.org; Animesh Chaturvedi
>> Subject: Questions about 4.2 RC
>>
>> Hi,
>>
>> I followed the testing procedure for the 4.2 RC, I am ready to vote +1 but I
>> have questions (hence the new thread, don't want to hijack the VOTE).
>>
>> 1. the CHANGES file points to the release notes, but where are the release
>> notes ? I know that no-one really stepped up on the RN but can't we at a
>> minimum do a JIRA query that lists the bugs fixed in 4.2 and the new
>> features ?
>>
>> 2. Under infrastructure when I view the DevCloud Zone, I get this in the log:
>> WARN  [cloud.api.ApiServer] (642225853@qtp-111037821-10:) Unknown API
>> command: listVmwareDcs This is not a deal breaker but why is our UI calling a
>> non-implemented API ? This sounds like introducing known issues. If it's not
>> implemented yet, remove it.
>
> The command is only available in non-oss build, but is still listed in 
> command.properties, as there is no separate file for commands non-oss build.
>
>>
>> 3. Under instances, the new tooltip shows a 'vm snapshot' icon. When you
>> use it, it snapshots but the snapshot is not shown under storage>view
>> snapshots ? Instead you see the snapshot under the instance view.
>> Proceeding to destroy the instance will destroy the snapshot, or at a
>> minimum we don't have access to it via the UI. It seems to be the difference
>> between listVMSnapshot and listSnapshots.
>
> It's by design, the vm snapshot is listed under vm->vm snapshot view, while 
> the volume snapshot listed under storage->snapshot view.
>
>>
>>
>> -Sebastien

RE: Questions about 4.2 RC - listVmwareDcs API

[Jessica Wang]

> This API is called by UI to implement toggle effect for icon "Add/Remove 
> VMware Datacenter".

[Jesisca] No, listVmwareDcs API was called by UI to get VMware DataCenter info 
to display in zone detail page (which has 3 fields: "VMware dataCenter Name", 
"VMware dataCenter vcenter", "VMware dataCenter Id"), NOT to toggle effect for 
icon "Add/Remove VMware Datacenter".


> [Chip] Shouldn't we consider making the UI respond appropriately to a missing 
> API 
> (i.e.: don't show that feature if the API response to that call is an error 
> saying that the API call doesn't exist)?

[Jessica] There is no way for UI to know whether an API command is missing or 
not before calling it.
After calling an API command, if API returns error "Unknown API command", UI 
will suppress the error message (i.e. UI will not pop up a dialog showing 
"Unknown API command"). 
The error "Unknown API command" was seen in the log, NOT on UI. 
However, I just checked in an UI enhancement to skip calling listVmwareDcs API 
if a zone doesn't have any VMware cluster(s).


-Original Message-
From: Chip Childers [mailto:chip.child...@sungard.com] 
Sent: Friday, September 06, 2013 9:08 AM
To: dev@cloudstack.apache.org
Cc: Animesh Chaturvedi
Subject: Re: Questions about 4.2 RC

On Fri, Sep 06, 2013 at 03:21:24PM +, Sateesh Chodapuneedi wrote:
> > -Original Message-
> > From: Edison Su [mailto:edison...@citrix.com]
> > Sent: 06 September 2013 02:08
> > To: dev@cloudstack.apache.org; Animesh Chaturvedi
> > Subject: RE: Questions about 4.2 RC
> > 
> > 
> > 
> > > -Original Message-
> > > From: sebgoa [mailto:run...@gmail.com]
> > > Sent: Thursday, September 05, 2013 1:22 AM
> > > To: dev@cloudstack.apache.org; Animesh Chaturvedi
> > > Subject: Questions about 4.2 RC
> > >
> > > Hi,
> > >
> > > I followed the testing procedure for the 4.2 RC, I am ready to vote +1
> > > but I have questions (hence the new thread, don't want to hijack the 
> > > VOTE).
> > >
> > > 1. the CHANGES file points to the release notes, but where are the
> > > release notes ? I know that no-one really stepped up on the RN but
> > > can't we at a minimum do a JIRA query that lists the bugs fixed in 4.2
> > > and the new features ?
> > >
> > > 2. Under infrastructure when I view the DevCloud Zone, I get this in the 
> > > log:
> > > WARN  [cloud.api.ApiServer] (642225853@qtp-111037821-10:) Unknown API
> > > command: listVmwareDcs This is not a deal breaker but why is our UI
> > > calling a non-implemented API ? This sounds like introducing known
> > > issues. If it's not implemented yet, remove it.
> > 
> > The command is only available in non-oss build, but is still listed in 
> > command.properties, as there is no separate file for commands non-oss
> > build.
> Yes, this command is only available in non-oss build and had to be placed in 
> command.properties as no separate file available for non-oss build.
> This API is called by UI to implement toggle effect for icon "Add/Remove 
> VMware Datacenter". This icon is associated with a cloudstack zone.
> If we drop the toggle functionality from UI then we need to have 2 icons 
> instead (one for "Add" and other for "Remove").

Shouldn't we consider making the UI respond appropriately to a missing
API (i.e.: don't show that feature if the API response to
that call is an error saying that the API call doesn't exist)?

RE: Questions about 4.2 RC - Unknown API command: listVmwareDcs

[Jessica Wang]

Sebastien,

>> [Sebastien] 2. Under infrastructure when I view the DevCloud Zone, I get 
>> this in the log:
>> WARN  [cloud.api.ApiServer] (642225853@qtp-111037821-10:) Unknown API
>> command: listVmwareDcs This is not a deal breaker but why is our UI calling a
>> non-implemented API ? This sounds like introducing known issues. If it's not
>> implemented yet, remove it.

> [Edison] The command is only available in non-oss build, but is still listed 
> in command.properties, as there is no separate file for commands non-oss 
> build.

There is no way for UI to tell it's oss build or non-oss build.
However, I just checked in an UI enhancement to skip calling listVmwareDcs API 
if a zone doesn't have any VMware cluster(s).

Jessica


-Original Message-
From: Edison Su [mailto:edison...@citrix.com] 
Sent: Thursday, September 05, 2013 1:38 PM
To: dev@cloudstack.apache.org; Animesh Chaturvedi
Subject: RE: Questions about 4.2 RC



> -Original Message-
> From: sebgoa [mailto:run...@gmail.com]
> Sent: Thursday, September 05, 2013 1:22 AM
> To: dev@cloudstack.apache.org; Animesh Chaturvedi
> Subject: Questions about 4.2 RC
> 
> Hi,
> 
> I followed the testing procedure for the 4.2 RC, I am ready to vote +1 but I
> have questions (hence the new thread, don't want to hijack the VOTE).
> 
> 1. the CHANGES file points to the release notes, but where are the release
> notes ? I know that no-one really stepped up on the RN but can't we at a
> minimum do a JIRA query that lists the bugs fixed in 4.2 and the new
> features ?
> 
> 2. Under infrastructure when I view the DevCloud Zone, I get this in the log:
> WARN  [cloud.api.ApiServer] (642225853@qtp-111037821-10:) Unknown API
> command: listVmwareDcs This is not a deal breaker but why is our UI calling a
> non-implemented API ? This sounds like introducing known issues. If it's not
> implemented yet, remove it.

The command is only available in non-oss build, but is still listed in 
command.properties, as there is no separate file for commands non-oss build.

> 
> 3. Under instances, the new tooltip shows a 'vm snapshot' icon. When you
> use it, it snapshots but the snapshot is not shown under storage>view
> snapshots ? Instead you see the snapshot under the instance view.
> Proceeding to destroy the instance will destroy the snapshot, or at a
> minimum we don't have access to it via the UI. It seems to be the difference
> between listVMSnapshot and listSnapshots.

It's by design, the vm snapshot is listed under vm->vm snapshot view, while the 
volume snapshot listed under storage->snapshot view.

> 
> 
> -Sebastien

RE: Questions about 4.2 RC - listVmwareDcs API - Here's the discovery API

[Jessica Wang]

Chip,

I just tested listApis and it worked!  ^_^

Yes, this is enough and I'll change UI to use listApis to determine whether to 
call listVmwareDcs API in zone detail page.

Thanks!

Jessica

-Original Message-
From: Chip Childers [mailto:chip.child...@sungard.com] 
Sent: Friday, September 06, 2013 1:49 PM
To: Jessica Wang
Cc: dev@cloudstack.apache.org; Animesh Chaturvedi; Edison Su; run...@gmail.com; 
Sateesh Chodapuneedi
Subject: Re: Questions about 4.2 RC - listVmwareDcs API

On Fri, Sep 06, 2013 at 08:21:38PM +0000, Jessica Wang wrote:
> > [Chip] Perhaps a future enhancement would be to use the discovery service 
> > to figure out what API's are being exposed by the specific management 
> > server, and adjust the UI accordingly.
> 
> [Jessica] +1 
> It will be great if server-side is able to provide this info (what API's are 
> being exposed).
> Then, yes, UI can definitely be adjusted accordingly.

Here's the discovery API ->
http://cloudstack.apache.org/docs/api/apidocs-4.1/root_admin/listApis.html

I think this would be enough for the functionality we're talking about,
right?

RE: Questions about 4.2 RC - listVmwareDcs API - Here's the discovery API

[Jessica Wang]

Chip,

The downside of using listApis to detect whether an API command is being 
exposed is that an error will appear in the log (not on UI) 
 
/client/api?command=listApis&name=listVmwareDcs

{
"listapisresponse": {
"uuidList": [],
"errorcode": 530,
"cserrorcode": ,
"errortext": "Api Discovery plugin was unable to find an api by that 
name or process any apis"
    }
}


Jessica


-Original Message-
From: Jessica Wang 
Sent: Friday, September 06, 2013 1:58 PM
To: 'Chip Childers'
Cc: dev@cloudstack.apache.org; Animesh Chaturvedi; Edison Su; run...@gmail.com; 
Sateesh Chodapuneedi
Subject: RE: Questions about 4.2 RC - listVmwareDcs API - Here's the discovery 
API

Chip,

I just tested listApis and it worked!  ^_^

Yes, this is enough and I'll change UI to use listApis to determine whether to 
call listVmwareDcs API in zone detail page.

Thanks!

Jessica

-Original Message-
From: Chip Childers [mailto:chip.child...@sungard.com] 
Sent: Friday, September 06, 2013 1:49 PM
To: Jessica Wang
Cc: dev@cloudstack.apache.org; Animesh Chaturvedi; Edison Su; run...@gmail.com; 
Sateesh Chodapuneedi
Subject: Re: Questions about 4.2 RC - listVmwareDcs API

On Fri, Sep 06, 2013 at 08:21:38PM +, Jessica Wang wrote:
> > [Chip] Perhaps a future enhancement would be to use the discovery service 
> > to figure out what API's are being exposed by the specific management 
> > server, and adjust the UI accordingly.
> 
> [Jessica] +1 
> It will be great if server-side is able to provide this info (what API's are 
> being exposed).
> Then, yes, UI can definitely be adjusted accordingly.

Here's the discovery API ->
http://cloudstack.apache.org/docs/api/apidocs-4.1/root_admin/listApis.html

I think this would be enough for the functionality we're talking about,
right?

RE: Questions about 4.2 RC - listVmwareDcs API

[Jessica Wang]

> [Chip] Perhaps a future enhancement would be to use the discovery service to 
> figure out what API's are being exposed by the specific management server, 
> and adjust the UI accordingly.

[Jessica] +1 
It will be great if server-side is able to provide this info (what API's are 
being exposed).
Then, yes, UI can definitely be adjusted accordingly.


-Original Message-
From: Chip Childers [mailto:chip.child...@sungard.com] 
Sent: Friday, September 06, 2013 12:33 PM
To: Jessica Wang
Cc: dev@cloudstack.apache.org; Animesh Chaturvedi; Edison Su; run...@gmail.com; 
Sateesh Chodapuneedi
Subject: Re: Questions about 4.2 RC - listVmwareDcs API

On Fri, Sep 06, 2013 at 06:30:52PM +, Jessica Wang wrote:
> > This API is called by UI to implement toggle effect for icon "Add/Remove 
> > VMware Datacenter".
> 
> [Jesisca] No, listVmwareDcs API was called by UI to get VMware DataCenter 
> info to display in zone detail page (which has 3 fields: "VMware dataCenter 
> Name", "VMware dataCenter vcenter", "VMware dataCenter Id"), NOT to toggle 
> effect for icon "Add/Remove VMware Datacenter".
> 
> 
> > [Chip] Shouldn't we consider making the UI respond appropriately to a 
> > missing API 
> > (i.e.: don't show that feature if the API response to that call is an error 
> > saying that the API call doesn't exist)?
> 
> [Jessica] There is no way for UI to know whether an API command is missing or 
> not before calling it.
> After calling an API command, if API returns error "Unknown API command", UI 
> will suppress the error message (i.e. UI will not pop up a dialog showing 
> "Unknown API command"). 
> The error "Unknown API command" was seen in the log, NOT on UI. 
> However, I just checked in an UI enhancement to skip calling listVmwareDcs 
> API if a zone doesn't have any VMware cluster(s).

Sounds like a good workaround.

Perhaps a future enhancement would be to use the discovery service to
figure out what API's are being exposed by the specific management
server, and adjust the UI accordingly.

-chip

questions about registerIso API and updateIsoPermissions API

[Jessica Wang]

Hi,

I have questions about registerIso API and updateIsoPermissions API.

(1) A normal user is allowed to specify isextractable property when registering 
an ISO (through registerIso API),
but NOT allowed to update isextractable property when updating an ISO (through 
updateIsoPermissions API).
Is this by design or it's just an API bug?

(2) A normal user is NOT allowed to specify isfeatured property when 
registering an ISO (through registerIso API),
but allowed to update isfeatured property when updating an ISO (through 
updateIsoPermissions API)?
Is this by design or it's just an API bug?

Jessica

RE: questions about registerIso API and updateIsoPermissions API

[Jessica Wang]

Alena,

> Jessica, did you mean updateIso? As updateIsoPermissions updates permissions 
> only. 
Alena, I meant UpdateIsoPermissions API, not updateIso API.
If you check Java file, it's UpdateIsoPermissionsCmd.java that extends 
BaseUpdateTemplateOrIsoPermissionsCmd.java which takes in isextractable 
parameter.

> Answering  your question - if user can specify the flag when registering the 
> template, he should be allowed to update it.
Thanks.

> Again, should be updateIso.
should be updateIsoPermissions

> its a bug if he can update the flag on existing object, but can't create the 
> object with this flag by default.
Thanks

Jessica

-Original Message-
From: Alena Prokharchyk 
Sent: Tuesday, October 08, 2013 5:21 PM
To: Jessica Wang; 
Cc: Nitin Mehta; Shweta Agarwal
Subject: Re: questions about registerIso API and updateIsoPermissions API

On 10/8/13 5:10 PM, "Jessica Wang"  wrote:

>Hi,
> 
>I have questions about registerIso API and updateIsoPermissions API.
> 
>(1) A normal user is allowed to specify isextractable property when
>registering an ISO (through registerIso API),
>
>but NOT allowed to update isextractable property when updating an ISO
>(through updateIsoPermissions API).
>Is this by design or it's just an API bug?

Jessica, did you mean updateIso? As UpdateIsoPermissions updates
permissions only. 
Answering  your question - if user can specify the flag when registering
the template, he should be allowed to update it.



> 
>(2) A normal user is NOT allowed to specify isfeatured property when
>registering an ISO (through registerIso API),
>
>but allowed to update isfeatured property when updating an ISO (through
>updateIsoPermissions API)?
>Is this by design or it's just an API bug?

Again, should be updateIso. And yes, its a bug if he can update the flag
on existing object, but can't create the object with this flag by default.


> 
>Jessica
>
>

RE: questions about registerIso API and updateIsoPermissions API

[Jessica Wang]

Nitin,

>  At the moment, I think that for Isos we should allow to edit it so would 
> call it an API bug.
Thanks.

> Register Iso does provide an option to mark an ISO featured. I see that in 
> the latest master.
That only works for admin, but NOT normal user.

If you log in as a normal user, then pass "isfeatured=true" to registerIso API, 
API will ignore it.
The newly registered template will have "isfeatured: false".

e.g.
http://10.215.3.26:8080/client/api?command=registerIso&response=json&sessionkey=u%2FVIHPJuPohidGKFd0lh6csG%2BfM%3D&name=normalUserIso1&displayText=normalUserIso1&url=http%3A%2F%2F10.223.110.231%2Fisos_64bit%2Fdummy.iso&zoneid=6bcd3bd9-591c-4d99-a164-d05b87df1b04&isfeatured=true&isextractable=false&bootable=true&osTypeId=b8cbfd6c-2d40-11e3-86aa-3c970e739c3e&ispublic=false&_=1381340961641
{
"registerisoresponse": {
"count": 1,
"iso": [
{
"id": "9b903876-f17c-4634-8463-8e3025259956",
"name": "normalUserIso1",
"displaytext": "normalUserIso1",
"ispublic": false,
"created": "2013-10-09T10:52:38-0700",
"isready": false,
"bootable": true,
"isfeatured": false,
"crossZones": false,
"ostypeid": "b8cbfd6c-2d40-11e3-86aa-3c970e739c3e",
"ostypename": "Apple Mac OS X 10.6 (32-bit)",
"account": "aaa_user",
"zoneid": "6bcd3bd9-591c-4d99-a164-d05b87df1b04",
"zonename": "jw-adv",
"status": "",
"domain": "aaa",
    "domainid": "47b09d73-84ef-48dc-9b73-1720bad600cb",
"isextractable": false,
"tags": []
}
]
}
}

Jessica

From: Nitin Mehta
Sent: Tuesday, October 08, 2013 5:27 PM
To: Jessica Wang; 
Cc: Alena Prokharchyk; Shweta Agarwal
Subject: Re: questions about registerIso API and updateIsoPermissions API

Answers inline.

From: Jessica Wang mailto:jessica.w...@citrix.com>>
Date: Tuesday 8 October 2013 5:10 PM
To: "mailto:dev@cloudstack.apache.org>>" 
mailto:dev@cloudstack.apache.org>>
Cc: Alena Prokharchyk 
mailto:alena.prokharc...@citrix.com>>, Nitin 
Mehta mailto:nitin.me...@citrix.com>>, Shweta Agarwal 
mailto:shweta.agar...@citrix.com>>
Subject: questions about registerIso API and updateIsoPermissions API

Hi,

I have questions about registerIso API and updateIsoPermissions API.

(1) A normal user is allowed to specify isextractable property when registering 
an ISO (through registerIso API),
but NOT allowed to update isextractable property when updating an ISO (through 
updateIsoPermissions API).
Is this by design or it's just an API bug?

Nitin>> This is a grey area. This was done for templates (Isos just inherited 
it) because derived templates may or may not belong to the same user and we 
want to follow the principle of least privilege.
At the moment, I think that for Isos we should allow to edit it so would call 
it an API bug.

(2) A normal user is NOT allowed to specify isfeatured property when 
registering an ISO (through registerIso API),
but allowed to update isfeatured property when updating an ISO (through 
updateIsoPermissions API)?
Is this by design or it's just an API bug?

Nitin>> Register Iso does provide an option to mark an ISO featured. I see that 
in the latest master.

Jessica

RE: questions about registerIso API and updateIsoPermissions API

[Jessica Wang]

Currently, at API level, a normal user is not allowed to specify "isfeatured" 
when registering ISO (API will ignore "isfeatured" parameter when a normal user 
passes it),
but a normal user is allowed to specify "isfeatured" when updating ISO.

Should we fix API to:
(1) allow a normal user to specify "isfeatured" when registering ISO (API won't 
ignore "isfeatured" parameter when a normal user passes it)

OR

(2) disallow a normal user to specify "isfeatured" when updating ISO

?


p.s. I'll do corresponding UI change after API is fixed.


From: Jessica Wang
Sent: Wednesday, October 09, 2013 11:01 AM
To: Nitin Mehta; 
Cc: Alena Prokharchyk; Shweta Agarwal
Subject: RE: questions about registerIso API and updateIsoPermissions API

Nitin,

>  At the moment, I think that for Isos we should allow to edit it so would 
> call it an API bug.
Thanks.

> Register Iso does provide an option to mark an ISO featured. I see that in 
> the latest master.
That only works for admin, but NOT normal user.

If you log in as a normal user, then pass "isfeatured=true" to registerIso API, 
API will ignore it.
The newly registered template will have "isfeatured: false".

e.g.
http://10.215.3.26:8080/client/api?command=registerIso&response=json&sessionkey=u%2FVIHPJuPohidGKFd0lh6csG%2BfM%3D&name=normalUserIso1&displayText=normalUserIso1&url=http%3A%2F%2F10.223.110.231%2Fisos_64bit%2Fdummy.iso&zoneid=6bcd3bd9-591c-4d99-a164-d05b87df1b04&isfeatured=true&isextractable=false&bootable=true&osTypeId=b8cbfd6c-2d40-11e3-86aa-3c970e739c3e&ispublic=false&_=1381340961641
{
"registerisoresponse": {
"count": 1,
"iso": [
{
"id": "9b903876-f17c-4634-8463-8e3025259956",
"name": "normalUserIso1",
"displaytext": "normalUserIso1",
"ispublic": false,
"created": "2013-10-09T10:52:38-0700",
"isready": false,
"bootable": true,
"isfeatured": false,
"crossZones": false,
"ostypeid": "b8cbfd6c-2d40-11e3-86aa-3c970e739c3e",
"ostypename": "Apple Mac OS X 10.6 (32-bit)",
"account": "aaa_user",
"zoneid": "6bcd3bd9-591c-4d99-a164-d05b87df1b04",
"zonename": "jw-adv",
"status": "",
    "domain": "aaa",
"domainid": "47b09d73-84ef-48dc-9b73-1720bad600cb",
"isextractable": false,
"tags": []
}
]
}
}

Jessica

From: Nitin Mehta
Sent: Tuesday, October 08, 2013 5:27 PM
To: Jessica Wang; 
Cc: Alena Prokharchyk; Shweta Agarwal
Subject: Re: questions about registerIso API and updateIsoPermissions API

Answers inline.

From: Jessica Wang mailto:jessica.w...@citrix.com>>
Date: Tuesday 8 October 2013 5:10 PM
To: "mailto:dev@cloudstack.apache.org>>" 
mailto:dev@cloudstack.apache.org>>
Cc: Alena Prokharchyk 
mailto:alena.prokharc...@citrix.com>>, Nitin 
Mehta mailto:nitin.me...@citrix.com>>, Shweta Agarwal 
mailto:shweta.agar...@citrix.com>>
Subject: questions about registerIso API and updateIsoPermissions API

Hi,

I have questions about registerIso API and updateIsoPermissions API.

(1) A normal user is allowed to specify isextractable property when registering 
an ISO (through registerIso API),
but NOT allowed to update isextractable property when updating an ISO (through 
updateIsoPermissions API).
Is this by design or it's just an API bug?

Nitin>> This is a grey area. This was done for templates (Isos just inherited 
it) because derived templates may or may not belong to the same user and we 
want to follow the principle of least privilege.
At the moment, I think that for Isos we should allow to edit it so would call 
it an API bug.

(2) A normal user is NOT allowed to specify isfeatured property when 
registering an ISO (through registerIso API),
but allowed to update isfeatured property when updating an ISO (through 
updateIsoPermissions API)?
Is this by design or it's just an API bug?

Nitin>> Register Iso does provide an option to mark an ISO featured. I see that 
in the latest master.

Jessica

RE: questions about registerIso API and updateIsoPermissions API

[Jessica Wang]

Thanks, Nitin.

I just filed an API bug for this:
https://issues.apache.org/jira/i#browse/CLOUDSTACK-4843


From: Nitin Mehta
Sent: Wednesday, October 09, 2013 2:08 PM
To: Jessica Wang; ; Alena Prokharchyk
Cc: Shweta Agarwal
Subject: Re: questions about registerIso API and updateIsoPermissions API

I think (1) is the right way to go.

From: Jessica Wang mailto:jessica.w...@citrix.com>>
Date: Wednesday 9 October 2013 12:47 PM
To: Nitin Mehta mailto:nitin.me...@citrix.com>>, 
"mailto:dev@cloudstack.apache.org>>" 
mailto:dev@cloudstack.apache.org>>, Alena 
Prokharchyk mailto:alena.prokharc...@citrix.com>>
Cc: Shweta Agarwal mailto:shweta.agar...@citrix.com>>
Subject: RE: questions about registerIso API and updateIsoPermissions API

Currently, at API level, a normal user is not allowed to specify "isfeatured" 
when registering ISO (API will ignore "isfeatured" parameter when a normal user 
passes it),
but a normal user is allowed to specify "isfeatured" when updating ISO.

Should we fix API to:
(1) allow a normal user to specify "isfeatured" when registering ISO (API won't 
ignore "isfeatured" parameter when a normal user passes it)

OR

(2) disallow a normal user to specify "isfeatured" when updating ISO

?


p.s. I'll do corresponding UI change after API is fixed.


From: Jessica Wang
Sent: Wednesday, October 09, 2013 11:01 AM
To: Nitin Mehta; mailto:dev@cloudstack.apache.org>>
Cc: Alena Prokharchyk; Shweta Agarwal
Subject: RE: questions about registerIso API and updateIsoPermissions API

Nitin,

>  At the moment, I think that for Isos we should allow to edit it so would 
> call it an API bug.
Thanks.

> Register Iso does provide an option to mark an ISO featured. I see that in 
> the latest master.
That only works for admin, but NOT normal user.

If you log in as a normal user, then pass "isfeatured=true" to registerIso API, 
API will ignore it.
The newly registered template will have "isfeatured: false".

e.g.
http://10.215.3.26:8080/client/api?command=registerIso&response=json&sessionkey=u%2FVIHPJuPohidGKFd0lh6csG%2BfM%3D&name=normalUserIso1&displayText=normalUserIso1&url=http%3A%2F%2F10.223.110.231%2Fisos_64bit%2Fdummy.iso&zoneid=6bcd3bd9-591c-4d99-a164-d05b87df1b04&isfeatured=true&isextractable=false&bootable=true&osTypeId=b8cbfd6c-2d40-11e3-86aa-3c970e739c3e&ispublic=false&_=1381340961641
{
"registerisoresponse": {
"count": 1,
"iso": [
{
"id": "9b903876-f17c-4634-8463-8e3025259956",
"name": "normalUserIso1",
"displaytext": "normalUserIso1",
"ispublic": false,
"created": "2013-10-09T10:52:38-0700",
"isready": false,
"bootable": true,
"isfeatured": false,
"crossZones": false,
"ostypeid": "b8cbfd6c-2d40-11e3-86aa-3c970e739c3e",
"ostypename": "Apple Mac OS X 10.6 (32-bit)",
"account": "aaa_user",
"zoneid": "6bcd3bd9-591c-4d99-a164-d05b87df1b04",
"zonename": "jw-adv",
"status": "",
"domain": "aaa",
"domainid": "47b09d73-84ef-48dc-9b73-1720bad600cb",
"isextractable": false,
"tags": []
}
]
}
}

Jessica

From: Nitin Mehta
Sent: Tuesday, October 08, 2013 5:27 PM
To: Jessica Wang; mailto:dev@cloudstack.apache.org>>
Cc: Alena Prokharchyk; Shweta Agarwal
Subject: Re: questions about registerIso API and updateIsoPermissions API

Answers inline.

From: Jessica Wang mailto:jessica.w...@citrix.com>>
Date: Tuesday 8 October 2013 5:10 PM
To: "mailto:dev@cloudstack.apache.org>>" 
mailto:dev@cloudstack.apache.org>>
Cc: Alena Prokharchyk 
mailto:alena.prokharc...@citrix.com>>, Nitin 
Mehta mailto:nitin.me...@citrix.com>>, Shweta Agarwal 
mailto:shweta.agar...@citrix.com>>
Subject: questions about registerIso API and updateIsoPermissions API

Hi,

I have questions about registerIso API and updateIsoPermissions API.

(1) A normal user is allowed to specify isextractable property when registering 
an ISO (through registerIso API),
but NOT allowed to update isextractable property when updating an ISO (through 
updateIsoPermissions API).
Is this by design or it's just an API bug?

Nitin>> This is a grey area. This was done for templates (Isos just inherited 
it) because derived templates may or may not belong to the same user and we 
want to follow the principle of least privilege.
At the moment, I think that for Isos we should allow to edit it so would call 
it an API bug.

(2) A normal user is NOT allowed to specify isfeatured property when 
registering an ISO (through registerIso API),
but allowed to update isfeatured property when updating an ISO (through 
updateIsoPermissions API)?
Is this by design or it's just an API bug?

Nitin>> Register Iso does provide an option to mark an ISO featured. I see that 
in the latest master.

Jessica

RE: UI accounts wizard broken

[Jessica Wang]

+1

-Original Message-
From: Brian Federle 
Sent: Thursday, October 10, 2013 12:55 PM
To: dev@cloudstack.apache.org
Cc: Animesh Chaturvedi; Jessica Wang; Sonny Chhen
Subject: RE: UI accounts wizard broken

Also, I am referring to this commit. I do not remember any active UI comitters 
including myself receiving a review request for this...

commit eaa41433715ba1a1137ad9f346ea8569e31e4560
Author: Ian Duffy 
Date:   Thu Jul 25 10:24:13 2013 +0100

Merge LDAPPlugin

Signed-off-by: Abhinandan Prateek 

-Original Message-
From: Brian Federle [mailto:brian.fede...@citrix.com] 
Sent: Thursday, October 10, 2013 12:46 PM
To: dev@cloudstack.apache.org
Cc: Animesh Chaturvedi; Jessica Wang; Sonny Chhen
Subject: UI accounts wizard broken

After reviewing the UI on the latest master, I noticed that the 'add account' 
dialog was changed substantially, and converted to a custom UI widget. 
Additionally, the password confirm field validation is broken, so I am unable 
to add a new account.

Can I know the reason this was converted to a custom widget, instead of using 
the standard createForm? This doesn't seem to really need something custom from 
the looks of it. I am mainly concerned since it is causing validation bugs as 
well as some display glitches, which could be avoided by using the standard 
widget toolkit.

Thanks,
Brian

RE: git commit: updated refs/heads/master to a59067e

[Jessica Wang]

Wei,

Because Network tab is for normal user and normal user is not allowed to add 
shared network.

Only root-admin is allowed to add shared network and root-admin should do it in 
Infrastructure tab. 
(Infrastructure tab is only available to root-admin)

Jessica

-Original Message-
From: Wei ZHOU [mailto:ustcweiz...@gmail.com] 
Sent: Tuesday, June 11, 2013 6:59 AM
To: dev@cloudstack.apache.org
Subject: Re: git commit: updated refs/heads/master to a59067e

Hi Jessica,

I was wondering why shared network can not be added here?

-Wei


2013/6/10 

> Updated Branches:
>   refs/heads/master 40982ccef -> a59067e94
>
>
> CLOUDSTACK UI - network menu - create guest network dialog - change label.
>
>
> Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo
> Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/a59067e9
> Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/a59067e9
> Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/a59067e9
>
> Branch: refs/heads/master
> Commit: a59067e94f7095a2448d342d5eed0ffee5f066c0
> Parents: 40982cc
> Author: Jessica Wang 
> Authored: Mon Jun 10 13:43:07 2013 -0700
> Committer: Jessica Wang 
> Committed: Mon Jun 10 13:43:07 2013 -0700
>
> --
>  ui/scripts/network.js | 7 +++
>  1 file changed, 3 insertions(+), 4 deletions(-)
> --
>
>
>
> http://git-wip-us.apache.org/repos/asf/cloudstack/blob/a59067e9/ui/scripts/network.js
> --
> diff --git a/ui/scripts/network.js b/ui/scripts/network.js
> index 9e60cbc..61468fc 100755
> --- a/ui/scripts/network.js
> +++ b/ui/scripts/network.js
> @@ -320,8 +320,8 @@
>  title: 'label.guest.networks',
>  listView: {
>actions: {
> -add: { //add Isolated guest network (can't add Shared guest
> network here)
> -  label: 'Add Isolated Guest Network',
> +add: {
> +  label: 'Add Isolated Guest Network with SourceNat',
>
>preFilter: function(args) { //Isolated networks is only
> supported in Advanced (SG-disabled) zone
>  if(args.context.zoneType != 'Basic')
> @@ -331,8 +331,7 @@
>},
>
>createForm: {
> -title: 'Add Isolated Guest Network',
> -desc: 'Add Isolated Guest Network with SourceNat',
> +title: 'Add Isolated Guest Network with SourceNat',
>  fields: {
>name: { label: 'label.name', validation: { required:
> true }, docID: 'helpGuestNetworkName' },
>displayText: { label: 'label.display.text', validation:
> { required: true }, docID: 'helpGuestNetworkDisplayText'},
>
>

cloudstack UI: add shared network

[Jessica Wang]

Wei,

> What do you think about show/hide the button according to account/user on 
> Network tab?
Network tab is for normal user.
We put everything that only root-admin is allowed to access in Infrastructure 
tab. This is by design. We probably won't change it.

> I can not find a page to add shared networks in Infracstruture tab.
Please go to Infrastructure tab > Zones > Physical Network tab > Guest > 
Network tab => "Add guest network" button

Jessica


From: Wei ZHOU [mailto:ustcweiz...@gmail.com]
Sent: Tuesday, June 11, 2013 10:57 AM
To: Jessica Wang
Subject: Re: git commit: updated refs/heads/master to a59067e

Jessica,

What do you think about show/hide the button according to account/user on 
Network tab?
I am now testing advanced zone with security groups. I can not find a page to 
add shared networks in Infracstruture tab.

-Wei

2013/6/11 Jessica Wang mailto:jessica.w...@citrix.com>>
Wei,

Because Network tab is for normal user and normal user is not allowed to add 
shared network.

Only root-admin is allowed to add shared network and root-admin should do it in 
Infrastructure tab.
(Infrastructure tab is only available to root-admin)

Jessica

-Original Message-
From: Wei ZHOU [mailto:ustcweiz...@gmail.com<mailto:ustcweiz...@gmail.com>]
Sent: Tuesday, June 11, 2013 6:59 AM
To: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>
Subject: Re: git commit: updated refs/heads/master to a59067e

Hi Jessica,

I was wondering why shared network can not be added here?

-Wei


2013/6/10 mailto:jessicaw...@apache.org>>

> Updated Branches:
>   refs/heads/master 40982ccef -> a59067e94
>
>
> CLOUDSTACK UI - network menu - create guest network dialog - change label.
>
>
> Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo
> Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/a59067e9
> Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/a59067e9
> Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/a59067e9
>
> Branch: refs/heads/master
> Commit: a59067e94f7095a2448d342d5eed0ffee5f066c0
> Parents: 40982cc
> Author: Jessica Wang mailto:jessicaw...@apache.org>>
> Authored: Mon Jun 10 13:43:07 2013 -0700
> Committer: Jessica Wang 
> mailto:jessicaw...@apache.org>>
> Committed: Mon Jun 10 13:43:07 2013 -0700
>
> --
>  ui/scripts/network.js | 7 +++
>  1 file changed, 3 insertions(+), 4 deletions(-)
> --
>
>
>
> http://git-wip-us.apache.org/repos/asf/cloudstack/blob/a59067e9/ui/scripts/network.js
> --
> diff --git a/ui/scripts/network.js b/ui/scripts/network.js
> index 9e60cbc..61468fc 100755
> --- a/ui/scripts/network.js
> +++ b/ui/scripts/network.js
> @@ -320,8 +320,8 @@
>  title: 'label.guest.networks',
>  listView: {
>actions: {
> -add: { //add Isolated guest network (can't add Shared guest
> network here)
> -  label: 'Add Isolated Guest Network',
> +add: {
> +  label: 'Add Isolated Guest Network with SourceNat',
>
>preFilter: function(args) { //Isolated networks is only
> supported in Advanced (SG-disabled) zone
>  if(args.context.zoneType != 'Basic')
> @@ -331,8 +331,7 @@
>},
>
>createForm: {
> -title: 'Add Isolated Guest Network',
> -desc: 'Add Isolated Guest Network with SourceNat',
> +title: 'Add Isolated Guest Network with SourceNat',
>  fields: {
>name: { label: 'label.name<http://label.name>', 
> validation: { required:
> true }, docID: 'helpGuestNetworkName' },
>displayText: { label: 'label.display.text', validation:
> { required: true }, docID: 'helpGuestNetworkDisplayText'},
>
>

RE: if anybody know how to restrict access to a specific zone

[Jessica Wang]

> I want to give access to a user to see only a specific zone.

What is the role of the user that you want to give access to see only a 
specific zone?
A normal-user, a domain-admin, or a root-admin?


-Original Message-
From: William Jiang [mailto:william.ji...@manwin.com] 
Sent: Tuesday, June 11, 2013 3:17 PM
To: dev@cloudstack.apache.org; users...@cloudstack.apache.org; 
us...@cloudstack.apache.org
Subject: if anybody know how to restrict access to a specific zone

Hi,

if anybody know how to restrict access to a specific zone? We have multiple 
zone in our cloudstack 3.0 and I want to give access to a user to see only a 
specific zone.

Thanks,
William
This e-mail may be privileged and/or confidential, and the sender does not 
waive any related rights and obligations. Any distribution, use or copying of 
this e-mail or the information it contains by other than an intended recipient 
is unauthorized. If you received this e-mail in error, please advise me (by 
return e-mail or otherwise) immediately. Ce courrier ?lectronique est 
confidentiel et prot?g?. L'exp?diteur ne renonce pas aux droits et obligations 
qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des 
renseignements qu'il contient par une personne autre que le (les) 
destinataire(s) d?sign?(s) est interdite. Si vous recevez ce courrier 
?lectronique par erreur, veuillez m'en aviser imm?diatement, par retour de 
courrier ?lectronique ou par un autre moyen.

RE: Git Push Summary

[Jessica Wang]

Chip,

> all my fixes that I've put to this branch, were originally committed to 
> master.
Me, too.

Jessica

-Original Message-
From: Alena Prokharchyk 
Sent: Tuesday, June 18, 2013 12:32 PM
To: Chip Childers; dev@cloudstack.apache.org
Cc: Jessica Wang; Min Chen
Subject: Re: Git Push Summary

Chip, all my fixes that I've put to this branch, were originally committed
to master. I cherry-picked them to the master-6-17-stable.


commit 5d0a1cee13fb3006f3e35cd221e553587ea20ce2
Author: Alena Prokharchyk 
Date:   Mon Jun 17 16:10:12 2013 -0700

CLOUDSTACK-2883: create default network offering with internal lb
support (if doesn't exist already)

commit 952fa2464da9f10b63fbba869922ee735c231c42
Author: Alena Prokharchyk 
Date:   Mon Jun 17 10:50:22 2013 -0700

LOUDSTACK-2914: handle situation when serviceProvider map is empty

commit fc16e29f992d81156a4e08a77da215f8276f4efe
Author: Alena Prokharchyk 
Date:   Mon Jun 17 10:09:52 2013 -0700

CLOUDSTACK-2914: default lb scheme to Public when the service LB is
enabled, and scheme is not specified explicitly



-Alena.


On 6/18/13 11:59 AM, "Chip Childers"  wrote:

>Min, Jessica, Alena,
>
>What's going on in this branch?
>
>The commits are curious.  Are these fixes going into master?
>
>On Mon, Jun 17, 2013 at 07:37:52PM +, Chiradeep Vittal wrote:
>> David, this is a temporary scratch branch to perform some integration
>> testing since atm the master looks stable.
>> 
>> On 6/17/13 11:57 AM, "David Nalley"  wrote:
>> 
>> >What is this branch for?
>> >On Jun 17, 2013 1:27 PM,  wrote:
>> >
>> >> Updated Branches:
>> >>   refs/heads/master-6-17-stable [created] fc16e29f9
>> >>
>> 
>> 
>

RE: NFS Cache storage query

[Jessica Wang]

Min,

> We may need to provide a way from UI to allow users to configure and display 
> their NFS cache.
Is there an API that list NFS cache?

Jessica

-Original Message-
From: Min Chen 
Sent: Friday, June 14, 2013 9:26 AM
To: dev@cloudstack.apache.org
Cc: Jessica Wang
Subject: Re: NFS Cache storage query

Hi Sanjeev,

In 4.2 release, we require that a NFS cache storage has to be added if
you choose S3 as the storage provider since we haven't refactored
hypervisor side code to handle s3 directly by bypassing NFS caching, which
is the goal for 4.3 release. I see an issue with current UI, where user
can only add cache storage when he/she adds a S3 storage. We may need to
provide a way from UI to allow users to configure and display their NFS
cache. You can file a JIRA ticket for this UI enhancement.

Thanks
-min

On 6/14/13 6:35 AM, "Chip Childers"  wrote:

>On Fri, Jun 14, 2013 at 01:06:30PM +, Sanjeev Neelarapu wrote:
>> Hi,
>> 
>> I have a query on how to add NFS Cache storage.
>> Before creating a zone if we create a secondary storage with s3 as the
>>storage provider and don't select NFS Cache Storage then we treat it as
>>S3 at region level.
>> Later I create a zone and at "add secondary storage" creation wizard in
>>UI if I select NFS as secondary storage provider will it be treated as
>>NFS Cache Storage? If not is there a way to add NFS cache storage for
>>that zone?
>> 
>> Thanks,
>> Sanjeev
>>
>
>Based on the thread talking about this [1], I'm not sure that it will be
>implemented this way anymore.
>
>-chip
>
>[1] http://markmail.org/message/c73nagj45q6iktfh

RE: NFS Cache storage query

[Jessica Wang]

Min, Edison,

Either way is fine with me.

Jessica

-Original Message-
From: Min Chen [mailto:min.c...@citrix.com] 
Sent: Tuesday, June 18, 2013 6:07 PM
To: Edison Su; dev@cloudstack.apache.org
Subject: Re: NFS Cache storage query

Edison, we can just add a parameter in listImageStoreCmd to show cache
store.

Thanks
-min

On 6/18/13 6:06 PM, "Edison Su"  wrote:

>Currently, no, I can add an API for it.
>
>> -Original Message-
>> From: Jessica Wang [mailto:jessica.w...@citrix.com]
>> Sent: Tuesday, June 18, 2013 4:24 PM
>> To: Min Chen
>> Cc: dev@cloudstack.apache.org
>> Subject: RE: NFS Cache storage query
>> 
>> Min,
>> 
>> > We may need to provide a way from UI to allow users to configure and
>> display their NFS cache.
>> Is there an API that list NFS cache?
>> 
>> Jessica
>> 
>> -Original Message-
>> From: Min Chen
>> Sent: Friday, June 14, 2013 9:26 AM
>> To: dev@cloudstack.apache.org
>> Cc: Jessica Wang
>> Subject: Re: NFS Cache storage query
>> 
>> Hi Sanjeev,
>> 
>>  In 4.2 release, we require that a NFS cache storage has to be added if
>> you choose S3 as the storage provider since we haven't refactored
>> hypervisor side code to handle s3 directly by bypassing NFS caching,
>>which is
>> the goal for 4.3 release. I see an issue with current UI, where user
>>can only
>> add cache storage when he/she adds a S3 storage. We may need to provide
>> a way from UI to allow users to configure and display their NFS cache.
>>You
>> can file a JIRA ticket for this UI enhancement.
>> 
>>  Thanks
>>  -min
>> 
>> On 6/14/13 6:35 AM, "Chip Childers"  wrote:
>> 
>> >On Fri, Jun 14, 2013 at 01:06:30PM +, Sanjeev Neelarapu wrote:
>> >> Hi,
>> >>
>> >> I have a query on how to add NFS Cache storage.
>> >> Before creating a zone if we create a secondary storage with s3 as
>> >>the storage provider and don't select NFS Cache Storage then we treat
>> >>it as
>> >>S3 at region level.
>> >> Later I create a zone and at "add secondary storage" creation wizard
>> >>in UI if I select NFS as secondary storage provider will it be treated
>> >>as NFS Cache Storage? If not is there a way to add NFS cache storage
>> >>for that zone?
>> >>
>> >> Thanks,
>> >> Sanjeev
>> >>
>> >
>> >Based on the thread talking about this [1], I'm not sure that it will
>> >be implemented this way anymore.
>> >
>> >-chip
>> >
>> >[1] http://markmail.org/message/c73nagj45q6iktfh
>

RE: NFS Cache storage query - an UI change where you can create a NFS Cache Storage independently

[Jessica Wang]

Sanjeev,

I've made an UI change where you can create a NFS Cache Storage independently.

After getting latest code from master branch, you'll see a new dropdown "Select 
view" in Infrastructure menu > Secondary Storage.

Change "Select view" to "Cache Storage", then you'll see "Add NFS Cache 
Storage" button on right top corner.

Jessica

-Original Message-
From: Sanjeev Neelarapu [mailto:sanjeev.neelar...@citrix.com] 
Sent: Friday, June 14, 2013 6:07 AM
To: dev@cloudstack.apache.org
Subject: NFS Cache storage query

Hi,

I have a query on how to add NFS Cache storage.
Before creating a zone if we create a secondary storage with s3 as the storage 
provider and don't select NFS Cache Storage then we treat it as S3 at region 
level.
Later I create a zone and at "add secondary storage" creation wizard in UI if I 
select NFS as secondary storage provider will it be treated as NFS Cache 
Storage? If not is there a way to add NFS cache storage for that zone?

Thanks,
Sanjeev

RE: Query String Request Authentication(QSRA) support by S3 providers

[Jessica Wang]

Thomas,

I've written down my comment in this bug.

Jessica

-Original Message-
From: Thomas O'Dowd [mailto:tpod...@cloudian.com] 
Sent: Thursday, June 27, 2013 8:04 PM
To: Min Chen
Cc: dev@cloudstack.apache.org; Jessica Wang
Subject: Re: Query String Request Authentication(QSRA) support by S3 providers

Hi Min/Jessica,

I attached an image to that issue to show what what my browser is
showing.

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

Tom.

On Fri, 2013-06-28 at 09:45 +0900, Thomas O'Dowd wrote:
> Hi Min,
> 
> Yes. I'll try it again today to check again but when I added Amazon S3
> as the S3 secondary storage and uploaded a template, I was not shown the
> "download template" link. However - for Cloudian S3, I am shown it so
> I'm wondering why.
> 
> Tom.
> 
> On Fri, 2013-06-28 at 00:26 +, Min Chen wrote:
> > Hi Tom,
> > 
> > Are you saying that you cannot see a Download Template button from UI
> > when Amazon S3 is added as secondary storage? I only tested with RiakCS
> > and Cloudian, so didn't see this issue. But I am CC Jessica her to confirm
> > what special handling is done in UI to enable/disable a button from UI.
> > 
> > Thanks
> > -min
> > 
> > On 6/27/13 5:23 PM, "Thomas O'Dowd"  wrote:
> > 
> > >Hi Min,
> > >
> > >Can you check this bug? I'm trying to test this feature for Amazon but
> > >having no luck getting the Download template link/button to appear.
> > >
> > >https://issues.apache.org/jira/browse/CLOUDSTACK-3220
> > >
> > >Thanks,
> > >
> > >Tom.
> > >
> > >On Fri, 2013-06-21 at 17:21 +, Min Chen wrote:
> > >> John,
> > >> 
> > >>  For S3, the api call createEntityExtractUrl is done on management
> > >>server
> > >> side; while for NFS secondary storage, if the implementation of
> > >> createEntityExtractUrl will involve some code be executed in ssvm to
> > >>copy
> > >> template from the install location to a public accessible web server
> > >> location.
> > >>  I don't quite understand some of your comments below. This API is not
> > >> used to write any information to S3 bucket/directory. This is used for
> > >> object already existed on S3, and we just provide a URL for user to
> > >> download a template from S3, just like how Amazon provided user a way to
> > >> user to extract a S3 object through generatePresignedUrl. We can discuss
> > >> more on this on collaboration conference.
> > >> 
> > >>  Thanks  
> > >>  -min
> > >> 
> > >> 
> > >> 
> > >> On 6/21/13 7:25 AM, "John Burwell"  wrote:
> > >> 
> > >> >Min,
> > >> >
> > >> >(I apologize for my belated reply -- I lost track of this draft in the
> > >> >chaos of the last couple of days.)
> > >> >
> > >> >Upon further review, I think I feel into the confusion between
> > >>management
> > >> >server and ssvm.  This code is executing on the management server side,
> > >> >correct?  Based on my "corrected" understanding is correct, I would
> > >>like
> > >> >to amend my thoughts.  Namely, I would like to see the driver
> > >>operations
> > >> >pushed out to the SSVM where we can use the stream.  As I think about
> > >>it,
> > >> >the management server should not need to interact with the driver.
> > >> >Simply yard up the DataStore attributes + details map and other extract
> > >> >parameters, and send them to the SSVM.  Using this information, the S3
> > >> >driver could open a stream to write the template out to the
> > >> >bucket/directory.  I recognize it changes the protocol between the
> > >> >management server and SSVM, but it simply both sides of the operation
> > >>by
> > >> >allowing the DataStore information to be treated opaquely until it is
> > >> >consumed by the driver to execute the write operation.  I also
> > >>recognize
> > >> >that we may a little late in the cycle to address it for 4.2, and it
> > >>may
> > >> >need to be part of the 4.3 enhancements.
> > >> >
> > >> >Thanks,
> > >> >-John
> > >> >
> > >> >On Jun 18, 2013, at 3:55 PM, Min Chen  wrote:

RE: Query String Request Authentication(QSRA) support by S3 providers

[Jessica Wang]

Thomas,

I checked the data you provided.

The reason that the 2 templates("MyTiny", "AnotherTiny") have no download 
button is because they are not ready 
(i.e. their "isready" property is false).

Download button is only available when "isready" property is true.

Jessica

-Original Message-
From: Thomas O'Dowd [mailto:tpod...@cloudian.com] 
Sent: Thursday, June 27, 2013 8:04 PM
To: Min Chen
Cc: dev@cloudstack.apache.org; Jessica Wang
Subject: Re: Query String Request Authentication(QSRA) support by S3 providers

Hi Min/Jessica,

I attached an image to that issue to show what what my browser is
showing.

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

Tom.

On Fri, 2013-06-28 at 09:45 +0900, Thomas O'Dowd wrote:
> Hi Min,
> 
> Yes. I'll try it again today to check again but when I added Amazon S3
> as the S3 secondary storage and uploaded a template, I was not shown the
> "download template" link. However - for Cloudian S3, I am shown it so
> I'm wondering why.
> 
> Tom.
> 
> On Fri, 2013-06-28 at 00:26 +, Min Chen wrote:
> > Hi Tom,
> > 
> > Are you saying that you cannot see a Download Template button from UI
> > when Amazon S3 is added as secondary storage? I only tested with RiakCS
> > and Cloudian, so didn't see this issue. But I am CC Jessica her to confirm
> > what special handling is done in UI to enable/disable a button from UI.
> > 
> > Thanks
> > -min
> > 
> > On 6/27/13 5:23 PM, "Thomas O'Dowd"  wrote:
> > 
> > >Hi Min,
> > >
> > >Can you check this bug? I'm trying to test this feature for Amazon but
> > >having no luck getting the Download template link/button to appear.
> > >
> > >https://issues.apache.org/jira/browse/CLOUDSTACK-3220
> > >
> > >Thanks,
> > >
> > >Tom.
> > >
> > >On Fri, 2013-06-21 at 17:21 +, Min Chen wrote:
> > >> John,
> > >> 
> > >>  For S3, the api call createEntityExtractUrl is done on management
> > >>server
> > >> side; while for NFS secondary storage, if the implementation of
> > >> createEntityExtractUrl will involve some code be executed in ssvm to
> > >>copy
> > >> template from the install location to a public accessible web server
> > >> location.
> > >>  I don't quite understand some of your comments below. This API is not
> > >> used to write any information to S3 bucket/directory. This is used for
> > >> object already existed on S3, and we just provide a URL for user to
> > >> download a template from S3, just like how Amazon provided user a way to
> > >> user to extract a S3 object through generatePresignedUrl. We can discuss
> > >> more on this on collaboration conference.
> > >> 
> > >>  Thanks  
> > >>  -min
> > >> 
> > >> 
> > >> 
> > >> On 6/21/13 7:25 AM, "John Burwell"  wrote:
> > >> 
> > >> >Min,
> > >> >
> > >> >(I apologize for my belated reply -- I lost track of this draft in the
> > >> >chaos of the last couple of days.)
> > >> >
> > >> >Upon further review, I think I feel into the confusion between
> > >>management
> > >> >server and ssvm.  This code is executing on the management server side,
> > >> >correct?  Based on my "corrected" understanding is correct, I would
> > >>like
> > >> >to amend my thoughts.  Namely, I would like to see the driver
> > >>operations
> > >> >pushed out to the SSVM where we can use the stream.  As I think about
> > >>it,
> > >> >the management server should not need to interact with the driver.
> > >> >Simply yard up the DataStore attributes + details map and other extract
> > >> >parameters, and send them to the SSVM.  Using this information, the S3
> > >> >driver could open a stream to write the template out to the
> > >> >bucket/directory.  I recognize it changes the protocol between the
> > >> >management server and SSVM, but it simply both sides of the operation
> > >>by
> > >> >allowing the DataStore information to be treated opaquely until it is
> > >> >consumed by the driver to execute the write operation.  I also
> > >>recognize
> > >> >that we may a little late in the cycle to address it for 4.2, and it
> > >

RE: Query String Request Authentication(QSRA) support by S3 providers

[Jessica Wang]

Min, 

> would you please take a look at this to see if UI can disable decoding in 
> displaying this download template url  
> returned from API?

I just changed UI to not decode the URL returned in extractTemplate, extractIso 
API.

Jessica


-Original Message-
From: Min Chen 
Sent: Wednesday, July 03, 2013 5:53 PM
To: dev@cloudstack.apache.org; Thomas O'Dowd
Cc: Jessica Wang
Subject: Re: Query String Request Authentication(QSRA) support by S3 providers

Jessica, would you please take a look at this to see if UI can disable
decoding in displaying this download template url returned from API?

Thanks
-min

On 7/3/13 5:38 PM, "Min Chen"  wrote:

>By examining further what returned from extractTemplateCmd api, I realized
>that the URL returned from API is different from what is displayed from
>pop-up dialog from UI. Directly using the link returned from API (with /
>encoded as %2F can successfully download the template. So the issue may
>not be that bad to upgrade Amazon SDK, but a simple UI issue. That is, is
>it possible for UI not to decode URLEncoded string in this case?
>
>Thanks
>-min
>
>On 7/3/13 5:22 PM, "Min Chen"  wrote:
>
>>Hi Tom,
>>
>>  I can reproduce this issue using Cloudian, after investigation, I
>>realized that this is a bug in Amazon SDK we have used, based on this
>>thread: 
>>http://stackoverflow.com/questions/15473582/amazon-s3-presigned-urls-esca
>>p
>>e
>>-the-slashes-in-the-key. When generatePresignedUrl is called it takes the
>>entire key and escapes it, and then creates a signature using the escaped
>>key. You cannot use the signature from the escaped key and combine it
>>with
>>the unescaped key in the URL. See the bug code here:
>>
>>  String resourcePath = "/" +
>>  ((bucketName != null) ? bucketName + "/" : "") +
>>  ((key != null) ? ServiceUtils.urlEncode(key) : "") +
>>  ((subResource != null) ? "?" + subResource : "");
>>
>>We have two options to fix this:
>>  1. Either upgrade Amazon SDK to use 1.4.3 version, someone in that
>>thread
>>claimed that it is fixed in that version, but I haven't checked that.
>>Currently CloudStack is using 1.3.21. Not sure if this will break
>>CloudStack cloud_bridge.
>>  2. Workaround by creating customized AmazonS3Client to change the
>>internal implementation on this.
>>
>>  Thanks
>>  -min
>>
>>
>>
>>On 7/2/13 11:31 PM, "Thomas O'Dowd"  wrote:
>>
>>>Excellent. The link is there now. Thank you Min. I verified that bug and
>>>closed it.
>>>
>>>However - now that I can finally click the download link... I ran into
>>>the issue that the link doesn't work on AWS or Cloudian. Please see this
>>>bug for details (latest 4.2 updates included in my test).
>>>
>>>https://issues.apache.org/jira/browse/CLOUDSTACK-3341
>>>
>>>Tom.
>>>
>>>On Tue, 2013-07-02 at 22:54 +, Min Chen wrote:
>>>> Hi Tom,
>>>>I investigated this issue through the db dump you provided in the
>>>>bug,
>>>> this is an issue with our db view template_view creation script, and
>>>>it
>>>> has been fixed in resolving
>>>> another bug (https://issues.apache.org/jira/browse/CLOUDSTACK-3314). I
>>>> have verified the fix using your db dump on my local setup. Please
>>>>check
>>>> out latest 4.2 or master code to try again.
>>>> 
>>>>Thanks
>>>>-min
>>>> 
>>>> On 7/2/13 2:18 PM, "Min Chen"  wrote:
>>>> 
>>>> >Tom, this seems like an issue with entry stored in our DB. I will
>>>>take
>>>>a
>>>> >look at this bug and update you. Just to clarify, this symptom only
>>>> >happens when you register these templates to Amazon S3, not for
>>>>Cloudian
>>>> >or RiakCS S3, right?
>>>> >
>>>> >Thanks
>>>> >-min
>>>> >
>>>> >On 7/1/13 7:27 PM, "Thomas O'Dowd"  wrote:
>>>> >
>>>> >>Yes thanks Jessica. I re-opened the bug again. I know its not a gui
>>>> >>problem per-say in that the template is not ready to show the
>>>>download
>>>> >>link. However, it never becomes ready is the actual problem. What
>>>>sets
>>>> >>the "isready" property to true? As far as

RE: Query String Request Authentication(QSRA) support by S3 providers

[Jessica Wang]

Sanjeev,

Thanks for the confirmation.

Jessica

-Original Message-
From: Sanjeev Neelarapu 
Sent: Thursday, July 18, 2013 11:05 PM
To: dev@cloudstack.apache.org; Jessica Wang
Cc: Edison Su; Thomas O'Dowd
Subject: RE: Query String Request Authentication(QSRA) support by S3 providers

Hi,

I have not seen the issue in extract template/iso after the changes. Works fine.

Thanks,
Sanjeev

-Original Message-
From: Min Chen [mailto:min.c...@citrix.com] 
Sent: Friday, July 19, 2013 5:08 AM
To: Jessica Wang
Cc: dev@cloudstack.apache.org; Edison Su; Thomas O'Dowd
Subject: Re: Query String Request Authentication(QSRA) support by S3 providers

Thanks Jessica. Tom, did you still see the issue?

-min

On 7/8/13 1:20 PM, "Jessica Wang"  wrote:

>Min,
>
>> would you please take a look at this to see if UI can disable 
>>decoding in displaying this download template url  returned from API?
>
>I just changed UI to not decode the URL returned in extractTemplate, 
>extractIso API.
>
>Jessica
>
>
>-Original Message-
>From: Min Chen
>Sent: Wednesday, July 03, 2013 5:53 PM
>To: dev@cloudstack.apache.org; Thomas O'Dowd
>Cc: Jessica Wang
>Subject: Re: Query String Request Authentication(QSRA) support by S3 
>providers
>
>Jessica, would you please take a look at this to see if UI can disable 
>decoding in displaying this download template url returned from API?
>
>Thanks
>-min
>
>On 7/3/13 5:38 PM, "Min Chen"  wrote:
>
>>By examining further what returned from extractTemplateCmd api, I 
>>realized that the URL returned from API is different from what is 
>>displayed from pop-up dialog from UI. Directly using the link returned 
>>from API (with / encoded as %2F can successfully download the 
>>template. So the issue may not be that bad to upgrade Amazon SDK, but 
>>a simple UI issue. That is, is it possible for UI not to decode 
>>URLEncoded string in this case?
>>
>>Thanks
>>-min
>>
>>On 7/3/13 5:22 PM, "Min Chen"  wrote:
>>
>>>Hi Tom,
>>>
>>> I can reproduce this issue using Cloudian, after investigation, I 
>>>realized that this is a bug in Amazon SDK we have used, based on this
>>>thread: 
>>>http://stackoverflow.com/questions/15473582/amazon-s3-presigned-urls-
>>>esc
>>>a
>>>p
>>>e
>>>-the-slashes-in-the-key. When generatePresignedUrl is called it takes 
>>>the entire key and escapes it, and then creates a signature using the 
>>>escaped key. You cannot use the signature from the escaped key and 
>>>combine it with the unescaped key in the URL. See the bug code here:
>>>
>>> String resourcePath = "/" +
>>> ((bucketName != null) ? bucketName + "/" : "") +
>>> ((key != null) ? ServiceUtils.urlEncode(key) : "") +
>>> ((subResource != null) ? "?" + subResource : "");
>>>
>>>We have two options to fix this:
>>> 1. Either upgrade Amazon SDK to use 1.4.3 version, someone in that 
>>>thread claimed that it is fixed in that version, but I haven't 
>>>checked that.
>>>Currently CloudStack is using 1.3.21. Not sure if this will break 
>>>CloudStack cloud_bridge.
>>> 2. Workaround by creating customized AmazonS3Client to change the 
>>>internal implementation on this.
>>>
>>> Thanks
>>> -min
>>>
>>>
>>>
>>>On 7/2/13 11:31 PM, "Thomas O'Dowd"  wrote:
>>>
>>>>Excellent. The link is there now. Thank you Min. I verified that bug 
>>>>and closed it.
>>>>
>>>>However - now that I can finally click the download link... I ran 
>>>>into the issue that the link doesn't work on AWS or Cloudian. Please 
>>>>see this bug for details (latest 4.2 updates included in my test).
>>>>
>>>>https://issues.apache.org/jira/browse/CLOUDSTACK-3341
>>>>
>>>>Tom.
>>>>
>>>>On Tue, 2013-07-02 at 22:54 +, Min Chen wrote:
>>>>> Hi Tom,
>>>>>   I investigated this issue through the db dump you provided in the 
>>>>>bug,  this is an issue with our db view template_view creation 
>>>>>script, and it  has been fixed in resolving  another bug 
>>>>>(https://issues.apache.org/jira/browse/CLOUDSTACK-3314).
>>>>>I
>>>>> have verified the fix using your db dump on my local setup. Please 
>>>>>check  out latest 4.2 or master code to try 

RE: Reformatting UI code

[Jessica Wang]

+1

-Original Message-
From: Brian Federle [mailto:brian.fede...@citrix.com] 
Sent: Monday, July 22, 2013 11:33 AM
To: dev@cloudstack.apache.org
Cc: Ian Duffy (i...@ianduffy.ie)
Subject: Reformatting UI code

Hello,

Recently I discovered that all JS and UI code have been reformatted to 4 spaces:

commit ad69bc8da3244b783dd003ddf3184fca2762c514
Author: Ian Duffy 
Date:   Thu Jul 18 15:39:28 2013 +0100

Format JS

While I do appreciate people coming in to help clean up the UI code, and don't 
mind if we change the indent level to be consistent with the rest of the code 
base, this commit is causing a lot of git conflicts with various development 
branches I'm working on. Please give a bit more heads up in the future about 
this, try to CC the main UI developers about it first before committing - right 
now myself and Jessica Wang (jessica.w...@citrix.com) do the majority of UI 
development.

Thanks,
Brian

RE: Reformatting UI code

[Jessica Wang]

Pranav, Ian, Sebastien,

The problem is the duration between the time Ian brought it up on the mailing 
list and the time Ian/Sebastien checked in the change to master branch is too 
short (less than 4 hours).

Ian brought it up on the mailing list at Thu 7/18/2013 5:44 AM (email subject 
is "Auto format javascript"). 
Sebastien checked in Ian's change to master branch at 7/18/2013 9:34 AM (Commit 
hash: ad69bc8da3244b783dd003ddf3184fca2762c514).

This is a big change of UI code.
In GIT's view, every line in JS files has been changed (If you look at code 
difference in GIT's history).
GIT sees it as "delete all lines and add new different lines".
I was unable to merge my check-in from master branch to 4.2 branch (or any 
other branch) since GIT sees JS files in master branch and other branches are 
totally different.

Shouldn't this kind of big change be checked in to a different branch (not 
master branch) first? Then, submit a merge request to community, wait for 72 
hours, then merge to master branch eventually?

Jessica


-Original Message-
From: Pranav Saxena [mailto:psb...@gmail.com] 
Sent: Monday, July 22, 2013 12:18 PM
To: dev@cloudstack.apache.org; Brian Federle
Cc: Ian Duffy (i...@ianduffy.ie)
Subject: Re: Reformatting UI code

Hey Brian,

Sorry to hear that it caused merge conflicts for you . But Ian did bring it
up on the mailing list and I suggested him to use the js beautifier tool
for reformatting the js code which I guess you missed probably because of
the "heavy" traffic on the dev list and thereafter Sebastien merged the
code when the discussion and the reviews ended. Anyways, I'll also try to
ping you personally on such occasions in the future to let you know if any
major changes are being committed. Now , probably you would need to do a
lot of rebasing , sorry for that !!

Thanks,
Pranav


On Tue, Jul 23, 2013 at 12:29 AM, Jessica Wang wrote:

> +1
>
> -Original Message-
> From: Brian Federle [mailto:brian.fede...@citrix.com]
> Sent: Monday, July 22, 2013 11:33 AM
> To: dev@cloudstack.apache.org
> Cc: Ian Duffy (i...@ianduffy.ie)
> Subject: Reformatting UI code
>
> Hello,
>
> Recently I discovered that all JS and UI code have been reformatted to 4
> spaces:
>
> commit ad69bc8da3244b783dd003ddf3184fca2762c514
> Author: Ian Duffy 
> Date:   Thu Jul 18 15:39:28 2013 +0100
>
> Format JS
>
> While I do appreciate people coming in to help clean up the UI code, and
> don't mind if we change the indent level to be consistent with the rest of
> the code base, this commit is causing a lot of git conflicts with various
> development branches I'm working on. Please give a bit more heads up in the
> future about this, try to CC the main UI developers about it first before
> committing - right now myself and Jessica Wang (jessica.w...@citrix.com)
> do the majority of UI development.
>
> Thanks,
> Brian
>

RE: Reformatting UI code

[Jessica Wang]

Sebastien,

Brian and I are fix 4.2 bugs.
Any fix for 4.2 bugs should go to both 4.2 branch and master branch.
That's why Brian and I still need to merge our check-in between master branch 
and 4.2 branch.

Jessica

-Original Message-
From: Sebastien Goasguen [mailto:run...@gmail.com] 
Sent: Monday, July 22, 2013 3:53 PM
To: Brian Federle
Cc: Jessica Wang; Pranav Saxena; Ian Duffy (i...@ianduffy.ie); 
dev@cloudstack.apache.org
Subject: Re: Reformatting UI code



On 23 Jul 2013, at 00:34, Brian Federle  wrote:

> In this case it was fine, I could resolve the conflicts by git's 
> -Xignore-space-change and reformatting accordingly.
> 
> The main issue was that I didn't see any indication that this was being 
> committed from reading the discussion thread. Since we're doing a lot of 
> bugfixing right now for 4.2, a large sweeping commit like this should at 
> least be posted as part of thread, so that there is heads-up so that we can 
> prepare any pending changes we have to avoid being blocked.
> 

Ok but this is not for 4.2. It was committed to master. How is it impacting 
your 4.2 fixes ?


> -Brian
> 
> -Original Message-
> From: Sebastien Goasguen [mailto:run...@gmail.com] 
> Sent: Monday, July 22, 2013 3:26 PM
> To: Jessica Wang
> Cc: Pranav Saxena; Ian Duffy (i...@ianduffy.ie); dev@cloudstack.apache.org; 
> Brian Federle
> Subject: Re: Reformatting UI code
> 
> Hi jessica,
> 
> Sorry this is causing you trouble. Ian us developing his ldap plugin in a 
> feature branch .
> This was a UI cosmetic code change, i saw that pranav shipped it in RB but 
> did not apply the patch. Since the three if us work in more or less the same 
> time zone i applied the patch quickly to master. I did think about other UI 
> work but since 4.2 is in feature freeze i did not think committing to master 
> would be a problem.
> 
> Moreover i did not know u were working on UI feature branches. Where can we 
> look at the feature descriptions ? 
> 
> I suppose u could revert the patch . But for features for 4.3 i think it 
> should be rebase of your feature branches . I dont think this change should 
> be impacting 4.2 not sure why u say thats the case.
> 
> Thoughts ?
> 
> -Sebastien
> 
> On 23 Jul 2013, at 00:07, Jessica Wang  wrote:
> 
>> Pranav, Ian, Sebastien,
>> 
>> The problem is the duration between the time Ian brought it up on the 
>> mailing list and the time Ian/Sebastien checked in the change to master 
>> branch is too short (less than 4 hours).
>> 
>> Ian brought it up on the mailing list at Thu 7/18/2013 5:44 AM (email 
>> subject is "Auto format javascript"). 
>> Sebastien checked in Ian's change to master branch at 7/18/2013 9:34 AM 
>> (Commit hash: ad69bc8da3244b783dd003ddf3184fca2762c514).
>> 
>> This is a big change of UI code.
>> In GIT's view, every line in JS files has been changed (If you look at code 
>> difference in GIT's history).
>> GIT sees it as "delete all lines and add new different lines".
>> I was unable to merge my check-in from master branch to 4.2 branch (or any 
>> other branch) since GIT sees JS files in master branch and other branches 
>> are totally different.
>> 
>> Shouldn't this kind of big change be checked in to a different branch (not 
>> master branch) first? Then, submit a merge request to community, wait for 72 
>> hours, then merge to master branch eventually?
>> 
>> Jessica
>> 
>> 
>> -Original Message-
>> From: Pranav Saxena [mailto:psb...@gmail.com]
>> Sent: Monday, July 22, 2013 12:18 PM
>> To: dev@cloudstack.apache.org; Brian Federle
>> Cc: Ian Duffy (i...@ianduffy.ie)
>> Subject: Re: Reformatting UI code
>> 
>> Hey Brian,
>> 
>> Sorry to hear that it caused merge conflicts for you . But Ian did 
>> bring it up on the mailing list and I suggested him to use the js 
>> beautifier tool for reformatting the js code which I guess you missed 
>> probably because of the "heavy" traffic on the dev list and thereafter 
>> Sebastien merged the code when the discussion and the reviews ended. 
>> Anyways, I'll also try to ping you personally on such occasions in the 
>> future to let you know if any major changes are being committed. Now , 
>> probably you would need to do a lot of rebasing , sorry for that !!
>> 
>> Thanks,
>> Pranav
>> 
>> 
>> On Tue, Jul 23, 2013 at 12:29 AM, Jessica Wang 
>> wrote:
>> 
>>> +1
>>> 
>>> -Original Message-
>>> From: Brian Federle [mailto:brian.fede...@citrix.com]
>>>

RE: Updating list view after data addition.

[Jessica Wang]

Ian,

> What is the correct way of handling this table update?

call "args.response.success()" with the embedded object returned in API 
response.

e.g. API response is: 
{
"createaccountresponse": {
"account": {
"id": "7005b368-5da6-4a8b-a588-e7c5c113c40e",
"name": "bbb_user",
"accounttype": 0,
"domainid": "25a1e8b0-6cce-44cb-b724-8f5543fd85b8","
~ ~ ~ 
}
}
}

pass the embedded object: 
   {
"id": "7005b368-5da6-4a8b-a588-e7c5c113c40e",
"name": "bbb_user",
"accounttype": 0,
"domainid": "25a1e8b0-6cce-44cb-b724-8f5543fd85b8","
~ ~ ~ 
   } 
to args.response.success()


like this:
==
success: function(json) {
var item = json.createaccountresponse.account;
args.response.success({
  data: item
});
}
==

Jessica

-Original Message-
From: Ian Duffy [mailto:i...@ianduffy.ie] 
Sent: Thursday, July 25, 2013 3:20 AM
To: CloudStack Dev
Subject: Updating list view after data addition.

Hi,

I've modified the "add account" screen to use a custom ui. The custom
UI displays a table of all LDAP users along with the required and
optional input fields.

When I add the user the user doesn't appear on the table of users
until the page is refreshed.

What is the correct way of handling this table update?

is it ok to do:

success: function(args) {
$('.list-view').listView('refresh');
close();
 }

Thanks,
Ian

RE: UI Query: createForm

[Jessica Wang]

Ian,

That's correct.

JQuery Validation only checks CSS class("disallowSpecialCharacters" in this 
case) of input field.
It doesn't check CSS class of label.

Jessica

-Original Message-
From: Ian Duffy [mailto:i...@ianduffy.ie] 
Sent: Thursday, July 25, 2013 6:02 AM
To: dev@cloudstack.apache.org
Subject: Re: UI Query: createForm

Hi,

Looking at this again.

It works if I add a class of required onto the input tag. For some
reason it doesn't pick up the field-required from the label.

On 24 July 2013 14:08, Ian Duffy  wrote:
> Hi Pranav,
>
> The "Required: true" in the creates that span required field
> automatically. The following is the result of its generated html:
> (Just using account as an example, account isn't required in practice)
>
> 
> 
> 
> *Account:
> 
> 
>  class="disallowSpecialCharacters" id="label_account">
> 
> 
>
> But it still allows the form to be submitted without account having data.
>
> On 24 July 2013 13:48, Pranav Saxena  wrote:
>> Sorry for missing this thread .Seems like the mail was automatically sent
>> to my citrix ID which doesn't exist anymore. Anyways, I gave a quick look
>> at what Ian is trying to do here and realized that he has probably
>> forgotten to add the "required" class in the form structure . Ian , you
>> might want to add something like this to your customized form  as shown
>> below . This might help you with form validation.
>>
>> var $astersikSpan = $('').addClass('field-required').html('*');
>> 
>> $name.find('label').prepend($astersikSpan);
>> 
>> 
>>if (field.validation == null ||
>> field.validation.required == false) {
>> 
>> $astersikSpan.hide();
>> 
>>   }
>>
>>
>> Thanks,
>> Pranav
>>
>>
>>
>>
>> On Wed, Jul 24, 2013 at 5:55 PM, Sebastien Goasguen wrote:
>>
>>> Parnav, Jessica or Brian, can you help Ian here ?
>>>
>>> thx
>>>
>>> On Jul 22, 2013, at 9:51 AM, Ian Duffy  wrote:
>>>
>>> > Hi,
>>> >
>>> > I'm having an issue with the below gisted snippets. For whatever
>>> > reason they do not get validated. Any idea why?
>>> >
>>> > https://gist.github.com/imduffy15/6053967
>>> >
>>> > Thanks,
>>> > Ian
>>>
>>>

RE: Switch dialog actions based on result from API call.

[Jessica Wang]

Ian, 
I don't think current widget code support it (that calls different dialogs for 
Add action depending on count number in listView).

Brian,
Please confirm it.

Jessica

-Original Message-
From: Ian Duffy [mailto:i...@ianduffy.ie] 
Sent: Thursday, July 25, 2013 7:36 AM
To: CloudStack Dev
Subject: Switch dialog actions based on result from API call.

Hi,

How would I go about modifying the UI to allow me to change the "Add
Account" screen to:

1) When listLdapConfigurations returns a count of less than 1 the
default cloudstack add account screen is given.
2) When listLdapConfigurations returns a count of greater than one my
custom LDAP add account screen is given.

What I have so far can be seen at:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=ui/scripts/accounts.js;h=e3e28e47a305bb53151a6e7c749cad355b872736;hb=ldapplugin

Thanks,
Ian

RE: Switch dialog actions based on result from API call.

[Jessica Wang]

Right.

Ian,
You are trying to call different dialog boxes.
I suggest you call the same dialog box, but show/hide different fields in the 
same dialog box depending on the count number of listView.
Like this:
=

add: {
 label: 'Add Account',
 messages: {
  notification: 
function(args) {

  return 'Add Account';
  }
 },
 createForm: {
  title: 'Add Account',
  preFilter: 
function(args) {
//if 
count number in listView is less than 1, hide field A/C/E, show field B/D.

//otherwise, show field A/C/E, hide field B/D.
  },
  fields: {

  A: { label: 'A'  },

  B: { label: 'B'  },

  C: { label: 'C'  },

  D: { label: 'D'  },

  E: { label: 'E'   }
  }
  action: 
function(args) {

  ~~~
  },
  notification: {

  ~~~
  }
 }
}


From: Pranav Saxena [mailto:psb...@gmail.com]
Sent: Thursday, July 25, 2013 10:59 AM
To: dev@cloudstack.apache.org; Jessica Wang; Brian Federle
Subject: Re: Switch dialog actions based on result from API call.

Unless and until the dialog box is the same and it's just about adding/removing 
more fields from the dialog box , it should be pretty much possible by adding 
"preFilters" and then using the count returned by that API to hide/remove those 
fields under the preFilter sections.  Basically a if/else check under the 
preFilters block.

If it's about triggering a new dialog box all together , then it might require 
you to do little more work . This might not be supported by the widget right 
now as Jessica pointed out.

Thanks,
Pranav

On Thu, Jul 25, 2013 at 11:23 PM, Jessica Wang 
mailto:jessica.w...@citrix.com>> wrote:
Ian,
I don't think current widget code support it (that calls different dialogs for 
Add action depending on count number in listView).

Brian,
Please confirm it.

Jessica

-Original Message-
From: Ian Duffy [mailto:i...@ianduffy.ie<mailto:i...@ianduffy.ie>]
Sent: Thursday, July 25, 2013 7:36 AM
To: CloudStack Dev
Subject: Switch dialog actions based on result from API call.

Hi,

How would I go about modifying the UI to allow me to change the "Add
Account" screen to:

1) When listLdapConfigurations returns a count of less than 1 the
default cloudstack add account screen is given.
2) When listLdapConfigurations returns a count of greater than one my
custom LDAP add account screen is given.

What I have so far can be seen at:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=ui/scripts/accounts.js;h=e3e28e47a305bb53151a6e7c749cad355b872736;hb=ldapplugin

Thanks,
Ian

RE: Switch dialog actions based on result from API call.

[Jessica Wang]

CSS style in screen1.png looks good   :)


-Original Message-
From: Ian Duffy [mailto:i...@ianduffy.ie] 
Sent: Friday, July 26, 2013 3:12 AM
To: Jessica Wang
Cc: dev@cloudstack.apache.org; Pranav Saxena; Brian Federle
Subject: Re: Switch dialog actions based on result from API call.

Got this going this morning. Thank you for your help.
Its a little messier than I would like but there doesn't seem to be a
work around.

With LDAP - http://ianduffy.ie/cloudstack/screen1.png
Without LDAP - http://ianduffy.ie/cloudstack/screen2.png

Thanks again,
Ian

RE: UI Plugin Feature Discussion

[Jessica Wang]

Chris,

> UI Internationalization:
> This would allow UI Plugins to contribute their own internationalized strings 
> to the global js dictionary. Each plugin would define a dictionary.js and 
> several dictionary_.js files. 

So, the translation will be done on client-side?


> Default value functions:
> Currently, the default value for a UI field must be a constant. I have 
> extended the dialog forms to allow default value functions which are given 
> the standard 'args' allowing default values to be determined at run time.

sounds good

> has_units field:
> I have added a new dialog field type called 'has_units'. This field has an 
> input box side by side with a select box. The select box is populated with 
> predefined units (MB, GB, TB, for example) and uses (also predefined) 
> conversion functions to allow automatic updating of the input box value when 
> the units select box is changed.

Cool


Jessica

-Original Message-
From: SuichII, Christopher [mailto:chris.su...@netapp.com] 
Sent: Wednesday, July 31, 2013 8:27 AM
To: 
Subject: UI Plugin Feature Discussion

I have a couple UI Plugin related features I'm close to wrapping up and I'd 
like to throw them out to take some feedback:

(I realize this is bad form to discuss the feature after implementation, so I 
apologize for that. However, everything here provides an optional feature for 
plugin developers and shouldn't pose any problem to the existing UI.)

UI Internationalization:
This would allow UI Plugins to contribute their own internationalized strings 
to the global js dictionary. Each plugin would define a dictionary.js and 
several dictionary_.js files. As each plugin is loaded, the appropriate 
plugin dictionary is loaded into the global js dictionary (with the global 
dictionary taking precedence in the event of a conflict).

Re-usable Zone Chart:
I have extended some functions in zoneChart.js to allow plugins to create 
charts by simply defining their own function which assembles the chart itself 
rather than having to define the chart in zoneChart.js

Dialog value field:
Currently, the identifying value of json objects is assumed to be 'id' or 
'name' (if 'id' doesn't exist). I have added the option of allowing fields to 
specify which json property should be the identifying value of an object.

Default value functions:
Currently, the default value for a UI field must be a constant. I have extended 
the dialog forms to allow default value functions which are given the standard 
'args' allowing default values to be determined at run time.

has_units field:
I have added a new dialog field type called 'has_units'. This field has an 
input box side by side with a select box. The select box is populated with 
predefined units (MB, GB, TB, for example) and uses (also predefined) 
conversion functions to allow automatic updating of the input box value when 
the units select box is changed.

Please let me know what the proper course of action is from here. Should I go 
ahead and submit diffs to reviewers or is there any discussion to be had before 
I do that?

Thanks,
Chris

RE: UI Plugin Feature Discussion

[Jessica Wang]

> I would suggest you to submit multiple patches for each category because that 
> way it will be easier to review and merge your changes.

+1 


-Original Message-
From: Pranav Saxena [mailto:psb...@gmail.com] 
Sent: Wednesday, July 31, 2013 10:30 AM
To: dev@cloudstack.apache.org; Brian Federle; Jessica Wang; Sonny Chhen
Subject: Re: UI Plugin Feature Discussion

Hey Chris ,

I think whatever proposals you have mentioned here make a lot of sense and
should help in a better user experience. I would suggest that you submit a
patch/multiple patches as per your convenience for the above mentioned
categories and then we can take it forward from there . I would suggest you
to submit multiple patches for each category because that way it will be
easier to review and merge your changes. A little explanation of the
functionality with each patch you submit would be much appreciated.

Copying Brian and Jessica to further help in facilitating this process
quickly . Thanks for your work.


On Wed, Jul 31, 2013 at 8:56 PM, SuichII, Christopher <
chris.su...@netapp.com> wrote:

> I have a couple UI Plugin related features I'm close to wrapping up and
> I'd like to throw them out to take some feedback:
>
> (I realize this is bad form to discuss the feature after implementation,
> so I apologize for that. However, everything here provides an optional
> feature for plugin developers and shouldn't pose any problem to the
> existing UI.)
>
> UI Internationalization:
> This would allow UI Plugins to contribute their own internationalized
> strings to the global js dictionary. Each plugin would define a
> dictionary.js and several dictionary_.js files. As each plugin is
> loaded, the appropriate plugin dictionary is loaded into the global js
> dictionary (with the global dictionary taking precedence in the event of a
> conflict).
>
> Re-usable Zone Chart:
> I have extended some functions in zoneChart.js to allow plugins to create
> charts by simply defining their own function which assembles the chart
> itself rather than having to define the chart in zoneChart.js
>
> Dialog value field:
> Currently, the identifying value of json objects is assumed to be 'id' or
> 'name' (if 'id' doesn't exist). I have added the option of allowing fields
> to specify which json property should be the identifying value of an object.
>
> Default value functions:
> Currently, the default value for a UI field must be a constant. I have
> extended the dialog forms to allow default value functions which are given
> the standard 'args' allowing default values to be determined at run time.
>
> has_units field:
> I have added a new dialog field type called 'has_units'. This field has an
> input box side by side with a select box. The select box is populated with
> predefined units (MB, GB, TB, for example) and uses (also predefined)
> conversion functions to allow automatic updating of the input box value
> when the units select box is changed.
>
> Please let me know what the proper course of action is from here. Should I
> go ahead and submit diffs to reviewers or is there any discussion to be had
> before I do that?
>
> Thanks,
> Chris
>

RE: [ACS41] Baremetal blockers

[Jessica Wang]

-Original Message-
From: Animesh Chaturvedi 
Sent: Thursday, March 21, 2013 2:56 PM
To: dev@cloudstack.apache.org
Cc: cloudstack-...@incubator.apache.org; Jessica Wang
Subject: RE: [ACS41] Baremetal blockers



> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Thursday, March 21, 2013 2:22 PM
> To: dev@cloudstack.apache.org
> Cc: cloudstack-...@incubator.apache.org; Jessica Wang
> Subject: RE: [ACS41] Baremetal blockers
> 
> 
> > >> > >
> > >> > > I am checking if  these can be reassigned. If it does not pan
> > >> > > out by
> > >> tomorrow I will propose to disable the feature for 4.1 release.
> > >> >
> > >> > I think that a decision is predicated on a more specific
> > >> > statement of what we mean by "disable".
> > >>
> > >> Pinging on this again.  I'm leaning towards agreement, but what
> > >> *exactly* can we do to disable it and (at the same time) minimize
> > >> the
> > >> knock- on effect of the change required to disable it.
> > > [Animesh>] There is no one available to pick up these defects in
> > > time for
> > 4.1 so we will disable the feature. Disable means Baremetal will be
> > removed from componentContext.xml , the API and UI will not be
> available.
> >
> > Are you sure that removing the plugin from componentContext.xml will
> > remove it from the UI?  (I'm not, that's why I'm asking)
> [Animesh>] Yes, discussed with Alex and Jessica.
[Animesh>] Will try out the change and submit a patch. Jessica anything else?
[Jessica W] Nothing else except removing Baremetal from listHypervisors API 
response and listSupportedNetworkServices API response.

RE: [ACS41] Baremetal blockers - To remove Baremetal from UI

[Jessica Wang]

"name": "PortForwarding",
"provider": [
{
"name": "NiciraNvp",
"canenableindividualservice": true
},
{
"name": "VirtualRouter",
"canenableindividualservice": true
},
{
"name": "VpcVirtualRouter",
"canenableindividualservice": true
}
],
"capability": []
},
{
"name": "SecurityGroup",
"provider": [
{
"name": "SecurityGroupProvider",
"canenableindividualservice": false
}
],
"capability": []
},
{
"name": "NetworkACL",
    "provider": [
{
"name": "VpcVirtualRouter",
"canenableindividualservice": true
}
],
"capability": [
{
"name": "SupportedProtocols",
"canchooseservicecapability": false
}
]
},
{
"name": "Connectivity",
"provider": [
{
"name": "BigSwitchVns",
"canenableindividualservice": true
},
{
"name": "NiciraNvp",
"canenableindividualservice": true
}
],
"capability": []
},
{
"name": "BaremetalPxeService",
"provider": [
{
"name": "BaremetalPxeProvider",
"canenableindividualservice": false
}
],
"capability": []
}
]
}
}



Jessica

-Original Message-
From: Jessica Wang [mailto:jessica.w...@citrix.com] 
Sent: Thursday, March 21, 2013 3:00 PM
To: Animesh Chaturvedi; dev@cloudstack.apache.org
Cc: cloudstack-...@incubator.apache.org
Subject: RE: [ACS41] Baremetal blockers



-Original Message-
From: Animesh Chaturvedi 
Sent: Thursday, March 21, 2013 2:56 PM
To: dev@cloudstack.apache.org
Cc: cloudstack-...@incubator.apache.org; Jessica Wang
Subject: RE: [ACS41] Baremetal blockers



> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Thursday, March 21, 2013 2:22 PM
> To: dev@cloudstack.apache.org
> Cc: cloudstack-...@incubator.apache.org; Jessica Wang
> Subject: RE: [ACS41] Baremetal blockers
> 
> 
> > >> > >
> > >> > > I am checking if  these can be reassigned. If it does not pan
> > >> > > out by
> > >> tomorrow I will propose to disable the feature for 4.1 release.
> > >> >
> > >> > I think that a decision is predicated on a more specific
> > >> > statement of what we mean by "disable".
> > >>
> > >> Pinging on this again.  I'm leaning towards agreement, but what
> > >> *exactly* can we do to disable it and (at the same time) minimize
> > >> the
> > >> knock- on effect of the change required to disable it.
> > > [Animesh>] There is no one available to pick up these defects in
> > > time for
> > 4.1 so we will disable the feature. Disable means Baremetal will be
> > removed from componentContext.xml , the API and UI will not be
> available.
> >
> > Are you sure that removing the plugin from componentContext.xml will
> > remove it from the UI?  (I'm not, that's why I'm asking)
> [Animesh>] Yes, discussed with Alex and Jessica.
[Animesh>] Will try out the change and submit a patch. Jessica anything else?
[Jessica W] Nothing else except removing Baremetal from listHypervisors API 
response and listSupportedNetworkServices API response.

RE: [ACS4.2] master blockers

[Jessica Wang]

I just resolved all of my bugs:

>CLOUDSTACK-1730    Jessica Wang
>CLOUDSTACK-1728    Jessica Wang
>CLOUDSTACK-1616    Jessica Wang
>CLOUDSTACK-1731    Jessica Wang


-Original Message-
From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com] 
Sent: Wednesday, March 27, 2013 10:05 PM
To: cloudstack dev
Cc: dev@cloudstack.apache.org
Subject: Re: [ACS4.2] master blockers 

Once again a reminder to close the following blockers and criticals in
master, if you are assigned but cannot figure out the issue please reach
out.

>CLOUDSTACK-1687Mice Xia
>CLOUDSTACK-1677Kelven Yang
>CLOUDSTACK-1774Rohit Yadav
>CLOUDSTACK-1721Prachi Damle
>CLOUDSTACK-1613Bharat Kumar
>CLOUDSTACK-1610frank zhang
>CLOUDSTACK-1591edison su
>CLOUDSTACK-1732Sheng Yang
>CLOUDSTACK-1739Bharat Kumar
>CLOUDSTACK-1392edison su
>CLOUDSTACK-1404edison su
>CLOUDSTACK-1753    Brian Federle
>CLOUDSTACK-1730Jessica Wang
>CLOUDSTACK-1707Mice Xia
>CLOUDSTACK-1672Mice Xia
>CLOUDSTACK-1513edison su
>CLOUDSTACK-1728Jessica Wang
>CLOUDSTACK-1619frank zhang
>CLOUDSTACK-1618frank zhang
>CLOUDSTACK-1607Nitin Mehta
>CLOUDSTACK-1635    edison su
>CLOUDSTACK-1614frank zhang
>CLOUDSTACK-1616Jessica Wang
>CLOUDSTACK-1639edison su
>CLOUDSTACK-1602edison su
>CLOUDSTACK-1737Anthony Xu
>CLOUDSTACK-1698Mice Xia
>CLOUDSTACK-1731Jessica Wang
>CLOUDSTACK-1440frank zhang
>CLOUDSTACK-1405edison su
>CLOUDSTACK-1646Bharat Kumar
>CLOUDSTACK-1534Bharat Kumar
>

-abhi
>

RE: CloudStack UI Authentication Mechanism

[Jessica Wang]

Donal,

> 1. How are API calls authenticated and authorized if they are not signed with 
> API keys?

API calls are authenticated and authorized by sessionkey returned by login API.

When logging in to cloudstack UI, cloudstack UI passes 
userName/password/domainName to login API, then login API returns: 
{
"loginresponse": {
"timeout": "1800",
"sessionkey": "SNneDo02sr+ZyXC9QjFS8zDlRkw=",
"username": "admin",
"registered": "false",
"userid": "7be457a7-eec0-1030-9ebb-c172f98ac43b",
"account": "admin",
"lastname": "User",
"domainid": "7be3ba5d-eec0-1030-9ebb-c172f98ac43b",
"firstname": "Admin",
"type": "1"
}
}

Then, UI passes sessionkey("SNneDo02sr+ZyXC9QjFS8zDlRkw=") to all API calls,
e.g.
http://localhost:8080/client/api?command=listZones&response=json&sessionkey=SNneDo02sr%2BZyXC9QjFS8zDlRkw%3D&_=1365111852798
http://localhost:8080/client/api?command=listHosts&response=json&sessionkey=SNneDo02sr%2BZyXC9QjFS8zDlRkw%3D&state=Alert&page=1&pageSize=4&_=1365112437658
http://localhost:8080/client/api?command=listVirtualMachines&response=json&sessionkey=SNneDo02sr%2BZyXC9QjFS8zDlRkw%3D&listAll=true&page=1&pagesize=20&_=1365112441706

Jessica


-Original Message-
From: Donal Lafferty [mailto:donal.laffe...@citrix.com] 
Sent: Thursday, April 04, 2013 4:21 AM
To: cloudstack-...@incubator.apache.org
Subject: CloudStack UI Authentication Mechanism

I noticed that the CloudStack UI allows VM control to accounts that don't have 
an API key set defined.

How does its authentication mechanism work?  E.g.


1.  How are API calls authenticated and authorized if they are 
not signed with API keys?

2.  Does this work equally well when LDAP is to authenticate 
username / password?


DL

RE: [Query] Advanced Zone with Security Groups

[Jessica Wang]

Yes (in master branch)

-Original Message-
From: Srikanteswararao Talluri [mailto:srikanteswararao.tall...@citrix.com] 
Sent: Monday, April 29, 2013 3:34 AM
To: dev@cloudstack.apache.org
Subject: [Query] Advanced Zone with Security Groups



Is Advanced Zone with Security Groups feature available for  XenServer 
deployments?

Thanks,
~Talluri

RE: [Query] Advanced Zone with Security Groups

[Jessica Wang]

Srikanteswararao,

I just confirmed with the server-side developer. He said the code is not in 
master branch yet.

Jessica


-Original Message-
From: Jessica Wang [mailto:jessica.w...@citrix.com] 
Sent: Monday, April 29, 2013 10:56 AM
To: dev@cloudstack.apache.org
Subject: RE: [Query] Advanced Zone with Security Groups

Yes (in master branch)

-Original Message-
From: Srikanteswararao Talluri [mailto:srikanteswararao.tall...@citrix.com] 
Sent: Monday, April 29, 2013 3:34 AM
To: dev@cloudstack.apache.org
Subject: [Query] Advanced Zone with Security Groups



Is Advanced Zone with Security Groups feature available for  XenServer 
deployments?

Thanks,
~Talluri

RE: [jira] [Commented] (CLOUDSTACK-2463) CS Upgrade 2.2.14 to 4.1.0 failed due to no public network found (configuration : advanced network with security groups)

[Jessica Wang]

I'll remove this option (Advance zone with SG) from UI in 4.1 branch.
Will submit a patch soon.


-Original Message-
From: Anthony Xu [mailto:xuefei...@citrix.com] 
Sent: Monday, May 13, 2013 1:46 PM
To: Alena Prokharchyk; dev@cloudstack.apache.org; Chip Childers
Subject: RE: [jira] [Commented] (CLOUDSTACK-2463) CS Upgrade 2.2.14 to 4.1.0 
failed due to no public network found (configuration : advanced network with 
security groups)

Advance zone with SG is not in 4.1.

Anthony

-Original Message-
From: Alena Prokharchyk 
Sent: Monday, May 13, 2013 1:37 PM
To: dev@cloudstack.apache.org; Chip Childers; Anthony Xu
Subject: Re: [jira] [Commented] (CLOUDSTACK-2463) CS Upgrade 2.2.14 to 4.1.0 
failed due to no public network found (configuration : advanced network with 
security groups)

Anthony, do we even support Advance zone with SG in 4.1? I thought you've 
checked it in in 4.2 only. If this is true, then:

* no upgrade support for SG enabled setups to 4.1 should be provided
* 4.1 UI shouldn't let you create Advance zone with SG enabled. If UI for SG 
enabled Advance zone was somehow merged to 4.1 branch, it should be reverted as 
there is no backend/db upgrade support exist there.


-Alena.



On 5/13/13 1:10 PM, "Paul Angus"  wrote:

>Done. :)
>
>Regards,
>
>Paul Angus
>S: +44 20 3603 0540 | M: +447711418784
>paul.an...@shapeblue.com
>
>-Original Message-
>From: Wei ZHOU [mailto:ustcweiz...@gmail.com]
>Sent: 13 May 2013 18:38
>To: dev@cloudstack.apache.org
>Subject: Re: [jira] [Commented] (CLOUDSTACK-2463) CS Upgrade 2.2.14 to
>4.1.0 failed due to no public network found (configuration : advanced 
>network with security groups)
>
>Thanks,  Paul.
>
>Could you login to the database and paste the result of the commands 
>Nicolas listed in Description?
>
>
>2013/5/13 Paul Angus (JIRA) 
>
>>
>> [
>> https://issues.apache.org/jira/browse/CLOUDSTACK-2463?page=com.atlass
>> i 
>> an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentI
>> d
>> =13656100#comment-13656100]
>>
>> Paul Angus commented on CLOUDSTACK-2463:
>> 
>>
>> On a clean build of ACS4.1-SNAPSHOT from 13/05/13 I created an 
>> advanced zone with security groups.
>>
>> When attempting to enable the zone I received the following message:
>>
>> 'Cannot enable this Zone since: Unable to find the default physical 
>> network with traffic=Public in the specified zone id'
>>
>> As it was an advanced zone with security groups I didn't get the 
>> option to add/configure a public network.
>>
>> > CS Upgrade 2.2.14 to 4.1.0 failed due to no public network found
>> (configuration : advanced network with security groups)
>> >
>> -
>> -
>> --
>> >
>> > Key: CLOUDSTACK-2463
>> > URL:
>> https://issues.apache.org/jira/browse/CLOUDSTACK-2463
>> > Project: CloudStack
>> >  Issue Type: Bug
>> >  Security Level: Public(Anyone can view this level - this is 
>> > the
>> default.)
>> >Affects Versions: 4.1.0
>> >Reporter: Nicolas Lamirault
>> >Assignee: Wei Zhou
>> >Priority: Blocker
>> > Fix For: 4.1.0
>> >
>> >
>> > According Wei Zhou last patch (
>> https://issues.apache.org/jira/browse/CLOUDSTACK-528), i can add a 
>> new secondary storage. The SSVM creation failed due to :
>> > 2013-05-13 15:17:52,868 DEBUG
>> [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) 
>> Zone 1 is ready to launch secondary storage VM
>> > 2013-05-13 15:17:52,879 INFO
>> [cloud.secstorage.PremiumSecondaryStorageManagerImpl]
>> (secstorage-1:null) No running secondary storage vms found in 
>> datacenter id=1, starting one
>> > 2013-05-13 15:17:52,889 INFO
>> [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) 
>> No stopped secondary storage vm is available, need to allocate a new 
>> secondary storage vm
>> > 2013-05-13 15:17:52,894 DEBUG
>> [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) 
>> Assign secondary storage vm from a newly started instance for request 
>> from data center : 1
>> > 2013-05-13 15:17:52,922 WARN [cloud.vm.SystemVmLoadScanner]
>> (secstorage-1:null) Unexpected exception Found 22 networks of type 
>> Guest when expect to find 1
>> > com.cloud.utils.exception.CloudRuntimeException: Found 22 networks 
>> > of
>> type Guest when expect to find 1
>> > at
>> com.cloud.storage.secondary.SecondaryStorageManagerImpl.createSecStor
>> a
>> geVmInstance(SecondaryStorageManagerImpl.java:552)
>> > at
>> com.cloud.storage.secondary.SecondaryStorageManagerImpl.startNew(Seco
>> n
>> daryStorageManagerImpl.java:499)
>> > at
>> com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity
>> (
>> SecondaryStorageManagerImpl.java:666)
>> > at
>> com.cloud.storage.secondary.SecondaryStorageManage

RE: [ACS41] CLOUDSTACK-2463 Patch?

[Jessica Wang]

Chip,

Brian will provide the UI patch (to hide Advanced zone with Security Groups 
option from UI).

Jessica

-Original Message-
From: Chip Childers [mailto:chip.child...@sungard.com] 
Sent: Tuesday, May 14, 2013 11:09 AM
To: ; Jessica Wang
Subject: [ACS41] CLOUDSTACK-2463 Patch?

Jessica,

How's the UI patch you mentioned coming along?

Any ETA?

-chip

RE: Create View Question

[Jessica Wang]

Nitin,

I added volume_view to schema-410to420.sql first.


I added volume_view at line 718 ~ line 818:
---
Author: Jessica Wang 
#mailto:jessicaw...@apache.org
Author date:1 month ago (Tue Apr 23 11:23:49 2013)
Commit date:1 month ago (Tue Apr 23 13:01:55 2013)
Commit hash:35e2072660d20b538bf6929d9c68eecb16ac8318

CLOUDSTACK-2120: mixed zone management - extend listVolumes API to return zone 
type.

Contained in branches: master
Contained in no tag
---


Two days later, you added another duplicate volume_view at line 1571 ~ line 
1672:
---
Author: Nitin Mehta 
#mailto:nitin.me...@citrix.com
Author date:1 month ago (Thu Apr 25 00:11:46 2013)
Commit date:1 month ago (Thu Apr 25 05:59:57 2013)
Commit hash:d1642a489ce76e055d60b2caf3ccfe4bb136b745

=initial changes

Contained in branches: master
Contained in no tag
---


Please drop one of them.

Thank you.

Jessica


-Original Message-
From: Min Chen 
Sent: Thursday, May 30, 2013 9:57 AM
To: Nitin Mehta; dev@cloudstack.apache.org
Cc: Jessica Wang
Subject: Re: Create View Question

Please work with Jessica to consolidate the two views created by you two
to come up with a final volume_view.

Thanks
-min

On 5/30/13 6:46 AM, "Nitin Mehta"  wrote:

>Sorry for missing the mail. I would need the new volume view for my
>feature to work.
>
>On 24/05/13 1:45 AM, "Min Chen"  wrote:
>
>>It is related to this commit d1642a489ce76e055d60b2caf3ccfe4bb136b745.
>>Schema-410to420.sql should have one section to define the new volume_view
>>for 4.2.0. 
>>CC Nitin here to see if his new volume_view should be used or the one
>>before his commit in this file.
>>
>>THanks
>>-min
>>
>>
>>On 5/23/13 12:50 PM, "Mike Tutkowski" 
>>wrote:
>>
>>>Hi,
>>>
>>>I've added a few fields (min, max, burst IOPS) to two tables and - in
>>>the
>>>process - noticed the following view is dropped and created twice:
>>>
>>>DROP VIEW IF EXISTS `cloud`.`volume_view`;
>>>CREATE VIEW `cloud`.`volume_view` AS
>>>
>>>I assume this is a bug and have removed (in my sandbox) the
>>>first occurrence.
>>>
>>>If anyone knows of a reason why we want to keep this code as is, please
>>>let
>>>me know as this change will otherwise be submitted when I submit my code
>>>for review tomorrow or early next week.
>>>
>>>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<http://solidfire.com/solution/overview/?video=play>
>>>**
>>
>

RE: form for createNetworkACL in ui passes label name instead of contents

[Jessica Wang]

Daan,

Which branch did you find the bug, 4.3 branch, 4.3-forward branch or master 
branch?

Jessica

-Original Message-
From: Alena Prokharchyk 
Sent: Tuesday, March 11, 2014 9:49 AM
To: dev@cloudstack.apache.org; Jessica Wang
Subject: Re: form for createNetworkACL in ui passes label name instead of 
contents

Jessica, can you help Daan?

-Alena.

On 3/11/14, 6:52 AM, "Daan Hoogland"  wrote:

>H,
>
>chasing a bug concerning cidr list length in acl creation I found that
>the form for adding acl list rules passes 'label.allow' instead of
>'allow' to the command being send. seams like someone did a halve
>checkin. I am looking how to fix it but unfamiliar in this terrain so
>any hints are usefull.
>
>this is master
>-- 
>Daan

RE: form for createNetworkACL in ui passes label name instead of contents

[Jessica Wang]

Daan,

Never mind. You did mention it's in master branch.
Will fix it.

Jessica

-Original Message-
From: Jessica Wang [mailto:jessica.w...@citrix.com] 
Sent: Tuesday, March 11, 2014 10:05 AM
To: daan.hoogl...@gmail.com
Cc: Alena Prokharchyk; dev@cloudstack.apache.org; Brian Federle; Stephen Turner
Subject: RE: form for createNetworkACL in ui passes label name instead of 
contents

Daan,

Which branch did you find the bug, 4.3 branch, 4.3-forward branch or master 
branch?

Jessica

-Original Message-
From: Alena Prokharchyk 
Sent: Tuesday, March 11, 2014 9:49 AM
To: dev@cloudstack.apache.org; Jessica Wang
Subject: Re: form for createNetworkACL in ui passes label name instead of 
contents

Jessica, can you help Daan?

-Alena.

On 3/11/14, 6:52 AM, "Daan Hoogland"  wrote:

>H,
>
>chasing a bug concerning cidr list length in acl creation I found that
>the form for adding acl list rules passes 'label.allow' instead of
>'allow' to the command being send. seams like someone did a halve
>checkin. I am looking how to fix it but unfamiliar in this terrain so
>any hints are usefull.
>
>this is master
>-- 
>Daan

RE: form for createNetworkACL in ui passes label name instead of contents

[Jessica Wang]

Daan,

I just fixed in master branch.
Please try it.

Thank you.

Jessica

-Original Message-
From: Jessica Wang 
Sent: Tuesday, March 11, 2014 10:16 AM
To: daan.hoogl...@gmail.com
Cc: Alena Prokharchyk; Brian Federle; Stephen Turner; dev@cloudstack.apache.org
Subject: RE: form for createNetworkACL in ui passes label name instead of 
contents

Daan,

Never mind. You did mention it's in master branch.
Will fix it.

Jessica

-Original Message-
From: Jessica Wang [mailto:jessica.w...@citrix.com] 
Sent: Tuesday, March 11, 2014 10:05 AM
To: daan.hoogl...@gmail.com
Cc: Alena Prokharchyk; dev@cloudstack.apache.org; Brian Federle; Stephen Turner
Subject: RE: form for createNetworkACL in ui passes label name instead of 
contents

Daan,

Which branch did you find the bug, 4.3 branch, 4.3-forward branch or master 
branch?

Jessica

-Original Message-
From: Alena Prokharchyk 
Sent: Tuesday, March 11, 2014 9:49 AM
To: dev@cloudstack.apache.org; Jessica Wang
Subject: Re: form for createNetworkACL in ui passes label name instead of 
contents

Jessica, can you help Daan?

-Alena.

On 3/11/14, 6:52 AM, "Daan Hoogland"  wrote:

>H,
>
>chasing a bug concerning cidr list length in acl creation I found that
>the form for adding acl list rules passes 'label.allow' instead of
>'allow' to the command being send. seams like someone did a halve
>checkin. I am looking how to fix it but unfamiliar in this terrain so
>any hints are usefull.
>
>this is master
>-- 
>Daan

RE: Resetting a VM is broken?

[Jessica Wang]

> [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"
>

RE: Resetting a VM is broken?

[Jessica Wang]

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<mailto: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<mailto: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<mailto: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<mailto: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<mailto:alena.prokharc...@citrix.com>> wrote:
>>>>>
>>>>>> don¹t see ³Reset Vm² option in UI; do you mean ³Reboot instance²?
>>>>>>

RE: Resetting a VM is broken?

[Jessica Wang]

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<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<mailto: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<mailto: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<mailto: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<mailto: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<mailto:mike.tutkow...@solidfire.com>> wrote:
>>>>
>>&

RE: Resetting a VM is broken?

[Jessica Wang]

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<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<mailto: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<mailto: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<mailto: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 diff

RE: Resetting a VM is broken?

[Jessica Wang]

+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?

[Jessica Wang]

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?

[Jessica Wang]

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

RE: Resetting a VM is broken?

[Jessica Wang]

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<mailto:n...@li.nux.ro>]
Sent: Thursday, March 20, 2014 2:04 PM
To: dev@cloudstack.apache.org<mailto: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<http://www.nux.ro>



--
Mike Tutkowski
Senior CloudStack Developer, SolidFire Inc.
e: mike.tutkow...@solidfire.com<mailto:mike.tutkow...@solidfire.com>
o: 303.746.7302
Advancing the way the world uses the 
cloud<http://solidfire.com/solution/overview/?video=play>(tm)

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

[Jessica Wang]

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: [VOTE] Apache CloudStack 4.3.0 (ninth round) - CLOUDSTACK-6266 Missing "Accounts" menu text as well as the entire menu itself

[Jessica Wang]

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

[Jessica Wang]

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: GRE isolation - no in service upgrade (4.1.1 to 4.3.0) - Is your zone an Advanced zone or Basic zone?

[Jessica Wang]

Florin,

Is your zone an Advanced zone or Basic zone?

Jessica

-Original Message-
From: Alena Prokharchyk 
Sent: Friday, March 21, 2014 11:53 AM
To: dev@cloudstack.apache.org; Florin Dumitrascu; Jessica Wang
Cc: Nguyen Anh Tu (t...@apache.org); Murali Reddy
Subject: Re: GRE isolation - no in service upgrade (4.1.1 to 4.3.0)

Florin, you have to add the provider to the physical network first, and
then enable it. To add a provider to physical network, use
addNetworkServiceProvider. To enable it after, use
updateNetworkServiceProvider
. Not sure why our UI doesn¹t have this functionality enabled. Jessica,
can you check out if the UI supports adding physical network providers,
and under what conditions?

Thanks,
Alena.


On 3/21/14, 11:47 AM, "Florin Dumitrascu"
 wrote:

>Hi,
>
>I have successfully tested GRE isolation with CS 4.3.0 RC8 installed from
>scratch on a minimal setup.
>
>I have moved then on to upgrading a more complex lab setup from CS 4.1.1
>to CS 4.3.0 RC9.
>I have followed the guidelines here for doing the upgrade:
>http://apache-cloudstack-release-notes.readthedocs.org/en/latest/rnotes.ht
>ml#upgrade-from-4-1-x-to-4-3
>
>Once CS was back up and running, I have created an OVS network offering
>using the GUI fix up from
>https://issues.apache.org/jira/browse/CLOUDSTACK-6162
>
>I tried then to enable the OVS service provider on the physical network,
>but discovered that no such provider is created.
>None in the GUI:
>http://imgur.com/ar8c7sX
>
>And none in the database:
>http://imgur.com/MsIdYrw
>
>So this means I pretty much need to re-configure the whole zone from
>scratch, since I do not know of another way to change the physical
>networks.
>
>If GRE is to be used in the production, this is a major drawback.
>
>Any thoughts ?
>
>Best Regards,
>Florin
>
>
>IMPORTANT NOTE: The information in this e-mail (and any attachments) is
>confidential. The contents may not be disclosed or used by anyone other
>than the addressee. If you are not the intended recipient, please notify
>the sender immediately or telephone: +353 (0)1 6204700. We cannot accept
>any responsibility for the accuracy or completeness of this message as it
>has been transmitted over a public network. If you suspect that the
>message may have been intercepted or amended, please call the sender.

RE: GRE isolation - no in service upgrade (4.1.1 to 4.3.0) - Is your zone an Advanced zone or Basic zone? (2)

[Jessica Wang]

Florin, 
UI doesn't show OVS service provider because database doesn't have OVS service 
provider. 
The reasons might be:
(1) You are using oss build (should be using noredist build).
(2) Your zone is a Basic zone (OVS service provider is only supported in 
Advanced zone)


Murali,
Is there other possibility?


Jessica

-Original Message-----
From: Jessica Wang 
Sent: Friday, March 21, 2014 1:15 PM
To: Alena Prokharchyk; Florin Dumitrascu
Cc: Nguyen Anh Tu (t...@apache.org); Murali Reddy; dev@cloudstack.apache.org
Subject: RE: GRE isolation - no in service upgrade (4.1.1 to 4.3.0) - Is your 
zone an Advanced zone or Basic zone?

Florin,

Is your zone an Advanced zone or Basic zone?

Jessica

-Original Message-
From: Alena Prokharchyk 
Sent: Friday, March 21, 2014 11:53 AM
To: dev@cloudstack.apache.org; Florin Dumitrascu; Jessica Wang
Cc: Nguyen Anh Tu (t...@apache.org); Murali Reddy
Subject: Re: GRE isolation - no in service upgrade (4.1.1 to 4.3.0)

Florin, you have to add the provider to the physical network first, and
then enable it. To add a provider to physical network, use
addNetworkServiceProvider. To enable it after, use
updateNetworkServiceProvider
. Not sure why our UI doesn¹t have this functionality enabled. Jessica,
can you check out if the UI supports adding physical network providers,
and under what conditions?

Thanks,
Alena.


On 3/21/14, 11:47 AM, "Florin Dumitrascu"
 wrote:

>Hi,
>
>I have successfully tested GRE isolation with CS 4.3.0 RC8 installed from
>scratch on a minimal setup.
>
>I have moved then on to upgrading a more complex lab setup from CS 4.1.1
>to CS 4.3.0 RC9.
>I have followed the guidelines here for doing the upgrade:
>http://apache-cloudstack-release-notes.readthedocs.org/en/latest/rnotes.ht
>ml#upgrade-from-4-1-x-to-4-3
>
>Once CS was back up and running, I have created an OVS network offering
>using the GUI fix up from
>https://issues.apache.org/jira/browse/CLOUDSTACK-6162
>
>I tried then to enable the OVS service provider on the physical network,
>but discovered that no such provider is created.
>None in the GUI:
>http://imgur.com/ar8c7sX
>
>And none in the database:
>http://imgur.com/MsIdYrw
>
>So this means I pretty much need to re-configure the whole zone from
>scratch, since I do not know of another way to change the physical
>networks.
>
>If GRE is to be used in the production, this is a major drawback.
>
>Any thoughts ?
>
>Best Regards,
>Florin
>
>
>IMPORTANT NOTE: The information in this e-mail (and any attachments) is
>confidential. The contents may not be disclosed or used by anyone other
>than the addressee. If you are not the intended recipient, please notify
>the sender immediately or telephone: +353 (0)1 6204700. We cannot accept
>any responsibility for the accuracy or completeness of this message as it
>has been transmitted over a public network. If you suspect that the
>message may have been intercepted or amended, please call the sender.

RE: GRE isolation - no in service upgrade (4.1.1 to 4.3.0) - Is your zone an Advanced zone or Basic zone? (2)

[Jessica Wang]

> [Alena] Not exactly like that. 
> [Alena] None of the providers are added to the physical network by default if 
> execute createPhysicalNetwork call via API. 
> [Alena] Our CS UI does this job - adding the providers to the network - for 
> you by calling addNetworkServiceProvider call. 

Actually, OVS provider is an exception.
UI doesn't do the job because server-side already does the job.
When you create an Advanced zone in 4.3 code, server-side will automatically 
add OVS provider to its physical network.
However, since your zone was created in 4.1 code and upgraded to 4.3, 
server-side won't automatically add OVS provider to its physical network.

Murali, please confirm.



-Original Message-
From: Alena Prokharchyk 
Sent: Friday, March 21, 2014 2:44 PM
To: Florin Dumitrascu; Jessica Wang; Murali Reddy; Florin Dumitrascu
Cc: Nguyen Anh Tu (t...@apache.org); dev@cloudstack.apache.org
Subject: Re: GRE isolation - no in service upgrade (4.1.1 to 4.3.0) - Is your 
zone an Advanced zone or Basic zone? (2)



On 3/21/14, 2:34 PM, "Florin Dumitrascu"
 wrote:

>Hi,
>
>Alena, my assumption is that the Ovs provider is created when you create
>the physical network with GRE isolation (if someone can confirm ...).
>When I configured CS RC8 from scratch, I could see the provider and
>enable it in the GUI.

Not exactly like that. None of the providers are added to the physical
network by default if execute createPhysicalNetwork call via API. Our CS
UI does this job - adding the providers to the network - for you by
calling addNetworkServiceProvider call.



>But when I have upgraded from CS 4.1.1 to 4.3.0 RC9, I have preserved the
>existing configuration with the existing physical network.
>So my assumption is that the physical network was not updated with the
>OVS provider (such a provider was not needed in CS 4.1.1).

So while you were on 4.1.1, GRE isolation was disabled? Did you enable it
on 4.3? If there is a way to enable new isolation on the physical network,
on my opinion - the UI should perform the background call and add all the
providers associated with this option, to the physical network. So it
would be a UI issue.

Or the case was the following - the GRE isolation was enabled on your
network while on 4.1.1, but new provider - OVS - was added in 4.3. And
this provider wasn't added to existing physical networks during the
upgrade. Then its a database upgrade bug.


Please confirm which one from the above is correct.

>
>Jessica, I am building CentOS RPM packages from the RC source, using
>"package.sh" script in the source packaging folder. Not aware about the
>difference between "oss" and "noredist".
>Also, my setup is for an advanced zone.
>
>Kind Regards,
>Florin
>
>
>
>-Original Message-
>From: Jessica Wang [mailto:jessica.w...@citrix.com]
>Sent: Friday, March 21, 2014 8:28 PM
>To: Florin Dumitrascu; Murali Reddy
>Cc: Nguyen Anh Tu (t...@apache.org); dev@cloudstack.apache.org; Alena
>Prokharchyk
>Subject: RE: GRE isolation - no in service upgrade (4.1.1 to 4.3.0) - Is
>your zone an Advanced zone or Basic zone? (2)
>
>Florin,
>UI doesn't show OVS service provider because database doesn't have OVS
>service provider.
>The reasons might be:
>(1) You are using oss build (should be using noredist build).
>(2) Your zone is a Basic zone (OVS service provider is only supported in
>Advanced zone)
>
>
>Murali,
>Is there other possibility?
>
>
>Jessica
>
>-Original Message-
>From: Jessica Wang
>Sent: Friday, March 21, 2014 1:15 PM
>To: Alena Prokharchyk; Florin Dumitrascu
>Cc: Nguyen Anh Tu (t...@apache.org); Murali Reddy;
>dev@cloudstack.apache.org
>Subject: RE: GRE isolation - no in service upgrade (4.1.1 to 4.3.0) - Is
>your zone an Advanced zone or Basic zone?
>
>Florin,
>
>Is your zone an Advanced zone or Basic zone?
>
>Jessica
>
>-Original Message-
>From: Alena Prokharchyk
>Sent: Friday, March 21, 2014 11:53 AM
>To: dev@cloudstack.apache.org; Florin Dumitrascu; Jessica Wang
>Cc: Nguyen Anh Tu (t...@apache.org); Murali Reddy
>Subject: Re: GRE isolation - no in service upgrade (4.1.1 to 4.3.0)
>
>Florin, you have to add the provider to the physical network first, and
>then enable it. To add a provider to physical network, use
>addNetworkServiceProvider. To enable it after, use
>updateNetworkServiceProvider
>. Not sure why our UI doesn¹t have this functionality enabled. Jessica,
>can you check out if the UI supports adding physical network providers,
>and under what conditions?
>
>Thanks,
>Alena.
>
>
>On 3/21/14, 11:47 AM, "Florin Dumitrascu"
> wrote:
>
>>Hi,
>>
>>I have successfully tested GRE isolation with CS 4.3.0 RC8 inst

RE: GRE isolation - no in service upgrade (4.1.1 to 4.3.0) - Is your zone an Advanced zone or Basic zone? (2)

[Jessica Wang]

+1


-Original Message-
From: Alena Prokharchyk 
Sent: Friday, March 21, 2014 4:18 PM
To: Jessica Wang; Florin Dumitrascu; Murali Reddy
Cc: Nguyen Anh Tu (t...@apache.org); dev@cloudstack.apache.org
Subject: Re: GRE isolation - no in service upgrade (4.1.1 to 4.3.0) - Is your 
zone an Advanced zone or Basic zone? (2)

Then its a DB upgrade bug. If the GRE isolation is supported on the
network in 4.1.1, DB upgrade should have inserted the provider to physical
network.

On 3/21/14, 3:51 PM, "Jessica Wang"  wrote:

>> [Alena] Not exactly like that.
>> [Alena] None of the providers are added to the physical network by
>>default if execute createPhysicalNetwork call via API.
>> [Alena] Our CS UI does this job - adding the providers to the network -
>>for you by calling addNetworkServiceProvider call.
>
>Actually, OVS provider is an exception.
>UI doesn't do the job because server-side already does the job.
>When you create an Advanced zone in 4.3 code, server-side will
>automatically add OVS provider to its physical network.
>However, since your zone was created in 4.1 code and upgraded to 4.3,
>server-side won't automatically add OVS provider to its physical network.
>
>Murali, please confirm.
>
>
>
>-Original Message-
>From: Alena Prokharchyk
>Sent: Friday, March 21, 2014 2:44 PM
>To: Florin Dumitrascu; Jessica Wang; Murali Reddy; Florin Dumitrascu
>Cc: Nguyen Anh Tu (t...@apache.org); dev@cloudstack.apache.org
>Subject: Re: GRE isolation - no in service upgrade (4.1.1 to 4.3.0) - Is
>your zone an Advanced zone or Basic zone? (2)
>
>
>
>On 3/21/14, 2:34 PM, "Florin Dumitrascu"
> wrote:
>
>>Hi,
>>
>>Alena, my assumption is that the Ovs provider is created when you create
>>the physical network with GRE isolation (if someone can confirm ...).
>>When I configured CS RC8 from scratch, I could see the provider and
>>enable it in the GUI.
>
>Not exactly like that. None of the providers are added to the physical
>network by default if execute createPhysicalNetwork call via API. Our CS
>UI does this job - adding the providers to the network - for you by
>calling addNetworkServiceProvider call.
>
>
>
>>But when I have upgraded from CS 4.1.1 to 4.3.0 RC9, I have preserved the
>>existing configuration with the existing physical network.
>>So my assumption is that the physical network was not updated with the
>>OVS provider (such a provider was not needed in CS 4.1.1).
>
>So while you were on 4.1.1, GRE isolation was disabled? Did you enable it
>on 4.3? If there is a way to enable new isolation on the physical network,
>on my opinion - the UI should perform the background call and add all the
>providers associated with this option, to the physical network. So it
>would be a UI issue.
>
>Or the case was the following - the GRE isolation was enabled on your
>network while on 4.1.1, but new provider - OVS - was added in 4.3. And
>this provider wasn't added to existing physical networks during the
>upgrade. Then its a database upgrade bug.
>
>
>Please confirm which one from the above is correct.
>
>>
>>Jessica, I am building CentOS RPM packages from the RC source, using
>>"package.sh" script in the source packaging folder. Not aware about the
>>difference between "oss" and "noredist".
>>Also, my setup is for an advanced zone.
>>
>>Kind Regards,
>>Florin
>>
>>
>>
>>-Original Message-
>>From: Jessica Wang [mailto:jessica.w...@citrix.com]
>>Sent: Friday, March 21, 2014 8:28 PM
>>To: Florin Dumitrascu; Murali Reddy
>>Cc: Nguyen Anh Tu (t...@apache.org); dev@cloudstack.apache.org; Alena
>>Prokharchyk
>>Subject: RE: GRE isolation - no in service upgrade (4.1.1 to 4.3.0) - Is
>>your zone an Advanced zone or Basic zone? (2)
>>
>>Florin,
>>UI doesn't show OVS service provider because database doesn't have OVS
>>service provider.
>>The reasons might be:
>>(1) You are using oss build (should be using noredist build).
>>(2) Your zone is a Basic zone (OVS service provider is only supported in
>>Advanced zone)
>>
>>
>>Murali,
>>Is there other possibility?
>>
>>
>>Jessica
>>
>>-Original Message-
>>From: Jessica Wang
>>Sent: Friday, March 21, 2014 1:15 PM
>>To: Alena Prokharchyk; Florin Dumitrascu
>>Cc: Nguyen Anh Tu (t...@apache.org); Murali Reddy;
>>dev@cloudstack.apache.org
>>Subject: RE: GRE isolation - no in service upgrade (4.1.1 to 4.3.0) - Is
>>your zone an Advanced zone or Basic zone?
>>
>>Florin,
>>
>>Is your zone an

[ACS44] cherry pick CLOUDSTACK-6477

[Jessica Wang]

Hi Hugo/Daan,

Would you please cherry-pick following commit from 4.4-forward branch to 4.4 
branch?

Commit: 62cac4f645205d590cbdd7c1102cace46034834c

CLOUDSTACK-6477: UI: Load Balancing - add VMs fails => error "Unable to decode 
parameter vmidipmap[0].vmip[]; if specifying an object array, please use 
parameter[index].field=XXX, ~ "

Thanks

Jessica

[ACS4.4] Cherry pick for CLOUDSTACK-6483

[Jessica Wang]

Hugo/Daan,



Could you please cherry-pick the following commit from 4.4-forward to 4.4 
branch?



Please cherry-pick Brian's 3 commits in the email below, then cherry-pick mine:



Commit hash:d5079e9cfa54a004a91295b1b2f24d2308e3000b

CLOUDSTACK- 6483: [UI-Loading balancing]Multiple UI issues while assigning the 
VM to LB rule.


Thank you.



Jessica


From: Brian Federle
Sent: Friday, May 02, 2014 10:38 AM
To: dev@cloudstack.apache.org
Cc: Jessica Wang
Subject: [ACS4.4] Cherry pick for CLOUDSTACK-6483

Please cherry-pick 4.4-forward commits for CLOUDSTACK-6483 (in this order):

0b03609c45ecb5b4525e6a7b5216c70032d94a39
7daabf6515509dc276b968c6ca042cf964a328da
430d14b67608039159403036dae3dc7af1e590f5

Thank you,
Brian

[ACS44] cherry pick CLOUDSTACK-6379

[Jessica Wang]

Hi Hugo/Daan,

Could you please cherry-pick following commit to 4.4 branch?

Commit hash:f4c726d7b842636e665ba4ca3616688e2b26192b

CLOUDSTACK-6379: UI:MS: Unable to create a user type Admin under a domain; No 
API being fired

Thanks,

Jessica

Re: Review Request 21221: CLOUDSTACK-6606: Fix: create network offering dailog box has greyed out (not selectable) providers for the connectivity service.

[Jessica Wang]

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

Ship it!


Ship It!

- Jessica Wang


On May 8, 2014, 3:39 p.m., Gabor Apati-Nagy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/21221/
> ---
> 
> (Updated May 8, 2014, 3:39 p.m.)
> 
> 
> Review request for cloudstack, Brian Federle, Jessica Wang, and Murali Reddy.
> 
> 
> Bugs: CLOUDSTACK-6606
> https://issues.apache.org/jira/browse/CLOUDSTACK-6606
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Add Network Offering page: Some providers are disabled based on the selection 
> state of the VPC checkbox. However, this should not be done for Connectivity 
> service. This patch fixes this.
> 
> 
> Diffs
> -
> 
>   ui/scripts/configuration.js 1b82188 
> 
> Diff: https://reviews.apache.org/r/21221/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Gabor Apati-Nagy
> 
>

[ACS44] cherry pick CLOUDSTACK-6606

[Jessica Wang]

Hi Hugo/Daan,

Could you please cherry-pick following commit to 4.4 branch?

Commit hash:0d7ddc4337568939f47de875f1a03f39b54e3b30

CLOUDSTACK-6606: create network offering dailog box has greyed out (not 
selectable) providers for the connectivity service.

Thanks,

Jessica

Re: Review Request 21109: [UI] New Zones tab for Templates and ISOs

[Jessica Wang]

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

Ship it!


Ship It!

- Jessica Wang


On May 6, 2014, 10:50 a.m., Gabor Apati-Nagy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/21109/
> ---
> 
> (Updated May 6, 2014, 10:50 a.m.)
> 
> 
> Review request for cloudstack, Brian Federle and Jessica Wang.
> 
> 
> Bugs: CLOUDSTACK-6565
> https://issues.apache.org/jira/browse/CLOUDSTACK-6565
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> [UI] New Zones tab for Templates and ISOs
> 
> 
> Diffs
> -
> 
>   client/WEB-INF/classes/resources/messages.properties eff2c3e 
>   ui/css/cloudstack3.css cb9fa35 
>   ui/dictionary.jsp 9cc030a 
>   ui/scripts/templates.js 67cc2fb 
> 
> Diff: https://reviews.apache.org/r/21109/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Gabor Apati-Nagy
> 
>

[ACS44] cherry pick CLOUDSTACK-6602 ([UI] createNetworkACL API action param value passed incorrectly)

[Jessica Wang]

Daan,


Could you please cherry-pick following commit from 4.4-forward to 4.4 branch?



Commit hash:95b7330d5696aa150f1845b76c6021885c919aea



CLOUDSTACK-6602: [UI] createNetworkACL API action param value passed incorrectly





Thank you.



Jessica

RE: [ACS4.4] i18n problems in Add Primary Storage dialog

[Jessica Wang]

Vetrivel,
Mike has reviewed it.

Mike,
thanks a lot!

Jessica

From: Vetrivel Chinnasamy
Sent: Thursday, June 26, 2014 5:07 AM
To: Mike Tutkowski; dev@cloudstack.apache.org
Cc: Brian Federle; Alena Prokharchyk; Jessica Wang
Subject: RE: [ACS4.4] i18n problems in Add Primary Storage dialog

Hi Mike,

Kindly accept my apology for the issue. I have used script to identify certain 
pattern of hardcoded strings and fixed them. Some exceptions like this got 
escaped from my unit testing also.

I have reverted the changes as suggested and created a patch for review.

Brian/Jessica, Could you please do the needful?

Review Request #23008<https://reviews.apache.org/r/23008/>.

Kindly accept my apology for inconvenience caused because of this issue.

Thanks.

Regards,
Vetri

P.S: I am reviewing again the externalization code changes committed in the 
past to avoid these type of issues.

From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: 26 June 2014 03:56
To: dev@cloudstack.apache.org; Vetrivel Chinnasamy
Cc: Brian Federle; Alena Prokharchyk; Jessica Wang
Subject: Re: [ACS4.4] i18n problems in Add Primary Storage dialog

By the way, what I was referring to with my proposed hack was just to fix the 
two situations ("SR Name-Label" and "Path") by hardcoding the English back in.

On Wed, Jun 25, 2014 at 2:34 PM, Mike Tutkowski 
mailto:mike.tutkow...@solidfire.com>> wrote:
It looks like these issues were introduced in 
182c31899bb353eac66a43ca4e81117c4fd06332 by vetrivelc with regards to 
externalizing hardcoded strings.

My guess is that this substitution was done in an automated fashion and some 
unintended consequences of the substitution logic occurred.

vetrivelc - Any chance you could take a look at these issues and decide on a 
way for us to proceed? This is in 4.4 code (first RC currently planned for this 
Friday), so it would be awesome if we could resolve these quickly.

One hack would be for us to just hard code the English words back, but of 
course these labels would then be incorrect in other languages (unless, of 
course, by coincidence the words happened to be the same in each lang).

Thanks!


 
$form.find('.form-item[rel=path]').css('display', 'inline-block');

 var $required = 
$form.find('.form-item[rel=path]').find(".name").find("label span");

-
$form.find('.form-item[rel=path]').find(".name").find("label").text("Path:").prepend($required);

+
$form.find('.form-item[rel=path]').find(".name").find("label").text('label.path'+":").prepend($required);



 
$form.find('.form-item[rel=smbUsername]').hide();

 
$form.find('.form-item[rel=smbPassword]').hide();

@@ -15414,7 +15414,7 @@



 
$form.find('.form-item[rel=path]').css('display', 'inline-block');

 var $required = 
$form.find('.form-item[rel=path]').find(".name").find("label span");

-
$form.find('.form-item[rel=path]').find(".name").find("label").text("Path:").prepend($required);

+
$form.find('.form-item[rel=path]').find(".name").find("label").text('label.path'+":").prepend($required);



 
$form.find('.form-item[rel=smbUsername]').css('display', 'inline-block');

 
$form.find('.form-item[rel=smbPassword]').css('display', 'inline-block');

@@ -15441,7 +15441,7 @@



 
$form.find('.form-item[rel=path]').css('display', 'inline-block');

 var $required = 
$form.find('.form-item[rel=path]').find(".name").find("label span");

-
$form.find('.form-item[rel=path]').find(".name").find("label").text("Path:").prepend($required);

+
$form.find('.form-item[rel=path]').find(".name").find("label").text('label.path'+":").prepend($required);



  

Re: Review Request 22019: CLOUDSTACK-6732: [OVS][UI] Network Service Providers page displays two ovs providers

[Jessica Wang]

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

Ship it!


Ship It!

- Jessica Wang


On May 29, 2014, 2:16 p.m., Gabor Apati-Nagy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/22019/
> ---
> 
> (Updated May 29, 2014, 2:16 p.m.)
> 
> 
> Review request for cloudstack, Brian Federle and Jessica Wang.
> 
> 
> Bugs: CLOUDSTACK-6732
> https://issues.apache.org/jira/browse/CLOUDSTACK-6732
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fixed: CLOUDSTACK-6732: [OVS][UI] Network Service Providers page displays two 
> ovs providers
> 
> 
> Diffs
> -
> 
>   ui/scripts/system.js 67e01f1 
> 
> Diff: https://reviews.apache.org/r/22019/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Gabor Apati-Nagy
> 
>

Re: Review Request 21817: [UI] New Zones tab for Templates and ISOs

[Jessica Wang]

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

Ship it!


Ship It!

- Jessica Wang


On May 22, 2014, 4:52 p.m., Gabor Apati-Nagy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/21817/
> ---
> 
> (Updated May 22, 2014, 4:52 p.m.)
> 
> 
> Review request for cloudstack and Jessica Wang.
> 
> 
> Bugs: CLOUDSTACK-6565
> https://issues.apache.org/jira/browse/CLOUDSTACK-6565
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> New diff with improved ui layout
> 
> 
> Diffs
> -
> 
>   ui/css/cloudstack3.css cb9fa35 
>   ui/dictionary.jsp 9cc030a 
>   ui/scripts/templates.js 67cc2fb 
> 
> Diff: https://reviews.apache.org/r/21817/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Gabor Apati-Nagy
> 
>

Unable to start SSVM in latest code of master branch: "Unable to start s-15-VM due to java.lang.NullPointerException at com.cloud.hypervisor.xen.resource.XenServer56FP1Resource.createVmFromTemplate(Xe

[Jessica Wang]

Hi,

My management server is unable to start SSVM in latest code of master branch.
Does anyone see the same error?


2013-10-23 15:02:25,287 WARN  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-2:ctx-2593db33) Unable to start s-15-VM due to
java.lang.NullPointerException
at 
com.cloud.hypervisor.xen.resource.XenServer56FP1Resource.createVmFromTemplate(XenServer56FP1Resource.java:196)
at 
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1635)
at 
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:557)
at 
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:59)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:187)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)


Thank you.

Jessica

Re: Review Request 15068: Change labels for VLAN to vNet

[Jessica Wang]

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

Ship it!


Ship It!

- Jessica Wang


On Nov. 1, 2013, 4:52 p.m., Chris Cameron wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15068/
> ---
> 
> (Updated Nov. 1, 2013, 4:52 p.m.)
> 
> 
> Review request for cloudstack, Brian Federle, Jessica Wang, Marcus Sorensen, 
> Pranav Saxena, and Toshiaki Hatano.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> We would like to change the labels for VLAN to vNet to make the term more 
> generic for VXLAN and VLAN. This relates to the work being done to add in 
> VXLAN support to Cloudstack.
> 
> 
> Diffs
> -
> 
>   client/WEB-INF/classes/resources/messages.properties 3210aca 
>   ui/dictionary.jsp 35cba22 
>   ui/scripts/network.js 12e5389 
>   ui/scripts/system.js 479883c 
> 
> Diff: https://reviews.apache.org/r/15068/diff/
> 
> 
> Testing
> ---
> 
> Checked through the GUI for changed elements.
> 
> 
> Thanks,
> 
> Chris Cameron
> 
>

Re: Review Request 15078: Fixed some html validation errors.

[Jessica Wang]

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

Ship it!


Ship It!

- Jessica Wang


On Nov. 5, 2013, 6:29 a.m., Rajani Karuturi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15078/
> ---
> 
> (Updated Nov. 5, 2013, 6:29 a.m.)
> 
> 
> Review request for cloudstack and Jessica Wang.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fixed some html validation errors.
> 
>  language tag in script is deprecated. used type
>  

RE: JavaScript Question - $isCustomizedIops.is(':checked')

[Jessica Wang]

Mike,

Your $isCustomizedIops is something like:


  
Custom disk iops
  
  

  
 

So, if you want to know whether the checkbox is checked or not, you should use  
"($isCustomizedIops.find('input[type=checkbox]').is(':checked')"  
instead of 
"($isCustomizedIops.is(':checked')" 

Jessica


-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] 
Sent: Wednesday, November 06, 2013 10:10 AM
To: dev@cloudstack.apache.org
Subject: Re: JavaScript Question

This is just a guess, but I'm thinking if the checkbox is not visible, then
":checked" always returns false (which would be weird).

I do make the checkbox visible before using ":checked", but it's possible
this visibility change doesn't take effect until after the event handler
finishes.

Any thoughts on this from people who do a lot of JavaScript (or anyone
else, of course). :)


$isCustomizedIops.css('display', 'inline-block');

if
($isCustomizedIops.is(':checked')) {
$minIops.hide();
$maxIops.hide();
} else {

$minIops.css('display', 'inline-block');

$maxIops.css('display', 'inline-block');
}


On Tue, Nov 5, 2013 at 10:50 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Hi,
>
> Does anyone know why this checkbox of mine always returns false?
>
> if ($isCustomizedIops.is(':checked')) {
> // do some stuff
> }
>
> That code is part of an event handler for a combobox (when the combobox
> changes to a certain state, I want to see if the checkbox that is revealed
> is in the checked state):
>
> args.$select.change(function() {
> var $isCustomizedIops = $form.find('.form-item[rel=isCustomizedIops]');
>
> if ($isCustomizedIops.is(':checked')) {
> // do some stuff
> }
> }
>
> The checkbox is set up like this:
>
> isCustomizedIops: {
> label: 'label.custom.disk.iops',
> docID:
> 'helpDiskOfferingCustomDiskIops',
> isBoolean: true,
> isReverse: true,
> isChecked: false
> },
>
> 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: Why is loginUrl parameter needed?

[Jessica Wang]

Demetrius,

> (3) Pass a "loginUrl" parameter to the login page which fills out the 
> g_loginResponse data structure.  

This is for an outside application(e.g. CloudPortal) to navigate into 
CloudStack UI without prompting credentials dialog (i.e.signle-sign-on).

e.g.
http://:8080/client/api?loginUrl=command=login&username=XXX&domainid=NNN×tamp=YYY&signature=


To get the single sign-on secret key, you must retrieve it from the CloudStack 
database under the configuration table for the key "security.singlesignon.key". 
Copy this key to the outside application, then pass a login request from the 
outside application to CloudStack as: 

http://:8080/client/api?loginUrl=command=login&username=XXX&domainid=NNN×tamp=YYY&signature=

The four parameters(domainId, username, timestamp, and signature) are required.

The timestamp parameter is simply the current system time in milliseconds. 
There is also a fault tolerance configurable value in the configuration table, 
"security.singlesignon.tolerance.millis" that can be changed to suit your 
preference. 
If the timestamp passed in as part of the login request differs from CloudStack 
Management Server time plus the fault tolerance time, the login request will 
fail.

Jessica


-Original Message-
From: Demetrius Tsitrelis [mailto:dtsitre...@live.com] 
Sent: Wednesday, December 04, 2013 10:10 AM
To: dev@cloudstack.apache.org
Subject: Why is loginUrl parameter needed?

In CloudStack, it seems that one can login via three methods:

(1) Connect to the API endpoint and use a login command with a user name and 
password.

(2) Connect to the API endpoint and use a login command with a user name and a 
signature based upon the "security.singlesignon.key" global setting.

(3) Pass a "loginUrl" parameter to the login page which fills out the 
g_loginResponse data structure.  

See $(document).ready() in cloud.core.callbacks.js in the ui/scripts directory.
It is that last option I am trying to understand.  What is the use case for 
this?  Are there examples of this parameter?
  

Re: Review Request 23884: Fixed CLOUDSTACK-5212: [UI]Need Support for the LXC for the Report sockets

[Jessica Wang]

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

Ship it!


Ship It!

- Jessica Wang


On July 24, 2014, 11:51 a.m., Rajani Karuturi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/23884/
> ---
> 
> (Updated July 24, 2014, 11:51 a.m.)
> 
> 
> Review request for cloudstack and Jessica Wang.
> 
> 
> Bugs: CLOUDSTACK-5212
> https://issues.apache.org/jira/browse/CLOUDSTACK-5212
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> added LXC to the list of hypervisors in js.
> 
> 
> Diffs
> -
> 
>   ui/scripts/system.js 9012580 
> 
> Diff: https://reviews.apache.org/r/23884/diff/
> 
> 
> Testing
> ---
> 
> manually tested that it shows up in the sockets page
> 
> 
> Thanks,
> 
> Rajani Karuturi
> 
>

Re: Review Request 23922: Fixed CLOUDSTACK-6980: UI for RegisterTemplate API does not expose requireshvm parameter

[Jessica Wang]

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

Ship it!


Ship It!

- Jessica Wang


On July 25, 2014, 9:58 a.m., Rajani Karuturi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/23922/
> ---
> 
> (Updated July 25, 2014, 9:58 a.m.)
> 
> 
> Review request for cloudstack and Jessica Wang.
> 
> 
> Bugs: CLOUDSTACK-6980
> https://issues.apache.org/jira/browse/CLOUDSTACK-6980
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> added requireshvm to the create form fields
> 
> 
> Diffs
> -
> 
>   client/WEB-INF/classes/resources/messages.properties 271ffec 
>   ui/dictionary.jsp beb082b 
>   ui/scripts/docs.js 2075e30 
>   ui/scripts/templates.js e12927c 
> 
> Diff: https://reviews.apache.org/r/23922/diff/
> 
> 
> Testing
> ---
> 
> manually tested register template
> 
> 
> Thanks,
> 
> Rajani Karuturi
> 
>

RE: [VOTE] git workflow

[Jessica Wang]

Exactly. This just shifts pain from one branch to another. 
I don't see any gains from this, either.
I vote "-1".

Jessica


-Original Message-
From: Min Chen [mailto:min.c...@citrix.com] 
Sent: Tuesday, August 05, 2014 11:27 AM
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] git workflow

Agree with Animesh. Didn't see any gains from this, we just shift pain
from one branch to another, so vote -1.

-min

On 8/2/14 9:50 PM, "Animesh Chaturvedi" 
wrote:

>+0
>
>While this protects master with only commits which are merges from
>release branch and keeps it clean but the issues that we have shift to
>develop branch. 
>
>
>> -Original Message-
>> From: Rajani Karuturi [mailto:rajani.karut...@citrix.com]
>> Sent: Thursday, July 31, 2014 3:28 AM
>> To: dev
>> Subject: [VOTE] git workflow
>> 
>> Hi All,
>> 
>> We had long discussions on the git flow.
>> I tried to capture the summary of it @
>> http://markmail.org/message/j5z7dxjcqxfkfhpj
>> This is updated on wiki @
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Git#Git-
>> ProposedGitflowbasedCheck-inProcess and is up for a vote:
>> 
>> Can you share your opinion on the proposal?
>> 
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>> 
>> 
>> Thanks,
>> ~Rajani
>> 
>> 
>

RE: [VOTE] Adapting git workflow for release branches

[Jessica Wang]

I agree with Edison.
I am -1 on this as well.


-Original Message-
From: Edison Su [mailto:edison...@citrix.com] 
Sent: Saturday, August 16, 2014 12:11 PM
To: dev
Subject: RE: [VOTE] Adapting git workflow for release branches

I agree with what Min said on thread: 
http://markmail.org/message/dqdlqu7phgijfelc, and not satisfied with your 
answer:
Currently we don't have a CI running continuously, no code review, it's too 
risky to let developer check in whatever commit they want into release branch. 
RM needs to have to control over what commit should be put into release branch 
and what should not, otherwise, we could get into a stage where no control on 
the quality.
How RM will do the control, that's something we could discuss. I know, current 
model is not scale, as RM needs to manually cherry pick commits into release 
branch. The way I thinking about, is all the commits put into release branch, 
must be put into review board, or gerrit, must be passed by CI and reviewers, 
then the commits can be put into release branch. 
For above reason, I am -1(binding) on your proposal for now until we solve the 
quality control problem. 

> -Original Message-
> From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
> Sent: Friday, August 15, 2014 3:25 AM
> To: dev
> Subject: [VOTE] Adapting git workflow for release branches
> 
> Hello everyone,
> 
> With reference to my proposal on changing our release-master commit flow
> [1], I would like to start a voting thread to decide on the adoption starting 
> 4.5
> release. Any opinion, ideas, modifications is welcome to help reach a
> consensus and improve our present situation.
> 
> Today's Friday so it will be only fair to extend the voting window to more
> than our usual 72 hours window.
> Therefore, we'll end this voting on Wednesday, 20 August 2014 at 18:00H
> UTC giving about 5 days of time for people to share what works and what
> does not. We'll stop anytime we've three -1s (binding).
> 
> Short summary:
> 
> - Base line protocol: Continuous changes from release/stable branches to
> master/unable branches
> - Get contributors more engaged with release branches by working (fixing
> bugs, docs etc.) on release branches first (and not on master)
> - Fixes on release branches are recommended (non strict enforcement) go
> via a hotfix/bugfix branch that get automatically tested by Jenkins, when
> they are green RMs get the changes to release branch
> 
> Long Summary of what we'll adopt: (I'm skipping writing them on wiki, as this
> may change/modify in this thread)
> 
> - Continuous flow of changes from stable branches to un-stables ones i.e.
> from release branches to master and from master to features etc. Use of
> merge -fast-forward is encourages over cherry-picking and -no-ff (no ff
> will create merge commit). This happens couple of times a day to ensure we
> get solid/robust changes from release branches (such as bugfixes etc.) on
> master, any conflicts will be resolved. If we do it continuously we'll also 
> save
> ourselves from a big conflict at the end of the release cycle and we'll also
> avoid missing/misplacing any commit when cherry-picking.
> 
> - After code freeze is declared and release branch is cut out, contributors
> work on fixing bugs and other changes (such as documentation,
> build/packaging fixes etc.) first on the release branch (and not master). This
> is not to restrict anyone working on master, features and other changes can
> keep landing on master as well. This is to encourage contributors to give
> more attention to release branches by at least fixing bugs on release
> branches first and not our current way where we fix it on master and ask
> RMs to cherry pick it to release branch.
> 
> - Changes to release branches can be done by pushing a bugfix/change
> branch and asking the RM to pick it up if they are tested. Our automated
> systems can perform checks on such branches too (starting with a suffix that
> can automatically trigger such builds/tests) and if everything is fine, RMs to
> land the changes to release branches.
> 
> - Nothing is written in stones, this should be change-able. And, this can only
> work if we all agree to follow this with 4.5
> 
> To make the best of this thread, please keep your reply short, constructive
> and to the point..
> Please share your opinion on this proposal with suitable reasons:
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> [1] http://markmail.org/message/ucixhhdbz3ajyv2a
> 
> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +41 779015219 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
> 
> 
> 
> Find out more about ShapeBlue and our range of CloudStack related services
> 
> IaaS Cloud Design & Build build//>
> CSForge - rapid IaaS deployment
> framework
> CloudStack Consulting
> Clou

RE: [VOTE] Adapting git workflow for release branches

[Jessica Wang]

My opinion is totally the same as Min's.


-Original Message-
From: Min Chen [mailto:min.c...@citrix.com] 
Sent: Tuesday, August 19, 2014 11:12 AM
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Adapting git workflow for release branches

I personally don't think introducing CI or gerrit or github pull request
will take away a committer's privilege to commit. If you are a stakeholder
who really care about your product, you will not be scared away by this
extra enforcement, this will actually make our cloudstack ecosystem better
and healthier, and will also benefit other contributors in the same
community. To me, this is not a punishment per se, your code is just not
directly committed in, and you can enhance it and commit later. We are not
even requesting for bug-free code, I know, that is not possible in
software world, but at least we should have some stableness in our code to
not block other peers. As far as I know, Linux has much better control
about what patch to be pulled in, which makes it much more stabler than
us. As for your traffic example, at least there we have DMV road test,
traffic light, traffic patrol infrastructure to have basic guard.
CI/gerrit are just like those basic enforcement infrastructure for
CloudStack development process.

I don't want this to become a two-person argument forever. I already
clearly explained my ideas and takes on this. Let's hear others.

Thanks
-min

On 8/19/14 10:55 AM, "Rohit Yadav"  wrote:

>tl;dr? hope you read it;
>
>On 19-Aug-2014, at 7:10 pm, Min Chen  wrote:
>
>> I will hesitate on this "No enforcement" approach in the flow. I bet
>>that
>> without some kind of enforcement, based on past experience, after one
>
>Stakeholder will always care. The system should be optimistic to allow
>things in and not to punish in advance.
>That’s how many scalable opensource project such as Linux, Firefox and
>our own Apache works (people over code that is).
>
>If you’ve any ideas please share. We’ve to find a “non-strict”
>enforcement to get best of all things and I don’t have a solution right
>now to suggest.
>
>“Strict enforcement” won’t be scalable anyway, hackers always find way
>around gaming the system.
>
>Unicorns, Santas and bug-less code perhaps don’t exist IMHO so may never
>guarantee code quality but only improve over time. Even things like
>pacemakers, realtime systems used in mining, surgery, aerospace, mars
>rover etc; openssl (heartbleed) have bugs and issues. This is not to say
>that we should not have code reviews, other processes and automated
>build/CI/smoke-tests are “not” needed, they are needed but they “should"
>come only gradually. I also think improvements are better severed in
>small nibbles than a one big main course.
>
>In my past startup, last year, I helped them introduce a non-strict code
>reviewing process and what it did was not to scare anyone but slowly and
>gradually everyone started using code reviews and that became a process
>now. What I learnt was that people like slow changes (don’t put the frog
>in hot water), processes should be effortless and invisible (you don’t
>have to think much on how to do it, like say driving a car or touch
>typing on keyboard), and a cultural change is best implemented without
>enforcement. For example, in a many countries people don’t honk i.e. the
>culture even if no one gets a ticket for honking which is my point we
>need an understanding, a guideline, a protocol to implement a culture not
>an “enforcement” or team of police.
>
>> release, we will come together to discuss flaw in our flow again:) Sorry
>> if I am too pessimistic on this.
>
>To introduce an enforcement would mean take away a committer’s privilege
>to commit. If you have some ideas start a thread.
>
>IMO “pessimistic approach" is not a good approach — you don't ban or
>restrict people driving cars just because of accidents or ban the
>Internet just because there are things you don’t like on it, or put
>people in jail just because they can commit a crime in future. I would
>want an open and transparent workflow/protocol/guideline that is
>agreeable to all/most of us and that does not impose any restrictions.
>
>Cheers.
>
>>
>> Thanks
>> -min
>>
>> On 8/19/14 10:00 AM, "Rohit Yadav"  wrote:
>>
>>> Hi,
>>>
>>> On 19-Aug-2014, at 6:48 pm, Min Chen  wrote:
>>>
 In that case, we should call out this procedure

 If (you¹re a committer) {
 Go create a hotfix branch and ask RM to pick it up
 } else {
 Go upload your patch and get RM to review your request from
reviewboard
 }


 in your proposal. I don't want people to have a misunderstanding that
 with
 this proposal, RM is not needed anymore. Actually, RM is MORE
IMPORTANT
 with this proposal.
>>>
>>> Yes.
>>>
 Also, we should also call out the enforcement plan for this procedure.
>>>
>>> Subjective. All committers have privilege to commit so enforcement will
>>> be unnecessary, instead if you find an issue with anyon

ASF JIRA seems down?

[Jessica Wang]

hi,

ASF JIRA seems down?

Jessica

RE: UI blocker

[Jessica Wang]

> cosmetic issues are not blockers 

+1


-Original Message-
From: Brian Federle 
Sent: Friday, January 17, 2014 10:41 AM
To: dev@cloudstack.apache.org
Cc: Jessica Wang; Sonny Chhen
Subject: RE: UI blocker

Sorry, but cosmetic issues are not blockers :) It would only be a blockers if 
the functionality were NOT usable in any shape or form, for both testing and 
end use.

i.e. -- if the fields were completely missing or garbled in some way, I would 
agree that we can classify the bug as blocking release. Looking 'ugly', no -- I 
implemented the scrollbars because most times API keys, etc. are usually very 
long strings, causing overflow on some browsers and in most usability cases 
people are mainly needing to just copy/paste the values into other fields. It's 
not the most elegant solution I understand, but this is also a small facet of 
the whole UI experience.

I am going to ask everyone to PLEASE respect this when determining priority on 
UI bugs -- I know things like this are somewhat ugly, but there are only a 
small handful of full-time UI developers working on CloudStack and it makes our 
lives harder if everyone is marking trivial stuff as show-stoppers.

At any rate, if you still think this is a blocker, you can feel free to look 
into it yourself, in which case write a review request and I'll take a look at 
it.

-Brian

-Original Message-
From: Sebastien Goasguen [mailto:run...@gmail.com] 
Sent: Thursday, January 16, 2014 11:56 AM
To: Brian Federle
Cc: dev@cloudstack.apache.org; Jessica Wang
Subject: Re: UI blocker


On Jan 16, 2014, at 2:48 PM, Brian Federle  wrote:

>>> Did you happen to check the View Users page ? the api/secret keys display 
>>> is being truncated.
> 
> Yes, though to fix that I'll have to rework a bit of the detail view layout 
> to allow more flexible sizing for long strings. File that as a separate bug 
> for the next release and I'll take a look at it.

No, I will keep that as a blocker. it's worse than the previous UI, feel free 
to comment in the bug and grab it.

> 
> -Original Message-
> From: Sebastien Goasguen [mailto:run...@gmail.com] 
> Sent: Thursday, January 16, 2014 11:17 AM
> To: Brian Federle
> Cc: dev@cloudstack.apache.org; Jessica Wang
> Subject: Re: UI blocker
> 
> 
> On Jan 16, 2014, at 1:39 PM, Brian Federle  wrote:
> 
>> Don't see any issues in the screenshot you posted. The variation in font 
>> size and weight, color, etc. are used to show contrast between content and 
>> titles. Sorry but I do not see this as a blocker issue :) Though feel free 
>> to tweak the fonts yourself.
>> 
> 
> It looks strange to me, maybe that's just me. I see too many variations and 
> it's disturbing.
> 
> Did you happen to check the View Users page ? the api/secret keys display is 
> being truncated. 
> 
>> -Brian
>> 
>> -Original Message-
>> From: sebgoa [mailto:run...@gmail.com] 
>> Sent: Thursday, January 16, 2014 1:43 AM
>> To: dev@cloudstack.apache.org
>> Cc: Jessica Wang; Brian Federle
>> Subject: UI blocker
>> 
>> Hi, after testing 4.3 I entered a blocker due to UI issues:
>> https://issues.apache.org/jira/browse/CLOUDSTACK-5882
>> 
>> It would be good to discuss, 
>> 
>> thanks,
>> 
>> -Sebastien
> 

RE: VM instance view UI is broken in 4.3-forward (This is an API bug, not UI bug. )

[Jessica Wang]

t;: 1,
"virtualmachine": [
{
"id": "7729de44-4f1f-41d8-9315-b6276a20e74b",
"domainid": "2b818452-8864-11e3-8fd5-3c970e739c3e",
"created": "2014-01-28T14:54:14-0800",
"haenable": false,
"zoneid": "20d44407-ca39-4506-90ea-97105d02bf8b",
"hostid": "b3d14a6a-89c7-4f5e-8587-3501e85c1b05",
"hostname": "xs-jessica",
"templateid": "2aa1dfaa-8864-11e3-8fd5-3c970e739c3e",
"templatename": "CentOS 5.6(64-bit) no GUI (XenServer)",
"templatedisplaytext": "CentOS 5.6(64-bit) no GUI (XenServer)",
"passwordenabled": false,
"serviceofferingid": "27f17c9c-e4e8-4c3c-874f-41d9759db9e9",
"serviceofferingname": "Medium Instance",
"cpunumber": 1,
"cpuspeed": 1000,
"memory": 1024,
"cpuused": "3.12%",
"networkkbsread": 0,
"networkkbswrite": 0,
"diskkbsread": 0,
"diskkbswrite": 0,
"diskioread": 0,
"diskiowrite": 0,
"guestosid": "2aaa019e-8864-11e3-8fd5-3c970e739c3e",
"rootdevicetype": "ROOT",
"securitygroup": [],
"nic": [
{
"id": "2013cdfe-a4aa-4fd0-8253-d4eba82809df",
"networkid": "e80c1282-692f-42bd-a910-009c46379685",
"networkname": "deployvm-network1",
"netmask": "255.255.255.0",
"gateway": "10.1.1.1",
"ipaddress": "10.1.1.28",
"isolationuri": "vlan://1061",
"broadcasturi": "vlan://1061",
"traffictype": "Guest",
"type": "Isolated",
"isdefault": true,
"macaddress": "02:00:0d:3d:00:01"
}
],
"hypervisor": "XenServer",
"instancename": "i-2-3-VM",
"tags": [],
"affinitygroup": [],
"displayvm": true,
"isdynamicallyscalable": true
}
]
}
}


Jessica

-Original Message-
From: Koushik Das 
Sent: Monday, January 27, 2014 1:44 AM
To: 
Cc: Jessica Wang
Subject: Re: VM instance view UI is broken in 4.3-forward

The only UI related commit I see is 81a83b5b31f0a237ae56449c60350160915f28f8.
List VM API is working fine.

On 27-Jan-2014, at 2:26 PM, Koushik Das  wrote:

> I noticed that VM instance view is broken in UI. It works fine in 4.3 branch. 
> It worked till commit d31fa09c7e5bb04fcc4594c0352d9b91171e9d1a.
> 
> -Koushik

RE: [VOTE] Apache CloudStack 4.3.0 (second round) - unable to manage Firewall, Port Forwarding or Load Balancing rules via the UI, the interfaces no longer exist.

[Jessica Wang]

Geoff,

> I am unable to manage Firewall, Port Forwarding or Load Balancing rules via 
> the UI, the interfaces no longer exist.  

Are you referring to the Configuration tab in IP Address detail page?
It's under Guest Network section or VPC section?

e.g. Network > Guest Network > IP Addresses > click a SourceNAT IP, or a 
Non-SourceNAT IP > Configuration tab is missing here?

e.g. Network > VPC > Router > IP Addresses > click a SourceNAT IP, or a 
Non-SourceNAT IP > Configuration tab is missing here?

Jessica


-Original Message-
From: Geoff Higginbottom [mailto:geoff.higginbot...@shapeblue.com] 
Sent: Wednesday, January 29, 2014 2:52 PM
To: dev@cloudstack.apache.org
Subject: RE: [VOTE] Apache CloudStack 4.3.0 (second round)

-1

I am unable to manage Firewall, Port Forwarding or Load Balancing rules via the 
UI, the interfaces no longer exist.  I did create a Port Forwarding Rule via 
the API successfully to prove it's just a UI issue.

VMs assigned to VPC's fail to deploy and are then deleted.

I was unable to complete my remaining tests as these required a working VPC and 
the ability to create Firewall, Port Forwarding and Load Balancing Rules for 
Isolated Networks.

Regards

Geoff Higginbottom

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbot...@shapeblue.com

-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
Sent: 29 January 2014 04:54
To: dev@cloudstack.apache.org
Subject: [VOTE] Apache CloudStack 4.3.0 (second 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: 66d0b3d45bda73205b59693baeeefdf27e6c9c66


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 (excluding weekend). I will count the VOTE 
Sunday night 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)

Need Enterprise Grade Support for Apache CloudStack?
Our CloudStack Infrastructure 
Support offers the 
best 24/7 SLA for CloudStack Environments.

Apache CloudStack Bootcamp training courses

**NEW!** CloudStack 4.2.1 training
18th-19th February 2014, Brazil. 
Classroom
17th-23rd March 2014, Region A. Instructor led, 
On-line
24th-28th March 2014, Region B. Instructor led, 
On-line
16th-20th June 2014, Region A. Instructor led, 
On-line
23rd-27th June 2014, Region B. Instructor led, 
On-line

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: [VOTE] Apache CloudStack 4.3.0 (second round) - unable to manage Firewall, Port Forwarding or Load Balancing rules via the UI, the interfaces no longer exist.

[Jessica Wang]

Geoff,

I fixed the bug yesterday in master branch.

I just merged the fix to 4.3-forward branch:


Branch: refs/heads/4.3-forward

Commit: 1ad7bce69b764d3d833a8682ec5016bfbeea394c

Parents: d38a503

Author: Jessica Wang mailto:jessicaw...@apache.org>>

Authored: Wed Jan 29 15:40:14 2014 -0800

Committer: Jessica Wang mailto:jessicaw...@apache.org>>

Committed: Wed Jan 29 15:40:14 2014 -0800


Jessica


From: Geoff Higginbottom [mailto:geoff.higginbot...@shapeblue.com]
Sent: Wednesday, January 29, 2014 3:41 PM
To: Jessica Wang
Cc: dev@cloudstack.apache.org; Animesh Chaturvedi; Brian Federle; Sudha 
Ponnaganti; Sangeetha Hariharan
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (second round) - unable to manage 
Firewall, Port Forwarding or Load Balancing rules via the UI, the interfaces no 
longer exist.

Hi Jessica.

Yes, I can get as far as the Source NAT IP Address but then all I have is the 
Details Tab but no Configuration Tab.
Regards

Geoff Higginbottom
CTO / Cloud Architect

D: +44 20 3603 0542 | S: +44 20 3603 0540 
| M: +447968161581

geoff.higginbot...@shapeblue.com<mailto:geoff.higginbot...@shapeblue.com> | 
www.shapeblue.com | 
Twitter:@cloudstackguru<https://twitter.com/#!/cloudstackguru>

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 
4HS


On 29 Jan 2014, at 23:18, "Jessica Wang" 
mailto:jessica.w...@citrix.com>> wrote:
Geoff,


I am unable to manage Firewall, Port Forwarding or Load Balancing rules via the 
UI, the interfaces no longer exist.

Are you referring to the Configuration tab in IP Address detail page?
It's under Guest Network section or VPC section?

e.g. Network > Guest Network > IP Addresses > click a SourceNAT IP, or a 
Non-SourceNAT IP > Configuration tab is missing here?

e.g. Network > VPC > Router > IP Addresses > click a SourceNAT IP, or a 
Non-SourceNAT IP > Configuration tab is missing here?

Jessica


-Original Message-
From: Geoff Higginbottom [mailto:geoff.higginbot...@shapeblue.com]
Sent: Wednesday, January 29, 2014 2:52 PM
To: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>
Subject: RE: [VOTE] Apache CloudStack 4.3.0 (second round)

-1

I am unable to manage Firewall, Port Forwarding or Load Balancing rules via the 
UI, the interfaces no longer exist.  I did create a Port Forwarding Rule via 
the API successfully to prove it's just a UI issue.

VMs assigned to VPC's fail to deploy and are then deleted.

I was unable to complete my remaining tests as these required a working VPC and 
the ability to create Firewall, Port Forwarding and Load Balancing Rules for 
Isolated Networks.

Regards

Geoff Higginbottom

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbot...@shapeblue.com<mailto:geoff.higginbot...@shapeblue.com>

-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
Sent: 29 January 2014 04:54
To: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>
Subject: [VOTE] Apache CloudStack 4.3.0 (second 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: 66d0b3d45bda73205b59693baeeefdf27e6c9c66


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 (excluding weekend). I will count the VOTE 
Sunday night 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)

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

Did anyone get this error in SecondaryStorageVM in master branch? => Exception in thread "main" java.lang.UnsupportedClassVersionError: com/cloud/agent/AgentShell : Unsupported major.minor version 51.

[Jessica Wang]

Hi,

Did anyone get this error in SecondaryStorageVM in master branch?

==

Exception in thread "main" java.lang.UnsupportedClassVersionError: com/cloud/age
nt/AgentShell : Unsupported major.minor version 51.0
 at java.lang.ClassLoader.defineClass1(Native Method)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:634)
 at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:14
2)
 at java.net.URLClassLoader.defineClass(URLClassLoader.java:277)
 at java.net.URLClassLoader.access$000(URLClassLoader.java:73)
 at java.net.URLClassLoader$1.run(URLClassLoader.java:212)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
 at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
Could not find the main class: com.cloud.agent.AgentShell. Program will exit.
==

Thanks.

Jessica

RE: [ANNOUNCE] New PMC Member: Mike Tutkowski

[Jessica Wang]

congrats, Mike


-Original Message-
From: Chip Childers [mailto:chipchild...@apache.org] 
Sent: Tuesday, February 04, 2014 8:21 AM
To: dev@cloudstack.apache.org
Subject: [ANNOUNCE] New PMC Member: Mike Tutkowski

The Project Management Committee (PMC) for Apache CloudStack has asked
Mike Tutkowski to join the PMC and we are pleased to announce that he
has accepted.

Join me in congratulating Mike!

-The CloudStack PMC

RE: [VOTE] Apache CloudStack 4.3.0 (third round) - CLOUDSTACK-6031 Virtual Router count not displaying in UI Infrastructure Screen

[Jessica Wang]

Geoff,

I just fixed CLOUDSTACK-6031 in 4.3-forward branch.

Jessica

-Original Message-
From: Geoff Higginbottom [mailto:geoff.higginbot...@shapeblue.com] 
Sent: Wednesday, February 05, 2014 4:29 AM
To: dev@cloudstack.apache.org
Subject: RE: [VOTE] Apache CloudStack 4.3.0 (third round)

-1

The UI no longer shows the correct number of Virtual Routers - it always show 
ZERO even when there are multiple VRs running.

Logged as CLOUDSTACK-6031

Regards

Geoff Higginbottom

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbot...@shapeblue.com

-Original Message-
From: Srikanteswararao Talluri [mailto:srikanteswararao.tall...@citrix.com]
Sent: 04 February 2014 13:26
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (third round)

+1

No product issues observed in BVT runs.

CloudStack built from commit: 8f63c2cf9c463373d774cb563e63fc56828e1418

On KVM(CentOS 6.3)/Test Run: #1185 and #1186

5 of the test failures are not valid because snapshots, scaling VM are not 
supported on KVM Hypervisor and more intermittent test script/env issue related 
to ssh.
---
Link to reports:
http://jenkins.buildacloud.org/job/test-smoke-matrix-4.3/1185/testReport/
http://jenkins.buildacloud.org/job/test-smoke-matrix-4.3/1186/testReport/

Total:97
Fail :5
Skip :2


name   passfailskip
test_loadbalance/ 3   0   0
test_guest_vlan_range/1   0   0
test_deploy_vms_with_varied_deploymentplanners/   3   0   0
test_non_contigiousvlan/  1   0   0
test_reset_vm_on_reboot/  1   0   0
test_resource_detail/ 1   0   0
test_scale_vm/0   1   0
test_ssvm/   10   0   0
test_network/ 7   0   0
test_disk_offerings/  3   0   0
test_volumes/ 8   1   0
test_affinity_groups/ 1   0   0
test_routers/ 9   0   0
test_deploy_vm_with_userdata/ 2   0   0
test_network_acl/ 1   0   0
test_vm_life_cycle/  10   0   0
test_privategw_acl/   1   0   0
test_internal_lb/ 1   0   0
test_deploy_vm/   1   0   0
test_global_settings/ 1   0   0
test_nic/ 1   0   0
test_public_ip_range/ 1   0   0
test_iso/ 5   0   1
test_service_offerings/   4   0   0
test_multipleips_per_nic/ 1   0   0
test_regions/ 1   0   0
test_templates/   7   0   1
test_vpc_vpn/ 2   0   0
test_vm_snapshots/0   3   0
test_portable_publicip/   2   0   0
test_pvlan/   1   0   0



On XenServer 6.2/Test Run: #1187 and #1188

3 failures are intermittent test script/env issues related to ssh.
---
Link to reports:
http://jenkins.buildacloud.org/job/test-smoke-matrix-4.3/1187/testReport/
http://jenkins.buildacloud.org/job/test-smoke-matrix-4.3/1188/testReport/

Total:97
Fail :3
Skip :2


name   passfailskip
test_loadbalance/ 3   0   0
test_guest_vlan_range/1   0   0
test_deploy_vms_with_varied_deploymentplanners/   3   0   0
test_non_contigiousvlan/  1   0   0
test_reset_vm_on_reboot/  1   0   0
test_resource_detail/ 1   0   0
test_scale_vm/1   0   0
test_ssvm/   10   0   0
test_network/ 7   0   0
test_disk_offerings/  3   0   0
test_volumes/ 9   0   0
test_affinity_groups/ 1   0   0
test_routers/ 9