RE: [DISCUSS] Change of the official CHAT channel

[Paul Angus]

Personally, I agree with Nux, I could live without yet another communication 
medium that I have to check. So I would prefer the searchable medium of the 
mailing lists with the fall back of maybe Slack for group calls or chats if 
really required.   Given the worldwide time zones we cover, real-time 
conversations are automatically going to exclude a large number of people.  The 
conversation threading in email clients allows me to see the subject of a 
conversation and decide if can or want to join in.

paul.an...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


-Original Message-
From: Andrija Panic  
Sent: 22 August 2019 19:28
To: Nux! 
Cc: dev 
Subject: Re: [DISCUSS] Change of the official CHAT channel

My whole idea is that having one (IRC) marketed on web pages, while using the 
other silently (Slack) makes less than zero sense to me.

And, for me, a tool is a tool, I'm not married to it (some people prefer vi 
editor and have religious attachments to it, I just use nano to get the job
done)

On Thu, Aug 22, 2019, 19:49 Nux!  wrote:

> I'm heavily against Slack or any other proprietary, closed solutions.
>
> I think it's a step back generally for the Internet at large and even 
> more so for an open source project; I can't reconcile the two in my 
> heart.
>
> Having said that, I believe the chat is dead not because it's IRC, but 
> because people prefer async comms (ie email). It'll be the same for 
> Slack.
>
>
> We should be promoting the mailing lists. They are active and the 
> archives are open to search engines etc and can further provide 
> helpful information to everyone.
>
> I won't -1 the decision, I don't want to be in the way of "progress", 
> but it's not a +1 either. I won't be using it.
>
> My 2p
>
>
> ---
> Sent from the Delta quadrant using Borg technology!
>
> On 2019-08-22 16:57, Andrija Panic wrote:
> > Hi guys,
> >
> > Since IRC is pretty dead, and we already have a Slack channel ( 
> > https://apachecloudstack.slack.com ) that we use atm, AND since 
> > there seems to be an official ASF slack channel at 
> > https://the-asf.slack.com/, I would like to open a discussion of the 
> > idea to "officially"  move (i.e.
> > marketing
> > this on all event pages and main web site) to that new CloudStack 
> > channel on the official ASF slack account/page - and abandon (close 
> > for good) all others chat channels.
> >
> > i.e. on this year conference page (http://us.cloudstackcollab.org/) 
> > we currently announce the IRC channel (???) to be the one (and AFAIK 
> > it's pretty dead) - so I would propose to move forward and update 
> > this, so the users can be aware of "alive" chat channel
> >
> > Suggestions, opinions ?
> >
> > Regards,
> >
> > Andrija Panić
>

Re: Cancel the async task in execution

[Sven Vogel]

We had the same problem and manually edit the async... table. So far I know 
there is nothing.

Von meinem iPhone gesendet


__

Sven Vogel
Teamlead Platform

EWERK RZ GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 11
F +49 341 42649 - 18
s.vo...@ewerk.com
www.ewerk.com

Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Frank Richter
Registergericht: Leipzig HRB 17023

Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 2-1:2011

EWERK-Blog | LinkedIn | Xing | Twitter | Facebook

Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.

Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist 
vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der 
bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, 
Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte 
informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die 
E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen 
Dank.

The contents of this e-mail (including any attachments) are confidential and 
may be legally privileged. If you are not the intended recipient of this 
e-mail, any disclosure, copying, distribution or use of its contents is 
strictly prohibited, and you should please notify the sender immediately and 
then delete it (including any attachments) from your system. Thank you.
> Am 06.08.2019 um 17:48 schrieb Riepl, Gregor (SWISS TXT) 
> :
>
> You can change the async_job DB record to error or similar, but that will 
> most likely not stop the task.
>
> We've done this in the past, but only when a job was stuck forever due to 
> incorrect error handling and not when it was still running.
>
> Is there nothing in the API to stop a running task?
> 
> From: li jerry 
> Sent: 06 August 2019 15:49
> To: users@cloudstack.apache.org 
> Subject: 答复: Cancel the async task in execution
>
> Restarting all mgmt has a big impact.
> If you can directly modify async_job to let the task abort, this will be very 
> good.
>
> 发件人: Andrija Panic
> 发送时间: 2019年8月6日 19:29
> 收件人: users
> 主题: Re: Cancel the async task in execution
>
> An aggressive way is to restart all mgmt servers - all async jobs will be
> cleared our / fail - but there is also a way to wipe from async_job table
> or similar, but I can't remember that from top of my head now...
>
>> On Tue, 6 Aug 2019 at 12:03, li jerry  wrote:
>>
>> Hello all
>>
>> Is there an asynchronous task already in progress, is there any way to
>> stop it and cancel it? (Can I change the database?)
>>
>> Scenes:
>> Volume migrates across the pool. Due to the large volume capacity, offline
>> migration takes a long, long, and long time, so it needs to be cancelled.
>>
>
>
> --
>
> Andrija Panić
>