[REVIVE][DISCUSS] Closing issues & PR after a certain time

[Daan Hoogland]

People,
I want to revive this discussion and bring Vishesh' PR under your
attention again.
The discussion there is mostly about the length of the period before closing.
So here I am going to state 1year - first warning, 1.5years second
warning, 2 years closing. What do you all think?

There are also issues that we might consider interesting but not
functionally complete or clear, we can convert those to github
discussions, and I would like to encourage all of you to do that as
sometimes issues will lead to issues and not to PRs and those are
basically discussions to be had.

please respond with your comments or put them in
https://github.com/apache/cloudstack/pull/8667

regards,

On 2024/02/16 09:17:02 Vishesh Jindal wrote:
> I have created a PR with the changes 
> here:https://github.com/apache/cloudstack/pull/8667
>
> I propose that we enable it. As Daan suggested, we can always remove the 
> action if it doesn't work out. And if a PR/issue gets closed, we can always 
> reopen it.
>
>
>
> ____
> From: Daan Hoogland 
> Sent: Wednesday, February 14, 2024 2:17 PM
> To: d...@cloudstack.apache.org 
> Subject: Re: [DISCUSS] Closing issues & PR after a certain time
>
> i'm a bit -0 on this. I agree that a lot of stale issues deserve
> closing, but others are really long term goals. I do not want to block
> this great idea but am just a bit worried about other great ideas
> getting lost. So I would propose to tag anything we close or not
> remove the stale tag, so these can be easily found. I am not worried
> too much about PRs, just issues.
>
> On the other hand, we can always remove the gha again, so maybe we
> should install it and see if it works for us.
>
> On Wed, Feb 14, 2024 at 4:49 AM Kiran Chavala
>  wrote:
> >
> > Good idea Vishesh
> >
> > +1 for using Githubactions
> >
> > Regards
> > Kiran
> >
> > From: Vishesh Jindal 
> > Date: Tuesday, 13 February 2024 at 6:33 PM
> > To: d...@cloudstack.apache.org 
> > Subject: [DISCUSS] Closing issues & PR after a certain time
> > Hi everyone,
> >
> > I was going through the issues and PRs, and I noticed that a lot of them 
> > are really old and some of them are waiting for the original author to 
> > reply.
> >
> > I wanted to discuss if we should add a github action 
> > (https://github.com/marketplace/actions/close-stale-issues) for auto 
> > closing the issues and PRs after a certain time.
> >
> > From the github actions' documentation, this is how it works:
> >
> >   *   Add a label "Stale" on issues and pull requests after 60 days of 
> > inactivity and comment on them
> >   *   Close the stale issues and pull requests after 7 days of inactivity
> >   *   If an update/comment occur on stale issues or pull requests, the 
> > stale label will be removed and the timer will restart
> >
> > Instead of using the defaults, I would like to:
> >
> >   *
> > mark the issue/PR stale after 90 days
> >   *
> >  close the stale issue/PR after 30 days
> >
> > Let me know if this sounds good. I will create the PR to set this up.
> >
> > Regards,
> > Vishesh
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> --
> Daan
>

Re: Shared guest network assigned to multiple domains

[Daan Hoogland]

ok, from what I know now I have exhausted my clues. Hope you get your
migration done expediently.

On Fri, Apr 26, 2024 at 2:29 PM Ruben Bosch  wrote:
>
> Hmm, that might be possible. However we would like to automate as much as
> possible. Changing existing IPs to unused ones is not an option, no.
>
> On Fri, Apr 26, 2024 at 2:25 PM Daan Hoogland 
> wrote:
>
> > ok, and you probably can't redistribute the IPs in the domain or
> > define the order of migration to be in line with the range?
> >
> > On Fri, Apr 26, 2024 at 2:01 PM Ruben Bosch  wrote:
> > >
> > > The target domain already exists with VMs running in it
> > >
> > > On Fri, Apr 26, 2024 at 1:46 PM Daan Hoogland 
> > > wrote:
> > >
> > > > so probably a stupoid suggestion, but why ot rename the domain then?
> > > >
> > > > On Fri, Apr 26, 2024 at 1:04 PM Ruben Bosch 
> > wrote:
> > > > >
> > > > > Hi Daan, cases may vary. For our first migration in the end all VMs
> > will
> > > > > move to the other domain.
> > > > >
> > > > > On Fri, Apr 26, 2024 at 12:32 PM Daan Hoogland <
> > daan.hoogl...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Ruben, do you need to move domainA completely to domainB or do you
> > > > > > need to move *some* VMs from it?
> > > > > >
> > > > > > On Fri, Apr 26, 2024 at 11:00 AM Ruben Bosch  > >
> > > > wrote:
> > > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > We're looking into the following. We are using advanced
> > networking
> > > > on ACS
> > > > > > > 4.16.1 (upgrading soon to 4.18.1). We have a guest network that
> > is
> > > > > > assigned
> > > > > > > to a specific domain A (ROOT/foo/domainA). Now we will need to
> > move
> > > > VMs
> > > > > > > from domain A to domain B (ROOT/bar/domainB) while preserving IP
> > > > > > addresses.
> > > > > > > We are exploring our options on how to make this a seamless
> > > > transition.
> > > > > > We
> > > > > > > have found that:
> > > > > > >
> > > > > > > - we cannot add the network with the same parameters again, as it
> > > > fails
> > > > > > on
> > > > > > > IP address start/end overlap check
> > > > > > > - we cannot add the extra domain in the "domain_network_ref"
> > table
> > > > as it
> > > > > > > yields no result
> > > > > > > - we can assign the domain to ROOT and ensure no other users can
> > > > claim
> > > > > > IPs
> > > > > > > by updating "state" in "user_ip_address"
> > > > > > >
> > > > > > > Are there any other options available that we can think of? I'm
> > > > looking
> > > > > > > forward to your input.
> > > > > > >
> > > > > > > Kind regards,
> > > > > > >
> > > > > > > Ruben Bosch
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Daan
> > > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Daan
> > > >
> >
> >
> >
> > --
> > Daan
> >



-- 
Daan

Re: Shared guest network assigned to multiple domains

[Daan Hoogland]

ok, and you probably can't redistribute the IPs in the domain or
define the order of migration to be in line with the range?

On Fri, Apr 26, 2024 at 2:01 PM Ruben Bosch  wrote:
>
> The target domain already exists with VMs running in it
>
> On Fri, Apr 26, 2024 at 1:46 PM Daan Hoogland 
> wrote:
>
> > so probably a stupoid suggestion, but why ot rename the domain then?
> >
> > On Fri, Apr 26, 2024 at 1:04 PM Ruben Bosch  wrote:
> > >
> > > Hi Daan, cases may vary. For our first migration in the end all VMs will
> > > move to the other domain.
> > >
> > > On Fri, Apr 26, 2024 at 12:32 PM Daan Hoogland 
> > > wrote:
> > >
> > > > Ruben, do you need to move domainA completely to domainB or do you
> > > > need to move *some* VMs from it?
> > > >
> > > > On Fri, Apr 26, 2024 at 11:00 AM Ruben Bosch 
> > wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > We're looking into the following. We are using advanced networking
> > on ACS
> > > > > 4.16.1 (upgrading soon to 4.18.1). We have a guest network that is
> > > > assigned
> > > > > to a specific domain A (ROOT/foo/domainA). Now we will need to move
> > VMs
> > > > > from domain A to domain B (ROOT/bar/domainB) while preserving IP
> > > > addresses.
> > > > > We are exploring our options on how to make this a seamless
> > transition.
> > > > We
> > > > > have found that:
> > > > >
> > > > > - we cannot add the network with the same parameters again, as it
> > fails
> > > > on
> > > > > IP address start/end overlap check
> > > > > - we cannot add the extra domain in the "domain_network_ref" table
> > as it
> > > > > yields no result
> > > > > - we can assign the domain to ROOT and ensure no other users can
> > claim
> > > > IPs
> > > > > by updating "state" in "user_ip_address"
> > > > >
> > > > > Are there any other options available that we can think of? I'm
> > looking
> > > > > forward to your input.
> > > > >
> > > > > Kind regards,
> > > > >
> > > > > Ruben Bosch
> > > >
> > > >
> > > >
> > > > --
> > > > Daan
> > > >
> >
> >
> >
> > --
> > Daan
> >



-- 
Daan

Re: Shared guest network assigned to multiple domains

[Daan Hoogland]

so probably a stupoid suggestion, but why ot rename the domain then?

On Fri, Apr 26, 2024 at 1:04 PM Ruben Bosch  wrote:
>
> Hi Daan, cases may vary. For our first migration in the end all VMs will
> move to the other domain.
>
> On Fri, Apr 26, 2024 at 12:32 PM Daan Hoogland 
> wrote:
>
> > Ruben, do you need to move domainA completely to domainB or do you
> > need to move *some* VMs from it?
> >
> > On Fri, Apr 26, 2024 at 11:00 AM Ruben Bosch  wrote:
> > >
> > > Hi all,
> > >
> > > We're looking into the following. We are using advanced networking on ACS
> > > 4.16.1 (upgrading soon to 4.18.1). We have a guest network that is
> > assigned
> > > to a specific domain A (ROOT/foo/domainA). Now we will need to move VMs
> > > from domain A to domain B (ROOT/bar/domainB) while preserving IP
> > addresses.
> > > We are exploring our options on how to make this a seamless transition.
> > We
> > > have found that:
> > >
> > > - we cannot add the network with the same parameters again, as it fails
> > on
> > > IP address start/end overlap check
> > > - we cannot add the extra domain in the "domain_network_ref" table as it
> > > yields no result
> > > - we can assign the domain to ROOT and ensure no other users can claim
> > IPs
> > > by updating "state" in "user_ip_address"
> > >
> > > Are there any other options available that we can think of? I'm looking
> > > forward to your input.
> > >
> > > Kind regards,
> > >
> > > Ruben Bosch
> >
> >
> >
> > --
> > Daan
> >



-- 
Daan

Re: Shared guest network assigned to multiple domains

[Daan Hoogland]

Ruben, do you need to move domainA completely to domainB or do you
need to move *some* VMs from it?

On Fri, Apr 26, 2024 at 11:00 AM Ruben Bosch  wrote:
>
> Hi all,
>
> We're looking into the following. We are using advanced networking on ACS
> 4.16.1 (upgrading soon to 4.18.1). We have a guest network that is assigned
> to a specific domain A (ROOT/foo/domainA). Now we will need to move VMs
> from domain A to domain B (ROOT/bar/domainB) while preserving IP addresses.
> We are exploring our options on how to make this a seamless transition. We
> have found that:
>
> - we cannot add the network with the same parameters again, as it fails on
> IP address start/end overlap check
> - we cannot add the extra domain in the "domain_network_ref" table as it
> yields no result
> - we can assign the domain to ROOT and ensure no other users can claim IPs
> by updating "state" in "user_ip_address"
>
> Are there any other options available that we can think of? I'm looking
> forward to your input.
>
> Kind regards,
>
> Ruben Bosch



-- 
Daan

Re: RVR's in master/master state

[Daan Hoogland]

thanks Gary, good te hear

On Fri, Apr 19, 2024 at 6:20 PM Gary Dixon 
wrote:

> Hi Daan
>
> Sorry - I forgot to post back what the issue turned out to be.
>
> We had a power outage in our building where our Dev environment is racked.
> After doing some tcp dumps on some vxlan interfaces I was seeing lots of
> bad checksums.
> Our Network engineer swore that the switches we're all OK but after
> re-applying the multicast config on the switches - all of the RVR's came
> back into a stable Master/Backup state across all VPC's.
> Hope this helps others if they are seeing strange behaviour with VPC RVR's
> when using VXLAN guest isolation
>
> BR
>
> Gary
>
>
>
> Gary Dixon
> Quadris Cloud Manager
> +44 (0) 161 537 4980 <+44%20(0)%20161%20537%204980>
>  +44 (0) 7989 717661 <+44%20(0)%207989%20717661>
> gary.di...@quadris.co.uk
> www.quadris.com
> Innovation House, 12‑13 Bredbury Business Park
> Bredbury Park Way, Bredbury, Stockport, SK6 2SN
> -Original Message-
> From: Daan Hoogland 
> Sent: Friday, April 19, 2024 3:08 PM
> To: users@cloudstack.apache.org
> Subject: Re: RVR's in master/master state
>
> sorry no one could help you Gary,
> Have you gotten any further on this issue?
>
> On Fri, Apr 5, 2024 at 4:59 PM Gary Dixon  >
> wrote:
>
> > HI all
> >
> >
> >
> > ACS 4.15.2
> >
> > Ubuntu 20.04
> >
> > KVM
> >
> > Adv Zone no sec groups
> >
> >
> >
> > We recently had to move all of our dev ACS environment virtual
> > management and mysql servers to a new isolated subnet for security
> reasons.
> >
> >
> >
> > Since then all of the VPC RVR’s are in master/master mode.
> >
> > If I restart a VPC with cleanup the RVR’s come back into a
> > master/backup state for a few minutes but then go into master/master
> > state rendering the VPC useless.
> >
> >
> >
> > In the cloud.log on one of the RVR’s it is full of these errors:
> >
> > “2024-04-05 14:51:43,843 ERROR Not able to setup source-nat for a
> > regular router yet”
> >
> >
> >
> > Can anyone point me in the right direction to resolve this issue ?
> >
> > Are there other logs I could look at or services on the RVR’s to check ?
> >
> >
> >
> > BR
> >
> >
> >
> > Gary
> >
> >
> > Gary Dixon
> > Quadris Cloud Manager
> > +44 (0) 161 537 4980 <+44%20(0)%20161%20537%204980>
> > +44 (0) 7989 717661 <+44%20(0)%207989%20717661>
> > gary.di...@quadris.co.uk
> > http://www.q/
> > uadris.com%2F=05%7C02%7CGary.Dixon%40quadris.co.uk%7C6d453f64080c
> > 449f243d08dc607a6e5c%7Cf1d6abf3d3b44894ae16db0fb93a96a2%7C0%7C0%7C6384
> > 91326163464980%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2l
> > uMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=tKsAdO2jZBj5qeL
> > CsCSOX0zLNsvyrXSeY7PegUCOBhE%3D=0
> > Innovation House, 12‑13 Bredbury Business Park Bredbury Park Way,
> > Bredbury, Stockport, SK6 2SN
> >
>
>
> --
> Daan
>


-- 
Daan

Re: Backup options

[Daan Hoogland]

looks like you've been quite complete in your sumup Jimmy

On Fri, Apr 12, 2024 at 3:41 AM Jimmy Huybrechts  wrote:
>
> Hi,
>
> What are the current backup options that work with Cloudstack?
>
> - Veeam enterprise
> - Networker
> - Backroll
>
> The above I found, backroll seems to not be very active anymore or I might be 
> mistaken? Github says last was 10 months ago.
>
> Are there any others too?
>
> --
> Jimmy



-- 
Daan

Re: ManageIQ + CloudStack

[Daan Hoogland]

Piotr,
sounds good. Are you willing to propose and mentor this effort?

On Thu, Apr 11, 2024 at 11:26 AM Piotr Pisz  wrote:
>
> Hi,
>
>
>
> I have an idea that could be implemented as part of GSOC 2024.
>
>
>
> We currently use vSphere+Automation Center for internal purposes, but we
> plan to migrate to CloudStack/OpenStack. Instead of vRealize Automation
> Center, we would like to use ManageIQ (supports vSphere and OpenStack) as a
> user portal.
>
>
>
> ManageIQ is a very good and universal solution, it would be ideal if, as
> part of Google Summer of Code 2024, an attempt was made to write a cloud
> provider for CloudStack.
>
>
>
>  
> https://www.manageiq.org/docs/guides/providers/writing_a_new_provider
>
>
>
> What do you think about it?
>
>
>
> Regards,
>
> Piotr
>


-- 
Daan

Re: CloudStack managing KVM Hypervisors on multiple architectures?

[Daan Hoogland]

good point Rishi,
I think you would have to separate the hardware into different
clusters at least, but maybe even separate zones. I never heard of
anybody doing a setup like yours.

On Wed, Apr 10, 2024 at 6:56 PM Rishi Misra  wrote:
>
> Can a CloudStack instance running on x86 manage deployments on both x86 and
> Raspberry Pi (or any other archs)?
>
> I am not sure how it will affect management SystemVMs given the different
> archs in the mix?
>
> Any pointers are greatly appreciated.
>
> Thanks!



-- 
Daan

Re: RVR's in master/master state

[Daan Hoogland]

sorry no one could help you Gary,
Have you gotten any further on this issue?

On Fri, Apr 5, 2024 at 4:59 PM Gary Dixon 
wrote:

> HI all
>
>
>
> ACS 4.15.2
>
> Ubuntu 20.04
>
> KVM
>
> Adv Zone no sec groups
>
>
>
> We recently had to move all of our dev ACS environment virtual management
> and mysql servers to a new isolated subnet for security reasons.
>
>
>
> Since then all of the VPC RVR’s are in master/master mode.
>
> If I restart a VPC with cleanup the RVR’s come back into a master/backup
> state for a few minutes but then go into master/master state rendering the
> VPC useless.
>
>
>
> In the cloud.log on one of the RVR’s it is full of these errors:
>
> “2024-04-05 14:51:43,843 ERRORNot able to setup source-nat for a
> regular router yet”
>
>
>
> Can anyone point me in the right direction to resolve this issue ?
>
> Are there other logs I could look at or services on the RVR’s to check ?
>
>
>
> BR
>
>
>
> Gary
>
>
> Gary Dixon
> Quadris Cloud Manager
> +44 (0) 161 537 4980 <+44%20(0)%20161%20537%204980>
>  +44 (0) 7989 717661 <+44%20(0)%207989%20717661>
> gary.di...@quadris.co.uk
> www.quadris.com
> Innovation House, 12‑13 Bredbury Business Park
> Bredbury Park Way, Bredbury, Stockport, SK6 2SN
>


-- 
Daan

Re: [DISCUSS] Define a release schedule for the project

[Daan Hoogland]

nice to see this discussion being had again and sorry to be late in
replying João,

I see no replies have come forward yet. Let's add a new
https://github.com/apache/cloudstack/discussions/new/choose for this
as well. I still feel my proposal is good and should have been
applied. but we can gather all kinds of proposals in one place and get
to some kind of improvement someday.

One point of criticism on your proposal, though not a breaking point,
is that it doesn't guarantee backwards compatibility, something we
have always maintained so far (through upgrade paths). Not being
chained to old to technical debt is good, but it should not leave
people behind ;) We do have a hardly ever used procedure to deprecate
old plugins for instance. we should think about applying that to API
and other namings as well.

regards,

On Fri, Mar 15, 2024 at 12:10 PM João Jandre Paraquetti
 wrote:
>
> Hi all,
>
> I had posted this message on another thread, but following Rohit's
> advice I've decided to create a new one for it. That being said, I have
> another proposal for the versioning scheme. Instead of dropping the "X"
> on our X.Y.Z.N, we can set a fixed schedule (that can be further
> discussed) for the version changes:
>
> - Every two years, we release a major version (X), which can contain
> changes that break backward compatibility, such as (but not limited to):
> removing unused/useless APIs, renaming APIs, and changing the default
> behavior of features. These changes must be discussed with the devs and
> be properly communicated to the community (via API deprecation, for
> example) at least one minor version before the major release;
> - Every semester, we release a minor version (Y) of the current major
> (X) version, these can contain new features/APIs, as long as the
> backward compatibility is maintained; also, feature/API deprecation
> should happen on these versions;
> - Every 2/3 months, we release patch versions (Z), that fix any bugs
> that were released with the major and minor versions, these versions
> should not contain any new features;
> - In extreme cases (such as with security issues) we work on and release
> security versions (N);
>
> The proposed schedule is only a sketch that can be worked on. However I
> believe that the project can benefit from:
> 1. A fixed release schedule;
> 2. A mechanism to introduce disruptive changes, so that the project can
> evolve and not be chained to the same features/API/limitation/technical
> debts forever.
>
> Furthermore, having a schedule allows us to have a project roadmap, that
> outlines the future deprecations, changes and big features.
>
> Best Regards,
>
> João Jandre.
>


-- 
Daan

Re: [VOTE] Apache CloudStack 4.18.2.0 RC2

[Daan Hoogland]

+1 binding
I checked the hashes alright and the log of commit/tag (Note this last
check is based on the recent TZ issues to make sure nothing slipped
through). Other than that trusting on the testing I was involved in
over the last month or so.

On Fri, Apr 12, 2024 at 1:37 PM João Jandre  wrote:
>
> Hi All,
>
> I've created a 4.18.2.0 release (RC2), with the following artifacts up
> for a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/tree/4.18.2.0-RC20240412T0825
> Commit: 154566f914c778d448d4ab07b47b2db874bbf982
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.18.2.0/
>
> PGP release keys (signed using 488D90DA107445E3243D162606F3CEC65B335790):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> Vote will be open for 120 hours (due to the weekend).
>
> 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)
>


-- 
Daan

Re: New PMC member: Slavka Peleva

[Daan Hoogland]

welcome aboard @slav...@apache.org

On Wed, Apr 10, 2024 at 1:11 PM Ivet Petrova  wrote:
>
> Hello all,
>
> The Project Management Committee (PMC) for Apache CloudStack
> has invited Slavka Peleva to become a PMC member and we are pleased
> to announce that they have accepted.
>
> Slavka has contributed in the past and has shown effort to make the
> project run smoothly
>
> Please join me in congratulating Slavka!
>
>
> Best regards,
>
>
>
>


-- 
Daan

Re: [VOTE] Apache CloudStack 4.18.2.0 RC1

[Daan Hoogland]

ok, if it is a regression (introduction of a bug on formerly working
functionality) It would mean a blocker and we can easily respin a new
RC. What do you think @João Jandre Paraquetti ?

On Mon, Apr 8, 2024 at 10:43 AM Rene Peinthor  wrote:
>
> Probably neither a blocker or critical, assuming the same bug (other
> driver) is currently in 4.19.0.
> But I feel bad knowing, that I would introduce a bug for other storage
> drivers.
>
> On Mon, Apr 8, 2024 at 10:30 AM Daan Hoogland 
> wrote:
>
> > Rene, is this a blocker (or critical issue) in your opinion ?
> >
> > On Mon, Apr 8, 2024 at 8:06 AM Rene Peinthor 
> > wrote:
> > >
> > > -1
> > >
> > > Because I would still this to be included:
> > > https://github.com/apache/cloudstack/pull/8790
> > >
> > > On Fri, Apr 5, 2024 at 9:11 PM João Jandre  wrote:
> > >
> > > > Hi All,
> > > >
> > > > I've created a 4.18.2.0 release (RC1), with the following artifacts up
> > > > for a vote:
> > > >
> > > > Git Branch and Commit SH:
> > > > https://github.com/apache/cloudstack/tree/4.18.2.0-RC20240405T1541
> > > > Commit: 0d19ffa61c76f592c77ea04a982e15e8575ceb45
> > > >
> > > > Source release (checksums and signatures are available at the same
> > > > location):
> > > > https://dist.apache.org/repos/dist/dev/cloudstack/4.18.2.0/
> > > >
> > > > PGP release keys (signed using
> > 488D90DA107445E3243D162606F3CEC65B335790):
> > > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> > > >
> > > > Vote will be open for 120 hours (due to the weekend).
> > > >
> > > > 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)
> > > >
> >
> >
> >
> > --
> > Daan
> >



-- 
Daan

Re: [VOTE] Apache CloudStack 4.18.2.0 RC1

[Daan Hoogland]

Rene, is this a blocker (or critical issue) in your opinion ?

On Mon, Apr 8, 2024 at 8:06 AM Rene Peinthor  wrote:
>
> -1
>
> Because I would still this to be included:
> https://github.com/apache/cloudstack/pull/8790
>
> On Fri, Apr 5, 2024 at 9:11 PM João Jandre  wrote:
>
> > Hi All,
> >
> > I've created a 4.18.2.0 release (RC1), with the following artifacts up
> > for a vote:
> >
> > Git Branch and Commit SH:
> > https://github.com/apache/cloudstack/tree/4.18.2.0-RC20240405T1541
> > Commit: 0d19ffa61c76f592c77ea04a982e15e8575ceb45
> >
> > Source release (checksums and signatures are available at the same
> > location):
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.18.2.0/
> >
> > PGP release keys (signed using 488D90DA107445E3243D162606F3CEC65B335790):
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> > Vote will be open for 120 hours (due to the weekend).
> >
> > 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)
> >



-- 
Daan

Re: cloudstack-agent setup

[Daan Hoogland]

Wingrunt,
Did you try reinstalling the agent?
did you check libvirt and qemu versions are supported?
can you check your java version?
This is not something I ever heard before. Logging will only stop if
your disk is full afaik.

On Fri, Apr 5, 2024 at 8:08 AM Wingrunt Platform  wrote:
>
> Hit a new wall.. My cloudstack agent suddenly started failing.
> Also I see its not spitting any logs to agent.log
>
> I understand kvm, libvirt etc to be setup and it is all done and working.
> agent simply won't start. I went through the blog configuring all kvm
> properties
> also other sites to configure. It was all starting perfectly. Not sure
> where I fried it.
> But agent will simply be resistant to start. Says Activating and dead.
>
> Questions summary:
> 1. Why has logging stopped ? How to configure ? I remember seeing it in
> agent.properties. Yes ?
> 2. Should CS manager UI be configured to integrate with the hypervisor (Kvm
> in my case). Should
>
> Once again thanks to all.
>
> Best regards
> RSK



-- 
Daan

Re: Volumes in "Destroy" Status

[Daan Hoogland]

Marty,
can you find the volume in ACS? If so it should provide you with the right UUID.
If this was the right one, check if they are removed from the backend
(and delete the entry from the DB). I didn't say that last part, the
internet is lying! The entries should be garbage collected
automatically ,so more trouble shooting might be advisable.

On Fri, Mar 15, 2024 at 4:42 AM Marty Godsey  wrote:
>
> Hello,
>
> Some volumes are in a destroy state, but cant be “deleted” from the GUI. I 
> still see them, but when I try to delete them, I get an error.
>
> The logs say
>
> 2024-03-14 23:41:55,355 DEBUG [c.c.h.x.r.XenServerStorageProcessor] 
> (DirectAgent-476:ctx-f6309c2e) (logid:fbda8187) Failed to delete volume
> The uuid you supplied was invalid.
>
> What's the best way to clear this and ensure this volume is gone?
>
> Thank you in advance.
>
>
>   *   Marty
>
>
>
>


-- 
Daan

Re: Migrating a system VM to another cluster results in no public access

[Daan Hoogland]

Hi,
sorry you didn't get any resolution so far. Did you get any further
with your issue?
Some questions;
Is there a public IP defined in ACS for the VMs?
Do the L2 switches have the same upstream subnet and v(x)lan?

I don't think you need to separate PODs. Not sure what you mean by that though.

On Wed, Mar 6, 2024 at 8:58 PM  wrote:
>
> Hello Community,
>
>
>
> There are two clusters in the same zone.
>
> Example
>
> clusterA
>
> clusterB
>
>
>
> Currently, the system VMs (CPVM & SSVM) exist in clusterA for both of them.
>
> If we migrate these two system VMs to clusterB, access to the system VMs'
> public IP will become unavailable.
>
>
>
> Although clusterA and clusterB are connected to different L2 switches
> physically, they are logically connected to the same L2 switch (LAG).
>
>
>
> I initially thought there was no need to separate the PODs, but is this a
> mistake?
>
> By the way, connections to the private IP are possible without any issues.
> We also confirmed that there are no missing configurations regarding the
> VLAN settings on the connected L2 switch.
>
>
>
> Thank you.
>


-- 
Daan

[ANNOUNCE] Rene Peinthor as committer

[Daan Hoogland]

devs and users,

The PMC have asked Rene Peinthor to become a committer to the Apache
CloudStack project and they  have accepted.

Please join me in congratulating Rene.

-- 
Daan

Re: [ANNOUNCE] New PMC Chair & VP Apache CloudStack Project - Daniel Salvador

[Daan Hoogland]

thanks Rohit,
go Daniel

On Thu, Mar 21, 2024 at 2:45 PM Rohit Yadav  wrote:
>
> All,
>
> It gives me great pleasure to announce that the ASF board has accepted 
> CloudStack PMC resolution of Daniel Augusto Veronezi Salvador as the next PMC 
> Chair / VP of the Apache CloudStack project.
>
> I would like to thank everyone for the support I've received over the past 
> year.
>
> Please join me in congratulating Daniel, the new CloudStack PMC Chair / VP.
>
> Best Regards,
> Rohit Yadav



-- 
Daan

Re: Invite to join the logging standard discussion

[Daan Hoogland]

Good call Daniel,
a lot of developer are (ex)operators as well, but we really need the
input from the community. I echo with great enthusiasm:
https://github.com/apache/cloudstack/discussions/8746

On Thu, Mar 7, 2024 at 7:44 PM Guto Veronezi  wrote:
>
> Hello guys,
>
> Hope you are doing fine.
>
> Currently, there is a discussion in GitHub [1] regarding the CloudStack
> logging standards. Mostly, logs are written based on the developer's
> feelings about what should be logged and how; however, operators are the
> ones constantly dealing with logs. With that in mind, I would like to
> invite operators to join the discussion, and present their points of
> view. This will enable us to create a standard that can benefit both
> operators and developers.
>
> Best regards,
> Daniel Salvador (gutoveronezi)
>
> [1] https://github.com/apache/cloudstack/discussions/8746
>


-- 
Daan

new committer: Vishesh Jindal (vishesh)

[Daan Hoogland]

users and devs,

The Project Management Committee (PMC) for Apache CloudStack
has invited Vishesh Jindal to become a committer and we are pleased
to announce that they have accepted.

Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.

Please join me in congratulating Vishesh.

-- 
on behalf of the PMC, Daan

Re: corrupt RVR causing host agent issues

[Daan Hoogland]

Gary, the mail does not display the screenshot for me. Also this is an old
version (4.15) I think you should upgrade.

What might be the root of your issue is that *you* have seen the physical
host crashed but CloudStack could not determine that. To prevent starting
the same VM twice it would withhold taking any action in such situations.

You may call this a bug or a "lack of feature", but the bottom line is that
this is expected behaviour.

I do not think a corrupt VR would crash a host.


On Mon, Feb 26, 2024 at 1:25 PM Gary Dixon 
wrote:

> ACS 4.15.2
>
> KVM
>
> Ubuntu 20.04
>
>
>
> Hi all
>
>
>
> We had a physical host crash on Friday due to hardware failure. This
> appeared to have caused issues with some RVR’s going into an ‘unknown’
> state.
>
>
>
> The strange thing was that on any host where a RVR in an unknown state was
> running – we could not console onto any VM’s on that host – nor could we
> SSH directly to the RVR from the host.
>
> The UI was showing all hosts agent state as ‘UP’
>
>
>
> Only when we restarted the ACS mgmt. service did we notice that the host
> agent where a RVR was running in an ‘unknown’ state then was in a
> ‘connecting’ state for some time – there were no networking issues either –
> host was pingable from the mgmt. server.
>
>
>
> We were then briefly able to console onto one of the RVR’s in an unknown
> state and then discovered that the RVR was indeed corrupt – this is the
> screenshot of the RVR terminal :
>
>
>
> We then marked the RVR in the DB as ‘stopped’ and virsh destroyed it
> directly on the host. We were then able to restart the VPC with cleanup
> which then re-created the corrupt RVR.
>
> It then appeared that once the corrupt RVR had gone – all other RVR’s in
> an unknown state transitioned to ‘backup’ state
>
>
>
> We are wondering if we have encountered a bug where if a corrupt RVR
> crashes the host cloudstack agent if ACS tries to do anything with the RVR
> – like restart it
>
>
>
> BR
>
>
>
> Gary
>
>
>
>
>
>
> Gary Dixon
> Quadris Cloud Manager
> 0161 537 4980 <0161%20537%204980>
>  +44 7989717661 <+44%207989717661>
> gary.di...@quadris.co.uk
> www.quadris.com
> Innovation House, 12‑13 Bredbury Business Park
> Bredbury Park Way, Bredbury, Stockport, SK6 2SN
>


-- 
Daan

Re: Console Proxy VM has high CPU usage

[Daan Hoogland]

hey Leo, you are @kohrar are you?
(https://github.com/apache/cloudstack/pull/8694)
as discussed further improvements might be desirable.

On Wed, Feb 21, 2024 at 7:36 PM Leo Leung  wrote:
>
> I did some basic performance analysis on the Java process and it appears the 
> high CPU usage stems from the NIOSocketInputStream class which is part of the 
> new secure KVM VNC feature released with ACS 4.18.
>
> In the mean time, I've sized up the Console Proxy VM compute offering with 
> more CPUs (1 vCPU for each potential connection) as each connection gobbles 
> up an entire core's worth of CPU.
>
> -Leo
>
>
> > On 02/20/2024 4:51 PM MST Leo Leung  wrote:
> >
> >
> > Just a quick update:
> >
> > - I see 100% CPU on the console proxy's java process if one or more VNC 
> > session is in use, even if nothing is happening in the session (such as a 
> > blank screen). Is this normal?
> > - The persistent 100% CPU appears to be triggered when I try to VNC to the 
> > console proxy itself. Connecting the console proxy to itself somehow causes 
> > the VNC connection to persist until I run 'systemctl restart cloud' on the 
> > console proxy and immediately disconnect from the console. Since the VNC 
> > connection happens to the underlying KVM process on the hypervisor, I'm not 
> > quite sure why this is even a problem.
> >
> > Is this a potential bug with the cloud/proxy service?
> >
> > -Leo
> >
> >
> > > On 02/20/2024 4:16 PM MST Leo Leung  wrote:
> > >
> > >
> > > Hello everyone,
> > >
> > > I am running CloudStack 4.18 and 4.19 in two separate environments and 
> > > notice that in both environments, the Console Proxy SystemVM is pretty 
> > > much pegging its single CPU. Logging in to the SystemVM, top reports the 
> > > java process that handles the VNC connections is constantly using ~100% 
> > > CPU. This behaviour happens even on a cleanly provisioned console proxy 
> > > (after deleting/recreating it) with only a 4-5 established VNC 
> > > connections (as reported by netstat -ntp).
> > >
> > > Is this normal? Does anyone else experience this behaviour? Should I 
> > > assign a larger console proxy compute offering?
> > >
> > > Thank-you in advance.
> > > -Leo



-- 
Daan

Re: readyForShutdown api call every second

[Daan Hoogland]

swen,
Not sure if I answered this already (think I did somewhere) so for the
innocent bystanders: this will happen to root users that have access
to the shutdown APIs, not to regular users. It is programmed thus in
the UI (the repetition)

On Mon, Feb 19, 2024 at 11:47 AM  wrote:
>
> Hi all,
>
>
>
> CS 4.19.0 upgrade from 4.18.1
>
>
>
> I observe that my UI is doing the following api call every second:
>
> /client/api/?command=readyForShutdown=json
>
>
>
> Is this expected? I found this api docu:
>
> https://cloudstack.apache.org/api/apidocs-4.19/apis/readyForShutdown.html
>
>
>
> But I do not really understand it. I already restarted cloudstack-management
> service on the management server.
>
>
>
> Any idea what triggers that api call?
>
>
>
> Regards,
>
> Swen
>


-- 
Daan

Re: CS 4.19.0.0 - UI Session Timeout

[Daan Hoogland]

Wilken, This is due to the saveShutdown feature. It should not happen
for regular users, only users with root admin rights. If this is a big
issue you can deny the API for the role root admin. You can create a
separate role if you still want it.

On Mon, Feb 19, 2024 at 9:59 AM W. Verleger - proIO GmbH
 wrote:
>
> Hi guys,
>
> I was wondering if the default session timeout for the UI has been changed 
> since CS 4.19.0.0?
> In CS 4.18 I've configured the session timeout variable in 
> "server.properties" to:
>
> # Max inactivity time in minutes for the session
> session.timeout=60
>
> But it seems to have no effect anymore. I will no longer get logged off 
> anymore at all.
> Is there a new variable?
>
> Thank you!
>
> Best regards,
>
> Wilken
>
>
> - proIO GmbH -
> Geschäftsführer: Swen Brüseke
> Sitz der Gesellschaft: Frankfurt am Main
>
> USt-IdNr. DE 267 075 918
> Registergericht: Frankfurt am Main - HRB 86239
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
> erhalten haben,
> informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
> Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
> gestattet.
>
> This e-mail may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this e-mail in error) 
> please notify
> the sender immediately and destroy this e-mail.
> Any unauthorized copying, disclosure or distribution of the material in this 
> e-mail is strictly forbidden.
>


-- 
Daan

Re: [VOTE] next version 20 instead of 4.20

[Daan Hoogland]

Vivek, we could, but the main idea is that we repair our versioning
system and make clear how we are actually dealing with our current
system, which is
major - new , possibly breaking features
minor - improvements and enhancements
tiny - urgent (security) fixes

and in addition we would go to 20 to indicate that is the follower of
4.19 not of 4. Someone may implement a new cloudstack (cloudstack5 for
instance) but this would not have anything to do with our current
versioning system.

On Tue, Feb 20, 2024 at 5:06 AM Vivek Kumar
 wrote:
>
> Why not 5.0 ? Then it will be like 5.1, 5.2 in the future.  Just asking ..!
>
>
> > On 19-Feb-2024, at 10:49 PM, Paul Angus  wrote:
> >
> > Hi Daan,
> >
> > Can you clarify what we are actually voting on please.
> >
> > In thread that is linked I've seen:
> >
> > "[the vote] will be to adjust to the semantic versioning system."
> > - you can't go to 20 AND keep semantic versioning. The act of going to 20 
> > breaks semantic versioning [1].
> >
> > " drop the 4 at version 20 and continue as usual with minor and patch level 
> > updates as we have in the past."
> > - what's supposed to come next ? in lieu of what would have been 4.21 will 
> > it be 21 ?  is it going to be 20.1 then 20.2 ?
> >
> > From the thread and how people are referring to 'minor versions', there is 
> > a misunderstanding as to what semantic versioning means. For our project 
> > its explained here [1].   Major versions meaning "probably going to break a 
> > load of people's stuff', with minor versions not breaking stuff (at least 
> > not on purpose). So I get calling them minor versions really underplays the 
> > changes it can hold.
> >
> >
> > I'm going to stick in a -1.  Not as hard 'no' to any changes, but I think 
> > the vote should be on 'A change to the version numbering scheme' and then 
> > what is proposed properly laid out.
> >
> >
> >
> >
> > [1]   https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases 
> > (section on versioning about 2/3 down)
> >
> > -Original Message-
> > From: Daan Hoogland 
> > Sent: Monday, February 19, 2024 12:50 PM
> > To: dev 
> > Cc: users 
> > Subject: [VOTE] next version 20 instead of 4.20
> >
> > LS,
> >
> > This is a vote on dev@c.a.o with cc to users@c.a.o. If you want to be 
> > counted please reply to dev@.
> >
> > As discussed in [1] we are deciding to drop the 4 from our versioning 
> > scheme. The result would be that the next major version will be 20 instead 
> > of 4.20, as it would be in a traditional upgrade. As 20 > 4 and the 
> > versions are processed numerically there are no technical impediments.
> >
> > +1 agree (next major version as 20
> > 0 (no opinion)
> > -1 disagree (keep 4.20 as the next version, give a reason)
> >
> > As this is a lazy consensus vote any -1 should be accompanied with a reason.
> >
> > [1] https://lists.apache.org/thread/lh45w55c3jmhm7w2w0xgdvlw78pd4p87
> >
> > --
> > Daan
>
>
> --
> This message is intended only for the use of the individual or entity to
> which it is addressed and may contain confidential and/or privileged
> information. If you are not the intended recipient, please delete the
> original message and any copy of it from your computer system. You are
> hereby notified that any dissemination, distribution or copying of this
> communication is strictly prohibited unless proper authorization has been
> obtained for such action. If you have received this communication in error,
> please notify the sender immediately. Although IndiQus attempts to sweep
> e-mail and attachments for viruses, it does not guarantee that both are
> virus-free and accepts no liability for any damage sustained as a result of
> viruses.



-- 
Daan

Re: [VOTE] next version 20 instead of 4.20

[Daan Hoogland]

Paul,

On Mon, Feb 19, 2024 at 6:21 PM Paul Angus  wrote:
>
> Hi Daan,
>
> Can you clarify what we are actually voting on please.
>
> In thread that is linked I've seen:
>
> "[the vote] will be to adjust to the semantic versioning system."
> - you can't go to 20 AND keep semantic versioning. The act of going to 20 
> breaks semantic versioning [1].

We are using a crooked semantic versioning system and that is entirely
due to maintaining the 4 in our versioning scheme. We have been
changing and adding major features on updating the second number (20
to be). We have been using the third number for bug fixes and minor
enhancements. And we have been using the fourth number for emergency
security fixes.

So we are not maintaining semantic versioning but going to semantic
versioning by repairing our system of versioning. You could say this
is a minor bugfix.

>
> " drop the 4 at version 20 and continue as usual with minor and patch level 
> updates as we have in the past."
> - what's supposed to come next ? in lieu of what would have been 4.21 will it 
> be 21 ?  is it going to be 20.1 then 20.2 ?

Yes, exactly. Except for dropping the 4, nothing will change.

>
> From the thread and how people are referring to 'minor versions', there is a 
> misunderstanding as to what semantic versioning means. For our project its 
> explained here [1].   Major versions meaning "probably going to break a load 
> of people's stuff', with minor versions not breaking stuff (at least not on 
> purpose). So I get calling them minor versions really underplays the changes 
> it can hold.
>
>
> I'm going to stick in a -1.  Not as hard 'no' to any changes, but I think the 
> vote should be on 'A change to the version numbering scheme' and then what is 
> proposed properly laid out.
>
>
>
>
> [1]   https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases 
> (section on versioning about 2/3 down)
>
> -Original Message-
> From: Daan Hoogland 
> Sent: Monday, February 19, 2024 12:50 PM
> To: dev 
> Cc: users 
> Subject: [VOTE] next version 20 instead of 4.20
>
> LS,
>
> This is a vote on dev@c.a.o with cc to users@c.a.o. If you want to be counted 
> please reply to dev@.
>
> As discussed in [1] we are deciding to drop the 4 from our versioning scheme. 
> The result would be that the next major version will be 20 instead of 4.20, 
> as it would be in a traditional upgrade. As 20 > 4 and the versions are 
> processed numerically there are no technical impediments.
>
> +1 agree (next major version as 20
> 0 (no opinion)
> -1 disagree (keep 4.20 as the next version, give a reason)
>
> As this is a lazy consensus vote any -1 should be accompanied with a reason.
>
> [1] https://lists.apache.org/thread/lh45w55c3jmhm7w2w0xgdvlw78pd4p87
>
> --
> Daan



-- 
Daan

[VOTE] next version 20 instead of 4.20

[Daan Hoogland]

LS,

This is a vote on dev@c.a.o with cc to users@c.a.o. If you want to be
counted please reply to dev@.

As discussed in [1] we are deciding to drop the 4 from our versioning
scheme. The result would be that the next major version will be 20
instead of 4.20, as it would be in a traditional upgrade. As 20 > 4
and the versions are processed numerically there are no technical
impediments.

+1 agree (next major version as 20
0 (no opinion)
-1 disagree (keep 4.20 as the next version, give a reason)

As this is a lazy consensus vote any -1 should be accompanied with a reason.

[1] https://lists.apache.org/thread/lh45w55c3jmhm7w2w0xgdvlw78pd4p87

-- 
Daan

Re: Secondary Storage VM not getting started

[Daan Hoogland]

On Mon, Feb 19, 2024 at 1:14 PM Kapil Bhuskute
 wrote:
>
> Hello Daan,
> What exactly did you mean by initiating the secondary storage?
> We have a secondary storage path and server name mentioned in the Cloudstack 
> management server wizard to add it, and that got added in the UI.
> It is a nfs export hosted on the same cloudstack server and is already 
> available with all required NFS permissions(rw,no_root_squash,sync).
> Is there any manual step required to initiate it?

No you shouldn't have to. Is the storage initiated with the templates
needed? You can check the path under /mnt/data/template/tmpl/ to see
if there are templates there. You can also check to see if the
templates are marked as ready?

>
> Kapil Bhuskute
>
>
> -Original Message-
> From: Daan Hoogland 
> Sent: Monday, February 19, 2024 1:55 PM
> To: users@cloudstack.apache.org
> Subject: Re: Secondary Storage VM not getting started
>
>CAUTION: This Email is from an EXTERNAL source. Ensure you trust this 
> sender before clicking on any links or attachments.
>
> Kapil,
> did you initiate your secondary storage (at 
> kvm01.p01.ops.sjc01.qualys.com:/mnt/data)?
> and did you export the storage for it from the nfs server?
> The error says there is a problem there.
>
> On Mon, Feb 19, 2024 at 7:35 AM Kapil Bhuskute  
> wrote:
> >
> > The secondary storage VM is not able to get deployed in CloudStack 4.19 
> > with below errors.
> >
> > Feb 16 13:25:08 qcs01 java[417597]: INFO  [o.a.c.e.o.VolumeOrchestrator] 
> > (secstorage-1:ctx-adb3bb9a ctx-2cb81e1f) (logid:67e774fb) Adding disk 
> > object [ROOT-6258] to VM [VM instance {"id":6258,"instanceName"
> > :"s-6258-VM","type":"SecondaryStorageVm","uuid":"a9520deb-ca26-4a6f-bc
> > 40-871841d05c28"}] Feb 16 13:25:11 qcs01 java[417597]: ERROR
> > [o.a.c.e.o.VolumeOrchestrator] (Work-Job-Executor-2:ctx-511f3201
> > job-9178/job-13001 ctx-8a4381d2) (logid:cbcf72ec) Unable to create volume 
> > [{"name":"ROOT-6258","uui d":"8444daf7-4145-4a40-8789-c623c5a5ad7c"}] due 
> > to [com.cloud.utils.exception.CloudRuntimeException: 
> > org.libvirt.LibvirtException: internal error: Child process (/usr/bin/mount 
> > -o nodev,nosuid,noexec kvm01.
> > p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222
> > /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) unexpected exit status 32:
> > mount.nfs: mounting
> > kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222
> > failed, reason given by server: No such file or directory Feb 16
> > 13:25:11 qcs01 java[417597]:
> > com.cloud.exception.StorageUnavailableException: Resource
> > [StoragePool:5] is unreachable: Unable to create volume
> > [{"name":"ROOT-6258","uuid":"8444daf7-4145-4a40-8789-c62
> > 3c5a5ad7c"}] due to [com.cloud.utils.exception.CloudRuntimeException:
> > org.libvirt.LibvirtException: internal error: Child process
> > (/usr/bin/mount -o nodev,nosuid,noexec
> > kvm01.p01.ops.sjc01.qualys.com:/mnt/d
> > ata/template/tmpl/1/222 /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) 
> > unexpected exit status 32: mount.nfs: mounting 
> > kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222 failed, reason 
> > given by server:
> > No such file or directory
> > Feb 16 13:25:41 qcs01 java[417597]: ERROR
> > [o.a.c.e.o.VolumeOrchestrator] (Work-Job-Executor-8:ctx-5417b759 
> > job-9178/job-13003 ctx-f6230d28) (logid:cbcf72ec) Unable to create volume 
> > [{"name":"ROOT-6258","uui d":"8444daf7-4145-4a40-8789-c623c5a5ad7c"}] due 
> > to [com.cloud.utils.exception.CloudRuntimeException: 
> > org.libvirt.LibvirtException: internal error: Child process (/usr/bin/mount 
> > -o nodev,nosuid,noexec kvm01.
> > p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222
> > /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) unexpected exit status 32:
> > mount.nfs: mounting
> > kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222
> > failed, reason given by server: No such file or directory Feb 16
> > 13:25:41 qcs01 java[417597]:
> > com.cloud.exception.StorageUnavailableException: Resource
> > [StoragePool:5] is unreachable: Unable to create volume
> > [{"name":"ROOT-6258","uuid":"8444daf7-4145-4a40-8789-c62
> > 3c5a5ad7c"}] due to [com.cloud.utils.exception.CloudRuntimeException:
> > org.libvirt.LibvirtException: internal error: Child process
> > (/usr/bin/mount -o nodev,nosuid,noexec
> > kvm01.p01.ops.sjc01.qualys.com:/mnt/d
> > ata/template/tmpl/1/222 /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) 
> > unexpected exit status 32: mount.nfs: mounting 
> > kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222 failed, reason 
> > given by server:
> > No such file or directory
> >
> > Regards,
> > Kapil Bhuskute
>
>
>
> --
> Daan



-- 
Daan

Re: Secondary Storage VM not getting started

[Daan Hoogland]

Kapil,
did you initiate your secondary storage (at
kvm01.p01.ops.sjc01.qualys.com:/mnt/data)?
and did you export the storage for it from the nfs server?
The error says there is a problem there.

On Mon, Feb 19, 2024 at 7:35 AM Kapil Bhuskute
 wrote:
>
> The secondary storage VM is not able to get deployed in CloudStack 4.19 with 
> below errors.
>
> Feb 16 13:25:08 qcs01 java[417597]: INFO  [o.a.c.e.o.VolumeOrchestrator] 
> (secstorage-1:ctx-adb3bb9a ctx-2cb81e1f) (logid:67e774fb) Adding disk object 
> [ROOT-6258] to VM [VM instance {"id":6258,"instanceName"
> :"s-6258-VM","type":"SecondaryStorageVm","uuid":"a9520deb-ca26-4a6f-bc40-871841d05c28"}]
> Feb 16 13:25:11 qcs01 java[417597]: ERROR [o.a.c.e.o.VolumeOrchestrator] 
> (Work-Job-Executor-2:ctx-511f3201 job-9178/job-13001 ctx-8a4381d2) 
> (logid:cbcf72ec) Unable to create volume [{"name":"ROOT-6258","uui
> d":"8444daf7-4145-4a40-8789-c623c5a5ad7c"}] due to 
> [com.cloud.utils.exception.CloudRuntimeException: 
> org.libvirt.LibvirtException: internal error: Child process (/usr/bin/mount 
> -o nodev,nosuid,noexec kvm01.
> p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222 
> /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) unexpected exit status 32: 
> mount.nfs: mounting 
> kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222
> failed, reason given by server: No such file or directory
> Feb 16 13:25:11 qcs01 java[417597]: 
> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:5] is 
> unreachable: Unable to create volume 
> [{"name":"ROOT-6258","uuid":"8444daf7-4145-4a40-8789-c62
> 3c5a5ad7c"}] due to [com.cloud.utils.exception.CloudRuntimeException: 
> org.libvirt.LibvirtException: internal error: Child process (/usr/bin/mount 
> -o nodev,nosuid,noexec kvm01.p01.ops.sjc01.qualys.com:/mnt/d
> ata/template/tmpl/1/222 /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) unexpected 
> exit status 32: mount.nfs: mounting 
> kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222 failed, reason 
> given by server:
> No such file or directory
> Feb 16 13:25:41 qcs01 java[417597]: ERROR [o.a.c.e.o.VolumeOrchestrator] 
> (Work-Job-Executor-8:ctx-5417b759 job-9178/job-13003 ctx-f6230d28) 
> (logid:cbcf72ec) Unable to create volume [{"name":"ROOT-6258","uui
> d":"8444daf7-4145-4a40-8789-c623c5a5ad7c"}] due to 
> [com.cloud.utils.exception.CloudRuntimeException: 
> org.libvirt.LibvirtException: internal error: Child process (/usr/bin/mount 
> -o nodev,nosuid,noexec kvm01.
> p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222 
> /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) unexpected exit status 32: 
> mount.nfs: mounting 
> kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222
> failed, reason given by server: No such file or directory
> Feb 16 13:25:41 qcs01 java[417597]: 
> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:5] is 
> unreachable: Unable to create volume 
> [{"name":"ROOT-6258","uuid":"8444daf7-4145-4a40-8789-c62
> 3c5a5ad7c"}] due to [com.cloud.utils.exception.CloudRuntimeException: 
> org.libvirt.LibvirtException: internal error: Child process (/usr/bin/mount 
> -o nodev,nosuid,noexec kvm01.p01.ops.sjc01.qualys.com:/mnt/d
> ata/template/tmpl/1/222 /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) unexpected 
> exit status 32: mount.nfs: mounting 
> kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222 failed, reason 
> given by server:
> No such file or directory
>
> Regards,
> Kapil Bhuskute



-- 
Daan

Re: Secondary storage cannot be deleted after migration completed

[Daan Hoogland]

Well ,

On Sat, Feb 17, 2024, 02:29 Mark Winnemueller
 wrote:

> Thanks for the response. Does that mean that manually (rsync/scp/mount +
> mv) is a viable option?
>
> In other words - I could mount the store3 volume on one of my gluster
> instances and mv the data from the gluster/ganesha brick to the mounted
> store3 - then remove the secondary storage?
>

You will have to reconcile the data in the ..-store-ref tables, but it
seems you hit s limitation of the system and this is a way around it.
Please Please test this in a test environment. I dont understand your issue
fully, but I have seen similar issues in older versions. The hacking
described did remedy the situation. I have successfully deleted secondary
storage in newer version without problems.


Thanks,
>
> Mark
>
> On 2/16/24 02:21, Daan Hoogland wrote:
> > Mark,
> > Did you also include checking for volumes and snapshots? This to be
> > sure you don't delete things still needed.
> > Check internal templates as well. These and any "all zones" templates
> > could be in the way, I am hesitant to manipulate the DB but when all
> > else fails this sometimes does solve such issues. It can also break
> > things so your "leery"  disposition makes sense.
> >
> > This can be a daunting task if your cloud is old, but:
> > check snapshot_store_ref, template_store_ref and volume_store_ref for
> > any items that might be still valuable and or should have been
> > deleted.
> >
> > hope this helps,
> >
> > On Thu, Feb 15, 2024 at 4:33 PM Mark Winnemueller
> >   wrote:
> >> Hello CloudStack users,
> >>
> >> Using CloudStack V 4.18.1.0 I cannot delete my secondary storage store1
> >> due to  "Cannot delete image store with active templates backup!". I
> >> have tried migrating the data to store3, and CloudStack says that it
> >> succeeded, but the data is still on the existing store1 and I'm not
> >> seeing all of the data on store2.
> >>
> >> Background:
> >>
> >> I think this is what confused things. I have gluster NFS across three
> >> machines with ganesha and was using that as secondary storage (picking
> >> one of the IP addresses of the gluster cluster). Because this is fragile
> >> I added keepalived to the gluster machines and added that as secondary
> >> storage. To be clear - they reference the same physical media. That's
> >> when I found out that Cloudstack would not delete store1 (because there
> >> is still data there).
> >>
> >> My first attempt to fix this was to create yet a third Secondary storage
> >> on our TrueNAS box. Migrating data to that storage yields "Successfully
> >> completed migrating Image store data" and "Cannot delete image store
> >> with active templates backup!" when trying to delete the primary
> storage.
> >>
> >> It seems that there are 2 ways to solve this - 1 is to manually move the
> >> data to store3, and then attempt to remove store1. The second is to
> >> change MySQL image_store table's removed value. The
> >> cloud.image_store.parent value is NULL for the two image stores, so I'm
> >> a little leery of that solution.
> >>
> >> Any help you can provide on the proper way to solve this will be
> >> appreciated.
> >>
> >> Thanks,
> >>
> >> Mark
> >>
> >> --
> >> Mark Winnemueller
> >> reThought DevOps Engineer
> >> 719.480.4609
> >> mark.winnemuel...@rethoughtinsurance.com
> >>
> >> --
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> Operating under CA license #0M61234
> >>
> >>
> >>
> >> NOTICE: You cannot bind,
> >> alter or cancel coverage without speaking to an authorized
> representative
> >> of reThought Insurance. Coverage cannot be bound without written
> >> confirmation from an authorized representative of reThought Insurance.
> This
> >> e-mail and any files transmitted with it are not encrypted and may
> contain
> >> privileged or other confidential information and is intended solely for
> the
> >> use of the individual or entity to whom they are addressed. If you are
> not
> >> the intended recipient or entity, or believe that you may have received
> >> this e-mail in error, please reply to the sender indicating that fact
> and
> >> delete the copy you received. In addition, you should not print, copy,
> >> re

Re: VXLAN+BGP with KVM/VTEP

[Daan Hoogland]

@David Amorin,

On Fri, Feb 9, 2024 at 12:47 AM David Amorín  wrote:
>
> Hi all,
>
> We are evaluating a change in our core network architecture, currently based 
> on VLANs with advanced network in ACS.
>
> The change we want to implement is VXLAN+BGP, using hypervisors with KVM as 
> VTEP (Thank you @Wido Den Hollander for 
> sharing your knowledge to the community, about this topic)
>
> Do you know what is the max number of VNIs, MACs that one hypevisor/VTE 
> should manage in a ACS zone?

Did you find out, David?

> I understand that if we have 400 hypervisors in just one zone, with a total 
> of 40.000 advanced networks and 120.000 MACs, each hypervisor as VTEP should 
> know/manage the 120k MACS. Is that correct? If so, do you identify any 
> performance issue for this hypervisor to manage these numbers?

You should be able to derive your number from that. Keep in mind that
the choice to work with shared networks or not also has an influence
on this.
Also in your calculation above, maybe you should divide by 400? but if
you want to be safe you could go for the 120k

Very interesting work you do, keep us informed of your findings please.



> We have some doubts about the scalability of this architecture, so any 
> feedback / recommendations of somebody using this architecture in production 
> will be very helpful.
>
> Thanks



--
Daan

Re: Secondary storage cannot be deleted after migration completed

[Daan Hoogland]

Mark,
Did you also include checking for volumes and snapshots? This to be
sure you don't delete things still needed.
Check internal templates as well. These and any "all zones" templates
could be in the way, I am hesitant to manipulate the DB but when all
else fails this sometimes does solve such issues. It can also break
things so your "leery"  disposition makes sense.

This can be a daunting task if your cloud is old, but:
check snapshot_store_ref, template_store_ref and volume_store_ref for
any items that might be still valuable and or should have been
deleted.

hope this helps,

On Thu, Feb 15, 2024 at 4:33 PM Mark Winnemueller
 wrote:
>
> Hello CloudStack users,
>
> Using CloudStack V 4.18.1.0 I cannot delete my secondary storage store1
> due to  "Cannot delete image store with active templates backup!". I
> have tried migrating the data to store3, and CloudStack says that it
> succeeded, but the data is still on the existing store1 and I'm not
> seeing all of the data on store2.
>
> Background:
>
> I think this is what confused things. I have gluster NFS across three
> machines with ganesha and was using that as secondary storage (picking
> one of the IP addresses of the gluster cluster). Because this is fragile
> I added keepalived to the gluster machines and added that as secondary
> storage. To be clear - they reference the same physical media. That's
> when I found out that Cloudstack would not delete store1 (because there
> is still data there).
>
> My first attempt to fix this was to create yet a third Secondary storage
> on our TrueNAS box. Migrating data to that storage yields "Successfully
> completed migrating Image store data" and "Cannot delete image store
> with active templates backup!" when trying to delete the primary storage.
>
> It seems that there are 2 ways to solve this - 1 is to manually move the
> data to store3, and then attempt to remove store1. The second is to
> change MySQL image_store table's removed value. The
> cloud.image_store.parent value is NULL for the two image stores, so I'm
> a little leery of that solution.
>
> Any help you can provide on the proper way to solve this will be
> appreciated.
>
> Thanks,
>
> Mark
>
> --
> Mark Winnemueller
> reThought DevOps Engineer
> 719.480.4609
> mark.winnemuel...@rethoughtinsurance.com
>
> --
>
>
>
>
>
>
>
>
>
> Operating under CA license #0M61234
>
>
>
> NOTICE: You cannot bind,
> alter or cancel coverage without speaking to an authorized representative
> of reThought Insurance. Coverage cannot be bound without written
> confirmation from an authorized representative of reThought Insurance. This
> e-mail and any files transmitted with it are not encrypted and may contain
> privileged or other confidential information and is intended solely for the
> use of the individual or entity to whom they are addressed. If you are not
> the intended recipient or entity, or believe that you may have received
> this e-mail in error, please reply to the sender indicating that fact and
> delete the copy you received. In addition, you should not print, copy,
> retransmit, disseminate, or otherwise use this information.
>
>


-- 
Daan

Re: [PROPOSAL] version naming : drop the 4.

[Daan Hoogland]

Well, to all users@these lists,
please comment.

The ratio is that cloudstack is called cloudstack4 as an evolutionary
result from the development at cloud.com and citrix and that all
version since 4.0 (the apache podling version) are basically major
versions according to semantic versioning. Keeping the 4 as version
number has no technical meaning and obfuscates the true state of the
software.
The idea is that we drop the 4 at version 20 and continue as usual
with minor and patch level updates as we have in the past.

Not all of the discussion around this is included in this mail, but
you can find it at
https://lists.apache.org/thread/lh45w55c3jmhm7w2w0xgdvlw78pd4p87

*Any* feedback is welcome.

On Thu, Feb 15, 2024 at 12:01 PM Rohit Yadav  wrote:
>
> (+ users)
>
> All,
>
> Generally speaking, any versioning/styling change can be perceived as a big 
> or concerning change by users (those existing or new ones trying/adopting). 
> So, we must get our message across properly and correctly.
>
> I'm not for or against cosmetics change in versioning, but I'm really keen if 
> we want to discuss if we can use this opportunity to streamline our LTS 
> release, improve how we upgrade CloudStack (i.e relook at our DB/upgrade 
> approach), make releases more linear and faster (avoid forking branches for 
> example), and try to change new defaults and drop some old API/arch things 
> (such as default API response type to json, but largely be backward 
> compatible). Some of these suggestions may be too large an undertaking and 
> make not be worth it.
>
>
> Overall, I've no objections if the consensus is to drop the "4." version 
> prefix. I also want to hear from our users if they've any feedback for us.
>
>
> Regards.
>
>
>
>
> 
> From: Guto Veronezi 
> Sent: Tuesday, February 13, 2024 18:34
> To: d...@cloudstack.apache.org 
> Subject: Re: [PROPOSAL] version naming : drop the 4.
>
> Daan,
>
> As we still plan to introduce disruptive changes (in a cautious and
> structured way) in the major versions, all my concerns are met; I do not
> have further technical reasons to keep the "4.".
>
> Best regards,
> Daniel Salvador (gutoveronezi)
>
> On 2/12/24 11:55, Daan Hoogland wrote:
> > bump,
> > @Daniel Salvador is there any technical reason to keep the 4? any
> > reason why there must be a 5 instead of a 21, 22 or 23? We are
> > maintaining 4 number semantic versioning for no reason, as I see it.
> >
> > On Tue, Jan 30, 2024 at 12:02 PM Daan Hoogland  
> > wrote:
> >> Daniel, "technical" reasons for dropping the 4 are all in the field of
> >> social engineering. In practice (as I think Wei also described) we are
> >> already treating the "minor" version number as major version. Since
> >> 4.0 or 4.1 (don´t remember) there has been renewed talk of a 5 , but
> >> never enough reason and or commitment to make it real. We could argue
> >> about it a lot.
> >>
> >> so
> >> ¨¨¨
> >> The main point is: *we have to understand the technical reasons for
> >> the proposal and what we expect from it before deciding anything.
> >> ¨¨¨
> >> The most important point is that we expect that people understand that
> >> we treat the number that now seems to be "minor" as major release
> >> numbers.
> >>
> >>
> >> On Fri, Jan 26, 2024 at 7:42 PM Wei ZHOU  wrote:
> >>> Hi Daniel,
> >>>
> >>> If we are discussing 5.0, I would have the same concern as you.
> >>> What we are discussing is dropping 4.x. The fact is, we will never release
> >>> 5.0 (anyone disagree ?)
> >>> In this case, the major version 4.x becomes useless.
> >>> If we compare 4.20.0/4.21.0 with 20.0/21.0, it is obvious which is better.
> >>> IMHO due to the similar reason, the Java version has been changed from 1.x
> >>> to java 1.7/1.8 (=java 7/8) then to java 11/14/17.
> >>> of course there will be some issues if semantic changes, I think it is
> >>> under control.
> >>>
> >>>
> >>>
> >>> Regarding the compatibility, I think we can change the APIs gradually.
> >>> I noticed the following recently when I tested VR upgrade to
> >>> debian12/python3
> >>>
> >>> root@r-431-VM:~# python
> >>> Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] on linux
> >>> Type "help", "copyright", "credits" or "license" for more information.
> >>>>>> import cgi
>

Re: [PROPOSE] RM for 4.19.1.0

[Daan Hoogland]

no worries as João proposed to release 4.18.2 in march, but let's
make sure we have a good period between the two.

On Mon, Feb 12, 2024 at 12:50 PM Suresh Anaparti
 wrote:
>
> Hi All,
>
> CloudStack 4.19.0.0 is the latest LTS release. There are already some open 
> issues [1]  and pull requests [2] targeted for 4.19.1.0 [3] release.
>
> I'd like to propose and put myself forward as the release manager for 
> 4.19.1.0 if no objections there. Please ping me (@sureshanaparti) on GitHub, 
> in case you want to include any Issue/PR in 4.19.1.0.
>
> I propose to have a window of at least 8 weeks (2 months), which allows the 
> community / users to test, use 4.19.0.0 and report any issues. We can aim to 
> cut RC1 in Q2 2024 (maybe, sometime in May-2024). I'll propose the timeline 
> details soon. I hope to have your support.
>
> Please let me know if you have any thoughts/comments.
>
> [1] 
> https://github.com/apache/cloudstack/issues?q=is%3Aopen+is%3Aissue+milestone%3A4.19.1.0
> [2] 
> https://github.com/apache/cloudstack/pulls?q=is%3Apr+milestone%3A4.19.1.0+is%3Aopen
> [3] https://github.com/apache/cloudstack/milestone/31
>
>
> Regards,
> Suresh
>
>
>


-- 
Daan

new website is life

[Daan Hoogland]

People,
we brought the new website. Please all have a look at
https://cloudstack.apache.org

thanks for any feedback

-- 
Daan

Re: VM utilisation issues

[Daan Hoogland]

Palash,
Are you logged in to the VM while measuring? That might explain (part) of
the difference.
What utilisation are you referring to? (cpu mem)
In the case of CPU; how many cpus are you measuring? (i.e. 95 ≃ 50*2)

On Tue, Feb 6, 2024 at 3:29 PM Palash Biswas  wrote:

> Hi Community,
>
> I have a VM. When i monitor the contents of the VM, it shows the
> utilisation is 95% and above.
>
> But from Cloudstack Metrics, it shows only 50% Max Utilisation.
>
> How does Cloudstack monitor the VM Metrics (CPU and Memory). Is there any
> way to make it more accurate?
>
> My Vm stats interval (vm.stats.interval) is set to 6Miliseconds (60
> Seconds)
>
> Regards,
> Palash
>
>
>

-- 
Daan

Re: Cloudstack Host HA

[Daan Hoogland]

fabio, I saw a new github issue for a similar nfs issue, was that
yours (i.e. are you cdfgallo)?

In your description below, it seems to me you are confusing host HA
and VM HA, the two are different and do not mix well. There are
technical reasons for that. I have not tested (limitation of warrantee
;) but have you tried using nfs4?

On Mon, Feb 5, 2024 at 1:06 PM  wrote:
>
> Hi all,
>
> I have a question about host HA.
> I have a cluster with KVM (QEMU emulator version 6.2.0) with NFS(v3)
> primary storage.
>
> I have dedicated 1 host in this cluster for HA but, when I tried to
> shutting down another host in order to test HA functionality, it stops
> with error: "Failed to get shared "write" lock Is another process using
> the image".
> Also, if I try to restart manually the VMs on any hosts, it fails with
> the same error.
> If I restart the hosts where the VMs were running, I'm able to start
> them back with no issues
>
> I made some investigation on this and found out this old issue
> (https://github.com/apache/cloudstack/pull/4567) which made me tought
> that this should be already sorted.
>
> What am I doing wrong?
> Thanks in advance,
> Br,
> F



-- 
Daan

Re: Primary Storage Migration UI

[Daan Hoogland]

Hey Antoine,
sounds like a bug to me. can you click on
github.com/apache/cloudstack/issues/new  ;) ?

On Fri, Feb 2, 2024 at 10:48 PM Antoine Boucher  wrote:
>
> In ACS version 4.18.1, when conducting a VM Primary Storage Migration, should 
> the list of potential destinations exclude any Primary Storages that are 
> disabled?
>
> It currently shows them all.
>
> Regards,
> Antoine
>
>


-- 
Daan

Re: Migrate a VM to another compute offering

[Daan Hoogland]

makes sense @swen. if you don't want the user to be aware of the
placements policies.

On Thu, Feb 1, 2024 at 10:20 AM  wrote:
>
> Hi Daan,
>
> thx for your input. I would not say I want to migrate a VM while scaling, I 
> would see it the other way around. I want to change the service offering and 
> this will include the need to migrate the VM. But at the end both 
> descriptions have the same result. :-)
> I will open an issue for an Improvement Request for this.
>
> Regards,
> Swen
>
> -----Ursprüngliche Nachricht-
> Von: Daan Hoogland 
> Gesendet: Donnerstag, 1. Februar 2024 09:57
> An: users@cloudstack.apache.org
> Betreff: Re: Migrate a VM to another compute offering
>
> what you try to do , without explicitly mentioning it, Sven is to migrate the 
> VM while scaling?I had a quick look but migrate APIs don't give an easily 
> answer either. Sounds like a 
> https://github.com/apache/cloudstack/issues/new/choose to me ;)
>
> On Wed, Jan 31, 2024 at 9:35 AM  wrote:
> >
> > Hi all,
> >
> >
> >
> > we are using 2 compute offerings, called offering1 and offering2. Both
> > offerings are "Custom constrained" with similar values for cpu and memory.
> > Both offerings are using the same disk offering.
> >
> > The only difference is that offering1 used host tag "group1" and
> > offering2 uses host tag "group2". My goal is to live scale (migrate) a
> > vm from
> > offering1 to offering2 via UI. When VM is running and I click the "Scale VM"
> > icon I only see offering1 in the popup window.
> >
> > When the VM is stopped and I click on the "Scale VM" icon, I only see
> > offering1 and other offerings using the same host tag. In both cases I
> > am unable to see offering2.
> >
> >
> >
> > Is my goal even possible without altering db directly?
> >
> >
> >
> > Regards,
> >
> > Swen
> >
>
>
> --
> Daan
>
>


-- 
Daan

Re: Snapshot download

[Daan Hoogland]

indeed Jimmy,
As Jithin says there is no API for this (afaik) so some spitting and
digging is needed. The snapshot must be there on some storage though,
as it can be restored.
let us know if you find a good work around and have an issue created.

On Thu, Feb 1, 2024 at 6:18 AM Jithin Raju  wrote:
>
> Hi Jimmy,
>
> This feature is not available yet (others may confirm), could you open a 
> feature request?
>
> -Jithin
>
> From: Jimmy Huybrechts 
> Date: Wednesday, 31 January 2024 at 9:38 PM
> To: users@cloudstack.apache.org 
> Subject: Snapshot download
> Hi,
>
> While doing some last tests before production I noticed there is no option to 
> download a vm snapshot (including memory if saved), now for some law 
> enforcement cases they will request such a snapshot with memory (after proper 
> warrants of course). How to download these in this case? Even if it needs to 
> be done manually from shell. Not being able to do it is not really an option 
> here unfortunately.
>
> --
> Jimmy
>
>
>


-- 
Daan

Re: Migrate a VM to another compute offering

[Daan Hoogland]

what you try to do , without explicitly mentioning it, Sven is to
migrate the VM while scaling?I had a quick look but migrate APIs don't
give an easily answer either. Sounds like a
https://github.com/apache/cloudstack/issues/new/choose to me ;)

On Wed, Jan 31, 2024 at 9:35 AM  wrote:
>
> Hi all,
>
>
>
> we are using 2 compute offerings, called offering1 and offering2. Both
> offerings are "Custom constrained" with similar values for cpu and memory.
> Both offerings are using the same disk offering.
>
> The only difference is that offering1 used host tag "group1" and offering2
> uses host tag "group2". My goal is to live scale (migrate) a vm from
> offering1 to offering2 via UI. When VM is running and I click the "Scale VM"
> icon I only see offering1 in the popup window.
>
> When the VM is stopped and I click on the "Scale VM" icon, I only see
> offering1 and other offerings using the same host tag. In both cases I am
> unable to see offering2.
>
>
>
> Is my goal even possible without altering db directly?
>
>
>
> Regards,
>
> Swen
>


-- 
Daan

Re: MAC address pool

[Daan Hoogland]

Christian,
I know when you add a NIC to a VM you can choose a MAC address in the
process [1], I am sure this is not what you mean, but it might help
solve your use-case. I think what you mention is not a feature. Would
you configure such a range on a zone/network/account ??? Maybe create
an issue [2] to refine the idea if the API i mention doesn't work.

[1] 
https://cloudstack.apache.org/api/apidocs-4.18/apis/addNicToVirtualMachine.html
[2] https://github.com/apache/cloudstack/issues/new/choose

On Tue, Jan 30, 2024 at 5:27 PM Christian Reichert
 wrote:
>
> Hello,
>
>
>
> I have an application running on vmware as hypervisor, the vm needs a MAC 
> address from the original vmware MAC address pool.
>
> Is there a way to change the pool CloudStack is assigning MAC addresses to a 
> new VM?
>
>
>
> Thanks and best regards,
>
>
>
> Christian



-- 
Daan

Re: Unable to add the host: Cannot find the server resources at

[Daan Hoogland]

Christian,
can you share how you tried adding the host (UI/CMK commands) And in
case of UI maybe the calls as the UI generated them by looking at the
dev tools network traffic?

On Wed, Jan 24, 2024 at 9:25 AM  wrote:
>
> Hello,
>
>
>
>Any workaround for this bug? "Unable to add the host: Cannot find the
> server resources at
> http://06.hostx.host/ZONE-001/DC-001//mub-in-001.hostx.host
>  "
>
>
>
> When attempting to add a second host to an existing cluster, I encounter an
> error. I suspect this may be caused by a duplicate "/" symbol, which occurs
> even when using the API.
>
>
>
> However, if I set up a new cluster without specifying any hosts, it operates
> correctly as it automatically discovers the hosts.
>
>
>
> This problem is present in CloudStack version 4.18.1.
>
>
> Regards,
>
> Cristian
>
>
>


-- 
Daan

Re: new website design

[Daan Hoogland]

I've been improving any points I got as criticism on the site.  I will
start a vote thread soon, though I don't think it is strictly
necessary. please have a final run through if you have time, thanks,

On Tue, Jan 23, 2024 at 1:08 PM Rohit Yadav  wrote:
>
> +1 overall, but there are a few things I would consider blockers:
>
> 1.  the blog page doesn't look same as on current blog (prod).
>
> https://cloudstack.staged.apache.org/blog (staging blog)
>
> versus
>
> https://cloudstack.apache.org/blog/ (current blog/prod.)
>
> If we can fix the blog listing and the  that should be okay.
>
> 2. The colour of the buttons in some places are different shades of blue, for 
> example on https://cloudstack.staged.apache.org the download/documentation 
> button and scroll down, we see button with a violet/navy-blue shade. Minor 
> css issue? I would expect button to match the theme, for example button 
> colour as in https://cloudstack.apache.org/blog/india-user-group-2024
>
> 3. Fact check all pages, for example the staging landing says 4.18.0.0 is 
> latest release and link/content around events. Before we migrate/transition, 
> all data must be latest/accurate as possible.
>
> 4. Minor issue - the logo on the staging site's landing page, uses old 
> dashboard, that could be replaced with what the latest/most-recent dashboard 
> looks like.
>
>
>
> Regards.
>
> 
> From: Sven Vogel 
> Sent: Monday, January 22, 2024 18:30
> To: d...@cloudstack.apache.org ; 
> priv...@cloudstack.apache.org 
> Cc: users 
> Subject: Re: new website design
>
> +1 looks nice
>
> Am Montag, den 01/22/2024 um 11:46 schrieb Nux:
>
>
>
> +1 - do it.
>
> On 2024-01-19 14:50, Daan Hoogland wrote:
> > As we get no major issues on it and we already voted to have this
> > design applied, is it alright to deploy this in the coming weeks?
> >
> > On Wed, Jan 17, 2024 at 8:31 PM Daan Hoogland
> > wrote:
> >>
> >> devs and users,
> >>
> >> back in august we had a small discussion about a new website
> design,
> >> led by Ivet [1]. In the meanwhile Rohit had investigated using
> >> docusaurus as a publishing mechanism for the site. After the last
> few
> >> weeks I have been working on integrating the two. The result so far
> >> can be viewed on the staging site [2]
> >>
> >> Please all have a look and give me any feedback you may have, so we
> >> can move this forward.
> >>
> >> [1]
> https://lists.apache.org/thread/fopjc3r4hjkp9nbkj9xzoxv406rowkso
> >> [2] https://cloudstack.staged.apache.org/
> >>
> >> --
> >> Daan
>
>
>


-- 
Daan

Re: [VOTE] Apache CloudStack 4.19.0.0 RC4

[Daan Hoogland]

signatures ok,
+1 (binding)

will also do a monkey test on simulator and retract my +1 if needed ;)

On Mon, Jan 29, 2024 at 7:58 AM Abhishek Kumar  wrote:
>
> Hi All,
>
> I've created a 4.19.0.0 release (RC4), with the following artifacts up for
> a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/tree/4.19.0.0-RC20240129T1021
> Commit: 2746225b999612f156e421199e34ef8de98a3664
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.19.0.0/
>
> PGP release keys (signed using 65518106473A09D7AF26B384A70BD2EAA74E2866):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> For testing purposes, I have uploaded the different distro packages to:
> http://download.cloudstack.org/testing/4.19.0.0-RC4/
>
> Since 4.16 the system VM template registration is no longer mandatory
> before upgrading, however, it can be downloaded from here if needed:
> https://download.cloudstack.org/systemvm/4.19/
>
> The vote will be open for 72 hours.
>
> 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)
>
> Regards,
> Abhishek



-- 
Daan

Re: Autoscaling with Multiple Load Balancers for Docker Containers

[Daan Hoogland]

ah, this looks like you want to involve something like terraform in
combination with a set of well prepared templates and autoscaling. I
do not think this will be "ready to go"/"out of the box"
functionality. For the autoscale group and for the container
deployment separately there is functionality, but tying the two
together will require extra wizardry.

On Tue, Jan 23, 2024 at 8:18 AM Palash Biswas  wrote:
>
> Here you go
>
>
>
> On Tue, 23 Jan 2024 at 3:04 PM, Daan Hoogland  wrote:
>>
>> Palesh, your image does not make it to the list.
>>
>> On Tue, Jan 23, 2024 at 6:16 AM Palash Biswas  wrote:
>>
>> > Hi Daan/Community
>> >
>> > I've created a simplified diagram to help illustrate my requirement.
>> > Essentially, I need to set up two Auto Scaling groups for VM3 and VM4, each
>> > of which hosts multiple containers, each with different port numbers.
>> >
>> > As you may know, when creating an Auto Scaling group, it's typically
>> > associated with a single Load Balancer (LB) and a single port. I'm seeking
>> > advice on how to associate multiple LBs or a single LB with multiple ports,
>> > or if there's an alternative solution that can help me achieve this
>> > architectural setup?
>> >
>> >
>> > I am using CloudStack 4.18.1.0
>> > [image: image.png]
>> >
>> > Regards,
>> > Palash
>> >
>> > On Mon, Jan 22, 2024 at 6:58 PM Daan Hoogland 
>> > wrote:
>> >
>> >> Palash,
>> >> can you please explain your use-case more precisely? What cloudstack
>> >> environment and configuration are you using?  what dimension do you
>> >> expect to scale?
>> >>
>> >> regards,
>> >>
>> >> On Mon, Jan 22, 2024 at 11:48 AM Palash Biswas 
>> >> wrote:
>> >> >
>> >> > Hello community,
>> >> >
>> >> > Is there a way to integrate multiple load balancers into the autoscaling
>> >> > group without using Kubernetes or Docker Swarm? I have Docker
>> >> containers on
>> >> > various ports, and I aim to achieve autoscaling for the VM. Please
>> >> provide
>> >> > guidance on implementing autoscaling with multiple running containers.
>> >> >
>> >> > Regards,
>> >> > Palash Biswas
>> >>
>> >>
>> >>
>> >> --
>> >> Daan
>> >>
>> >
>>
>> --
>> Daan



-- 
Daan

Re: Autoscaling with Multiple Load Balancers for Docker Containers

[Daan Hoogland]

Palesh, your image does not make it to the list.

On Tue, Jan 23, 2024 at 6:16 AM Palash Biswas  wrote:

> Hi Daan/Community
>
> I've created a simplified diagram to help illustrate my requirement.
> Essentially, I need to set up two Auto Scaling groups for VM3 and VM4, each
> of which hosts multiple containers, each with different port numbers.
>
> As you may know, when creating an Auto Scaling group, it's typically
> associated with a single Load Balancer (LB) and a single port. I'm seeking
> advice on how to associate multiple LBs or a single LB with multiple ports,
> or if there's an alternative solution that can help me achieve this
> architectural setup?
>
>
> I am using CloudStack 4.18.1.0
> [image: image.png]
>
> Regards,
> Palash
>
> On Mon, Jan 22, 2024 at 6:58 PM Daan Hoogland 
> wrote:
>
>> Palash,
>> can you please explain your use-case more precisely? What cloudstack
>> environment and configuration are you using?  what dimension do you
>> expect to scale?
>>
>> regards,
>>
>> On Mon, Jan 22, 2024 at 11:48 AM Palash Biswas 
>> wrote:
>> >
>> > Hello community,
>> >
>> > Is there a way to integrate multiple load balancers into the autoscaling
>> > group without using Kubernetes or Docker Swarm? I have Docker
>> containers on
>> > various ports, and I aim to achieve autoscaling for the VM. Please
>> provide
>> > guidance on implementing autoscaling with multiple running containers.
>> >
>> > Regards,
>> > Palash Biswas
>>
>>
>>
>> --
>> Daan
>>
>

-- 
Daan

Re: Miscellaneous Questions about Cloudstack

[Daan Hoogland]

On Mon, Jan 22, 2024 at 12:16 PM Bryan Tiang 
wrote:

> Hi Dan,
>
it's Daan (long a)


> I see, my screenshots arent going through. Let me resend the questions and
> images again.
>
> *Question 1:*
> How can we get instances created to be done in a Project? It seems
> whatever we create is not captured within a project. Moreover, we can seem
> to be move items between projects. Is the only way to do it via direct API
> calls?
>
the only way at the moment is via API calls indeed. No UI implementation
for this.

*Question 2:*
> Refer to screenshot below. It say ‘RX 6.45GB’ and ’TX 4.42GB’. What is
> this exactly? It doesn’t look like bandwidth.
>
> These are network usage over time, not bandwidth.

*Question 3:*
> What are the out of bounds way to monitor the traffic of the private
> gateway in the VR?
>
Sorry, I do not have a concise answer to that.

*Question 4:*
> We have a large range of public IP addresses. Under VPC > Public IP
> Addresses, we'd like to acquire a specific IP address that is pretty far
> down the range, but it's not available in the drop down box. When entered
> manually, the IP address is also not found.
>
> this one is a feature request for the UI, I think. There is not pagination
for all long lists implemented, so this needs to be done still. I don't
think there are plans for it atm.

Regards,
> Bryan
> On 22 Jan 2024 at 3:08 PM +0800, Daan Hoogland ,
> wrote:
>
> On Mon, Jan 22, 2024 at 7:56 AM Bryan Tiang 
> wrote:
>
> Hi Community,
>
> Have some questions, about using cloudstack from UI perspective.
>
> *Question 1:*
> We have created a VPC and instances under ROOT>DOMAIN
> We are wondering if there's a direct way to move the VPC and instances to
> ROOT>DOMAIN>PROJECT instead, without having to create a new VPC in
> ROOT>DOMAIN>PROJ and migrate the instances over one by one
>
> there are
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcloudstack.apache.org%2Fapi%2Fapidocs-4.18%2Fapis%2FassignVirtualMachine.html=05%7C02%7C%7C38c1290b342149beea2908dc1b18e3ba%7C84df9e7fe9f640afb435%7C1%7C0%7C638415040908126960%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=fyXU2UpvDCzh6mO%2FUwJUeGzh0RzBOOFZoznk3gkyzLM%3D=0
> and
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcloudstack.apache.org%2Fapi%2Fapidocs-4.18%2Fapis%2FassignVolume.html=05%7C02%7C%7C38c1290b342149beea2908dc1b18e3ba%7C84df9e7fe9f640afb435%7C1%7C0%7C638415040908134498%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=J1IXSCcc%2BcZdcAhl08Bln0n1p5gtoKsMQGXltDpDlt4%3D=0
> .
> We don't have such an API for networks and I don't think it is implemented
> in the UI yet.
>
>
> *Question 2:*
> When viewing instance details, we can see ingress and egress Network
> utilization. Is this figure the total network usage for the instance? If
> yes, how is it calculated? Since last boot, since instance creation or
> something else?
> [image: WhatsApp Image 2024-01-22 at 1.22.19 PM.jpeg]
>
> It is reported from the VR.
>
>
> *Question 3:*
>
> We have setup a VPC private gateway to connect to a remote data center for
> specific use case. Is there a way to monitor the network utilization of
> this private gateway? Besides that, is there any way to limit the bandwidth
> usage and overall network utilization?
>
> There are out-of-bounds way, but this functionality is not implemented in
> the VR.
>
> *Question 4:*
>
> We have a large range of public IP addresses. Under VPC > Public IP
> Addresses, we'd like to acquire a specific IP address that is pretty far
> down the range, but it's not available in the drop down box. When entered
> manually, the IP address is also not found.
>
> Can you try with an command line tool? like cmk?
> sounds like either a misconfiguration or a bug.
>
> I think your images are blocked:
>
> [image: WhatsApp Image 2024-01-22 at 1.40.13 PM.jpeg]
>
> Regards,
> Bryan
>
>
> regards, (and hope I didn't disappoint you too much;)
>
> --
> Daan
>
>

-- 
Daan

Re: Autoscaling with Multiple Load Balancers for Docker Containers

[Daan Hoogland]

Palash,
can you please explain your use-case more precisely? What cloudstack
environment and configuration are you using?  what dimension do you
expect to scale?

regards,

On Mon, Jan 22, 2024 at 11:48 AM Palash Biswas  wrote:
>
> Hello community,
>
> Is there a way to integrate multiple load balancers into the autoscaling
> group without using Kubernetes or Docker Swarm? I have Docker containers on
> various ports, and I aim to achieve autoscaling for the VM. Please provide
> guidance on implementing autoscaling with multiple running containers.
>
> Regards,
> Palash Biswas



-- 
Daan

Re: Miscellaneous Questions about Cloudstack

[Daan Hoogland]

On Mon, Jan 22, 2024 at 7:56 AM Bryan Tiang  wrote:

> Hi Community,
>
> Have some questions, about using cloudstack from UI perspective.
>
> *Question 1:*
> We have created a VPC and instances under ROOT>DOMAIN
> We are wondering if there's a direct way to move the VPC and instances to
> ROOT>DOMAIN>PROJECT instead, without having to create a new VPC in
> ROOT>DOMAIN>PROJ and migrate the instances over one by one
>
there are
https://cloudstack.apache.org/api/apidocs-4.18/apis/assignVirtualMachine.html
and https://cloudstack.apache.org/api/apidocs-4.18/apis/assignVolume.html.
We don't have such an API for networks and I don't think it is implemented
in the UI yet.


> *Question 2:*
> When viewing instance details, we can see ingress and egress Network
> utilization. Is this figure the total network usage for the instance? If
> yes, how is it calculated? Since last boot, since instance creation or
> something else?
> [image: WhatsApp Image 2024-01-22 at 1.22.19 PM.jpeg]
>
It is reported from the VR.


*Question 3:*
> We have setup a VPC private gateway to connect to a remote data center for
> specific use case. Is there a way to monitor the network utilization of
> this private gateway? Besides that, is there any way to limit the bandwidth
> usage and overall network utilization?
>
There are out-of-bounds way, but this functionality is not implemented in
the VR.

*Question 4:*
> We have a large range of public IP addresses. Under VPC > Public IP
> Addresses, we'd like to acquire a specific IP address that is pretty far
> down the range, but it's not available in the drop down box. When entered
> manually, the IP address is also not found.
>
Can you try with an command line tool? like cmk?
sounds like either a misconfiguration or a bug.

I think your images are blocked:

> [image: WhatsApp Image 2024-01-22 at 1.40.13 PM.jpeg]
>
> Regards,
> Bryan
>

regards, (and hope I didn't disappoint you too much;)

-- 
Daan

Re: Unable to Setup Private Gateway

[Daan Hoogland]

glad to hear you got through this. Strange though that the template
should be reinstalled. I am sure you mean that you re-instantiated the
router, right? As in restart network with cleanup?

On Mon, Jan 22, 2024 at 7:30 AM Bryan Tiang  wrote:
>
> Hi Daan,
>
> After few days of troubleshooting, we managed to resolve the issue.
>
> Change 1 - Reconfigure Network Config outside of Cloudstack
> Change 2 - Reinstall Router VR Template (Due to router in an unknown state)
>
> Regards,
> Bryan
> On 19 Jan 2024 at 10:26 PM +0800, Daan Hoogland , 
> wrote:
> > Bryan,
> > Did you follow this:
> > http://docs.cloudstack.apache.org/en/4.18.1.0/adminguide/networking/virtual_private_cloud_config.html#adding-a-private-gateway-to-a-vpc?
> > what tools did you use to test it?
> >
> > On Wed, Jan 17, 2024 at 9:49 AM Bryan Tiang  wrote:
> > >
> > > Hi All,
> > >
> > > We're setting up Private Gateway on VPC but not able to get the 
> > > connection to work. The connection is successful from switch to Private 
> > > Gateway IP using VLAN 995.
> > >
> > > However when Private Gateway is created in VPC, the connection failed 
> > > when tested from Virtual Router.
> > >
> > > Physical Network 3 is also used for Management & Public Network
> > >
> > > Is there any other config that we could have missed?
> > >
> > > Regards,
> > > Hunter
> >
> >
> >
> > --
> > Daan



-- 
Daan

Re: Failed to authenticate Veeam API service due to:Connection reset - Veeam 12

[Daan Hoogland]

I think Veeam 11 and up are not yet supported Cristian. there is a PR
out for that: https://github.com/apache/cloudstack/pull/8241

On Fri, Jan 19, 2024 at 12:53 PM  wrote:
>
> Hello,
>
>
>
> I'm struggling to link CloudStack with Veeam 12 and I keep encountering the
> same issue: "Failed to authenticate Veeam API service due to: Connection
> reset."
>
> My question is, should I be connecting to the API on the Veeam Enterprise
> Manager or the Backup and Replication server? I'm asking because the
> instructions aren't clear on this point.
>
>
>   - Veeam B server URL. Default: http://
>  :9398/api/ but
> B API does not run on 9398 it is on 9419, only the Veeam Backup Ent
> Manager API runs on 9398 and 9399.
>
>
>
> Anyone using with Veeam 12.
>
>
>
> Thank you,
>
> Cristian
>


-- 
Daan

Re: new website design

[Daan Hoogland]

As we get no major issues on it and we already voted to have this
design applied, is it alright to deploy this in the coming weeks?

On Wed, Jan 17, 2024 at 8:31 PM Daan Hoogland  wrote:
>
> devs and users,
>
> back in august we had a small discussion about a new website design,
> led by Ivet [1]. In the meanwhile Rohit had investigated using
> docusaurus as a publishing mechanism for the site. After the last few
> weeks I have been working on integrating the two. The result so far
> can be viewed on the staging site [2]
>
> Please all have a look and give me any feedback you may have, so we
> can move this forward.
>
> [1] https://lists.apache.org/thread/fopjc3r4hjkp9nbkj9xzoxv406rowkso
> [2] https://cloudstack.staged.apache.org/
>
> --
> Daan



-- 
Daan

Re: Unable To Delete Secondary Storage

[Daan Hoogland]

when all volumes templates and snapshots are removed you should be able to
remove a sector, but it can be very troublesome indeed. when removing a
zone, also removing physical network can block it because of IP addresses
in use and such. Hope you got your job done ;)

On Thu, Jan 18, 2024 at 4:47 AM Bryan Tiang 
wrote:

> Morning All,
>
> Just to update, we managed to resolve the issue, but it had to be done
> manually from the db.
>
> Manually alter DB to remove templates from old zone
>
> Successfully removed old templates > Old Secondary Storage > Old Zone
>
> Changed "state" to "inactive" and added date & time to "removed"
>
>
> Regards,
> Bryan
> On 16 Jan 2024 at 12:53 PM +0800, Bryan Tiang ,
> wrote:
>
> Hi Community,
>
> We're trying to remove secondary storage but we need to delete the
> existing templates first
> However, we're receiving this error Failed to delete template
>
> Error message from management server
> Jan 16 11:23:49 N2NCLOUDMY1MG01 java[87629]: ERROR
> [o.a.c.s.i.BaseImageStoreDriverImpl] (API-Job-Executor-1:ctx-259f8594
> job-9377 ctx-9f923096) (logid:c104e949) No remote endpoint to send command,
> check if host or ssvm is down?
>
> Ultimately we're trying to remove the zone, therefore we've also removed
> hosts associated to this zone
>
> 
>
> Regards,
> Bryan
>
>

-- 
Daan

Re: Upload ISO from local using SSL Offloading

[Daan Hoogland]

Wilken,

by ssl-offloading do you mean you have a proxy in front of your
MS(ses) and your MS running on an http port in a trusted network?
Pretty sure this won't work, a work around would be to upload to a url
and register from there.
did the ms log give you any more information before that message?

On Wed, Jan 17, 2024 at 5:53 PM W. Verleger - proIO GmbH
 wrote:
>
> Hi,
>
> Is there anyone using SSL offloading and able to use "Images" `a "upload ISO 
> from local" in CS 4.18.1.0 ?
>
> I receive the following error message in CS:
>
> Network Error
> Unable to reach the management server or a browser extension may be blocking 
> the network request.
>
> And MGMT server log:
>
> 024-01-17 17:27:01,611 DEBUG [o.a.c.s.e.DefaultEndPointSelector] 
> (Upload-Monitor-1:ctx-87ab24ff) (logid:2ed291e7) Coudn't find ssvm for 
> urlhttp://my.domain.com/upload/f63853e9-d9bc-46aa-b04c-6de181a939c2
>
> (my.domain.com as placeholder)
>
> Can anyone help how to achieve ISO upload from local?
> Thank  you!
>
>
> Best regards,
> Wilken
>
>
> - proIO GmbH -
> Geschäftsführer: Swen Brüseke
> Sitz der Gesellschaft: Frankfurt am Main
>
> USt-IdNr. DE 267 075 918
> Registergericht: Frankfurt am Main - HRB 86239
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
> erhalten haben,
> informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
> Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
> gestattet.
>
> This e-mail may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this e-mail in error) 
> please notify
> the sender immediately and destroy this e-mail.
> Any unauthorized copying, disclosure or distribution of the material in this 
> e-mail is strictly forbidden.
>


-- 
Daan

Re: Specify Primary Storage location for snapshots

[Daan Hoogland]

Granwille,
to my knowledge creating a snapshot always takes place on the storage the
volume is on and only after created can it be moved. I am not sure if this
is a "law of physics" or a rule like guideline.

On Wed, Jan 17, 2024 at 12:36 PM Granwille Strauss
 wrote:

> Good Day
>
> When making snapshots, the snapshot first stores the file in primary
> storage and then transports it to secondary storage and afterwards deletes
> it from primary leaving the copy on secondary storage. We currently use
> local kvm server as the primary storage for our VM instances. This means
> that the KVM host has limited disk space left to temporarily save that
> snapshot. Is it possible for us to specify a primary path where snapshot
> can temporarily store snapshots before moving it to secondary storage? We
> have an extra NFS server, which we cant to use as primary, because it has
> enough space for this purpose. Please let me know?
> --
> Regards / Groete
>
>  Granwille Strauss  //  Senior Systems Admin
>
> *e:* granwi...@namhost.com
> *m:* +264 81 323 1260 <+264813231260>
> *w:* www.namhost.com
>
>  
> 
> 
> 
>
>
> 
>
> Namhost Internet Services (Pty) Ltd,
>
> 24 Black Eagle Rd, Hermanus, 7210, RSA
>
>
>
> The content of this message is confidential. If you have received it by
> mistake, please inform us by email reply and then delete the message. It is
> forbidden to copy, forward, or in any way reveal the contents of this
> message to anyone without our explicit consent. The integrity and security
> of this email cannot be guaranteed over the Internet. Therefore, the sender
> will not be held liable for any damage caused by the message. For our full
> privacy policy and disclaimers, please go to
> https://www.namhost.com/privacy-policy
>
> [image: Powered by AdSigner]
> 
>


-- 
Daan

Re: Unable to Setup Private Gateway

[Daan Hoogland]

Bryan,
Did you follow this:
http://docs.cloudstack.apache.org/en/4.18.1.0/adminguide/networking/virtual_private_cloud_config.html#adding-a-private-gateway-to-a-vpc?
what tools did you use to test it?

On Wed, Jan 17, 2024 at 9:49 AM Bryan Tiang  wrote:
>
> Hi All,
>
> We're setting up Private Gateway on VPC but not able to get the connection to 
> work. The connection is successful from switch to Private Gateway IP using 
> VLAN 995.
>
> However when Private Gateway is created in VPC, the connection failed when 
> tested from Virtual Router.
>
> Physical Network 3 is also used for Management & Public Network
>
> Is there any other config that we could have missed?
>
> Regards,
> Hunter



-- 
Daan

Re: Backing up Cloudstack and KVM Hosts

[Daan Hoogland]

Granwille,

There are Networker and BackRoll. Both have a ACS plugging, though the
BackRoll one isn't yet merged. These are VM level solutions though. For
server I would not recommend trying to restore servers but just remove
faulty ones and add replacements to your zone/pods/clusters.

makes sense?


On Tue, Jan 16, 2024 at 3:48 PM Granwille Strauss
 wrote:

> Hi Guys
>
> Compliments of the new year! I would like to confirm what's the best way
> to backup a cloudstack and KVM server? Or what is the approach that most
> use? Do you guys make full server Image backups of the Cloudstack server
> with tools such as Veam or Acronis for example?
>
> Then, for a KVM host where VMs use local primary storage, what's the
> recommended way to backup your KVM servers in the event of hardware
> failure? I basically want to confirm what's the best way to backup the
> dedicated KVM and Cloudstack servers in case of *hardware* failures.
>
> What recommended solutions work best that have been tried and tested?
> --
> Regards / Groete
>
>  Granwille Strauss  //  Senior Systems Admin
>
> *e:* granwi...@namhost.com
> *m:* +264 81 323 1260 <+264813231260>
> *w:* www.namhost.com
>
>  
> 
> 
> 
>
>
> 
>
> Namhost Internet Services (Pty) Ltd,
>
> 24 Black Eagle Rd, Hermanus, 7210, RSA
>
>
>
> The content of this message is confidential. If you have received it by
> mistake, please inform us by email reply and then delete the message. It is
> forbidden to copy, forward, or in any way reveal the contents of this
> message to anyone without our explicit consent. The integrity and security
> of this email cannot be guaranteed over the Internet. Therefore, the sender
> will not be held liable for any damage caused by the message. For our full
> privacy policy and disclaimers, please go to
> https://www.namhost.com/privacy-policy
>
> [image: Powered by AdSigner]
> 
>


-- 
Daan

Re: Change isolation method

[Daan Hoogland]

did somemore digging and asking around. better not do it. just
redefine your zone.

On Fri, Jan 19, 2024 at 2:45 PM Daan Hoogland  wrote:
>
> Francisco, I am not sure if you can. The API doesn't support it so it
> would be rather ugly to do so. Let us know if you get any further with
> this.
>
> On Fri, Dec 29, 2023 at 10:12 AM Francisco Arencibia Quesada
>  wrote:
> >
> > Good morning guys,
> >
> > I need to change a zone's isolation method from VLAN to VXLAN. I can't find
> > an option for this. Is this possible? Do I  need to create a new zone from
> > scratch?
> >
> > Kind regards
> >
> > --
> > *Francisco Arencibia Quesada.*
> > *DevOps Engineer*
>
>
>
> --
> Daan



-- 
Daan

Re: I need to force delete primary storage definition

[Daan Hoogland]

Jimmy,
did you try this
https://cloudstack.apache.org/api/apidocs-4.18/apis/deleteStoragePool.html
(with force=true) ?

On Sat, Jan 13, 2024 at 9:34 AM Jeremy Hansen  wrote:
>
> Is there a way I can delete a primary storage configuration if the storage no 
> longer exists?  This is a test cluster but I’d like to understand how to 
> recover from this situation.  The volumes that were left behind on this 
> storage isn’t important.  How can I force delete this storage or the two 
> volumes left behind?  4.18.0.0.
>
> Thank you
> -jeremy
>
>
>


-- 
Daan

Re: Apache CloudStack and Ceph Day - February 22, Amsterdam

[Daan Hoogland]

I live in his backyard, will there as well.

On Tue, Jan 9, 2024 at 3:58 PM Wido den Hollander
 wrote:
>
>
>
> Op 09/01/2024 om 13:45 schreef Ivet Petrova:
> > Dear community members,
> >
> > We managed to finalised the date for our joint event with the Ceph 
> > community.
> > I am happy to share that we are doing it on February 22nd, in Amsterdam, 
> > Netherlands.
> > The event will be hosted by Adyen, the address is: Rokin 49, 1012 KK 
> > Amsterdam, The Netherlands
> >
> > Two things at this stage:
> >
> > 1. We still have a few speaking slots free (actually 2 slots only). If you 
> > are interested to present at the event, please submit your talk proposal 
> > now.
> > https://forms.gle/TnBfxS2cKWfe28CS6
> >
> > 2. We would be happy if we can see more people from the community, so 
> > register as an attendee here:
> > https://www.eventbrite.nl/e/cloudstack-and-ceph-day-netherlands-2024-tickets-700177167757
> >
> > Look forward to meeting you in Amsterdam!
>
> Yes! That's like my backyard. I'll be there!
>
> Wido
>
> >
> > Best regards,
> >
> >
> >
> >
> >



-- 
Daan

Re: Issue with GRE Tunnel between a VM and outside server

[Daan Hoogland]

Friborz, any progress?
not a gre expert but glad to see you get on with your problem.

On Sat, Jan 6, 2024 at 10:39 PM Fariborz Navidan  wrote:
>
> Hi Dear Experts,
>
> We are running Cs 4.15.0.0 with 2 KVM hosts having security groups enabled
> zone. We have a VM which a GRE tunnel has been setup between it and a
> server outside our network. Both hosts had been rebooted a few days ago due
> to power interruption. Before the reboot happens, the GRE tunnel was
> working properly on the mentioned VM. However after the reboot, GRE tunnel
> can be established but machines cannot reach each other via the tunnel's
> private IP address. All ports and protocols are already added to ingress
> rule set of security group which VM belongs to.
>
> Below is output of "ip a" and "ip r" commands on the VM running on our CS
> infrastructure.
>
> root@cdn-fr-1-kajgana-net:~# ip a
> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group
> default qlen 1000
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
>valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
>valid_lft forever preferred_lft forever
> 2: ens3:  mtu 1500 qdisc pfifo_fast state
> UP group default qlen 1000
> link/ether 1e:00:85:00:02:4d brd ff:ff:ff:ff:ff:ff
> inet 164.132.223.34/28 brd 164.132.223.47 scope global ens3
>valid_lft forever preferred_lft forever
> inet6 fe80::1c00:85ff:fe00:24d/64 scope link
>valid_lft forever preferred_lft forever
> 3: gre0@NONE:  mtu 1476 qdisc noop state DOWN group default qlen 1000
> link/gre 0.0.0.0 brd 0.0.0.0
> 4: gretap0@NONE:  mtu 1462 qdisc noop state DOWN group
> default qlen 1000
> link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
> 5: erspan0@NONE:  mtu 1450 qdisc noop state DOWN group
> default qlen 1000
> link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
> 6: gre1@NONE:  mtu 1476 qdisc noqueue state
> UNKNOWN group default qlen 1000
> link/gre 164.132.223.34 peer 89.205.123.34
> inet 192.168.169.1/30 scope global gre1
>valid_lft forever preferred_lft forever
> inet6 fe80::200:5efe:a484:df22/64 scope link
>valid_lft forever preferred_lft forever
>
> root@cdn-fr-1-kajgana-net:~# ip r
> default via 164.132.223.46 dev ens3
> 164.132.223.32/28 dev ens3 proto kernel scope link src 164.132.223.34
> 192.168.169.0/30 dev gre1 proto kernel scope link src 192.168.169.1
>
> IP address of tunnel's other endpoint is 192.168.169.2 which is unreachable
> from the VM. It looks like GRE tunnel has been established but traffic
> cannot be p[assed through.
>
> Is there something we need to do with iptables rules on the hosts to allow
> GRE traffic or is there anything else we can do to address this issue?
>
> Thanks in advance.
> Regards.



-- 
Daan

Re: Cloudstack 4.18.1.0 new feature (local volume snapshot changed)

[Daan Hoogland]

mikko, you can set the option to true. I would recommend against the
mounting hack you propose as it may conflict when things get copied to
and from primary <-> secondary

On Fri, Dec 29, 2023 at 4:56 PM Mikko Kaipila  wrote:
>
> I noticed that already. But why this changed to primary storage and
> hopefully there is a option to change this back to secondary. If not I
> consider to mount secondary to primary suitable but this is a dirty trick.
>
> pe 29. jouluk. 2023 klo 16.20 João Jandre Paraquetti 
> kirjoitti:
>
> > Hello, Mikko
> >
> > The snapshot.backup.to.secondary global configuration dictates whether
> > snapshots will stay on primary storage or will be backed up to secondary
> > storage.
> >
> > Best regards,
> > João Jandre
> >
> > On 12/29/23 10:50, Mikko Kaipila wrote:
> > > Hi,
> > >
> > > It seems that volume snapshot changed into primary storage instead of
> > secondary storage.
> > >
> > > Is there somewhere option to change this (back) to secondary storage? I
> > havent find option in global settings .
> > >
> > > There is only option to copy snapshot from primary to secondary.
> > >
> > > Regards
> > > Mikko
> > >
> >



-- 
Daan

Re: Change isolation method

[Daan Hoogland]

Francisco, I am not sure if you can. The API doesn't support it so it
would be rather ugly to do so. Let us know if you get any further with
this.

On Fri, Dec 29, 2023 at 10:12 AM Francisco Arencibia Quesada
 wrote:
>
> Good morning guys,
>
> I need to change a zone's isolation method from VLAN to VXLAN. I can't find
> an option for this. Is this possible? Do I  need to create a new zone from
> scratch?
>
> Kind regards
>
> --
> *Francisco Arencibia Quesada.*
> *DevOps Engineer*



-- 
Daan

Re: RHEL 8 hosts not recognized as UEFI enabled

[Daan Hoogland]

Medcludin, did you try adding the details? also did you check on the
hosts whether it is supported and somehow the configuration isn't
different?

On Thu, Nov 23, 2023 at 5:35 PM Mevludin Blazevic
 wrote:
>
> Hi all,
>
> for some reason, only 4 out of 20 hosts are enabled in the database as
> UEFI enabled, although all of them were installed identically (RHEL 8,
> cloudstack-agent and corresponding ovmf packages). In the DB, there are
> only 4 entries in host_details with host.uefi.enable = true. However,
> there are no entries with host.uefi.enable = false. Is there any quick
> workaround without removing and adding the host again?
>
> Best,
>
> Mevludin
>


-- 
Daan

Re: Cloudstack VM HA with 2 primary storage

[Daan Hoogland]

Yu Huang,
I guess nobody has done this (as you are not getting any responses)
Did you do further experiments ? how did you fare?

On Thu, Nov 23, 2023 at 7:50 AM Yu Huang Chan  wrote:
>
> Hi All,
>
> According to the CloudStock documentation, HA for hosts and HA-enabled KVM
> VMs only work with primary storage and must have iSCSI or NFS storage.
> In our current setup, the primary storage is Linstor raw block storage.
> To enable HA for hosts and HA-enabled KVM VM features, is it possible that
> we create another primary storage NFS with a capacity of only 200 MB for
> the heartbeat file?
>
> Hence, our setup will have two primary storages: the first is raw block
> storage, and the second is a small NFS with 200MB. Is it workable in this
> scenario?
>
> Any recommendations and best practices for production setup?
>
> Regards,
> Yu Huang



-- 
Daan

Re: [VOTE] Apache CloudStack 4.19.0.0 RC2

[Daan Hoogland]

agreed, thanks Abhi

On Thu, Jan 18, 2024 at 1:07 PM Abhishek Kumar  wrote:
>
> Hi all,
>
> Thanks you for your vote Nicolas and Daan.
> Thank you Wei for the tests. The reported issue will be a blocker for people 
> installing and upgrading on Ubuntu hosts.
> We already have a fix and test results on the PR 
> https://github.com/apache/cloudstack/pull/8524 look good.
>
> I'll work with contributors and cut a new RC with this fix.
>
> Regards,
> Abhishek
>
> On Wed, 17 Jan 2024 at 20:59, Wei ZHOU  wrote:
>>
>> Hi Daan,
>>
>> multipath is not used in our environments at all.
>> The tests for PR https://github.com/apache/cloudstack/pull/8524 look ok
>> until now. Let's wait for the test results.
>>
>> -Wei
>>
>> On Wed, 17 Jan 2024 at 15:16, Daan Hoogland  wrote:
>>
>> > Wei, is this with a VM/Volume not using multipath itself? If it is it
>> > is definitely a reason to create a new RC, if it isn't I think we can
>> > manage a known issue for a new feature.
>> >
>> > On Wed, Jan 17, 2024 at 2:50 PM Wei ZHOU  wrote:
>> > >
>> > > Thanks Ahbishek, and everyone tested or is testing RC2.
>> > >
>> > > I ran some tests on a ubuntu22 environment , and got the following
>> > > exception when stopping VMs.
>> > >
>> > > 2024-01-17 12:56:26,053 DEBUG [c.c.a.t.Request]
>> > > (AgentManager-Handler-17:null) (logid:) Seq 2-8295911988593164342:
>> > > Processing:  { Ans: , MgmtId: 32989056598488, via: 2, Ver: v1, Flags: 10,
>> > >
>> > [{"com.cloud.agent.api.Answer":{"result":"false","details":"java.lang.NullPointerException
>> > > at com.cloud.utils.script.Script.getExitValue(Script.java:74)
>> > > at
>> > >
>> > com.cloud.hypervisor.kvm.storage.MultipathSCSIAdapterBase.runScript(MultipathSCSIAdapterBase.java:476)
>> > > at
>> > >
>> > com.cloud.hypervisor.kvm.storage.MultipathSCSIAdapterBase.disconnectPhysicalDiskByPath(MultipathSCSIAdapterBase.java:226)
>> > > at
>> > >
>> > com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.disconnectPhysicalDiskByPath(KVMStoragePoolManager.java:205)
>> > > at
>> > >
>> > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.cleanupDisk(LibvirtComputingResource.java:3335)
>> > > at
>> > >
>> > com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStopCommandWrapper.execute(LibvirtStopCommandWrapper.java:101)
>> > > at
>> > >
>> > com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStopCommandWrapper.execute(LibvirtStopCommandWrapper.java:49)
>> > > at
>> > >
>> > com.cloud.hypervisor.kvm.resource.wrapper.LibvirtRequestWrapper.execute(LibvirtRequestWrapper.java:78)
>> > > at
>> > >
>> > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1903)
>> > >
>> > > The workaround is
>> > > chmod +x /usr/share/cloudstack-common/scripts/storage/multipath/*.sh
>> > > The PR to fix it : https://github.com/apache/cloudstack/pull/8524
>> > >
>> > >
>> > > Please note, this is not a -1 on the RC2. If we think this is not a
>> > > critical issue, we need to update the upgrade instruction for it.
>> > >
>> > >
>> > > -Wei
>> > >
>> > > On Mon, 15 Jan 2024 at 13:04, Abhishek Kumar 
>> > wrote:
>> > >
>> > > > Hi All,
>> > > >
>> > > > I've created a 4.19.0.0 release (RC2), with the following artifacts up
>> > for
>> > > > a vote:
>> > > >
>> > > > Git Branch and Commit SH:
>> > > > https://github.com/apache/cloudstack/tree/4.19.0.0-RC20240115T1418
>> > > > Commit: 38bd4fd72bdae354c4b0f615a4861fc84d67b29a
>> > > >
>> > > > Source release (checksums and signatures are available at the same
>> > > > location):
>> > > > https://dist.apache.org/repos/dist/dev/cloudstack/4.19.0.0/
>> > > >
>> > > > PGP release keys (signed using
>> > 65518106473A09D7AF26B384A70BD2EAA74E2866):
>> > > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>> > > >
>> > > > For testing purposes, I have uploaded the different distro packages to:
>> > > > http://download.cloudstack.org/testing/4.19.0.0-RC2/
>> > > >
>> > > > Since 4.16 the system VM template registration is no longer mandatory
>> > > > before upgrading, however, it can be downloaded from here if needed:
>> > > > https://download.cloudstack.org/systemvm/4.19/
>> > > >
>> > > > The vote will be open for 72 hours.
>> > > >
>> > > > 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)
>> > > >
>> > > > Regards,
>> > > > Abhishek
>> > > >
>> >
>> >
>> >
>> > --
>> > Daan
>> >



-- 
Daan

new website design

[Daan Hoogland]

devs and users,

back in august we had a small discussion about a new website design,
led by Ivet [1]. In the meanwhile Rohit had investigated using
docusaurus as a publishing mechanism for the site. After the last few
weeks I have been working on integrating the two. The result so far
can be viewed on the staging site [2]

Please all have a look and give me any feedback you may have, so we
can move this forward.

[1] https://lists.apache.org/thread/fopjc3r4hjkp9nbkj9xzoxv406rowkso
[2] https://cloudstack.staged.apache.org/

-- 
Daan

Re: [VOTE] Apache CloudStack 4.19.0.0 RC2

[Daan Hoogland]

Wei, is this with a VM/Volume not using multipath itself? If it is it
is definitely a reason to create a new RC, if it isn't I think we can
manage a known issue for a new feature.

On Wed, Jan 17, 2024 at 2:50 PM Wei ZHOU  wrote:
>
> Thanks Ahbishek, and everyone tested or is testing RC2.
>
> I ran some tests on a ubuntu22 environment , and got the following
> exception when stopping VMs.
>
> 2024-01-17 12:56:26,053 DEBUG [c.c.a.t.Request]
> (AgentManager-Handler-17:null) (logid:) Seq 2-8295911988593164342:
> Processing:  { Ans: , MgmtId: 32989056598488, via: 2, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":"false","details":"java.lang.NullPointerException
> at com.cloud.utils.script.Script.getExitValue(Script.java:74)
> at
> com.cloud.hypervisor.kvm.storage.MultipathSCSIAdapterBase.runScript(MultipathSCSIAdapterBase.java:476)
> at
> com.cloud.hypervisor.kvm.storage.MultipathSCSIAdapterBase.disconnectPhysicalDiskByPath(MultipathSCSIAdapterBase.java:226)
> at
> com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.disconnectPhysicalDiskByPath(KVMStoragePoolManager.java:205)
> at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.cleanupDisk(LibvirtComputingResource.java:3335)
> at
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStopCommandWrapper.execute(LibvirtStopCommandWrapper.java:101)
> at
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStopCommandWrapper.execute(LibvirtStopCommandWrapper.java:49)
> at
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtRequestWrapper.execute(LibvirtRequestWrapper.java:78)
> at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1903)
>
> The workaround is
> chmod +x /usr/share/cloudstack-common/scripts/storage/multipath/*.sh
> The PR to fix it : https://github.com/apache/cloudstack/pull/8524
>
>
> Please note, this is not a -1 on the RC2. If we think this is not a
> critical issue, we need to update the upgrade instruction for it.
>
>
> -Wei
>
> On Mon, 15 Jan 2024 at 13:04, Abhishek Kumar  wrote:
>
> > Hi All,
> >
> > I've created a 4.19.0.0 release (RC2), with the following artifacts up for
> > a vote:
> >
> > Git Branch and Commit SH:
> > https://github.com/apache/cloudstack/tree/4.19.0.0-RC20240115T1418
> > Commit: 38bd4fd72bdae354c4b0f615a4861fc84d67b29a
> >
> > Source release (checksums and signatures are available at the same
> > location):
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.19.0.0/
> >
> > PGP release keys (signed using 65518106473A09D7AF26B384A70BD2EAA74E2866):
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> > For testing purposes, I have uploaded the different distro packages to:
> > http://download.cloudstack.org/testing/4.19.0.0-RC2/
> >
> > Since 4.16 the system VM template registration is no longer mandatory
> > before upgrading, however, it can be downloaded from here if needed:
> > https://download.cloudstack.org/systemvm/4.19/
> >
> > The vote will be open for 72 hours.
> >
> > 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)
> >
> > Regards,
> > Abhishek
> >



-- 
Daan

Re: [VOTE] Apache CloudStack 4.19.0.0 RC2

[Daan Hoogland]

+1 (binding)

both signatures checked, otherwise as I was heavily involved I am
trusting in all testing done along the way.

On Mon, Jan 15, 2024 at 1:04 PM Abhishek Kumar  wrote:
>
> Hi All,
>
> I've created a 4.19.0.0 release (RC2), with the following artifacts up for
> a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/tree/4.19.0.0-RC20240115T1418
> Commit: 38bd4fd72bdae354c4b0f615a4861fc84d67b29a
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.19.0.0/
>
> PGP release keys (signed using 65518106473A09D7AF26B384A70BD2EAA74E2866):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> For testing purposes, I have uploaded the different distro packages to:
> http://download.cloudstack.org/testing/4.19.0.0-RC2/
>
> Since 4.16 the system VM template registration is no longer mandatory
> before upgrading, however, it can be downloaded from here if needed:
> https://download.cloudstack.org/systemvm/4.19/
>
> The vote will be open for 72 hours.
>
> 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)
>
> Regards,
> Abhishek



-- 
Daan

new PMC member Harikrishna Patnala

[Daan Hoogland]

users and dev,

The PMC have invited Harikrishna to join their ranks and he has
gracefully accepted. Please join me in congratulating Hari.

-- 
Daan

new committer: João Jandre Paraquetti

[Daan Hoogland]

community,
The PMC have invited João Jandre Paraquetti to join the project as a
committer and the invitation was gratefully accepted.
Please join me in welcoming João.
Congratulations João,

-- 
Daan

new committer Vladimir Petrov

[Daan Hoogland]

community,

The PMC has decided Vladi to become a committer and he has gracefully
accepted. Please join me in welcoming Vladi to the project as
committer.
Congratulations Vladi

-- 
Daan

Re: [VOTE] Adopt Github Discusssions as Users Forum

[Daan Hoogland]

+0 , I agree with Nux but we are already assimilated , so resistance
is more than just futile. If we keep mirroring to the mailing lists we
will always be able to set ourselves free again,

On Thu, Dec 7, 2023 at 10:00 AM Abhishek Kumar  wrote:
>
> +1 (binding)
>
> GH discussions looks better medium right now.
>
> On Tue, 5 Dec 2023 at 21:41, Wido den Hollander
>  wrote:
>
> > -0: Agree with Nux (see his concern in another e-mail)
> >
> > Op 04/12/2023 om 22:56 schreef Nux:
> > > -0 - I have voiced my concerns already.
> > >
> > >
> > > On 2023-12-04 08:01, Rohit Yadav wrote:
> > >> All,
> > >>
> > >> Following the discussion thread on adopting Github Discussions as
> > >> users forum [1], I put the following proposal for a vote:
> > >>
> > >>
> > >>   1.  Adopt and use Github Discussions as user forums.
> > >>   2.  The Github Discussions feature is tied with the
> > >> users@cloudstack.apache.org mailing list (PR:
> > >> https://github.com/apache/cloudstack/pull/8274).
> > >>   3.  Any project governance and decision-making thread such as
> > >> voting, releases etc. should continue to use the project mailing lists.
> > >>
> > >> Vote will be open for 120 hours (by Friday, 8th Dec).
> > >>
> > >> 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)
> > >>
> > >> [1] https://lists.apache.org/thread/hs0295hw9rnmhoh9l2qo5hc4b62hhvk8
> > >>
> > >>
> > >> Regards.
> >



-- 
Daan

Re: new committer Bryan Lima

[Daan Hoogland]

excuse me everybody, and mostly Bryan, for my C technology applied.
We have invited Bryan to become  a committer and not to the PMC (yet)

On Thu, Nov 30, 2023 at 10:11 AM Jimmy Huybrechts  wrote:
>
> Congratulations Bryan!
>
> --
> Jimmy
>
> Van: Daan Hoogland 
> Datum: donderdag, 30 november 2023 om 10:07
> Aan: dev , users 
> CC: PMC 
> Onderwerp: new committer Bryan Lima
> All,
>
> The Project Management Committee (PMC) for Apache CloudStack
> has invited Bryan Lima to become a PMC member and we are pleased
> to announce that they have accepted.
>
> Bryan has contributed himself and assisted in reviewing and testing
> the work of others. He has shown to be responsive, constructive and
> pleasant to work with.
>
> please join me in congratulating Bryan
>
> --
> Daan



-- 
Daan

new committer Bryan Lima

[Daan Hoogland]

All,

The Project Management Committee (PMC) for Apache CloudStack
has invited Bryan Lima to become a PMC member and we are pleased
to announce that they have accepted.

Bryan has contributed himself and assisted in reviewing and testing
the work of others. He has shown to be responsive, constructive and
pleasant to work with.

please join me in congratulating Bryan

-- 
Daan

Re: Import / Export Settings CS 4.18.1.0

[Daan Hoogland]

for global settings I'm sure a data base table export as inserts would
be easiest.
what do you mean by the etc?

On Wed, Nov 29, 2023 at 1:58 PM W. Verleger - proIO GmbH
 wrote:
>
> Hi,
>
> Is there a way to export all Cloudstack settings/configurations (global 
> settings etc) and import them into a fresh Cloudstack installation?
>
> Thank you!
>
>
> Best regards,
>
> Wilken Verleger
>
>
> - proIO GmbH -
> Geschäftsführer: Swen Brüseke
> Sitz der Gesellschaft: Frankfurt am Main
>
> USt-IdNr. DE 267 075 918
> Registergericht: Frankfurt am Main - HRB 86239
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
> erhalten haben,
> informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
> Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
> gestattet.
>
> This e-mail may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this e-mail in error) 
> please notify
> the sender immediately and destroy this e-mail.
> Any unauthorized copying, disclosure or distribution of the material in this 
> e-mail is strictly forbidden.
>


-- 
Daan

Re: Time sync problem, event not showing

[Daan Hoogland]

Raihan,
You can see the activity for those events in the logs?
And do you see events in the database events table?

On Wed, Nov 29, 2023 at 4:33 AM Raihan Jana Prasetya
 wrote:
>
> Hello,
> I was changing my users timezone setting because i'm troubleshooting when
> kubernetes cluster created with error state, before i don't have any
> trouble with it.
>
> I change accounts>admin>view users>admin>edit>Timezone=Asia/Jakarta
> Use Local Timezone=False on the top right corner
>
> And then i install ntp
> root@cloudstack:~# date
> Wed Nov 29 10:24:58 AM WIB 2023
> root@cloudstack:~# timedatectl
>Local time: Wed 2023-11-29 10:25:01 WIB
>Universal time: Wed 2023-11-29 03:25:01 UTC
>  RTC time: Wed 2023-11-29 03:25:01
> Time zone: Asia/Jakarta (WIB, +0700)
> System clock synchronized: yes
>   NTP service: n/a
>   RTC in local TZ: no
>
> now i noticed the events won't log any activity



-- 
Daan

new PMC member: Abhishek Kumar

[Daan Hoogland]

The Project Management Committee (PMC) for Apache CloudStack
has invited Abhishek Kumar to become a PMC member and we are pleased
to announce that they have accepted.

Abhishek has contributed in the past and has shown effort to make the
project run smoothly. He is also the Release Manager for the upcoming
4.19 release.

please join me in congratulating Abhishek

-- 
Daan

Re: Bank Client requires VM Firewall in between subnets

[Daan Hoogland]

Bryan,
there is a Palo Alto  plugin, but I am not sure how advanced it is. As
for intrusion detection I would put it in front of the CloudStack
installation. The virtual router is one thing you want to protect for
instance.

I'd need to see the proposed design to give any more judgemental advice.

On Tue, Nov 21, 2023 at 8:19 AM Bryan Tiang  wrote:
>
> Hi All,
>
> I have a potential client who is a bank, and requires a VPC, 3 Subnets, with 
> each subnet segregated by a firewall.
>
> We proposed the idea of using Network ACLs, but they didn’t accept the idea. 
> They want packet filtering, intrusion prevention features etc which are all 
> features of a full fledge firewall.
>
> Is it possible to install a VM Firewall from Fortinet/Palo Alto, use those to 
> segregate the traffic between the 3 subnets instead? All via cloudstack?
>
> If not, any idea how I could go around this?
>
> Regards,
> Bryan



-- 
Daan

Re: Documentation on instances live migration with KVM

[Daan Hoogland]

For documentation:

you
- fork/clone https://github.com/apache/cloudstack-documentation/
- create a new branch for your changes
- edit the docs in your branch
- push your changes to your upstream fork
- use https://github.com/apache/cloudstack-documentation/pull/new to
create the PR

It might require some studying if you're totally new to this.

call for help if need be

On Mon, Nov 20, 2023 at 5:27 PM Jimmy Huybrechts  wrote:
>
> I actually have never created a PR before ;) Where do I start?
>
> --
> Jimmy
>
> Van: Daan Hoogland 
> Datum: maandag, 20 november 2023 om 16:57
> Aan: users@cloudstack.apache.org 
> Onderwerp: Re: Documentation on instances live migration with KVM
> :D
> looking forward to your doc PR ;)
>
> On Mon, Nov 20, 2023 at 2:34 PM Jimmy Huybrechts  wrote:
> >
> > I noticed the documentation on instances is not entirely correct as it it 
> > says:
> >
> > (KVM) The Instance must not be using local disk storage. (On XenServer and 
> > VMware, Instance live migration with local disk is enabled by CloudStack 
> > support for XenMotion and vMotion.)
> >
> > Well, I’m using local storage on KVM and I’ve done like 6 live migrations 
> > with local storage until now, it worked fine every of those 6 times :)
> >
> > --
> > Jimmy
>
>
>
> --
> Daan



-- 
Daan

Re: Documentation on instances live migration with KVM

[Daan Hoogland]

:D
looking forward to your doc PR ;)

On Mon, Nov 20, 2023 at 2:34 PM Jimmy Huybrechts  wrote:
>
> I noticed the documentation on instances is not entirely correct as it it 
> says:
>
> (KVM) The Instance must not be using local disk storage. (On XenServer and 
> VMware, Instance live migration with local disk is enabled by CloudStack 
> support for XenMotion and vMotion.)
>
> Well, I’m using local storage on KVM and I’ve done like 6 live migrations 
> with local storage until now, it worked fine every of those 6 times :)
>
> --
> Jimmy



-- 
Daan

Re: Failed to fetch any free - False - ACS 4.18.1

[Daan Hoogland]

I did a quick search but cannot find a way this could happen. If you
can reproduce the situation please let us know Cristian

On Thu, Nov 16, 2023 at 5:30 PM  wrote:
>
> After I executed :
>
> select * from cloud.user_ip_address where removed is null and allocated is 
> null and state !='Free';
>
> I saw this (export as insert):
>
> INSERT INTO cloud.user_ip_address 
> (uuid,account_id,domain_id,public_ip_address,data_center_id,source_nat,allocated,vlan_db_id,one_to_one_nat,vm_id,state,mac_address,source_network_id,network_id,physical_network_id,is_system,vpc_id,dnat_vmip,is_portable,display,removed,created,rule_state,forsystemvms)
>  VALUES
>  
> ('fd4a170b-127e-444d-bf7d-b6ad5529122b',NULL,NULL,'217.xx.2xx.12',7,0,NULL,63,0,NULL,'Allocated',1163,247,NULL,213,0,NULL,NULL,0,1,NULL,NULL,NULL,0);
>
> There was no date for Allocated, it was with NULL.
>
> Thank you,
> Cristian
>
>
>
> -Original Message-
> From: Daan Hoogland 
> Sent: Thursday, November 16, 2023 5:33 PM
> To: users@cloudstack.apache.org
> Subject: Re: Failed to fetch any free - False - ACS 4.18.1
>
> just to recap Christian,
> You had one with state free and removed null and now it works again?
> Even though there where free IP before? that should not have been a problem. 
> I think that is a bug. Can you exact how you fixed it?
>
> On Thu, Nov 16, 2023 at 4:26 PM  wrote:
> >
> > Hi Wei,
> >
> >   Thank you for this!  There was 1 IP with removed null and state free. I 
> > fixed.
> >
> >
> > Regards,
> > Cristian
> >
> >
> >
> > -Original Message-
> > From: Wei ZHOU 
> > Sent: Thursday, November 16, 2023 12:49 PM
> > To: users@cloudstack.apache.org
> > Subject: Re: Failed to fetch any free - False - ACS 4.18.1
> >
> > Is it possible that an IP is not allocated but the state is not Free ?
> >
> > The sql query below should return empty results.
> >
> > select * from cloud.user_ip_address where removed is null and
> > allocated is null and state !='Free';
> >
> > -Wei
> >
> >
> > On Thu, 16 Nov 2023 at 10:11, Daan Hoogland  wrote:
> >
> > > strange Christian,
> > >
> > > I checked the code and the only thing I can think of is that
> > > creating a DB lock fails.
> > >
> > > if (_ipAddressDao.lockRow(possibleAddr.getId(), true) != null) {
> > > final IPAddressVO userIp =
> > > _ipAddressDao.findById(possibleAddr.getId());
> > > if (userIp.getState() == State.Free) {
> > > possibleAddr.setState(State.Allocating);
> > > if (_ipAddressDao.update(possibleAddr.getId(), possibleAddr)) {
> > > finalAddress = possibleAddr;
> > > break;
> > > }
> > > }
> > > }
> > >
> > > Unfortunately, no further logging can be turned on to investigate.
> > >
> > > is this a persistent error (i.e. remains after restarting system
> > > components like the MS and the DB)?
> > >
> > > On Wed, Nov 15, 2023 at 5:52 PM  wrote:
> > > >
> > > >
> > > > Hello,
> > > >
> > > >
> > > >
> > > > Today, I tried to deploy new VMs, but I encountered the following error:
> > > > failed to fetch any free public IP address. This is incorrect, as
> > > > even on the dashboard, I can see 12/22 for Public and 172/212 for
> > > > Shared. For
> > > this
> > > > deployment, I used the Shared/guest network. I also checked the
> > > > database
> > > and
> > > > saw 41 free IPs for this zone.
> > > >
> > > >
> > > > Any suggestions?
> > > >
> > > >
> > > > 2023-11-15 11:18:53,441 INFO  [c.c.h.v.m.VirtualMachineMO]
> > > > (DirectAgent-19:ctx-a91068e2 usa-nyc-001.test.host, cmd:
> > > > GetVolumeStatsCommand) (logid:851b339a) Look for disk device info
> > > > from volume : ROOT-6215_2.vmdk with base name: ROOT-6215_2
> > > >
> > > > 2023-11-15 11:18:53,441 INFO  [c.c.h.v.m.VirtualMachineMO]
> > > > (DirectAgent-19:ctx-a91068e2 usa-nyc-001.test.host, cmd:
> > > > GetVolumeStatsCommand) (logid:851b339a) Test against disk device,
> > > controller
> > > > key: 1000, unit number: 0
> > > >
> > > > 2023-11-15 11:18:53,441 INFO  [c.c.h.v.m.VirtualMachineMO]
> > > > (DirectAgent-19:ctx-a91068e2 usa-nyc-001.test.host, cmd:
> > > > GetVolumeStat

Re: Failed to fetch any free - False - ACS 4.18.1

[Daan Hoogland]

just to recap Christian,
You had one with state free and removed null and now it works again?
Even though there where free IP before? that should not have been a
problem. I think that is a bug. Can you exact how you fixed it?

On Thu, Nov 16, 2023 at 4:26 PM  wrote:
>
> Hi Wei,
>
>   Thank you for this!  There was 1 IP with removed null and state free. I 
> fixed.
>
>
> Regards,
> Cristian
>
>
>
> -Original Message-
> From: Wei ZHOU 
> Sent: Thursday, November 16, 2023 12:49 PM
> To: users@cloudstack.apache.org
> Subject: Re: Failed to fetch any free - False - ACS 4.18.1
>
> Is it possible that an IP is not allocated but the state is not Free ?
>
> The sql query below should return empty results.
>
> select * from cloud.user_ip_address where removed is null and allocated is 
> null and state !='Free';
>
> -Wei
>
>
> On Thu, 16 Nov 2023 at 10:11, Daan Hoogland  wrote:
>
> > strange Christian,
> >
> > I checked the code and the only thing I can think of is that creating
> > a DB lock fails.
> >
> > if (_ipAddressDao.lockRow(possibleAddr.getId(), true) != null) {
> > final IPAddressVO userIp =
> > _ipAddressDao.findById(possibleAddr.getId());
> > if (userIp.getState() == State.Free) {
> > possibleAddr.setState(State.Allocating);
> > if (_ipAddressDao.update(possibleAddr.getId(), possibleAddr)) {
> > finalAddress = possibleAddr;
> > break;
> > }
> > }
> > }
> >
> > Unfortunately, no further logging can be turned on to investigate.
> >
> > is this a persistent error (i.e. remains after restarting system
> > components like the MS and the DB)?
> >
> > On Wed, Nov 15, 2023 at 5:52 PM  wrote:
> > >
> > >
> > > Hello,
> > >
> > >
> > >
> > > Today, I tried to deploy new VMs, but I encountered the following error:
> > > failed to fetch any free public IP address. This is incorrect, as
> > > even on the dashboard, I can see 12/22 for Public and 172/212 for
> > > Shared. For
> > this
> > > deployment, I used the Shared/guest network. I also checked the
> > > database
> > and
> > > saw 41 free IPs for this zone.
> > >
> > >
> > > Any suggestions?
> > >
> > >
> > > 2023-11-15 11:18:53,441 INFO  [c.c.h.v.m.VirtualMachineMO]
> > > (DirectAgent-19:ctx-a91068e2 usa-nyc-001.test.host, cmd:
> > > GetVolumeStatsCommand) (logid:851b339a) Look for disk device info
> > > from volume : ROOT-6215_2.vmdk with base name: ROOT-6215_2
> > >
> > > 2023-11-15 11:18:53,441 INFO  [c.c.h.v.m.VirtualMachineMO]
> > > (DirectAgent-19:ctx-a91068e2 usa-nyc-001.test.host, cmd:
> > > GetVolumeStatsCommand) (logid:851b339a) Test against disk device,
> > controller
> > > key: 1000, unit number: 0
> > >
> > > 2023-11-15 11:18:53,441 INFO  [c.c.h.v.m.VirtualMachineMO]
> > > (DirectAgent-19:ctx-a91068e2 usa-nyc-001.test.host, cmd:
> > > GetVolumeStatsCommand) (logid:851b339a) Test against disk backing :
> > [nyc001]
> > > i-2-6215-VMAMS/ROOT-6215_2.vmdk
> > >
> > > 2023-11-15 11:18:53,441 INFO  [c.c.h.v.m.VirtualMachineMO]
> > > (DirectAgent-19:ctx-a91068e2 usa-nyc-001.test.host, cmd:
> > > GetVolumeStatsCommand) (logid:851b339a) Disk backing : [nyc001]
> > > i-2-6215-VMAMS/ROOT-6215_2.vmdk matches ==> scsi0:0
> > >
> > > 2023-11-15 11:18:54,194 INFO  [c.c.n.NetworkModelImpl]
> > > (qtp1444635922-323:ctx-a813b819 ctx-3b16875f) (logid:2b3f6d9b)
> > > Checking permission for account admin
> > > (17274c5e-d492-11e5-86c3-000c298715c8) on network
> > > TestHost-Public-NYC (1bece1dc-d9c1-4bff-b5aa-67333a6830ae)
> > >
> > > 2023-11-15 11:18:54,309 INFO  [c.c.v.VirtualMachineManagerImpl]
> > > (qtp1444635922-323:ctx-a813b819 ctx-3b16875f) (logid:2b3f6d9b)
> > > allocating virtual machine from
> > > template:391d4eab-1506-44be-b743-5ae7bd0f4ad7 with
> > > hostname:i-2-6262-VMAMS and 1 networks
> > >
> > > 2023-11-15 11:18:54,325 ERROR [c.c.n.IpAddressManagerImpl]
> > > (qtp1444635922-323:ctx-a813b819 ctx-3b16875f) (logid:2b3f6d9b)
> > > Failed to fetch any free
> > >
> > > public IP address
> > >
> > > 2023-11-15 11:18:54,340 ERROR [c.c.a.ApiServer]
> > > (qtp1444635922-323:ctx-a813b819 ctx-3b16875f) (logid:2b3f6d9b)
> > > unhandled exception executing api command:
> > >

Re: Failed to fetch any free - False - ACS 4.18.1

[Daan Hoogland]

strange Christian,

I checked the code and the only thing I can think of is that creating
a DB lock fails.

if (_ipAddressDao.lockRow(possibleAddr.getId(), true) != null) {
final IPAddressVO userIp = _ipAddressDao.findById(possibleAddr.getId());
if (userIp.getState() == State.Free) {
possibleAddr.setState(State.Allocating);
if (_ipAddressDao.update(possibleAddr.getId(), possibleAddr)) {
finalAddress = possibleAddr;
break;
}
}
}

Unfortunately, no further logging can be turned on to investigate.

is this a persistent error (i.e. remains after restarting system
components like the MS and the DB)?

On Wed, Nov 15, 2023 at 5:52 PM  wrote:
>
>
> Hello,
>
>
>
> Today, I tried to deploy new VMs, but I encountered the following error:
> failed to fetch any free public IP address. This is incorrect, as even on
> the dashboard, I can see 12/22 for Public and 172/212 for Shared. For this
> deployment, I used the Shared/guest network. I also checked the database and
> saw 41 free IPs for this zone.
>
>
> Any suggestions?
>
>
> 2023-11-15 11:18:53,441 INFO  [c.c.h.v.m.VirtualMachineMO]
> (DirectAgent-19:ctx-a91068e2 usa-nyc-001.test.host, cmd:
> GetVolumeStatsCommand) (logid:851b339a) Look for disk device info from
> volume : ROOT-6215_2.vmdk with base name: ROOT-6215_2
>
> 2023-11-15 11:18:53,441 INFO  [c.c.h.v.m.VirtualMachineMO]
> (DirectAgent-19:ctx-a91068e2 usa-nyc-001.test.host, cmd:
> GetVolumeStatsCommand) (logid:851b339a) Test against disk device, controller
> key: 1000, unit number: 0
>
> 2023-11-15 11:18:53,441 INFO  [c.c.h.v.m.VirtualMachineMO]
> (DirectAgent-19:ctx-a91068e2 usa-nyc-001.test.host, cmd:
> GetVolumeStatsCommand) (logid:851b339a) Test against disk backing : [nyc001]
> i-2-6215-VMAMS/ROOT-6215_2.vmdk
>
> 2023-11-15 11:18:53,441 INFO  [c.c.h.v.m.VirtualMachineMO]
> (DirectAgent-19:ctx-a91068e2 usa-nyc-001.test.host, cmd:
> GetVolumeStatsCommand) (logid:851b339a) Disk backing : [nyc001]
> i-2-6215-VMAMS/ROOT-6215_2.vmdk matches ==> scsi0:0
>
> 2023-11-15 11:18:54,194 INFO  [c.c.n.NetworkModelImpl]
> (qtp1444635922-323:ctx-a813b819 ctx-3b16875f) (logid:2b3f6d9b) Checking
> permission for account admin (17274c5e-d492-11e5-86c3-000c298715c8) on
> network TestHost-Public-NYC (1bece1dc-d9c1-4bff-b5aa-67333a6830ae)
>
> 2023-11-15 11:18:54,309 INFO  [c.c.v.VirtualMachineManagerImpl]
> (qtp1444635922-323:ctx-a813b819 ctx-3b16875f) (logid:2b3f6d9b) allocating
> virtual machine from template:391d4eab-1506-44be-b743-5ae7bd0f4ad7 with
> hostname:i-2-6262-VMAMS and 1 networks
>
> 2023-11-15 11:18:54,325 ERROR [c.c.n.IpAddressManagerImpl]
> (qtp1444635922-323:ctx-a813b819 ctx-3b16875f) (logid:2b3f6d9b) Failed to
> fetch any free
>
> public IP address
>
> 2023-11-15 11:18:54,340 ERROR [c.c.a.ApiServer]
> (qtp1444635922-323:ctx-a813b819 ctx-3b16875f) (logid:2b3f6d9b) unhandled
> exception executing api command: [Ljava.lang.String;@4a8c9f6c
>
> com.cloud.utils.exception.CloudRuntimeException: Failed to fetch any free
> public IP address
>
> at
> com.cloud.network.IpAddressManagerImpl.lambda$assignAndAllocateIpAddressEntr
> y$0(IpAddressManagerImpl.java:374)
>
> at com.cloud.utils.db.Transaction.execute(Transaction.java:40)
>
> at
> com.cloud.network.IpAddressManagerImpl.assignAndAllocateIpAddressEntry(IpAdd
> ressManagerImpl.java:339)
>
> at
> com.cloud.network.IpAddressManagerImpl.fetchNewPublicIp(IpAddressManagerImpl
> .java:821)
>
> at
> com.cloud.network.IpAddressManagerImpl.fetchNewPublicIp(IpAddressManagerImpl
> .java:810)
>
> at
> com.cloud.network.IpAddressManagerImpl.assignPublicIpAddress(IpAddressManage
> rImpl.java:778)
>
> at
> com.cloud.network.IpAddressManagerImpl$10.doInTransactionWithoutResult(IpAdd
> ressManagerImpl.java:2240)
>
> at
> com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(
> TransactionCallbackWithExceptionNoReturn.java:25)
>
> at
> com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(
> TransactionCallbackWithExceptionNoReturn.java:21)
>
> at com.cloud.utils.db.Transaction.execute(Transaction.java:40)
>
> at
> com.cloud.network.IpAddressManagerImpl.allocateDirectIp(IpAddressManagerImpl
> .java:2220)
>
> at
> com.cloud.network.guru.DirectNetworkGuru$1.doInTransactionWithoutResult(Dire
> ctNetworkGuru.java:324)
>
> at
> com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(
> TransactionCallbackWithExceptionNoReturn.java:25)
>
> at
> com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(
> TransactionCallbackWithExceptionNoReturn.java:21)
>
> at com.cloud.utils.db.Transaction.execute(Transaction.java:40)
>
> at
> com.cloud.network.guru.DirectNetworkGuru.allocateDirectIp(DirectNetworkGuru.
> java:317)
>
> at
> com.cloud.network.guru.DirectNetworkGuru.allocate(DirectNetworkGuru.java:290
> )
>
> 

Re: [PROPOSE] ACS 4.19.0.0 release

[Daan Hoogland]

After consulting with Abhishek I have started to move PRs and issues out of
the 4.19 and 4.18.2 milestones. I think we are not going to make the dates
mentioned anyway but want to reduce the delay as much as possible.

Please be responsive on your PRs and issues if you want them in, I will not
touch the milestones of any item that has had activity in the last week.

hope you all forgive me one day,

On Thu, Oct 26, 2023 at 12:50 PM Abhishek Kumar <
abhishek.ku...@shapeblue.com> wrote:

> Hi all,
>
> Update on the current state of the 4.19.0.0 milestone. Currently, there
> are still 179 open items in the 4.19.0.0 milestone [1]. We still have many
> exciting new features which need some work in the form code-changes or
> review and testing.
> Also, there are some issues and PRs in 4.18.2.0 milestone [2] which are
> marked major in severity.
> Based on this I would like to propose moving the earlier suggested
> timeline further and the revised timeline can be,
>
> - Announce code freeze around mid of the next month, November 2023
> - RC1 can be expected thereafter in the second half of November 2023
>
> If you have got an active PR with a new feature or fix that you would like
> to see in 4.19.0.0 release please comment with your interest on the Github
> item.
>
> Regards,
> Abhishek
>
> [1] https://github.com/apache/cloudstack/milestone/24
> [2] https://github.com/apache/cloudstack/milestone/29
> 
> From: Abhishek Kumar 
> Sent: 11 October 2023 12:49
> To: d...@cloudstack.apache.org ;
> users@cloudstack.apache.org 
> Subject: Re: [PROPOSE] ACS 4.19.0.0 release
>
> Hi all,
>
> Update on the current state of the 4.19.0.0 milestone. Currently, there
> are around 189 open items in the 4.19.0.0 milestone with 73 open PRs and
> 116 open issues.
> Also, there are some issues and PRs in 4.18.2.0 milestone which are marked
> major in severity.
> Considering these and the fact that there are some interesting new
> features in the milestone that still need some changes, review, or testing
> we may see some deviation in the earlier suggested timeline.
>
>   *   Code freeze can be expected towards the end of the month, October
> 2023
>   *   RC1 can be expected thereafter in the month of November 2023
>
> Also, if you have got an active PR with a new feature or fix that you
> would like to see in 4.19.0.0 release please comment with your interest on
> the Github item.
>
> Regards,
> Abhishek
>
>
> 
> From: Daan Hoogland 
> Sent: 29 September 2023 15:22
> To: d...@cloudstack.apache.org 
> Cc: users@cloudstack.apache.org 
> Subject: Re: [PROPOSE] ACS 4.19.0.0 release
>
> Please note that these figures are not including any issues or PRs marked
> for 4.18.2. We have a lot to filter out.
>
> On Fri, Sep 29, 2023 at 11:33 AM Abhishek Kumar <
> abhishek.ku...@shapeblue.com> wrote:
>
> > Hi all,
> >
> > Update on the current state of the 4.19.0.0 milestone. Currently, there
> > are 203 open items in the 4.19.0.0 milestone with 72 open PRs and 131
> open
> > issues.
> > Considering the earlier suggested timeline, from next week, we will have
> > to triage the open items more diligently to move the inactive items out
> of
> > the milestone.
> > The release timeline remains the same:
> >
> >   *   Code freeze, and stabilization to accept only critical/blocker
> > issues in the second half of October 2023. We should be in a better
> > position to have a specific date in a week or so.
> >   *   Cut 4.19.0.0 RC1 towards the end of October 2023.
> >
> > Looking forward to your support.
> >
> > Regards,
> > Abhishek
> >
> > 
> > From: Abhishek Kumar 
> > Sent: 17 August 2023 22:47
> > To: d...@cloudstack.apache.org ;
> > users@cloudstack.apache.org 
> > Subject: [PROPOSE] ACS 4.19.0.0 release
> >
> > Hi,
> >
> > Thanks all for your support on my 4.19 RM proposal thread!
> >
> > I propose the following timeline for the 4.19.0.0 release. Keep in mind
> > 4.18.1.0 release work is also currently in progress and is being managed
> by
> > Wei.
> >
> > - (8 plus weeks) Ongoing – Mid-October 2023: Accept all bugs, issues,
> > improvements allowed in LTS [1]
> > - (1 week) Stabilise the main (or 4.19) branch, accept only
> > critical/blocker issues (if any)
> > - End October 2023 and onwards: Cut 4.19.0.0 RC1 and further RCs if
> > necessary, start/conclude vote, and finish release work
> >
> > I hope to get support from all active contributors during the process of
&g

Re: Changing Network Offering Network Rate after creation

[Daan Hoogland]

No Marty,
the reason is that multiple networks may use the same offering. You can add
an offering with a higher rate and then update the network with the new
offering.

On Thu, Nov 9, 2023 at 7:11 AM  wrote:

> Is there a way to change the network offering network rate after the fact?
> I
> have an L2 network offering that I would like to change to a higher rate,
> and I do not see any way through the GUI to do this. Is this a CloudMonkey
> command?
>
>
>
> Marty
>
>

-- 
Daan

Re: Redundant router - Isolated Network

[Daan Hoogland]

Christian,
this option has been purposefully removed because it was used accidentally
too often. To create a network as redundant you need to select the
appropriate network_offering for it.
see these APIs:
https://cloudstack.apache.org/api/apidocs-4.18/apis/createNetwork.html
https://cloudstack.apache.org/api/apidocs-4.18/apis/updateNetwork.html

On Wed, Nov 8, 2023 at 10:18 AM  wrote:

> Hello,
>
>
>
>  I'm trying to enable a redundant router in an isolated network. The
> issue I have is that I do not find the option to do this in the UI 4.18.1.
> Is this a bug or is it not possible? I remember that it was possible in the
> previous versions.
>
>
> Thanks,
>
> Cristian
>
>

-- 
Daan

Re: Ratio billing over 24h

[Daan Hoogland]

I mean try startdate="2023-11-06'T'00:00:00"
enddate="2023-11-06'T'23:59:59". Does that give the expected output?

On Tue, Nov 7, 2023 at 1:37 PM Francisco Arencibia Quesada <
arencibia.franci...@gmail.com> wrote:

> 24h of ratio :)
>
> it should always be less or equal than 24h right?
> The result above 24 h is breaking my head.
>
> On Tue, Nov 7, 2023 at 1:32 PM Daan Hoogland 
> wrote:
>
> > Fransisco,
> >
> > Do these happen to be 48 hour ratios?
> >
> > startdate="2023-11-06'T'00:00:00" enddate="2023-11-07'T'00:00:00", could
> > just be one second more than you intend to find.
> >
> > On Tue, Nov 7, 2023 at 12:45 PM Francisco Arencibia Quesada <
> > arencibia.franci...@gmail.com> wrote:
> >
> > > Good morning guys,
> > >
> > > I have created a script to get the ratios, and for some reason is
> giving
> > me
> > > more than 24h, I have checked the calculation and it is correct, do you
> > > know why this could be?
> > >
> > >
> > > the time frame I'm using has the following format:
> > > startdate="2023-11-06'T'00:00:00" enddate="2023-11-07'T'00:00:00"
> > >
> > >
> > > This is my script output:
> > > Processing page 1: 500 VMs running
> > > Processing page 2: 500 VMs running
> > > Processing page 3: 500 VMs running
> > > Processing page 4: 500 VMs running
> > > Processing page 5: 500 VMs running
> > > Processing page 6: 500 VMs running
> > > Processing page 7: 500 VMs running
> > > Processing page 8: 500 VMs running
> > > Processing page 9: 171 VMs running
> > > 4171 VMs running found
> > > Processing page 1: 500 public IP addresses
> > > Processing page 2: 500 public IP addresses
> > > Processing page 3: 500 public IP addresses
> > > Processing page 4: 500 public IP addresses
> > > Processing page 5: 500 public IP addresses
> > > Processing page 6: 500 public IP addresses
> > > Processing page 7: 500 public IP addresses
> > > Processing page 8: 500 public IP addresses
> > > Processing page 9: 500 public IP addresses
> > > Processing page 10: 197 public IP addresses
> > > 4697 public IP addresses found
> > > Processing page 1: 497 disks in ready status
> > > Processing page 2: 500 disks in ready status
> > > Processing page 3: 500 disks in ready status
> > > Processing page 4: 498 disks in ready status
> > > Processing page 5: 500 disks in ready status
> > > Processing page 6: 500 disks in ready status
> > > Processing page 7: 500 disks in ready status
> > > Processing page 8: 500 disks in ready status
> > > Processing page 9: 500 disks in ready status
> > > Processing page 10: 500 disks in ready status
> > > Processing page 11: 183 disks in ready status
> > > 5178 disks in ready status found
> > > Processing page 1: 11963.4 usagetype 1
> > > Processing page 2: 11973.3 usagetype 1
> > > Processing page 3: 11962.9 usagetype 1
> > > Processing page 4: 11979.1 usagetype 1
> > > Processing page 5: 11924.1 usagetype 1
> > > Processing page 6: 11922.2 usagetype 1
> > > Processing page 7: 11993.6 usagetype 1
> > > Processing page 8: 11923.5 usagetype 1
> > > Processing page 9: 4077.14 usagetype 1
> > > 99719.24 usagetype 1 found
> > > Processing page 1: 11958.3 usagetype 3
> > > Processing page 2: 12000 usagetype 3
> > > Processing page 3: 11976 usagetype 3
> > > Processing page 4: 11989.2 usagetype 3
> > > Processing page 5: 11976.1 usagetype 3
> > > Processing page 6: 12000 usagetype 3
> > > Processing page 7: 11985.9 usagetype 3
> > > Processing page 8: 12000 usagetype 3
> > > Processing page 9: 12000 usagetype 3
> > > Processing page 10: 4214.53 usagetype 3
> > > 112100.03 usagetype 3 found
> > > Processing page 1: 11939.5 usagetype 6
> > > Processing page 2: 11976 usagetype 6
> > > Processing page 3: 12000 usagetype 6
> > > Processing page 4: 11891.6 usagetype 6
> > > Processing page 5: 11958.7 usagetype 6
> > > Processing page 6: 11909.5 usagetype 6
> > > Processing page 7: 11976 usagetype 6
> > > Processing page 8: 11983.4 usagetype 6
> > > Processing page 9: 11918.6 usagetype 6
> > > Processing page 10: 12000 usagetype 6
> > > Processing page 11: 10080.1 usagetype 6
> > > 129633.4 usagetype 6 found
> > > Total VMs running: 4171
> > > Total public IP addresses: 4697
> > > Total disks in ready status: 5178
> > > Total hours for usage type 1 [VM]: 99719.24
> > > Total hours for usage type 3 [IP]: 112100.03
> > > Total hours for usage type 6 [disk]: 129633.40
> > > Getting ratios
> > > Ratio of billed hours per VM: 23.90
> > > Ratio of billed hours per public ip: 23.86
> > > Ratio of billed hours per volumen: 25.03
> > >
> > >
> > > Regards
> > > --
> > > *Francisco Arencibia Quesada.*
> > > *DevOps Engineer*
> > >
> >
> >
> > --
> > Daan
> >
>
>
> --
> *Francisco Arencibia Quesada.*
> *DevOps Engineer*
>


-- 
Daan

Re: Ratio billing over 24h

[Daan Hoogland]

Fransisco,

Do these happen to be 48 hour ratios?

startdate="2023-11-06'T'00:00:00" enddate="2023-11-07'T'00:00:00", could
just be one second more than you intend to find.

On Tue, Nov 7, 2023 at 12:45 PM Francisco Arencibia Quesada <
arencibia.franci...@gmail.com> wrote:

> Good morning guys,
>
> I have created a script to get the ratios, and for some reason is giving me
> more than 24h, I have checked the calculation and it is correct, do you
> know why this could be?
>
>
> the time frame I'm using has the following format:
> startdate="2023-11-06'T'00:00:00" enddate="2023-11-07'T'00:00:00"
>
>
> This is my script output:
> Processing page 1: 500 VMs running
> Processing page 2: 500 VMs running
> Processing page 3: 500 VMs running
> Processing page 4: 500 VMs running
> Processing page 5: 500 VMs running
> Processing page 6: 500 VMs running
> Processing page 7: 500 VMs running
> Processing page 8: 500 VMs running
> Processing page 9: 171 VMs running
> 4171 VMs running found
> Processing page 1: 500 public IP addresses
> Processing page 2: 500 public IP addresses
> Processing page 3: 500 public IP addresses
> Processing page 4: 500 public IP addresses
> Processing page 5: 500 public IP addresses
> Processing page 6: 500 public IP addresses
> Processing page 7: 500 public IP addresses
> Processing page 8: 500 public IP addresses
> Processing page 9: 500 public IP addresses
> Processing page 10: 197 public IP addresses
> 4697 public IP addresses found
> Processing page 1: 497 disks in ready status
> Processing page 2: 500 disks in ready status
> Processing page 3: 500 disks in ready status
> Processing page 4: 498 disks in ready status
> Processing page 5: 500 disks in ready status
> Processing page 6: 500 disks in ready status
> Processing page 7: 500 disks in ready status
> Processing page 8: 500 disks in ready status
> Processing page 9: 500 disks in ready status
> Processing page 10: 500 disks in ready status
> Processing page 11: 183 disks in ready status
> 5178 disks in ready status found
> Processing page 1: 11963.4 usagetype 1
> Processing page 2: 11973.3 usagetype 1
> Processing page 3: 11962.9 usagetype 1
> Processing page 4: 11979.1 usagetype 1
> Processing page 5: 11924.1 usagetype 1
> Processing page 6: 11922.2 usagetype 1
> Processing page 7: 11993.6 usagetype 1
> Processing page 8: 11923.5 usagetype 1
> Processing page 9: 4077.14 usagetype 1
> 99719.24 usagetype 1 found
> Processing page 1: 11958.3 usagetype 3
> Processing page 2: 12000 usagetype 3
> Processing page 3: 11976 usagetype 3
> Processing page 4: 11989.2 usagetype 3
> Processing page 5: 11976.1 usagetype 3
> Processing page 6: 12000 usagetype 3
> Processing page 7: 11985.9 usagetype 3
> Processing page 8: 12000 usagetype 3
> Processing page 9: 12000 usagetype 3
> Processing page 10: 4214.53 usagetype 3
> 112100.03 usagetype 3 found
> Processing page 1: 11939.5 usagetype 6
> Processing page 2: 11976 usagetype 6
> Processing page 3: 12000 usagetype 6
> Processing page 4: 11891.6 usagetype 6
> Processing page 5: 11958.7 usagetype 6
> Processing page 6: 11909.5 usagetype 6
> Processing page 7: 11976 usagetype 6
> Processing page 8: 11983.4 usagetype 6
> Processing page 9: 11918.6 usagetype 6
> Processing page 10: 12000 usagetype 6
> Processing page 11: 10080.1 usagetype 6
> 129633.4 usagetype 6 found
> Total VMs running: 4171
> Total public IP addresses: 4697
> Total disks in ready status: 5178
> Total hours for usage type 1 [VM]: 99719.24
> Total hours for usage type 3 [IP]: 112100.03
> Total hours for usage type 6 [disk]: 129633.40
> Getting ratios
> Ratio of billed hours per VM: 23.90
> Ratio of billed hours per public ip: 23.86
> Ratio of billed hours per volumen: 25.03
>
>
> Regards
> --
> *Francisco Arencibia Quesada.*
> *DevOps Engineer*
>


-- 
Daan

Re: Network ratelimiting

[Daan Hoogland]

sounds like a doc issue to me, the global settings are not actualised on
each resource and some of them are not even actualised unless you restart
the management server. Only details of a particular resource (i.e. the
local override of the setting) are sometimes actualised, depending on the
type.

On Tue, Nov 7, 2023 at 1:17 PM Jimmy Huybrechts 
wrote:

> I’m still finding out new things every day :)
>
> I noticed all offerings set to 200Mbit by default which equals to around
> 23MB/s, I changed the globals to 1 Gbit now and I can see all network
> offerings were updated to 1000Mbit too.
> However that made no difference in any instance that was set to the
> network offering of 200mbit before. I actually had to shutdown an instance
> and boot it back up before it got the gbit speeds.
>
> Was this because I adjusted the global speeds? Or is that always the case
> if you set / adjust the ratelimiting? (good to know up front) and wasn’t
> mentioned on the docs.
>
> --
> Jimmy
>


-- 
Daan

Re: Cant Create new system routers

[Daan Hoogland]

you beat us all to it marty ;)
Glad the issue is fixed

On Tue, Nov 7, 2023 at 8:27 AM  wrote:

> I found my issue. 
>
>
>
> Redownloading the template fixed the issue, I just forgot to make it a
> SYSTEM vs. USER type
>
>
>
> Marty
>
>
>
> From: ma...@gonsource.com 
> Sent: Tuesday, November 7, 2023 2:18 AM
> To: users@cloudstack.apache.org
> Subject: RE: Cant Create new system routers
>
>
>
> I started looking at the templates and I changed the Xenserver template
> back to the default 4.17.0 template. I know this would not work in general,
> but I wanted to see if it would create the VM at least.
>
>
>
> It created the VM.
>
>
>
> So, I went and redownloaded the system VM from the Cloudstack site and the
> issue comes back.
>
>
>
> Is there an issue with the 4.18.1 template download?
>
>
>
> Regards,
>
> Marty
>
>
>
>
>
> From: ma...@gonsource.com   <
> ma...@gonsource.com  >
> Sent: Tuesday, November 7, 2023 12:48 AM
> To: users@cloudstack.apache.org 
> Subject: Cant Create new system routers
>
>
>
> Hello,
>
>
>
> I am running 4.18.1.0, and for some reason, it will not let me create new
> domain routers. The error in the log says:
>
>
>
> No suitable pools found for volumes
>
>
>
> It's like it can't find enough storage for the router VM. But, I can
> create new VMs with no issues on domains with existing routers and all show
> as good on the storage side and the Cloudstack side. I do not have the
> setting checked to use local storage. I rebooted the management server and
> still no good.
>
>
>
> Any assistance would be greatly appreciated.
>
>
>
> Thank you,
>
> Marty
>
>
>
>
>
>

-- 
Daan

Re: Adjust offerings

[Daan Hoogland]

could you add an issue Jimmy,
https://github.com/apache/cloudstack/issues/new
I'll help you refine it if needed.

mazzel,

On Mon, Nov 6, 2023 at 12:12 PM Jimmy Huybrechts 
wrote:

> Maybe the global setting would the best one here? So people can decide for
> themselves if they want it (and take the risks with it) or use it as it is
> now.
>
> --
> Met vriendelijke groet,
> Jimmy Huybrechts
>
> Van: Daan Hoogland 
> Datum: maandag, 6 november 2023 om 11:55
> Aan: users@cloudstack.apache.org 
> Onderwerp: Re: Adjust offerings
> I'm not sure how to formulate the best enhancement request yet, but there
> surely is one in there.
> for instance:
> - extra input parameters to the request that will be ignore in case the
> offering is in use
> - a force flag
> - a global setting that will allow it
>
> I am really not sure which will be the best to consider.
>
>
> On Mon, Nov 6, 2023 at 11:51 AM Jimmy Huybrechts 
> wrote:
>
> > Not the cpu and such perse but it would have been nice if I could adjust
> > the default egress rules from deny to allow and being able to adjust the
> > storage from shared to local.
> >
> > I can see a reason why you do not want this for running instances but I
> > have no instances using this yet.
> >
> > Is there a way I can copy one, adjust what I need and save it as a new
> > one? If not that would be a good request :)
> >
> > --
> > Jimmy
> >
> >
> >
>
> --
> Daan
>


-- 
Daan

Re: Adjust offerings

[Daan Hoogland]

I'm not sure how to formulate the best enhancement request yet, but there
surely is one in there.
for instance:
- extra input parameters to the request that will be ignore in case the
offering is in use
- a force flag
- a global setting that will allow it

I am really not sure which will be the best to consider.


On Mon, Nov 6, 2023 at 11:51 AM Jimmy Huybrechts 
wrote:

> Not the cpu and such perse but it would have been nice if I could adjust
> the default egress rules from deny to allow and being able to adjust the
> storage from shared to local.
>
> I can see a reason why you do not want this for running instances but I
> have no instances using this yet.
>
> Is there a way I can copy one, adjust what I need and save it as a new
> one? If not that would be a good request :)
>
> --
> Jimmy
>
>
>

-- 
Daan

Re: Adjust offerings

[Daan Hoogland]

not according to that page, Loges.

request parameters are

Request parameters
*Parameter Name* Description Required
*id* *the ID of the service offering to be updated* *true*
*displaytext* *the display text of the service offering to be updated*
*false*
*name* *the name of the service offering to be updated* *false*
*sortkey* *sort key of the service offering, integer* *false*

The rest are only output

On Mon, Nov 6, 2023 at 11:30 AM Logeswaran T
 wrote:

> Hi Daan,
>
> Using update service offering API, I think we are able to change CPU speed,
> memory, etc.., Please check this URL.
>
>
> https://cloudstack.apache.org/api/apidocs-4.8/domain_admin/updateServiceOffering.html
>
> Regards,
> Loges
> www.stackbill.com
>
> On Mon, Nov 6, 2023 at 3:56 PM Daan Hoogland 
> wrote:
>
> > Yes Loges,
> > but only a limited number of attributes. I think Jimmy wants to be able
> to
> > also change #cpu, cpu-speed,memory etc
> >
> > On Mon, Nov 6, 2023 at 11:21 AM Logeswaran T
> >  wrote:
> >
> > > Hi Jimmy,
> > >
> > > You can able to update the compute or other offerings through API.
> > >
> > > Please check this URL: https://cloudstack.apache.org/api/apidocs-4.18/
> > >
> > > Regards,
> > > Loges
> > > www.stackbill.com
> > >
> > >
> > >
> > >
> > > On Mon, Nov 6, 2023 at 3:44 PM Jimmy Huybrechts 
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > The most annoying I’ve found until now is that you can’t adjust any
> > > > offerings, other then it’s name, description and availability.
> > > >
> > > > For example, in the source nat offering I wanted to have the egress
> > > policy
> > > > adjusted from deny to allow, now I have to fully recreate it for just
> > one
> > > > adjustment.
> > > > The same is that every offering inside compute or system is set to
> > shared
> > > > storage while I’m using local so I would have to recreate literally
> > every
> > > > offering.
> > > >
> > > > Is there a way to adjust these offerings without needing to recreate
> > them
> > > > all?
> > > >
> > > > --
> > > > Jimmy
> > > >
> > >
> > > --
> > >
> > >
> > >
> > >
> > > *This E-mail is confidential. It may also be legally privileged. If you
> > > are not the addressee you may not copy, forward, disclose or use any
> part
> > > of
> > > it. If you have received this message in error, please delete it and
> all
> > > copies
> > > from your system and notify the sender immediately by return E-mail.
> > > Internet
> > > communications cannot be guaranteed to be timely, secure, error or
> > > virus-free.
> > > The sender does not accept liability for any errors or
> > > omissions*
> > >
> >
> >
> > --
> > Daan
> >
>
> --
>
>
>
>
> *This E-mail is confidential. It may also be legally privileged. If you
> are not the addressee you may not copy, forward, disclose or use any part
> of
> it. If you have received this message in error, please delete it and all
> copies
> from your system and notify the sender immediately by return E-mail.
> Internet
> communications cannot be guaranteed to be timely, secure, error or
> virus-free.
> The sender does not accept liability for any errors or
> omissions*
>


-- 
Daan

Re: Adjust offerings

[Daan Hoogland]

Yes Loges,
but only a limited number of attributes. I think Jimmy wants to be able to
also change #cpu, cpu-speed,memory etc

On Mon, Nov 6, 2023 at 11:21 AM Logeswaran T
 wrote:

> Hi Jimmy,
>
> You can able to update the compute or other offerings through API.
>
> Please check this URL: https://cloudstack.apache.org/api/apidocs-4.18/
>
> Regards,
> Loges
> www.stackbill.com
>
>
>
>
> On Mon, Nov 6, 2023 at 3:44 PM Jimmy Huybrechts 
> wrote:
>
> > Hi,
> >
> > The most annoying I’ve found until now is that you can’t adjust any
> > offerings, other then it’s name, description and availability.
> >
> > For example, in the source nat offering I wanted to have the egress
> policy
> > adjusted from deny to allow, now I have to fully recreate it for just one
> > adjustment.
> > The same is that every offering inside compute or system is set to shared
> > storage while I’m using local so I would have to recreate literally every
> > offering.
> >
> > Is there a way to adjust these offerings without needing to recreate them
> > all?
> >
> > --
> > Jimmy
> >
>
> --
>
>
>
>
> *This E-mail is confidential. It may also be legally privileged. If you
> are not the addressee you may not copy, forward, disclose or use any part
> of
> it. If you have received this message in error, please delete it and all
> copies
> from your system and notify the sender immediately by return E-mail.
> Internet
> communications cannot be guaranteed to be timely, secure, error or
> virus-free.
> The sender does not accept liability for any errors or
> omissions*
>


-- 
Daan

Re: Adjust offerings

[Daan Hoogland]

Jimmy,

There is a good reason for that, though we could implement a setting and
then allow it if it is true.
The reason is that the offerings may be in use by VMs and restart of those
VMs could lead to unexpected results. In a public offering for instance
tariffs may change as a result. I can understand how an enterprise install
could benefit of it but wouldn't want to change the default behaviour.

regards,

On Mon, Nov 6, 2023 at 11:15 AM Jimmy Huybrechts 
wrote:

> Hi,
>
> The most annoying I’ve found until now is that you can’t adjust any
> offerings, other then it’s name, description and availability.
>
> For example, in the source nat offering I wanted to have the egress policy
> adjusted from deny to allow, now I have to fully recreate it for just one
> adjustment.
> The same is that every offering inside compute or system is set to shared
> storage while I’m using local so I would have to recreate literally every
> offering.
>
> Is there a way to adjust these offerings without needing to recreate them
> all?
>
> --
> Jimmy
>


-- 
Daan

Re: calcru: runtime went backwards, is this a normal behavior when creating a snapshot?

[Daan Hoogland]

@angel,
depending on your KVM/Qemu/libvirt versions a VM might be temporarily
stopped before taking a snapshot. Might this have something to do with it?

On Thu, Oct 26, 2023 at 4:29 AM an...@nttec.com.INVALID
 wrote:

> I was creating a snapshot of my VM which has freebsd 13.2 and has pfsense
> installed in it, when I encounter this logs
>
>
> Oct 26 01:37:00  kernel: calcru: runtime went backwards from 446770083
> usec to 30112729 usec for pid 374 (pf purge)
> Oct 26 01:37:00 kernel: calcru: runtime went backwards from 10196 usec to
> 686 usec for pid 1014 (getty)
> Oct 26 01:37:00 kernel: calcru: runtime went backwards from 10004 usec to
> 673 usec for pid 1015 (getty)
> Oct 26 01:37:00 kernel: calcru: runtime went backwards from 8803 usec to
> 592 usec for pid 1016 (getty)
> Oct 26 01:37:00  kernel: calcru: runtime went backwards from 8894 usec to
> 599 usec for pid 1017 (getty)
> Oct 26 01:37:00 kernel: calcru: runtime went backwards from 4317 usec to
> 290 usec for pid 1018 (getty)
> Oct 26 01:37:00 kernel: calcru: runtime went backwards from 10787 usec to
> 726 usec for pid 1402 (su)
> Oct 26 01:37:00 kernel: calcru: runtime went backwards from 93858 usec to
> 11396 usec for pid 86394 (php-cgi)
> Oct 26 01:37:00  kernel: calcru: runtime went backwards from 20818 usec to
> 1402 usec for pid 79867 (nginx)
> Oct 26 01:37:00 kernel: calcru: runtime went backwards from 68016993 usec
> to 4591667 usec for pid 79868 (nginx)
> Oct 26 01:37:00 kernel: calcru: runtime went backwards from 11359864 usec
> to 765565 usec for pid 79868 (nginx)
> Oct 26 01:37:00 kernel: calcru: runtime went backwards from 3575 usec to
> 240 usec for pid 381 (pflogd)
> Oct 26 01:37:00 kernel: calcru: runtime went backwards from 62569305 usec
> to 4225742 usec for pid 79869 (nginx)
> Oct 26 01:37:00  kernel: calcru: runtime went backwards from 13883970 usec
> to 935669 usec for pid 79869 (nginx)
> Oct 26 01:37:00 kernel: calcru: runtime went backwards from 77969052 usec
> to 5264356 usec for pid 79870 (nginx)
> Oct 26 01:37:00 kernel: calcru: runtime went backwards from 12238871 usec
> to 836457 usec for pid 79870 (nginx)
> Oct 26 01:37:00 kernel: calcru: runtime went backwards from 53601263 usec
> to 3622343 usec for pid 79871 (nginx)
> Oct 26 01:37:00 kernel: calcru: runtime went backwards from 5634804 usec
> to 379741 usec for pid 79871 (nginx)
> Oct 26 01:37:11 kernel: calcru: runtime went backwards from 18452780 usec
> to 1287573 usec for pid 0 (kernel)
> Oct 26 01:37:11  kernel: calcru: runtime went backwards from 3 usec to 0
> usec for pid 0 (kernel)
>
>
>
> is this a normal behavior when creating a snapshot?
>
>

-- 
Daan