You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cloudstack.apache.org by sebgoa <ru...@gmail.com> on 2013/09/05 10:21:42 UTC

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.

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.
 

-Sebastien

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

Posted by Jessica Wang <Je...@citrix.com>.

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.su@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:runseb@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

Posted by Jessica Wang <Je...@citrix.com>.

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.childers@sungard.com] 
Sent: Friday, September 06, 2013 1:49 PM
To: Jessica Wang
Cc: dev@cloudstack.apache.org; Animesh Chaturvedi; Edison Su; runseb@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

Posted by Jessica Wang <Je...@citrix.com>.

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": 9999,
        "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; runseb@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.childers@sungard.com] 
Sent: Friday, September 06, 2013 1:49 PM
To: Jessica Wang
Cc: dev@cloudstack.apache.org; Animesh Chaturvedi; Edison Su; runseb@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

Posted by Chip Childers <ch...@sungard.com>.

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

Posted by Jessica Wang <Je...@citrix.com>.

> [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.childers@sungard.com] 
Sent: Friday, September 06, 2013 12:33 PM
To: Jessica Wang
Cc: dev@cloudstack.apache.org; Animesh Chaturvedi; Edison Su; runseb@gmail.com; Sateesh Chodapuneedi
Subject: Re: Questions about 4.2 RC - listVmwareDcs API

On Fri, Sep 06, 2013 at 06:30:52PM +0000, 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

Re: Questions about 4.2 RC - listVmwareDcs API

Posted by Chip Childers <ch...@sungard.com>.

On Fri, Sep 06, 2013 at 06:30:52PM +0000, 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

RE: Questions about 4.2 RC - listVmwareDcs API

Posted by Jessica Wang <Je...@citrix.com>.

> 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.childers@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 +0000, Sateesh Chodapuneedi wrote:
> > -----Original Message-----
> > From: Edison Su [mailto:Edison.su@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:runseb@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

Posted by Chip Childers <ch...@sungard.com>.

On Fri, Sep 06, 2013 at 03:21:24PM +0000, Sateesh Chodapuneedi wrote:
> > -----Original Message-----
> > From: Edison Su [mailto:Edison.su@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:runseb@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

Posted by Sateesh Chodapuneedi <sa...@citrix.com>.

> -----Original Message-----
> From: Edison Su [mailto:Edison.su@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:runseb@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").
> 
> >
> > 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

Posted by Marcus Sorensen <sh...@gmail.com>.

Yes, preferably we skip the initial template copy altogether and go
straight to the clone with the template info and new destination disk.

Sorry, shouldn't have hijacked the thread :)
On Sep 5, 2013 5:38 PM, "Edison Su" <Ed...@citrix.com> wrote:

>
>
> > -----Original Message-----
> > From: Marcus Sorensen [mailto:shadowsor@gmail.com]
> > Sent: Thursday, September 05, 2013 3:34 PM
> > To: Animesh Chaturvedi
> > Cc: dev@cloudstack.apache.org
> > Subject: Re: Questions about 4.2 RC
> >
> > So I guess I need to figure out of that is broken, or if it's marvin,
> and if it's
> > marvin, how to fix it.
> >
> > Now that I've gotten past that, I see the storage refactor has broken
> CLVM.
> > I'll file a bug, but it looks like the process is doing something like:
> >
> > copy template to primary storage, then create copy of primary storage
> > template as new volume
> >
> > This breaks CLVM, because it used to just do:
> >
> > copy template to primary storage as new volume
> >
> > Since we can't efficiently clone in CLVM, it expects to always copy the
> > template from secondary storage, rather than copying to primary first and
> > then copying the whole template from the primary back to the same disks.
> 1)
> > because it thrashes the disks, and 2) copying the template is usually
> much
> > faster because the template is sparse, and the logical volume is not, so
> > copying a 10G template with a real size of 500M is much faster than
> copying a
> > 10G logical volume to another 10G logical volume.
> >
> > in KVMStorageProcessor.java cloneVolumeFromBaseTemplate:
> >
> >             if (primaryPool.getType() == StoragePoolType.CLVM) {
> >                 vol = templateToPrimaryDownload(templatePath,
> primaryPool);
> >             }
>
> If the copycommand passes the template path on secondary storage will
> solve the issue, right?
> Let me figure it out.
> >
> > This will never work, because templateToPrimaryDownload expects
> > secondary storage, and we have copied the template to primary storage and
> > are passing that. e.g.:
> >
> > {
> >     "org.apache.cloudstack.storage.command.CopyCommand": {
> >         "destTO": {
> >             "org.apache.cloudstack.storage.to.VolumeObjectTO": {
> >                 "accountId": 2,
> >                 "dataStore": {
> >
> "org.apache.cloudstack.storage.to.PrimaryDataStoreTO": {
> >                         "host": "localhost",
> >                         "id": 2,
> >                         "path": "/vg0",
> >                         "poolType": "CLVM",
> >                         "port": 0,
> >                         "uuid": "4e00fe65-c47e-4b85-afe8-4f97fb8689d0"
> >                     }
> >                 },
> >                 "format": "QCOW2",
> >                 "hypervisorType": "KVM",
> >                 "id": 9,
> >                 "name": "ROOT-9",
> >                 "size": 1073741824,
> >                 "uuid": "d73f3a2b-9e63-4faf-a45b-d6fcf7633793",
> >                 "vmName": "i-2-9-VM",
> >                 "volumeId": 9,
> >                 "volumeType": "ROOT"
> >             }
> >         },
> >         "executeInSequence": true,
> >         "srcTO": {
> >             "org.apache.cloudstack.storage.to.TemplateObjectTO": {
> >                 "accountId": 2,
> >                 "checksum": "44cd0e6330a59f031460bc18a40c95a2",
> >                 "displayText": "tiny",
> >                 "format": "QCOW2",
> >                 "hvm": true,
> >                 "hypervisorType": "KVM",
> >                 "id": 201,
> >                 "imageDataStore": {
> >
> "org.apache.cloudstack.storage.to.PrimaryDataStoreTO": {
> >                         "host": "localhost",
> >                         "id": 2,
> >                         "path": "/vg0",
> >                         "poolType": "CLVM",
> >                         "port": 0,
> >                         "uuid": "4e00fe65-c47e-4b85-afe8-4f97fb8689d0"
> >                     }
> >                 },
> >                 "name": "201-2-a04f958e-0aed-3642-960f-a675a2ee1c44",
> >                 "origUrl":
> > "http://mirrors.betterservers.com/template/tiny-centos-63.qcow2",
> >                 "path": "c8da0364-6f94-4c71-9c1d-74078e55bbb8",
> >                 "uuid": "7dcdb1fb-e7e3-4de0-bf93-13d3e6c4ade5"
> >             }
> >         },
> >         "wait": 0
> >     }
> > }
> >
> > Also, format should be 'RAW', I believe, not 'QCOW2'.
> >
> > On Thu, Sep 5, 2013 at 3:40 PM, Animesh Chaturvedi
> > <an...@citrix.com> wrote:
> > >
> > >
> > >> -----Original Message-----
> > >> From: Marcus Sorensen [mailto:shadowsor@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-
> > v
> > >> pc-
> > >> 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.
> > > [Animesh>] Marcus from the spec "The cloudStack UI will enable the
> > element/provider automatically as a part of physical network creation".
> > >
> > >
> > >>
> > >> On Thu, Sep 5, 2013 at 2:37 PM, Edison Su <Ed...@citrix.com>
> wrote:
> > >> >
> > >> >
> > >> >> -----Original Message-----
> > >> >> From: sebgoa [mailto:runseb@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

Posted by Edison Su <Ed...@citrix.com>.


> -----Original Message-----
> From: Marcus Sorensen [mailto:shadowsor@gmail.com]
> Sent: Thursday, September 05, 2013 3:34 PM
> To: Animesh Chaturvedi
> Cc: dev@cloudstack.apache.org
> Subject: Re: Questions about 4.2 RC
> 
> So I guess I need to figure out of that is broken, or if it's marvin, and if it's
> marvin, how to fix it.
> 
> Now that I've gotten past that, I see the storage refactor has broken CLVM.
> I'll file a bug, but it looks like the process is doing something like:
> 
> copy template to primary storage, then create copy of primary storage
> template as new volume
> 
> This breaks CLVM, because it used to just do:
> 
> copy template to primary storage as new volume
> 
> Since we can't efficiently clone in CLVM, it expects to always copy the
> template from secondary storage, rather than copying to primary first and
> then copying the whole template from the primary back to the same disks. 1)
> because it thrashes the disks, and 2) copying the template is usually much
> faster because the template is sparse, and the logical volume is not, so
> copying a 10G template with a real size of 500M is much faster than copying a
> 10G logical volume to another 10G logical volume.
> 
> in KVMStorageProcessor.java cloneVolumeFromBaseTemplate:
> 
>             if (primaryPool.getType() == StoragePoolType.CLVM) {
>                 vol = templateToPrimaryDownload(templatePath, primaryPool);
>             }

If the copycommand passes the template path on secondary storage will solve the issue, right?
Let me figure it out.
> 
> This will never work, because templateToPrimaryDownload expects
> secondary storage, and we have copied the template to primary storage and
> are passing that. e.g.:
> 
> {
>     "org.apache.cloudstack.storage.command.CopyCommand": {
>         "destTO": {
>             "org.apache.cloudstack.storage.to.VolumeObjectTO": {
>                 "accountId": 2,
>                 "dataStore": {
>                     "org.apache.cloudstack.storage.to.PrimaryDataStoreTO": {
>                         "host": "localhost",
>                         "id": 2,
>                         "path": "/vg0",
>                         "poolType": "CLVM",
>                         "port": 0,
>                         "uuid": "4e00fe65-c47e-4b85-afe8-4f97fb8689d0"
>                     }
>                 },
>                 "format": "QCOW2",
>                 "hypervisorType": "KVM",
>                 "id": 9,
>                 "name": "ROOT-9",
>                 "size": 1073741824,
>                 "uuid": "d73f3a2b-9e63-4faf-a45b-d6fcf7633793",
>                 "vmName": "i-2-9-VM",
>                 "volumeId": 9,
>                 "volumeType": "ROOT"
>             }
>         },
>         "executeInSequence": true,
>         "srcTO": {
>             "org.apache.cloudstack.storage.to.TemplateObjectTO": {
>                 "accountId": 2,
>                 "checksum": "44cd0e6330a59f031460bc18a40c95a2",
>                 "displayText": "tiny",
>                 "format": "QCOW2",
>                 "hvm": true,
>                 "hypervisorType": "KVM",
>                 "id": 201,
>                 "imageDataStore": {
>                     "org.apache.cloudstack.storage.to.PrimaryDataStoreTO": {
>                         "host": "localhost",
>                         "id": 2,
>                         "path": "/vg0",
>                         "poolType": "CLVM",
>                         "port": 0,
>                         "uuid": "4e00fe65-c47e-4b85-afe8-4f97fb8689d0"
>                     }
>                 },
>                 "name": "201-2-a04f958e-0aed-3642-960f-a675a2ee1c44",
>                 "origUrl":
> "http://mirrors.betterservers.com/template/tiny-centos-63.qcow2",
>                 "path": "c8da0364-6f94-4c71-9c1d-74078e55bbb8",
>                 "uuid": "7dcdb1fb-e7e3-4de0-bf93-13d3e6c4ade5"
>             }
>         },
>         "wait": 0
>     }
> }
> 
> Also, format should be 'RAW', I believe, not 'QCOW2'.
> 
> On Thu, Sep 5, 2013 at 3:40 PM, Animesh Chaturvedi
> <an...@citrix.com> wrote:
> >
> >
> >> -----Original Message-----
> >> From: Marcus Sorensen [mailto:shadowsor@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-
> v
> >> pc-
> >> 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.
> > [Animesh>] Marcus from the spec "The cloudStack UI will enable the
> element/provider automatically as a part of physical network creation".
> >
> >
> >>
> >> On Thu, Sep 5, 2013 at 2:37 PM, Edison Su <Ed...@citrix.com> wrote:
> >> >
> >> >
> >> >> -----Original Message-----
> >> >> From: sebgoa [mailto:runseb@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

Posted by Marcus Sorensen <sh...@gmail.com>.

So I guess I need to figure out of that is broken, or if it's marvin,
and if it's marvin, how to fix it.

Now that I've gotten past that, I see the storage refactor has broken
CLVM. I'll file a bug, but it looks like the process is doing
something like:

copy template to primary storage, then create copy of primary storage
template as new volume

This breaks CLVM, because it used to just do:

copy template to primary storage as new volume

Since we can't efficiently clone in CLVM, it expects to always copy
the template from secondary storage, rather than copying to primary
first and then copying the whole template from the primary back to the
same disks. 1) because it thrashes the disks, and 2) copying the
template is usually much faster because the template is sparse, and
the logical volume is not, so copying a 10G template with a real size
of 500M is much faster than copying a 10G logical volume to another
10G logical volume.

in KVMStorageProcessor.java cloneVolumeFromBaseTemplate:

            if (primaryPool.getType() == StoragePoolType.CLVM) {
                vol = templateToPrimaryDownload(templatePath, primaryPool);
            }

This will never work, because templateToPrimaryDownload expects
secondary storage, and we have copied the template to primary storage
and are passing that. e.g.:

{
    "org.apache.cloudstack.storage.command.CopyCommand": {
        "destTO": {
            "org.apache.cloudstack.storage.to.VolumeObjectTO": {
                "accountId": 2,
                "dataStore": {
                    "org.apache.cloudstack.storage.to.PrimaryDataStoreTO": {
                        "host": "localhost",
                        "id": 2,
                        "path": "/vg0",
                        "poolType": "CLVM",
                        "port": 0,
                        "uuid": "4e00fe65-c47e-4b85-afe8-4f97fb8689d0"
                    }
                },
                "format": "QCOW2",
                "hypervisorType": "KVM",
                "id": 9,
                "name": "ROOT-9",
                "size": 1073741824,
                "uuid": "d73f3a2b-9e63-4faf-a45b-d6fcf7633793",
                "vmName": "i-2-9-VM",
                "volumeId": 9,
                "volumeType": "ROOT"
            }
        },
        "executeInSequence": true,
        "srcTO": {
            "org.apache.cloudstack.storage.to.TemplateObjectTO": {
                "accountId": 2,
                "checksum": "44cd0e6330a59f031460bc18a40c95a2",
                "displayText": "tiny",
                "format": "QCOW2",
                "hvm": true,
                "hypervisorType": "KVM",
                "id": 201,
                "imageDataStore": {
                    "org.apache.cloudstack.storage.to.PrimaryDataStoreTO": {
                        "host": "localhost",
                        "id": 2,
                        "path": "/vg0",
                        "poolType": "CLVM",
                        "port": 0,
                        "uuid": "4e00fe65-c47e-4b85-afe8-4f97fb8689d0"
                    }
                },
                "name": "201-2-a04f958e-0aed-3642-960f-a675a2ee1c44",
                "origUrl":
"http://mirrors.betterservers.com/template/tiny-centos-63.qcow2",
                "path": "c8da0364-6f94-4c71-9c1d-74078e55bbb8",
                "uuid": "7dcdb1fb-e7e3-4de0-bf93-13d3e6c4ade5"
            }
        },
        "wait": 0
    }
}

Also, format should be 'RAW', I believe, not 'QCOW2'.

On Thu, Sep 5, 2013 at 3:40 PM, Animesh Chaturvedi
<an...@citrix.com> wrote:
>
>
>> -----Original Message-----
>> From: Marcus Sorensen [mailto:shadowsor@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.
> [Animesh>] Marcus from the spec "The cloudStack UI will enable the element/provider automatically as a part of physical network creation".
>
>
>>
>> On Thu, Sep 5, 2013 at 2:37 PM, Edison Su <Ed...@citrix.com> wrote:
>> >
>> >
>> >> -----Original Message-----
>> >> From: sebgoa [mailto:runseb@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

Posted by Animesh Chaturvedi <an...@citrix.com>.


> -----Original Message-----
> From: Marcus Sorensen [mailto:shadowsor@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.
[Animesh>] Marcus from the spec "The cloudStack UI will enable the element/provider automatically as a part of physical network creation".


> 
> On Thu, Sep 5, 2013 at 2:37 PM, Edison Su <Ed...@citrix.com> wrote:
> >
> >
> >> -----Original Message-----
> >> From: sebgoa [mailto:runseb@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 (2)

Posted by Marcus Sorensen <sh...@gmail.com>.

I didn't have it. I ran across it this afternoon, but wasn't sure if
it did all of the proper setup or if it was the equivalent of enabling
the provider (which as mentioned wasn't enough when I tried manually).
Thanks for confirming, I'll commit it.

On Thu, Sep 5, 2013 at 10:45 PM, Prasanna Santhanam <ts...@apache.org> wrote:
> Yes, that is all that is required. This doesn't enable the internal lb
> provider for you?
>
> On Thu, Sep 05, 2013 at 10:41:02PM -0600, Marcus Sorensen wrote:
>> So this look right to you?
>>
>> diff --git a/tools/devcloud-kvm/devcloud-kvm-advanced.cfg
>> b/tools/devcloud-kvm/devcloud-kvm-advanced.cfg
>> index 45bdfce..8e77809 100644
>> --- a/tools/devcloud-kvm/devcloud-kvm-advanced.cfg
>> +++ b/tools/devcloud-kvm/devcloud-kvm-advanced.cfg
>> @@ -47,6 +47,10 @@
>>                          {
>>                              "broadcastdomainrange": "ZONE",
>>                              "name": "VpcVirtualRouter"
>> +                        },
>> +                        {
>> +                            "broadcastdomainrange": "ZONE",
>> +                            "name": "InternalLbVm"
>>                          }
>>                      ]
>>                  },
>>
>> On Thu, Sep 5, 2013 at 10:37 PM, Prasanna Santhanam <ts...@apache.org> wrote:
>> > On Thu, Sep 05, 2013 at 05:06:02PM -0600, Marcus Sorensen wrote:
>> >> Thanks. It must be the marvin deployment then that's causing me grief.
>> >> I haven't manually filled out the UI in awhile.
>> >
>> > Marvin handles internallbvm deployment as well. Your providers should
>> > now look like below.Then sync marvin and you should be ready to go.
>> >
>> > "providers": [
>> >                         {
>> >                             "broadcastdomainrange": "ZONE",
>> >                             "name": "VirtualRouter"
>> >                         },
>> >                         {
>> >                             "broadcastdomainrange": "ZONE",
>> >                             "name": "VpcVirtualRouter"
>> >                         },
>> >                         {
>> >                             "broadcastdomainrange": "ZONE",
>> >                             "name": "InternalLbVm"
>> >                         }
>> >                     ],
>> >
>> > see the setup/dev/advanced.cfg. I keep that updated usually.
>> >
>> > --
>> > Prasanna.,
>> >
>> > ------------------------
>> > Powered by BigRock.com
>> >
>
> --
> Prasanna.,
>
> ------------------------
> Powered by BigRock.com
>

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

Posted by Prasanna Santhanam <ts...@apache.org>.

Yes, that is all that is required. This doesn't enable the internal lb
provider for you?

On Thu, Sep 05, 2013 at 10:41:02PM -0600, Marcus Sorensen wrote:
> So this look right to you?
> 
> diff --git a/tools/devcloud-kvm/devcloud-kvm-advanced.cfg
> b/tools/devcloud-kvm/devcloud-kvm-advanced.cfg
> index 45bdfce..8e77809 100644
> --- a/tools/devcloud-kvm/devcloud-kvm-advanced.cfg
> +++ b/tools/devcloud-kvm/devcloud-kvm-advanced.cfg
> @@ -47,6 +47,10 @@
>                          {
>                              "broadcastdomainrange": "ZONE",
>                              "name": "VpcVirtualRouter"
> +                        },
> +                        {
> +                            "broadcastdomainrange": "ZONE",
> +                            "name": "InternalLbVm"
>                          }
>                      ]
>                  },
> 
> On Thu, Sep 5, 2013 at 10:37 PM, Prasanna Santhanam <ts...@apache.org> wrote:
> > On Thu, Sep 05, 2013 at 05:06:02PM -0600, Marcus Sorensen wrote:
> >> Thanks. It must be the marvin deployment then that's causing me grief.
> >> I haven't manually filled out the UI in awhile.
> >
> > Marvin handles internallbvm deployment as well. Your providers should
> > now look like below.Then sync marvin and you should be ready to go.
> >
> > "providers": [
> >                         {
> >                             "broadcastdomainrange": "ZONE",
> >                             "name": "VirtualRouter"
> >                         },
> >                         {
> >                             "broadcastdomainrange": "ZONE",
> >                             "name": "VpcVirtualRouter"
> >                         },
> >                         {
> >                             "broadcastdomainrange": "ZONE",
> >                             "name": "InternalLbVm"
> >                         }
> >                     ],
> >
> > see the setup/dev/advanced.cfg. I keep that updated usually.
> >
> > --
> > Prasanna.,
> >
> > ------------------------
> > Powered by BigRock.com
> >

-- 
Prasanna.,

------------------------
Powered by BigRock.com

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

Posted by Marcus Sorensen <sh...@gmail.com>.

So this look right to you?

diff --git a/tools/devcloud-kvm/devcloud-kvm-advanced.cfg
b/tools/devcloud-kvm/devcloud-kvm-advanced.cfg
index 45bdfce..8e77809 100644
--- a/tools/devcloud-kvm/devcloud-kvm-advanced.cfg
+++ b/tools/devcloud-kvm/devcloud-kvm-advanced.cfg
@@ -47,6 +47,10 @@
                         {
                             "broadcastdomainrange": "ZONE",
                             "name": "VpcVirtualRouter"
+                        },
+                        {
+                            "broadcastdomainrange": "ZONE",
+                            "name": "InternalLbVm"
                         }
                     ]
                 },

On Thu, Sep 5, 2013 at 10:37 PM, Prasanna Santhanam <ts...@apache.org> wrote:
> On Thu, Sep 05, 2013 at 05:06:02PM -0600, Marcus Sorensen wrote:
>> Thanks. It must be the marvin deployment then that's causing me grief.
>> I haven't manually filled out the UI in awhile.
>
> Marvin handles internallbvm deployment as well. Your providers should
> now look like below.Then sync marvin and you should be ready to go.
>
> "providers": [
>                         {
>                             "broadcastdomainrange": "ZONE",
>                             "name": "VirtualRouter"
>                         },
>                         {
>                             "broadcastdomainrange": "ZONE",
>                             "name": "VpcVirtualRouter"
>                         },
>                         {
>                             "broadcastdomainrange": "ZONE",
>                             "name": "InternalLbVm"
>                         }
>                     ],
>
> see the setup/dev/advanced.cfg. I keep that updated usually.
>
> --
> Prasanna.,
>
> ------------------------
> Powered by BigRock.com
>

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

Posted by Prasanna Santhanam <ts...@apache.org>.

On Thu, Sep 05, 2013 at 05:06:02PM -0600, Marcus Sorensen wrote:
> Thanks. It must be the marvin deployment then that's causing me grief.
> I haven't manually filled out the UI in awhile.

Marvin handles internallbvm deployment as well. Your providers should
now look like below.Then sync marvin and you should be ready to go.

"providers": [
                        {   
                            "broadcastdomainrange": "ZONE",
                            "name": "VirtualRouter"
                        },  
                        {   
                            "broadcastdomainrange": "ZONE",
                            "name": "VpcVirtualRouter"
                        },  
                        {   
                            "broadcastdomainrange": "ZONE",
                            "name": "InternalLbVm"
                        }   
                    ],  

see the setup/dev/advanced.cfg. I keep that updated usually.

-- 
Prasanna.,

------------------------
Powered by BigRock.com

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

Posted by Marcus Sorensen <sh...@gmail.com>.

Thanks. It must be the marvin deployment then that's causing me grief.
I haven't manually filled out the UI in awhile.

On Thu, Sep 5, 2013 at 4:01 PM, Jessica Wang <Je...@citrix.com> wrote:
> 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.Wang@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:shadowsor@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 <Ed...@citrix.com> wrote:
>>
>>
>>> -----Original Message-----
>>> From: sebgoa [mailto:runseb@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