[GitHub] [cloudstack-primate] rhtyd commented on issue #7: [WIP] Feature/vm wizard

2019-11-04 Thread GitBox
rhtyd commented on issue #7: [WIP] Feature/vm wizard
URL: https://github.com/apache/cloudstack-primate/pull/7#issuecomment-549441371
 
 
   @iceteabottle that's good idea as well, so basically show features 
templates? However, per the old CloudStack templates have a sort order so I 
don't know if that would break anything esp. in env with large number of 
templates. cc @PaulAngus @svenvogel ?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-primate] iceteabottle commented on issue #7: [WIP] Feature/vm wizard

2019-11-04 Thread GitBox
iceteabottle commented on issue #7: [WIP] Feature/vm wizard
URL: https://github.com/apache/cloudstack-primate/pull/7#issuecomment-549421284
 
 
   > Nice @iceteabottle - do you think instead we could have an explicit tab of 
featured templates (use the star icon), rest looks great!
   
   Thanks. Maybe I could pin the featured above instead of breaking the OS tabs 
logic. What do you think, @rhtyd ?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-primate] rhtyd commented on issue #7: [WIP] Feature/vm wizard

2019-11-04 Thread GitBox
rhtyd commented on issue #7: [WIP] Feature/vm wizard
URL: https://github.com/apache/cloudstack-primate/pull/7#issuecomment-549406169
 
 
   Nice @iceteabottle - do you think instead we could have an explicit tab of 
featured templates (use the star icon), rest looks great!


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-primate] iceteabottle commented on issue #7: [WIP] Feature/vm wizard

2019-11-04 Thread GitBox
iceteabottle commented on issue #7: [WIP] Feature/vm wizard
URL: https://github.com/apache/cloudstack-primate/pull/7#issuecomment-549403949
 
 
   I updated the tagging of the isos.
   ![Bildschirmfoto 2019-11-04 um 16 21 
26](https://user-images.githubusercontent.com/13260952/68132606-48aee000-ff1f-11e9-83fc-79f233d14791.png)
   
   I plan to apply this tagging also for the template selection.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[PRIMATE][SIG] Meeting notes (4 Nov 2019)

2019-11-04 Thread Rohit Yadav
All,

We had our first Primate SIG meeting, here are the meeting notes and summary of 
actions:

Information and Discuss:

  *   Introductions - Bobby, Gabriel, Paul, Rohit, Rudi, Shiv, Sven
  *   High-level project updates discussed (same as last week, no major changes)
  *   Technical preview project/progress board: 
https://github.com/apache/cloudstack-primate/projects/1
  *   Full end to end demo discussed towards the end of the call

Actions and agreements:

  *   QA automation discussion: Travis integration/usage, R and explore unit 
testing
  *   Shiv/Indiqus - manual QA resource availability possible (half-month - Nov 
& Dec) - initial QA round
  *   Rudi/Indiqus - Focus on an action plan for QA automation testing and 
CI/CD pipeline, propose an action plan by next call, and a QA resource from 
Indiqus to start cursory manual testing (TBD)
  *   Sven/EWerk to conduct planning and get back on resourcing, roughly one 
(part-time) dev available in next 2-3 months
  *   Florian/EWerk to continue work on VM deployment wizard for next 2 weeks, 
to pick next tasks after that
  *   Gabriel/PCExtreme proposed a live demo of Primate on PR for manual 
verification/testing, to discuss with Wido for resource donation (VMs) for 
hosting the git-bot and live running preview service (Paul shared similar 
example on the CloudStack docs repo, where a bot builds and gives link on each 
PR of a built docs env)
  *   Gabriel and Rudi to collaborate towards the per PR review/live preview 
setup (CI/CD)
  *   Rohit-Anurag/ShapeBlue - continue to work on zone deployment and attempt 
completion in next two weeks, along with help towards PR review, testing etc.
  *   Bobby/ShapeBlue - manual QA (unavailable for next 2 week, may commence in 
a month's time)


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

rohit.ya...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 



Re: Virtual machines volume lock manager

2019-11-04 Thread Wei ZHOU
We have similar discussion before actually.
see PR https://github.com/apache/cloudstack/pull/2722 and PR
https://github.com/apache/cloudstack/pull/2984
We have made similar changes as describe in PR 2722. It caused duplicated
vms.

The change in PR 2984 (same behavior in old cloudstack versions) is not
ideal for us.

-Wei




On Wed, 30 Oct 2019 at 13:46, Andrija Panic  wrote:

> true, true... Forgot these cases while I was running KVM.
>
> Check if that VM is using a compute offering which is marked as "HA
> enabled" - and if YES< then Wei is 100% right (you can confirm this from
> logs - checking for info on starting that VM on specific hypervisor etc)
> THough, IF doing live migration, I assume it should play fair/nice with HA
> and HA should not kick in.
>
> Wei can you confirm if these 2 play together nice ^^^ ?
>
> Cheers
>
> On Wed, 30 Oct 2019 at 13:11, Wei ZHOU  wrote:
>
> > Hi Rakesh,
> >
> > The duplicated VM is not caused by migration, but by HA.
> >
> > -Wei
> >
> > On Wed, 30 Oct 2019 at 11:31, Rakesh Venkatesh <
> www.rakeshv@gmail.com>
> > wrote:
> >
> > > Hi Andrija
> > >
> > >
> > > Sorry for the late reply.
> > >
> > > Im using 4.7 version of ACS. Qemu version 1:2.5+dfsg-5ubuntu10.40
> > >
> > > Im not sure if ACS job failed or libvirt job as I didnt see into logs.
> > > Yes the vm will be in paused state during migration but after the
> failed
> > > migration, the same vm was in "running" state on two different
> > hypervisors.
> > > We wrote a script to find out how duplicated vm's are running and found
> > out
> > > that more than 5 vm's had this issue.
> > >
> > >
> > > On Mon, Oct 28, 2019 at 2:42 PM Andrija Panic  >
> > > wrote:
> > >
> > > > I've been running KVM public cloud up to recently and have never seen
> > > such
> > > > behaviour.
> > > >
> > > > What versions (ACS, qemu, libvrit) are you running?
> > > >
> > > > How does the migration fail - ACS job - or libvirt job?
> > > > destination VM is by default always in PAUSED state, until the
> > migration
> > > is
> > > > finished - only then the destination VM (on the new host) will get
> > > RUNNING,
> > > > while previously pausing the original VM (on the old host).
> > > >
> > > > i,e.
> > > > phase1  source vm RUNNING, destination vm PAUSED (RAM content
> being
> > > > copied over... takes time...)
> > > > phase2  source vm PAUSED, destination vm PAUSED (last bits of RAM
> > > > content are migrated)
> > > > phase3  source vm destroyed, destination VM RUNNING.
> > > >
> > > > Andrija
> > > >
> > > > On Mon, 28 Oct 2019 at 14:26, Rakesh Venkatesh <
> > > www.rakeshv@gmail.com>
> > > > wrote:
> > > >
> > > > > Hello Users
> > > > >
> > > > >
> > > > > Recently we have seen cases where when the Vm migration fails,
> > > cloudstack
> > > > > ends up running two instances of the same VM on different
> > hypervisors.
> > > > The
> > > > > state will be "running" and not any other transition state. This
> will
> > > of
> > > > > course lead to corruption of disk. Does CloudStack has any option
> of
> > > > volume
> > > > > locking so that two instances of the same VM wont be running?
> > > > > Anyone else has faced this issue and found some solution to fix it?
> > > > >
> > > > > We are thinking of using "virtlockd" of libvirt or implementing
> > custom
> > > > lock
> > > > > mechanisms. There are some pros and cons of the both the solutions
> > and
> > > i
> > > > > want your feedback before proceeding further.
> > > > >
> > > > > --
> > > > > Thanks and regards
> > > > > Rakesh venkatesh
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Andrija Panić
> > > >
> > >
> > >
> > > --
> > > Thanks and regards
> > > Rakesh venkatesh
> > >
> >
>
>
> --
>
> Andrija Panić
>


[GitHub] [cloudstack-primate] rhtyd commented on issue #9: Several minor fixes

2019-11-04 Thread GitBox
rhtyd commented on issue #9: Several minor fixes
URL: https://github.com/apache/cloudstack-primate/pull/9#issuecomment-549290986
 
 
   Thanks @shwstppr I'll proceed with merging, per the guideline of at least a 
single lgtm.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-primate] rhtyd merged pull request #9: Several minor fixes

2019-11-04 Thread GitBox
rhtyd merged pull request #9: Several minor fixes
URL: https://github.com/apache/cloudstack-primate/pull/9
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services