I think the VMware traffic label issue is related to these two:
https://issues.apache.org/jira/browse/CLOUDSTACK-4943
https://issues.apache.org/jira/browse/CLOUDSTACK-5012

Seems that CloudStack wrongfully append strings in traffic labels, but the
issues were marked as "non-reproducible."

-------------------------------------------------------------------------------------------
Yu-Heng (Ryan) Lei, Associate Researcher
Cloud Computing Dept, Chunghwa Telecom Labs
ryan...@cht.com.tw or ryanlei750...@gmail.com


On Sun, Mar 23, 2014 at 6:55 AM, ilya musayev
<ilya.mailing.li...@gmail.com>wrote:

> I did find some issue - but relatively minor and nothing that could not
> have been fixed via UI.
>
> I will open JIRA to address the issues.
>
> In the nutshell, i noticed some UI inconsistency and the way some pages
> are presented - this is minor but the issue was seen in both latest Firefox
> and Chrome on OSX.
>
> Another issue was related to VMware, if you define vSwitch0 under physical
> network labels for MGMT, Public, Guest and Storage, ACS 4.3 looks for a
> vSwitch named "vSwitch0vSwitch0".
>
> There is "vSwitch0" label that is defined as default in case nothing was
> supplied for vSwitch0 name - which is vSpheres default vSwitch, however, i
> decided to define it anyway to see what happens - surely enough it broke.
> It appears instead of replacing my value defined in UI, ACS appends my
> value + default value. As a result, vSwitch0vSwitch0 - is invalid vSwitch
> in VMware, and attempts to deploy SysVMs fail. I havent tried defining
> other vSwitches because all my test hypervisors only leverage vSwitch0.
>
> If i undefine the vSwitch0 label, ACS then picks up proper default
> vSwitch0.
>
>
> On 3/22/14, 3:39 AM, Wilder Rodrigues wrote:
>
>> Great news!
>>
>> Have a nice weekend, guys and gals!
>>
>> Cheers,
>> Wilder
>>
>> Sent from my iPhone
>>
>>  On 21 Mar 2014, at 20:08, "Animesh Chaturvedi" <
>>> animesh.chaturv...@citrix.com> wrote:
>>>
>>>
>>>
>>> The vote has *passed* with the following results (binding PMC votes
>>> indicated with a "*" next to their name:
>>>
>>> +1 : Animesh*, Edison*, Ilya*, Amogh, Wilder
>>> +0 : Daan *
>>> -1 : Tanner (The issue CLOUDSTACK-6266 could not be reproduced )
>>>
>>> I'm going to proceed with moving the release into the distribution repo
>>> now and other release tasks.
>>>
>>> Thanks
>>> Animesh
>>>
>>>
>>>  -----Original Message-----
>>>> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>>>> Sent: Tuesday, March 18, 2014 12:06 PM
>>>> To: dev@cloudstack.apache.org
>>>> Subject: [VOTE] Apache CloudStack 4.3.0 (ninth round)
>>>>
>>>>
>>>>
>>>>
>>>> Hi All,
>>>>
>>>>
>>>>
>>>> I've created a 4.3.0 release, with the following artifacts up for a
>>>>
>>>> vote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Git Branch and Commit SH:
>>>>
>>>> https://git-wip-
>>>> us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
>>>> Commit:  0810029f274878eca8fd74b44ab1117054e929a5
>>>>
>>>>
>>>> List of changes:
>>>>
>>>> New Features in 4.3: https://issues.apache.org/
>>>> jira/issues/?filter=12325248
>>>>
>>>> Improvement in 4.3: https://issues.apache.org/
>>>> jira/issues/?filter=12325249
>>>>
>>>> Issues fixed in 4.3 https://issues.apache.org/
>>>> jira/issues/?filter=12326161
>>>>
>>>> Known Issues in 4.3: https://issues.apache.org/
>>>> jira/issues/?filter=12326162
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Source release (checksums and signatures are available at the same
>>>>
>>>> location):
>>>>
>>>> https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
>>>>
>>>>
>>>>
>>>> PGP release keys (signed using 94BE0D7C):
>>>>
>>>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>>>
>>>>
>>>>
>>>> Testing instructions are here:
>>>>
>>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+pro
>>>> cedure
>>>>
>>>>
>>>>
>>>> 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
>>>>
>>>
>

Reply via email to