Re: Upgrading OS on hypervisors

Hello Ivan We upgrade only when critical security patch is released like meltdown and L1TF else we don't do upgrades for every single kernel release Sent from my iPhone > On 13-Dec-2018, at 11:05 PM, Ivan Kudryavtsev > wrote: > > Rakesh, > No magic exists. Migrate forth, reboot, and migrate

Re: Upgrading OS on hypervisors

Rakesh, No magic exists. Migrate forth, reboot, and migrate back. What I'm really wondering about is why you upgrade every time, Ubuntu releases a new kernel... There are a pretty small amount of fixes related to KVM and hosts are located in the private networks, they are single-tenant. Maybe you

Upgrading OS on hypervisors

Hello Folks I have a question regarding upgrading OS on hypervisor. We have few platforms with around 200 hypervisors in each platforms. Every time a new Ubuntu kernel comes in with new security patch like L1TF fix or other , we need to upgrade kernel on all hypervisors. Before rebooting

Re: Resource Allocation Question

In my case, hyperthreading number of cores (whatever OS sees as number of cores) times the TurboBoost GHZ is what I get, so for 2x8 cored 2.6Ghz (32 cores with hyperthreading) I get 32 x 3.4 Ghz, which is not what you can achieve at any time (that frequency can be obtained on only very few cores

Re: CloudStack Collab in Brazil

Hello CloudStackers, I had a few meetings with the TDC folks, and we seem to be moving on. They have a slightly different organization than ApacheCon though. Therefore, we were asked to provide them with some “track topics” that fit in the area of Cloud Computing. Then, we could direct

Re: Resource Allocation Question

You have a four core CPU, with 8 threads each? Then, each thread is 2.4 GHz. So, 2.4 * 4 * 8. On Thu, Dec 13, 2018 at 6:14 PM Asai wrote: > Greetings, > > I have a simple question regarding Cloudstack resource allocation. > > In the dashboard, I’m seeing that our Memory is 25 out of 30 GB and

Resource Allocation Question

Greetings, I have a simple question regarding Cloudstack resource allocation. In the dashboard, I’m seeing that our Memory is 25 out of 30 GB and the circle is colored red. # of CPUs is 20 out of 24 and is colored red. But CPU is 33 GHz out of 76 GHz. We have a single Xeon E5-2620 v3 @

Re: How to Reorganise Storage Tags

Hi Melanie, I did change it, yes (tags on existing offerings) and no need to restart mgmt, just I once had to wait for a minute or two, but Im sure it was me messed up something at that specific moment. Tags are evaluated during creation of the volume only (and obviously when changing offering

Re: How to Reorganise Storage Tags

Hi andrija, thanks a lot for your answer. Indeed is absolutely sufficient for me to know that I may change disk_offering_id for a volume. I would assume it is not necessary to shut down/restart the VM or restart management service, but will try tomorrow. I will figure out a suitable path to

Re: How to Reorganise Storage Tags

Hi Melanie, when moving volume to new storage, when you want to change disk offering (or compute offering for ROOT disk...), ACS doesn't allow that - it lists only offerings that have same tag as current offering (not good...) We have inhouse patch, so that you CAN do that, by making sure to

Re: URGENT: Unable to schedule async job for command com.cloud.vm.VmWorkStart, unexpected exception

Done it once (8h old DB)...make sure to kill any new VMs that were created in that period of time (and volumes/templates on the end storage). You might run into situation that some VMs are i.e. powered on during that last 8h, so DB state for that VM will not be in sync with reality, but that

Re: AW:DNS in virtual router not stable

Hi, Ben, Thanks for the reply. We have been thinking about updating /etc/hosts of each of the VM to add the entries for other VMs. Then we don't have dependency to the DNS in the virtual router. But there's lots of work as VMs are being added / removed continuously in our case. I just hope

Re: new committer: Boris Stoyanov (AKA Bobby)

Congrats Bobby, much deserved! From: Paul Angus Sent: Thursday, December 13, 2018 3:22 AM To: users@cloudstack.apache.org; d...@cloudstack.apache.org Cc: Boris Stoyanov Subject: new committer: Boris Stoyanov (AKA Bobby) Hi Everyone, The Project Management

AW:DNS in virtual router not stable

Hi Ivan, I've seen this problem to. The solution is to handle your ip address by the host youre adding static by api or gui. The router VM uses the old host entries set in /etc/hosts if you cleanup vpc network. The host file will be cleared. Kind Regards Ben Von meinem Huawei-Mobiltelefon

Re: new committer: Boris Stoyanov (AKA Bobby)

Congratulations Bobby! David Merrill Senior Systems Engineer, Managed and Private/Hybrid Cloud Services OTELCO 92 Oak Street, Portland ME 04101 office 207.772.5678 www.otelco.com /business/managed-services Confidentiality Message The information contained in this e-mail

Re: URGENT: Unable to schedule async job for command com.cloud.vm.VmWorkStart, unexpected exception

Hi all, is there anyone who tried to restore the database a day ago and restarted cloudstack manager? The two situations differ for the status of the VM / VR and I do not know what to expect and bearing in mind that the problem could recur. The statistics don't interest me. Il 13/12/18

DNS in virtual router not stable

Hi, all, We are using Cloudstack 4.9.2 with KVM and advance networking We are having VPC network, and need to continuously adding / removing VM. One issue we found is, from time-to-time, on the VM deployed, it gets error that the hostname of the other VM is not resolved. We dig into the

How to Reorganise Storage Tags

Hi all, we are currently reorganizing our SAN Setup and I would like to introduce new storage tags on my existing volumes. I was naively assuming to simply change the tags or offering by GUI or API calls. Does not seem to work. Only way to change the tags, seems to be by using a new disk

Re: URGENT: Unable to schedule async job for command com.cloud.vm.VmWorkStart, unexpected exception

Hi On 12/13/18 11:50 AM, Ugo Vasi wrote: > Hi René , > the cloustack installation is 4.11.1.0. From the issue you reported to > me I do not understand if the problem has been solved or not.. > > The big problem is that I can not perform any new jobs. > > In addition to the stopped VM there are

Re: new committer: Boris Stoyanov (AKA Bobby)

Thanks all! It’s an honor for me, I look forward to brake your code! :) Bobby. boris.stoya...@shapeblue.com  www.shapeblue.com Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue > On 13 Dec 2018, at 13:49, Gabriel Beims Bräscher wrote: > > Congrats Bobby, well deserved! > >

Re: new committer: Boris Stoyanov (AKA Bobby)

Congrats Bobby, well deserved! Em qui, 13 de dez de 2018 às 09:24, Rohit Yadav escreveu: > Welcome Bobby (Boris)! Well deserved. > > > - Rohit > > > > > > > From: Paul Angus > Sent: Thursday, December 13, 2018 2:52:12 PM > To:

Re: new committer: Boris Stoyanov (AKA Bobby)

Welcome Bobby (Boris)! Well deserved. - Rohit From: Paul Angus Sent: Thursday, December 13, 2018 2:52:12 PM To: users@cloudstack.apache.org; d...@cloudstack.apache.org Cc: Boris Stoyanov Subject: new committer: Boris Stoyanov

Re: new committer: Boris Stoyanov (AKA Bobby)

Congratulations Bobby! Regards, Nicolas Vazquez From: Dingane Hlaluku Sent: Thursday, December 13, 2018 7:54:56 AM To: d...@cloudstack.apache.org; users@cloudstack.apache.org Cc: Boris Stoyanov Subject: Re: new committer: Boris Stoyanov (AKA Bobby)

Re: new committer: Boris Stoyanov (AKA Bobby)

Congratulations Bobby, well deserved. Regards, From: Glenn Wagner Sent: Thursday, December 13, 2018 12:20:36 PM To: d...@cloudstack.apache.org; users@cloudstack.apache.org Cc: Boris Stoyanov Subject: RE: new committer: Boris Stoyanov (AKA Bobby) Congrats Bobby

Re: URGENT: Unable to schedule async job for command com.cloud.vm.VmWorkStart, unexpected exception

Hi René , the cloustack installation is 4.11.1.0. From the issue you reported to me I do not understand if the problem has been solved or not.. The big problem is that I can not perform any new jobs. In addition to the stopped VM there are two routes that were running on the host that has

RE: new committer: Boris Stoyanov (AKA Bobby)

Congrats Bobby -Glenn glenn.wag...@shapeblue.com  www.shapeblue.com Winter Suite, 1st Floor, The Avenues, Drama Street, Somerset West, Cape Town 7129South Africa @shapeblue -Original Message- From: Paul Angus Sent: Thursday, 13 December 2018 11:22 AM To:

Re: new committer: Boris Stoyanov (AKA Bobby)

Congratulations Bobby! Regards, Dag Sonstebo Cloud Architect ShapeBlue S: +44 20 3603 0540 | dag.sonst...@shapeblue.com | http://www.shapeblue.com | Twitter:@ShapeBlue On 13/12/2018, 09:29, "Paul Angus" wrote: Hi

Re: new committer: Boris Stoyanov (AKA Bobby)

Congrats Bobby ! On Thu, 13 Dec 2018 at 10:58, Sateesh Chodapuneedi < sateesh.chodapune...@accelerite.com> wrote: > Hearty Congratulations, Bobby! > Well deserved. > Bobby has been actively helping with validation of MRs under review. Also > helping users in users list. > > Regards, > Sateesh >

Re: URGENT: Unable to schedule async job for command com.cloud.vm.VmWorkStart, unexpected exception

Hi I think you hit https://github.com/apache/cloudstack/issues/2880 Is this already 4.11.2? We have also seen this in our lab, could not really reproduce it, seems to be a race condition. Regards René On 12/13/18 9:01 AM, Ugo Vasi wrote: > Hi all, > I'm trying to reboot a vm after the host it

Re: new committer: Boris Stoyanov (AKA Bobby)

Hearty Congratulations, Bobby! Well deserved. Bobby has been actively helping with validation of MRs under review. Also helping users in users list. Regards, Sateesh -Original Message- From: Paul Angus Reply-To: "d...@cloudstack.apache.org" Date: Thursday, 13 December 2018 at 14:59

Re: URGENT: Unable to schedule async job for command com.cloud.vm.VmWorkStart, unexpected exception

We have verified that the problem is not tied to a vm but it also concerns the other VMs that are stopped. Trying to restart them gives the same error message. Restoring the previous day's database which problems might imply? Il 13/12/18 09:01, Ugo Vasi ha scritto: Hi all, I'm trying to

Re: new committer: Boris Stoyanov (AKA Bobby)

Great to hear. :-) > Am 13.12.2018 um 10:29 schrieb Paul Angus : > > Hi Everyone, > > The Project Management Committee (PMC) for Apache CloudStack > has invited Boris Stoyanov to become a committer and we are pleased > to announce that he has accepted. > > Please join me in congratulating

new committer: Boris Stoyanov (AKA Bobby)

Hi Everyone, The Project Management Committee (PMC) for Apache CloudStack has invited Boris Stoyanov to become a committer and we are pleased to announce that he has accepted. Please join me in congratulating Bobby! Being a committer enables easier contribution to the project since there is no

URGENT: Unable to schedule async job for command com.cloud.vm.VmWorkStart, unexpected exception

Hi all, I'm trying to reboot a vm after the host it ran on crashed and restarted from the HA system. All the VMs running on the rebooted host were restarted on other hosts except one. In the web interface and using cloudmonkey I get this message:   "Unable to schedule async job for command