On Jan 13, 2014, at 1:08 PM, Santhosh Edukulla <santhosh.eduku...@citrix.com> wrote:
> 1. requests package and nosetests2.7 are required to work with tests. > > 2. As such Simulator (as mentioned below ) works and so inquired to remove it > from blocker, but its the profile which needs changes and so mentioned below > notes to fix the profile if agreed. Anyways, however way. we decide and > agreed to go, we will fix it. > Yes please fix the profile -don't remove it- > 3. Again i am totally with you on doing changes in a separate branch. As > mentioned in one of the threads earlier and after that discussion, we have > not done any changes "thereafter" to marvin and we are doing it separately in > a private branch and will call for a merge once done. > Committing to a topic branch should not prevent you to submit reviews. There is a 'marvin_refactor' branch, you can just check it out, rebase it with master and start working there. When you submit a review, we can apply the patches to that branch. I don't know what you mean by 'private branch', it's better to do the work in the open (and recommended) on a topic/feature branch in the apache repo. > Let me know. > > Regards, > Santhosh > ________________________________________ > From: sebgoa [run...@gmail.com] > Sent: Monday, January 13, 2014 12:56 PM > To: Santhosh Edukulla > Cc: dev@cloudstack.apache.org; gir...@clogeny.com; Prasanna Santhanam > Subject: Re: [ACS 4.3] RC update > > On Jan 13, 2014, at 6:45 PM, Santhosh Edukulla <santhosh.eduku...@citrix.com> > wrote: > >> Hi Sebastian, >> >> 1. I was able to get the simulator up and running following the below >> instructions @link: >> >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Simulator+integration >> >> mvn -Pdeveloper -Dsimulator clean install >> mvn -Pdeveloper -pl developer -Ddeploydb >> mvn -Pdeveloper -pl developer -Ddeploydb-simulator >> mvn -pl client jetty:run -Dsimulator >> >> Thereafter deploying a datacenter worked either by "python >> deployDataCenter.py -i <path_to_config>" or "python deployAndRun.py -c >> <path_to_config>" >> >> 2. Also, running python executable as part of mvn life cycle, will throw >> some errors because of different python versions available on client and >> packages relying to work only on 2.7+. >> >> 3. Just a Question: Using the below mentioned way a documented one of >> running and using simulator? If not as such using above mentioned notes >> under 1 are still available to work with simulator, >> can we remove the bug from blocker category?\ >> >> mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/basic.cfg -pl >> :cloud-marvin integration-test >> >> 4. Also, the above mentioned way@3 worked anytime on python2.6? >> >> 5. Regarding the cleaning up of pom.xml, i am planning to remove >> marvin.setup and marvin.test profiles altogether from tools/marvin/pom.xml? >> let me know your thoughts? As such again fitting them in to mvn cycle has >> some issues with different python and nose versions compatibility running >> inside its lifecycle? If not so, i can fix to clean up the removed arguments >> for deployAndRun.py? >> <argument>-t</argument> >> - <argument>/tmp/t.log</argument> >> - <argument>-r</argument> >> - <argument>/tmp/r.log</argument> >> - <argument>-f</argument> >> - >> <argument>${resolved.basedir}/marvin/testSetupSuccess.py</argument> >> >> > > The simulator works, indeed what is broken is the maven profile, since the > arguments of deployAndRun are changed. So the profile needs to be fixed. > > AFAIK Marvin was not working on python2.6 due to url lib compat issue. If > it's fixed now, that's good news as it will ease install on CentOS. > > I am sure there is a reason why Prasanna created those Maven profiles for > marvin, probably for the BVT ? This needs to be investigated before removing > them. I would prefer fixing the profiles. > > While Marvin may have had some limitations before your changes, folks may > have build things around them that a change of arguments just basically broke. > > So I would want to hear from Prasanna that the maven profiles can be safely > removed or see the profiles fixed so that they work with your changes, prior > to removing this bug as a blocker. > > For future development I strongly suggest that your changes not be committed > to release branches but instead all go to a topic branch (that Girish or I > can create for you), once all changes are made and tested we can merge. > > thanks, > > -Sebastien > > >> Thanks! >> Santhosh >> ________________________________________ >> From: sebgoa [run...@gmail.com] >> Sent: Monday, January 13, 2014 8:26 AM >> To: dev@cloudstack.apache.org >> Cc: gir...@clogeny.com; Prasanna Santhanam; Santhosh Edukulla >> Subject: Re: [ACS 4.3] RC update >> >> On Jan 11, 2014, at 7:08 AM, Animesh Chaturvedi >> <animesh.chaturv...@citrix.com> wrote: >> >>> Folks >>> >>> Today is the scheduled RC date for ACS 4.3 We are very close with just a >>> few lingering issues below. >>> >>> >>> >>> | Jayapal Reddy | CLOUDSTACK-5848 : [Upgrade3.0.6-4.3]"Unable to >>> parse VLAN tag" message when network associated with SRX external firewall >>> device is rebooted. >>> | >>> | edison su | CLOUDSTACK-5831 : As regular user , when trying to >>> take a snapshot , snapshot succeeds but user is presented with "The given >>> command does not exist or it is not available for user" message. >>> | >>> | Unassigned | CLOUDSTACK-5743 : Download ROOT Volume when the VM >>> is in stopped state is failing with "Forbidden You don't have permission to >>> access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server" | >>> | Likitha Shetty | CLOUDSTACK-5707 : Hitting multiple exceptions when >>> the Vsphere client is upgraded to 5.5 from 5.1 >>> | >>> | Daan Hoogland | CLOUDSTACK-5502 : [Automation] createVlanIpRange >>> API failing, if you pass VLAN >>> >>> | >>> | Marcus Sorensen | CLOUDSTACK-5432 : [Automation] Libvtd getting >>> crashed and agent going to alert start >>> >>> | >>> | Sateesh Chodapuneedi | CLOUDSTACK-5408 : [Automation] Failed to deploy vm >>> in vmware environment with error "due to java.io.IOException: Cannot run >>> program "mount": java.io.IOException: error=12, Cannot allocate memory" >>> | >>> | Wei Zhou | CLOUDSTACK-5144 : [Automation]: Basic Zone >>> Security Groups - SSH to VM is allowed even when there is no ingress rule >>> defined for the security group >>> | >>> >>> >>> If you have not played with 4.3 yet please take it for a spin and call out >>> any critical issues, I plan to build an RC early next week. >>> >> >> Animesh, I just created a blocker: >> >> https://issues.apache.org/jira/browse/CLOUDSTACK-5864 >> >> The simulator has been broken with recent changes in marvin >> >> >>> Thanks >>> Animesh >>> >>> -----Original Message----- >>> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] >>> Sent: Tuesday, January 07, 2014 10:51 AM >>> To: dev@cloudstack.apache.org >>> Subject: [ACS 4.3] RC update >>> >>> Folks >>> >>> Happy new year everyone. I hope you all had a good recharging time off >>> during holiday. I want to bring our attention and focus to getting the 4.3 >>> release out the door. While our scheduled RC date is this Friday 1/10 but >>> we still have many open blocker and critical. Please review your backlog of >>> issues and bring them to resolution ASAP and provide a "Due Date" in the >>> bug. We need to absolutely make sure upgrades are working. If you >>> encounter upgrade issue please file them as blockers. I will escalate all >>> current upgrade issues to blocker. >>> >>> For the most recent release status please visit the 4.3 Release Dashboard >>> [1]. I am following up on individual issues directly in JIRA so do watch >>> JIRA emails >>> >>> [1] http://s.apache.org/dFk >>> >>> Thanks >>> Animesh >
