Re: [VOTE] Apache CloudStack 4.20.0.0 RC1

[Wei ZHOU]

Hi João, and Daan,

I think there was something wrong in the forward-merge or branches.

For example, I can find the file Qcow2HeaderField.java in 4.18.2.4 and
4.19.1.2

https://github.com/apache/cloudstack/blob/4.18.2.4/services/secondary-storage/server/src/main/java/org/apache/cloudstack/storage/formatinspector/Qcow2HeaderField.java
https://github.com/apache/cloudstack/blob/4.19.1.2/services/secondary-storage/server/src/main/java/org/apache/cloudstack/storage/formatinspector/Qcow2HeaderField.java

However, it cannot be found in 4.18/4.19/main branches and
4.20.0.0-RC20241011T0947
 as
well.


-Wei



On Fri, Oct 11, 2024 at 2:54 PM João Jandre  wrote:

> Hi All,
>
> I've created a 4.20.0.0 release (RC1), with the following artifacts up
> for a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/tree/4.20.0.0-RC20241011T0947
> Commit: cd4acc1fa6219ce0ec5f44978c76bf5b859b98e0
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.20.0.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)
>
>

Re: Acronis backup plugin

[Wei ZHOU]

Hi Wido,

AFAIK, Acronis uses an agent installed inside the guest VMs to backup
files, disks, etc.
It is an os-level backup, not a vm-level backup.
In my opinion, users can use Acronis without any codes on CloudStack.


-Wei

On Fri, Oct 11, 2024 at 10:51 AM Wido den Hollander 
wrote:

> Hi,
>
> On the website I see Acronis listed as backup partner:
> https://cloudstack.apache.org/integrations/
>
> Nobody inside Acronis seems to know anything about it and a search in
> the code yields nothing either:
>
> wido-macbook:cloudstack wido$ grep -iIR acronis *
> wido-macbook:cloudstack wido$
>
> Does anybody have an idea?
>
> Wido
>

Re: ISCSI WITH KVM

[Wei ZHOU]

It looks like a migrate flag UNSAFE needs to set
https://java.libvirt.org/javadoc/org/libvirt/Domain.MigrateFlags.html#UNSAFE

Can you file a github issue ?


-Wei

On Thu, Oct 10, 2024 at 9:18 PM Sanjay Kumar  wrote:

> Hi
>
> We are trying to add iscsi with kvm in our infra with multiple host and it
> is working with one host only. is there any guide line for iscsi use as
> share storage with kvm.
>
> Migration failed.
> Exception during migrate: org.libvirt.LibvirtException: Unsafe migration:
> Migration without shared storage is unsafe
>
> Any help would be really appreciated. Thank you!
>
> Regards,
> SK
>

Re: Removal of unused plugins

[Wei ZHOU]

Hi João,

Thanks for the reply.

I agree that the deprecation/removal of plugins should only happen in major
releases.


Kind regards,
Wei


On Thu, Sep 19, 2024 at 1:56 PM João Jandre  wrote:

> Hello all, Wei
>
> I think that's a great initiative, we should definitely trim the
> codebase of old and unused integration/features. However, I think we
> should not do this in a minor release. We could decide on what plugins
> should be removed and announce/deprecate them in the next release.
> However, the removal of features should only happen in major releases.
>
> I would like to once again bring back the recent discussions on
> versioning:
> https://lists.apache.org/thread/lh45w55c3jmhm7w2w0xgdvlw78pd4p87,
> https://lists.apache.org/thread/4zs8d15ghvvwwro46ry5zjf8fn8x0t88,
> https://lists.apache.org/thread/o6o9h3qp8gqrpq4v7o81tl6vp51tkjhg, and
> https://github.com/apache/cloudstack/discussions/8970. I think we should
> really sit down and discuss the direction that we want to bring the
> project. We should build a consensus on a versioning schema that will
> come with the proper mechanisms of deprecating/removing features, as
> well as introducing breaking changes.
>
> Looking at those discussions and Daniel's topics of discussions (see
>
> https://github.com/apache/cloudstack/discussions/8970#discussioncomment-9754199)
>
> here would be my new proposal:
>
> 1. **Looking at our history, what would be the ideal cadence of major
> releases for our context and why?** On average, we take 9 months to
> release a new minor version. Considering that our 'minor' versions are
> where our major changes happen, we could take this cadence of minor
> versions and transfer it into major ones. Furthermore, as we will have
> mechanisms to introduce breaking changes (and those tend to take time),
> we should add some padding on those 9 months and make it 1 year. We also
> do not need to decide on a specific month to release the version, we
> could have a quarter (Q1/Q2/Q3/Q4) that is when the version is scheduled
> to release. That way, we will have some predictability on when the
> release is out, but also some flexibility.
> 2. **How and when should we define the RM for each major?** For the
> 'how', I like the current system of someone volunteering and the
> community voting on them; I don't see any reason to change this. As for
> the 'when', the week following a new release, we should already have a
> new RM to guide the next one. This way, we avoid having an aimless
> project for too long.
> 3. **How should we introduce disruptive changes and remove
> compatibility?** For our first major release, I think we should announce
> these changes as soon as the discussions about versioning are over and
> introduce these changes on that release. But for the future, the better
> method would be: on one major release, we announce the disruptive
> changes and deprecate the necessary code; on the next one we introduce
> the changes.
> 4. **What are the community's common goals?** From our discussions, it
> seems like a part of the community wants to keep the project as is and
> not introduce too many breaking changes. However, we also have another
> part of the community that wants to evolve the project and try to make
> it even better. As always with a community we should strive to build a
> consensus on changes, if they should or not happen. We could have an
> annual discussion planned to map what are the next year's goals, as well
> as decide on things that should not change (at least at the time). This
> discussion could be held at the start of a new major release cycle so
> that the RM has a north to follow and steer the community efforts.  I
> think that one common goal that we should try to achieve is the creation
> of an automated release process. We could create a pipeline that does
> most (or all) the release process so that we only have to approve it
> (and tweak it if needed) before releasing.
> 5. **Regarding minor releases, should we flexibilize it more or be more
> rigid?** I think we should concentrate our big and new features on the
> major versions; while tweaks and bug fixes would go on the minor
> releases. This way, we can have more stable minor releases that do not
> introduce too much stuff at a time. Focusing on the major releases for
> new features will allow us to better test them and do better quality
> control.
>
> If there is further interest in continuing the discussion on the release
> process/versioning, please create a new thread so we can discuss it and
> hammer it down.
>
> Best regards,
>
> João Jandre
>
> On 9/18/24 11:19, Wei ZHOU wrote:
> > Thanks Byran.
> >
> > I think we will defin

Re: Removal of unused plugins

[Wei ZHOU]

Thanks Byran.

I think we will definitely keep the following the plugins
- kvm, vmware, xenserver, simulator
- ovs, vxlan, nsx, tungsten, internal-lb

hyperv is not well-maintained, but I prefer to keep it. ovm/ovm3/ucs
support could be dropped.

for the network plugins, I do not have preferences. good to know that Palo
alto is interested.
in ACS 4.21 or 4.22, you might see some more VNF improvements (e.g. a
provider framework and an implementation)


Kind regards,
Wei


On Wed, Sep 18, 2024 at 3:25 PM Bryan Tiang 
wrote:

> Hi Wei Zhou,
>
> We dont use any of the plugins listed, but some do stand out:
>
> # HyperV # We dont use it right now, but would definitely use it if it was
> more mature. Some enterprise-ey applications we use require HyperV (other
> than Vmware) for some reason (Eg. Oneidentity Privilege Access Mgmt
> System), so we maintain a small cluster of HyperV outside of cloudstack.
> But if there's no intention to enhance these, id suggest to remove it. With
> people moving out of Vmware and looking for alternatives, Cloudstack docs
> should show the fairly supported items. Its just better on optics and CS
> adoption.
>
> # Palo Alto # I believe this was built by CloudOps by Aptum in 2014? We
> were researching this extensively cause we wanted to implement some NGFW
> capabilities in our setup, but it seems the project wasn't maintained over
> the years. Im not sure whos using it, but it's sad there wasn't much
> uptake. Probably because Palo Alto is really expensive now. If there was a
> fortinet plugin, we'd be very interested. But right now, we settled on
> using VNF + L2 Networks.
>
> Note: Please dont remove VXLAN plugin... will self destruct.
>
>
>

Re: Removal of unused plugins

[Wei ZHOU]

Hi,

It looks like the formatting is lost.
Below are the plugins in red in my previous email.

- plugins/hypervisors

hyperv
ovm
ovm3
ucs

- plugins/network-elements

bigswitch
cisco-vnmc
elastic-loadbalancer
netscaler
stratosphere-ssp
brocade-vcs
juniper-contrail
nicira-nvp
opendaylight
palo-alto



Kind regards,
Wei

On Wed, Sep 18, 2024 at 11:37 AM Wei ZHOU  wrote:

> Hi all,
>
> There are some plugins in CloudStack which have not been updated for some
> years. I think we should remove some of the plugins in the next releases.
>
> For hypervisors, we have a wiki page to maintain the EOL dates:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Hypervisor+and+Management+Server+OS+EOL+Dates
> (thanks Rohit)
>
> We lack the information of network plugins.
>
> Anyone (or knows someone else) is using the following plugins in red ?
>
> *- plugins/hypervisors*
>
>
>
> * - baremetal- hyperv- kvm- ovm- ovm3- simulator- ucs- vmware- xenserver*
>
> *- plugins/network-elements*
>
>
>- bigswitch
>- cisco-vnmc
>- elastic-loadbalancer
>- internal-loadbalancer
>- netscaler
>- nsx
>- ovs
>- stratosphere-ssp
>- vxlan
>- brocade-vcs
>- dns-notifier
>- globodns
>- juniper-contrail
>- nicira-nvp
>- opendaylight
>- palo-alto
>- tungsten
>
>
>
> Thank you !
>
> Kind regards,
> Wei
>
>
>
>
>
>

Re: New PMC member: Suresh Anaparti

[Wei ZHOU]

Congratulations Suresh !

-Wei

On Wed, Sep 18, 2024 at 12:52 PM Rohit Yadav  wrote:

> The Project Management Committee (PMC) for Apache CloudStack
> has invited Suresh Anaparti to become a PMC member and we are pleased
> to announce that they have accepted.
>
> Suresh has contributed in the past and has shown effort to make the
> project run smoothly. He also has served as the release manager for
> CloudStack releases 4.16.1.0 and 4.19.1.0.
>
> Please join me in congratulating Suresh
>
> Regards,
> Rohit Yadav
>

Removal of unused plugins

[Wei ZHOU]

Hi all,

There are some plugins in CloudStack which have not been updated for some
years. I think we should remove some of the plugins in the next releases.

For hypervisors, we have a wiki page to maintain the EOL dates:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Hypervisor+and+Management+Server+OS+EOL+Dates
(thanks Rohit)

We lack the information of network plugins.

Anyone (or knows someone else) is using the following plugins in red ?

*- plugins/hypervisors*



* - baremetal- hyperv- kvm- ovm- ovm3- simulator- ucs- vmware- xenserver*

*- plugins/network-elements*


   - bigswitch
   - cisco-vnmc
   - elastic-loadbalancer
   - internal-loadbalancer
   - netscaler
   - nsx
   - ovs
   - stratosphere-ssp
   - vxlan
   - brocade-vcs
   - dns-notifier
   - globodns
   - juniper-contrail
   - nicira-nvp
   - opendaylight
   - palo-alto
   - tungsten



Thank you !

Kind regards,
Wei

Re: Preferred storage pool (preferred.storage.pool)

[Wei ZHOU]

Hi,

It depends on the disk offerings.
If the disk offering says it uses local storage, volumes will be created on
the local storage pool. otherwise on the ceph rbd.
`preferred.storage.pool` is useless in your case.

-Wei


On Tue, Sep 17, 2024 at 9:53 AM Sanjay Kumar  wrote:

> Hi Wei,
>
> Thanks for the quick revert.
>
> We have to cluster in our setup, one is rbd and one is local. I want to set
> the uuid of primary storage of local  in preferred.storage.pool from global
> setting then the vm will create in local or rbd pool?
>
>
> Thank you
>
>
>
> On Tue, Sep 17, 2024 at 1:13 PM Wei ZHOU  wrote:
>
> > What's your question ?
> >
> > It is an account-level setting, you can set different values per account
> or
> > domain.
> >
> > -Wei
> >
> > On Tue, Sep 17, 2024 at 9:25 AM Sanjay Kumar 
> > wrote:
> >
> > > Hello!
> > >
> > > Please let us know if we use this option(preferred.storage.pool), then
> > all
> > > VMs will use this pool which uuid we will use with this setting.
> > >
> > >
> > > Any help would be really appreciated. Thank you!
> > >
> > > Regards,
> > > SK
> > >
> >
>

Re: Preferred storage pool (preferred.storage.pool)

[Wei ZHOU]

What's your question ?

It is an account-level setting, you can set different values per account or
domain.

-Wei

On Tue, Sep 17, 2024 at 9:25 AM Sanjay Kumar  wrote:

> Hello!
>
> Please let us know if we use this option(preferred.storage.pool), then all
> VMs will use this pool which uuid we will use with this setting.
>
>
> Any help would be really appreciated. Thank you!
>
> Regards,
> SK
>

Re: Port Forwarding in Network

[Wei ZHOU]

Thanks for sharing. Interesting

How many cpu and memory does you VR have ?


-Wei
On Thursday, August 29, 2024, Bryan Tiang  wrote:

> Hi Alex and Wei Zhou,
>
> Thanks for the input, so it seems this new feature is more beneficial for
> those who are currently using Shared Networks.
>
> We have 50 AutoscaleGroups in a single VR because our company mainly
> distributes/broadcasts stock prices from multiple exchanges to public
> users, so lots of micro services that need to autoscale instantaneously
> when the markets suddenly spike/rally which can result in 1 - 10x traffic
> bursts.
>
> However, most of our Autoscale Groups consists of API Gateways to route
> traffic to different network tiers and micro services. This is what takes
> up lots of Autoscale Groups.
>
> We had to duplicate lots of API Gateway into multiple Autoscale Groups
> because the current feature only allows load balancing to 1 single port.
>
> So this is more of a workaround for us to overcome the current Autoscale
> feature limitation.
>
> I think something worth mentioning is that our Autoscale Group, load
> balances traffic to other Autoscale Groups.
>
> For example:
>
> Internet -> ASG LB (API GW) -> ASG LB (Microservice 1) -> Database
>
> And in some cases, we have this as well:
>
> Internet -> ASG LB (API GW) -> ASG LB (Microservice 1) -> ASG LB
> (Microservice 2)-> Database
>
> I guess makes the VR very busy.
>
> Happy to share more, sounds like our use is bit extreme… but it works so
> far though. Its only the CPU Utilisation that’s concerning… (memory is
> always around 40% so not a bottleneck there)
>
> Regards,
> Bryan
> On 29 Aug 2024 at 11:27 PM +0800, Alex Mattioli <
> alex.matti...@shapeblue.com>, wrote:
> > Hi Bryan,
> >
> > What's your use case for 50 autoscale groups in 1 VR? When designing the
> feature we never envisioned more than 2 or 3.
> >
> > In NAT mode you should be able to get some 3gpbs through the VR, in
> ROUTED mode then some 6-7gbps. Those numbers do go down (considerably
> sometimes) with the number of firewall rules, load balancing, etc... you
> have setup in the network.
> >
> > You'll need to create new networks in ROUTED mode, there's no migration
> path from NATTED mode to ROUTED mode.
> >
> > You definitely can allow all traffic in the firewall and setup firewall
> rules in each individual VM.
> >
> > In this initial implementation there's no load balancer in ROUTED mode,
> so no Autoscale groups. But it is definitely a possible improvement for
> future versions.
> >
> > Cheers
> > Alex
> >
> >
> >
> >
> > -Original Message-
> > From: Bryan Tiang 
> > Sent: Thursday, August 29, 2024 11:11 AM
> > To: us...@cloudstack.apache.org; us...@cloudstack.apache.org
> > Cc: dev@cloudstack.apache.org
> > Subject: RE: Port Forwarding in Network
> >
> > Hey Alex,
> >
> > It’s exiting to hear this new features coming about, and that the VR
> performance will be improved as a result of pure routing.
> >
> > We have a pain point right now where our VR is at 75% CPU when handling
> 200Mbps Internet Traffic. Probably because we have 50 Autoscale Groups
> within that 1 VR… (VR is 4Core,4GB).
> >
> > We have plans support 1Gb-5Gbps Internet Bandwidth within a single VR
> one day, but if it’s already at 75%… kinda worrying for us. So this is
> exciting.
> >
> > I went through the design document and have few questions. Is this going
> to be a new network? Or can existing VPC networks upgrade to Routed Mode?
> >
> > Since every VM will get to have its own Public IP, does it mean every VM
> can have its own firewall rules now?
> >
> > Will this feature be available for Autoscale Groups? We are heavy users
> of it.
> >
> > Regards,
> > Bryan
> > On 29 Aug 2024 at 4:22 AM +0800, Alex Mattioli <
> alex.matti...@shapeblue.com>, wrote:
> > > Hi Marty,
> > >
> > >
> > >
> > > Here's the documentation for Routed Mode and Simple Dynamic Routing, I
> did the original design and my colleague @Wei Zhou<mailto:Wei.Zhou@
> shapeblue.com> refined and implemented it.
> > >
> > > https://cwiki.apache.org/confluence/pages/viewpage.
> action?pageId=306153967
> > >
> > > https://cwiki.apache.org/confluence/pages/viewpage.
> action?pageId=315492858
> > >
> > > Cheers,
> > >
> > > Alex
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > -Original M

Re: Port Forwarding in Network

[Wei ZHOU]

Hi,

See my inline reply

> Is this going to be a new network? Or can existing VPC networks upgrade
to Routed Mode?

You need to create a new network offering, and a new network.

> Since every VM will get to have its own Public IP, does it mean every VM
can have its own firewall rules now?

every VM has an IP which you can access, if routes are configured.
Firewall rules are applied on the network level.

> Will this feature be available for Autoscale Groups? We are heavy users
of it.

at this moment no. In the future if Autoscale is supported for shared
networks, it will work with routed networks as well.


-Wei

On Thu, Aug 29, 2024 at 4:11 PM Bryan Tiang 
wrote:

> Hey Alex,
>
> It’s exiting to hear this new features coming about, and that the VR
> performance will be improved as a result of pure routing.
>
> We have a pain point right now where our VR is at 75% CPU when handling
> 200Mbps Internet Traffic. Probably because we have 50 Autoscale Groups
> within that 1 VR… (VR is 4Core,4GB).
>
> We have plans support 1Gb-5Gbps Internet Bandwidth within a single VR one
> day, but if it’s already at 75%… kinda worrying for us. So this is exciting.
>
> I went through the design document and have few questions. Is this going
> to be a new network? Or can existing VPC networks upgrade to Routed Mode?
>
> Since every VM will get to have its own Public IP, does it mean every VM
> can have its own firewall rules now?
>
> Will this feature be available for Autoscale Groups? We are heavy users of
> it.
>
> Regards,
> Bryan
> On 29 Aug 2024 at 4:22 AM +0800, Alex Mattioli <
> alex.matti...@shapeblue.com>, wrote:
> > Hi Marty,
> >
> >
> >
> > Here's the documentation for Routed Mode and Simple Dynamic Routing, I
> did the original design and my colleague @Wei Zhou wei.z...@shapeblue.com> refined and implemented it.
> >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=306153967
> >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=315492858
> >
> > Cheers,
> >
> > Alex
> >
> >
> >
> >
> >
> >
> >
> > -Original Message-
> > From: Marty Godsey 
> > Sent: Wednesday, August 28, 2024 11:07 AM
> > To: us...@cloudstack.apache.org
> > Subject: Re: Port Forwarding in Network
> >
> >
> >
> > Thank you, Alex. I am excited about that addition. Even having the
> ability to not have to NAT is very useful.
> >
> >
> >
> > Regards,
> >
> > Marty Godsey
> >
> > Rudio, LLC
> >
> >
> >
> > Book Time: https://calendly.com/rudio-martyg
> >
> > Support: supp...@rudio.net<mailto:supp...@rudio.net
> ?subject=Rudio%20Support<mailto:supp...@rudio.net%
> 3cmailto:supp...@rudio.net?subject=Rudio%20Support>>
> >
> > Ph: 859-328-1100
> >
> > The content of this email is intended for the person or entity to which
> it is addressed only. This email may contain confidential information. If
> you are not the person to whom this message is addressed, be aware that any
> use, reproduction, or distribution of this message is strictly prohibited.
> If you received this in error, please contact the sender and immediately
> delete this email and any attachments.
> >
> >
> >
> >
> >
> > From: Alex Mattioli  alex.matti...@shapeblue.com>>
> >
> > Date: Tuesday, August 27, 2024 at 11:56 AM
> >
> > To: us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org> <
> us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org>>
> >
> > Subject: RE: Port Forwarding in Network
> >
> > WARNING: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
> >
> >
> >
> >
> >
> > Hi Marty,
> >
> >
> >
> > There are two PRs in progress, one for Routed Mode for IPv4 in Isolated
> Networks and VPCs and another for Simple Dynamic Route with BGP.
> >
> >
> >
> > With Routed Mode you'll be able to assign public IPs directly to VMs,
> this should be ready for ACS 4.20, which will be routed via the ACS VR.
> >
> > This has been possible for IPv6 since ACS 4.17 and will work in a
> similar way (with some differences) for IPv4. Here's a video explaining how
> it works for IPv6: https://www.youtube.com/watch?v=UvCSmU1TjRY&t=1583s
> >
> >
> >
> > As mentioned before, if you want to skip the VR completely then you need
> to use Shared Networks, 

Re: Integration of console access fails for 4.18.2.1

[Wei ZHOU]

Try this


https://cloudstack.apache.org/api/apidocs-4.18/apis/createConsoleEndpoint.html


On Wednesday, August 14, 2024, Fariborz Navidan 
wrote:

> Hello Everyone,
>
> I am using "getCommandQuery" API passing "cmd=access", "vm" and "apiKey"
> parameters to integrate console access to our own client panel. We have two
> ACS installations, v4.15.0.0 and 4.18.2.1. If I call the API against v4.15
> management server it returns a query string for console access and by
> appending it to the management server URL I'm able to view the VM's console
> in the browser. However, If I run the same command against v4.18 and append
> the returned query string to the management server URL, I just get "failed"
> string displayed in the browser. The query string returned from vf4.18 has
> all the parameters. Below is the example of URL I'm building using the
> returned query string:
>
> http://
> :8080/console?apiKey=w19-cW1y9pPW8epJTCXZznnW0oz4fbifGW
> lTfoy_rrVpfhZLUqz_pQ5rysSm442KPL4jEcBNsWMdlTE4V3
> 2txQ&cmd=access&vm=3257f9bd-ae5f-448d-a052-6eded88f1d44&
> signature=UniJRaHso9nV8TW1%2BTkYXmJDvsY%3D
>
> Any help would be appreciated.
>
> Thanks.
>

Re: [PROPOSAL] Update the 4.20.0.0 release schedule

[Wei ZHOU]

Thanks João.

It looks good to me.


Kind regards,
Wei

On Fri, Jul 26, 2024 at 4:06 PM João Jandre Paraquetti
 wrote:
>
> Hi Abhisar, all,
>
> We have been postponing 4.20.0.0 for some time now, in August we will
> reach the mark of 6 months without a minor release. I would like to not
> stray too far from this 6 month mark. That being said, we can postpone
> the release again. However, unless we have a security issue or something
> of sorts, I will be against postponing it further.
>
> Here's the proposed updated schedule:
>
> - On the second week of September, we freeze the main branch. That means any
> feature must be in by the first week of September. Only accept
> critical/blocker issues until the third week of September.
> - On the third week of September, cut 4.20.0.0 RC1 and further RCs if
> necessary, start/conclude vote, and finish release work.
>
> What are your thoughts?
>
> Best regards,
> João Jandre
>
> On 7/25/24 06:46, Abhisar Sinha wrote:
> > Hi João,
> >
> > Thanks for managing the 4.20.0.0 release.
> >
> > I am working on a PR (File System as a first-class feature in Cloudstack) 
> > which we can consider as a 'must have'.
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Storage+Filesystem+as+a+First+Class+Feature
> > Dev work is almost done, And I'll open the PR for review by the end of this 
> > month.
> >
> > But keeping the review and validation times in mind, it will be tough to 
> > meet the suggested dates.
> > Can we postpone the freeze to early September? I believe that will give us 
> > enough time to get the feature merged with satisfactory quality.
> > Please let me know your thoughts.
> >
> > Thanks,
> > Abhisar
> > 
> > From: João Jandre Paraquetti 
> > Sent: Saturday, May 25, 2024 12:24 AM
> > To: us...@cloudstack.apache.org ; 
> > dev@cloudstack.apache.org 
> > Subject: Re: [PROPOSAL] Update the 4.20.0.0 release schedule
> >
> > Hi Suresh, all
> >
> > I agree that we should release 4.19.1.0 before 4.20.0.0, also, there are
> > some features missing on 4.20.0.0 still that I'd like to get in, so more
> > time wouldn't hurt.
> >
> > That being said, here is the updated schedule I propose:
> >
> > - On the third week of August, we freeze the main branch. That means any
> > feature must be in by the second week of August. Only accept
> > critical/blocker issues until the last week of August.
> > - On the last week of August, cut 4.20.0.0 RC1 and further RCs if
> > necessary, start/conclude vote, and finish release work.
> >
> > What are your thoughts?
> >
> > Also, does anyone have any "must have" Issues/PRs for 4.20.0.0? If so,
> > could you share them via this thread or ping me (@JoaoJandre) on Github?
> >
> > Best Regards,
> > João Jandre.
> >
> > On 5/23/24 13:39, Suresh Anaparti wrote:
> >> Hi João Jandre,
> >>
> >> I think, it's better to do 4.19.1.0 before 4.20.0.0, and schedule 4.20.0.0 
> >> release a month or two after 4.19.1.0 release. Considering the 4.19.1.0 
> >> timelines proposed [1], you can target 4.20.0.0 in Q3, around Aug end (or 
> >> early Sept). Please let me know your thoughts.
> >>
> >> [1] https://lists.apache.org/thread/fo8s9qzh625c4fk8rgzjhpdn9kfgoqsp
> >>
> >>
> >> Regards,
> >> Suresh
> >>
> >> From: João Jandre 
> >> Date: Monday, 6 May 2024 at 7:37 PM
> >> To: dev@cloudstack.apache.org , 
> >> us...@cloudstack.apache.org 
> >> Subject: [PROPOSAL] Update the 4.20.0.0 release schedule
> >> Hi all,
> >>
> >> Regarding the original 4.20.0.0 release schedule proposed here:
> >> https://lists.apache.org/thread/nyoddmwydz2t59hsfs7gf0vozlf7n434, I
> >> would like to propose an update to it.
> >>
> >> Considering that:
> >> 1. The community expended a lot of time working to fix the CVEs that
> >> were recently found;
> >> 2. The community is busy with 4.19.1.0;
> >> 3. The original schedule would put the COCEU 2024 and the RC1 on the
> >> same week;
> >>
> >> I think we should postpone the 4.20.0.0 release for at least a month.
> >> That being said, here is the updated schedule I propose:
> >>
> >> - On the first week of July, we freeze the main branch. That means any
> >> feature must be in by the last week of June. Only accept
> >> critical/blocker issues until the second week of July.
> >> - On the second week of July, cut 4.20.0.0 RC1 and further RCs if
> >> necessary, start/conclude vote, and finish release work.
> >>
> >> What are your thoughts?
> >>
> >> Best Regards,
> >> João Jandre
> >>
> >>
> >>
> >>
> >
> >
> >

Re: stored procedures and versions (Was: [VOTE] Apache CloudStack 4.19.1.0 (RC1))

[Wei ZHOU]

+1

procedures can be created before db upgrades

-Wei

On Fri, Jul 12, 2024 at 1:40 PM Daan Hoogland  wrote:
>
> This is a bit off topic, so renaming the thread. Can we instate a
> similar procedure as for views for stored procedures?
>
> it seems to me we can de exactly the same for those stored procedures
> and maybe even hijack the views dir so no issues occur with those in
> the future. It would guarantee these are recreated on every update and
> also always have the latest version as needed.
>
> On Fri, Jul 12, 2024 at 11:37 AM Suresh Kumar Anaparti
>  wrote:
> ...
> > > 
> > > From: Nux 
> > > Sent: Friday, July 12, 2024 02:44
> > > To: dev@cloudstack.apache.org 
> > > Cc: users 
> > > Subject: Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
> > >
> > > Rohit,
> > >
> > > That's a very good point about the routines, thanks for sharing how to
> > > restore them.
> ...
> > > On 2024-07-11 12:52, Rohit Yadav wrote:
> ...
> > > >  *
> > > > I hit an issue with idempotent routines missing on cloud_usage db
> > > > (borrowed them from mbx env with: mysqldump --no-create-db
> > > > --no-create-info --no-data --routines cloud_usage >
> > > > cloud_usage-routines.sql ; and applied this in my homelab env; likely
> > > > my fault while moving DB servers and forgot the -R option where I
> > > > forgot to backup the routines)
>
> --
> Daan

Re: [VOTE] Apache CloudStack Kubernetes Provider 1.1.0 RC1

[Wei ZHOU]

+1 (binding)

Verified via the following steps

1. create a CKS cluster with k8s 1.30.0 and weavenet 2.8.1

2. delete cloudstack-kubernetes-provider 1.0.0
kubectl delete -f
https://raw.githubusercontent.com/apache/cloudstack-kubernetes-provider/main/deployment.yaml

3.  install 1.1.0-rc1
kubectl apply -f
https://github.com/apache/cloudstack-kubernetes-provider/releases/download/v1.1.0-rc1/deployment.yaml

4. create nginx pod and service with type=LoadBalancer.
Public IP is acquired, LB rules are added

5. delete the nginx service.
Public IP is released


Thanks Vishesh, great job !


-Wei

On Wed, Jun 19, 2024 at 8:13 AM Vishesh Jindal
 wrote:
>
> Hi All,
>
> I made a mistake and didn't create the release on dist.apache.org. Please 
> discard my previous email.
>
> I've created a new CloudStack Kubernetes Provider 1.1.0 release (RC1), with 
> the following artifacts up for a vote:
>
> Git Branch and Commit SHA:
> https://github.com/apache/cloudstack-kubernetes-provider/tree/59c3e7b21c39eefb2306bb8504bcef901a9d
> Commit: 59c3e7b21c39eefb2306bb8504bcef901a9d
>
> Source release (checksums and signatures are available at the same location):
> https://dist.apache.org/repos/dist/dev/cloudstack/kubernetes-provider-1.1.0/
>
> PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> For users convenience:
> * docker hub - 
> https://hub.docker.com/r/apache/cloudstack-kubernetes-provider/tags
>
> * Kubernetes manifest for the rc release: 
> https://github.com/apache/cloudstack-kubernetes-provider/releases/download/v1.1.0-rc1/deployment.yaml
>
> Vote will be open for 120 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
> Vishesh
>
> 
>
>
>
> From: Vishesh Jindal
> Sent: Tuesday, June 18, 2024 6:36 PM
> To: us...@cloudstack.apache.org ; 
> dev@cloudstack.apache.org 
> Subject: [VOTE] Apache CloudStack Kubernetes Provider 1.1.0 RC1
>
> Hi All,
>
> I've created a 1.1.0 release (RC1) for Apache CloudStack Kubernetes Provider, 
> with the following artifacts up for
> a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack-kubernetes-provider/tree/v1.1.0-rc1
>
> Commit: 774a144876d2c875c61becab00e0487692130302
>
> Deployment manifest:
> https://github.com/apache/cloudstack-kubernetes-provider/releases/download/v1.1.0-rc1/deployment.yaml
>
> Docker image:
> apache/cloudstack-kubernetes-provider:v1.1.0-rc1
>
> Docker image manifest digest:
> sha256:38dc0a4413657b9c88cdcb28ef330e49aee6fb972a4cbc4055a0608b9f8bf7b8
>
> You can check the changelog for the release 
> here:https://github.com/apache/cloudstack-kubernetes-provider/releases/tag/v1.1.0-rc1
>
> Vote will be open for 120 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
> Vishesh

Re: Endpoint response is different than the docs

[Wei ZHOU]

Hi,

you can run "mvn -P developer,systemvm clean install -pl tools/apidoc/"
the api doc can be found at tools/apidoc/target/xmldoc/apis/

The api parameters and responses come from the java classes.

-Wei

On Fri, Jun 14, 2024 at 4:11 PM Ahmed Awlaqi
 wrote:
>
> Thanks, is there a docs on how to use this script? I see some variables I
> need to pass but not sure what they are.
>
> On Thu, 13 Jun 2024 at 16:03, Pearl d'Silva 
> wrote:
>
> > The build-apidoc.sh script:
> > https://github.com/apache/cloudstack/blob/main/tools/apidoc/build-apidoc.sh
> > is responsible for generating the API docs.
> >
> > Regards.
> >
> >
> >
> > 
> > From: Ahmed Awlaqi 
> > Sent: June 13, 2024 9:39 AM
> > To: dev@cloudstack.apache.org 
> > Subject: Re: Endpoint response is different than the docs
> >
> > Hi,
> >
> > I will try to submit a PR for it but do you where I can find the code that
> > generates the API docs to test it.
> >
> > On Thu, Jun 13, 2024 at 2:40 PM Pearl d'Silva 
> > wrote:
> >
> > > Hi,
> > >
> > > There does seem to be a difference in the API command definition and the
> > > actual response generated. You may either raise an issue at
> > > https://github.com/apache/cloudstack/issues or could also contribute
> > > towards a fix. The issue seems to be at:
> > >
> > >
> > >
> > https://github.com/apache/cloudstack/blob/main/api/src/main/java/org/apache/cloudstack/api/command/admin/storage/heuristics/RemoveSecondaryStorageSelectorCmd.java#L30
> > > vs
> > >
> > >
> > https://github.com/apache/cloudstack/blob/main/api/src/main/java/org/apache/cloudstack/api/command/admin/storage/heuristics/RemoveSecondaryStorageSelectorCmd.java#L43
> > >
> > >
> > > Thanks,
> > > Pearl
> > >
> > >
> > >
> > >
> > > 
> > > From: Ahmed Awlaqi 
> > > Sent: June 13, 2024 8:04 AM
> > > To: dev@cloudstack.apache.org 
> > > Subject: Endpoint response is different than the docs
> > >
> > > Hi,
> > >
> > > I faced a problem where the endpoint response is different from what is
> > > written in the docs the endpoint is `removeSecondaryStorageSelector` in
> > > here
> > >
> > >
> > https://cloudstack.apache.org/api/apidocs-4.19/apis/removeSecondaryStorageSelector.html
> > > we see the response tags but actually non of them are actually returned
> > and
> > > I get `{"success":true}`.
> > >
> > > --
> > >  
> > >
> > > --
> > > The information in this message is confidential, and only intended for
> > the
> > > addressee(s). If you are not the person to whom this message is
> > addressed,
> > > you are hereby notified that any disclosure, reproduction, distribution
> > or
> > > use of this message is strictly prohibited. If you received this in
> > error,
> > > please inform the sender and delete the message without copying or
> > opening
> > > it.
> > >
> >
> > --
> >  
> >
> > --
> > The information in this message is confidential, and only intended for the
> > addressee(s). If you are not the person to whom this message is addressed,
> > you are hereby notified that any disclosure, reproduction, distribution or
> > use of this message is strictly prohibited. If you received this in error,
> > please inform the sender and delete the message without copying or opening
> > it.
> >
>
> --
>  
>
> --
> The information in this message is confidential, and only intended for the
> addressee(s). If you are not the person to whom this message is addressed,
> you are hereby notified that any disclosure, reproduction, distribution or
> use of this message is strictly prohibited. If you received this in error,
> please inform the sender and delete the message without copying or opening
> it.

Re: Api docs

[Wei ZHOU]

Hi,

You can find the code at https://github.com/apache/cloudstack-www


-Wei

On Tue, Jun 11, 2024 at 2:29 PM Ahmed Awlaqi
 wrote:
>
> Hi, I wanna know where can I find the code for this website
> https://cloudstack.apache.org/api/ I found a mistake and would like to fix
> it.
>
> --
>  
>
> --
> The information in this message is confidential, and only intended for the
> addressee(s). If you are not the person to whom this message is addressed,
> you are hereby notified that any disclosure, reproduction, distribution or
> use of this message is strictly prohibited. If you received this in error,
> please inform the sender and delete the message without copying or opening
> it.

Re: [PROPOSE] RM for cloudstack-kubernetes-provider v1.1.0

[Wei ZHOU]

Thanks Vishesh for the volunteering.
There was no cloudstack-kubernetes-provider release in the past 3
years, glad to see there are some new commits in the last weeks. Great
job !

no specific PRs/issues are needed for me.
looking forward to the new release


-Wei


On Tue, Jun 11, 2024 at 11:26 AM Vishesh Jindal
 wrote:
>
> Hi all,
>
> Cloudstack kuberentes provider is due for a release since the last release 
> was in 2021. I would like to propose myself as a Release Manager for the 
> v1.1.0 release.
>
> You can check the PRs merged since the last release here: 
> https://github.com/apache/cloudstack-kubernetes-provider/compare/v1.0.0...main
>
> Let me know if there is any specific issue/PR which needs to be addressed. If 
> there are no additional changes, I will cut an RC next week.
>
> Thanks!
> Vishesh
>
>
>

Re: Help setting up Cloud Stack development environment

[Wei ZHOU]

Hi Gaurav,

Welcome to the community.

I suggest you create a docker container (for instance, rocky8/9 or
ubuntu 22.04). The doc is out-of-date.

-Wei

On Thu, Jun 6, 2024 at 12:43 PM gaurav joshi  wrote:
>
> Hi,
>
> I have been trying to set up my cloudstack dev environment in Windows but I 
> am facing some issues. It will be helpful if I can get some guidance as I am 
> new to this environment and cloud on whole.
> I followed the steps as mentioned in this link :
> Setting up a CloudStack dev environment on Windows - Apache Cloudstack - 
> Apache Software Foundation
>
> I installed cygwin and followed all the steps as mentioned . On executing 
> step 13
> And running command :
> mvn -Pdeveloper,systemvm clean install -DskipTests
>
> I receive the following error
> "Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec"
>
> I have attached the screenshot of the error for your reference.
>
> I am using OS - Windows 11 Pro
> I am running this code after taking the
> git clone https://github.com/apache/cloudstack.git
> git checkout 4.19
>
> Also I would like to ask if there is an updated version of this document.
>
> I would be really grateful for any help on this topic.
>
> Thanks and Regards,
> Gaurav Joshi
>

Re: [Proposal] Storage Filesystem as a First Class Feature

[Wei ZHOU]

> @Wei Zhou If the network into which the StorageVM runs IPv6 (as per your 
> implementation of IPv6) it should automatically get an IPv6 IP, correct?

yes,it should get Ipv6 addr advertised by cloudstack VR. @Alexblue.com
we need to make sure IPv6 is enabled in the storagefs vm (Ipv6 is
disabled by default in systemvm template as far as I know), and proper
firewall rules are applied.

> @Wido den Hollander @Wei ZhouHow much effort do you guys thing it would it 
> take to add support to VirtioFS?  I'm not super aware of it, what would the 
> benefits be? (I've quickly looked at Wido's links, but I rather get info from 
> you guys directly).
I see the benefits . However I do not know a strong use case of it.
maybe @wido can advise ?

On Thu, Jun 6, 2024 at 11:01 AM Alex Mattioli
 wrote:
>
>
> @Wei Zhou If the network into which the StorageVM runs IPv6 (as per your 
> implementation of IPv6) it should automatically get an IPv6 IP, correct?
>
> @Wido den Hollander @Wei ZhouHow much effort do you guys thing it would it 
> take to add support to VirtioFS?  I'm not super aware of it, what would the 
> benefits be? (I've quickly looked at Wido's links, but I rather get info from 
> you guys directly).
>
> Cheers
> Alex
>
>
>
>
> -Original Message-
> From: Wei ZHOU 
> Sent: Thursday, June 6, 2024 10:50 AM
> To: dev@cloudstack.apache.org
> Cc: Abhisar Sinha 
> Subject: Re: [Proposal] Storage Filesystem as a First Class Feature
>
> Hi Wido,
>
> Thanks for your feedback.
>
> It is a great idea to support virtio-fs. We could add VIRTIOFS as a valid 
> value of enum ExportProtocol, and implement it in a separate plugin in the 
> future.
> Have you tested virtio-fs before ? Could you share more info if possible?
> - is it supported by libvirt-java ?
> - does it support hot plug or hot unplug ?
>
> I agree with you that we should consider IPv6 (ip and firewall rules) in 
> storagefs vm.
> cc abhisar.si...@shapeblue.com
>
>
> Kind regards,
> Wei
>
> On Thu, Jun 6, 2024 at 6:43 AM Wido den Hollander  
> wrote:
> >
> >
> >
> > Op 04/06/2024 om 06:04 schreef Abhisar Sinha:
> > > Hi,
> > >
> > > I would like to propose supporting storage filesystem as a first-class 
> > > feature in Cloudstack.
> > > The File Share can be associated with one or more guest networks or vpc 
> > > tiers and can be used by any VM on the network in a shared manner. It is 
> > > designed to be resizable and highly available. This feature can later be 
> > > used as integration endpoints with the CSI driver, go-sdk, Terraform, 
> > > Ansible and others.
> > >
> > > The draft functional spec is here :
> > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Storage+Files
> > > ystem+as+a+First+Class+Feature
> > >
> > > Looking forward to your comments and suggestions.
> > >
> >
> > I think this is great! Especially the Storage VM. Few things to keep
> > in
> > mind:
> >
> > - Have we thought about passthrough of FileSystems coming from the HV
> > and being passed through to the VM [0]
> > - The StorageFsVm, can we make sure it supports IPv6 from the start,
> > best would be if it. Make sure all the code at least supports this for
> > ACLs and such. The VM itself should obtain an IPv6 address when
> > possible and open the proper ports in it's firewall
> >
> > Wido
> >
> > [0]:
> > - https://virtio-fs.gitlab.io/
> > - https://chrisirwin.ca/posts/sharing-host-files-with-kvm/
> >
> >
> > > Thanks,
> > > Abhisar
> > >
> > >
> > >
> > >

Re: [Proposal] Storage Filesystem as a First Class Feature

[Wei ZHOU]

Hi Wido,

Thanks for your feedback.

It is a great idea to support virtio-fs. We could add VIRTIOFS as a
valid value of enum ExportProtocol, and implement it in a separate
plugin in the future.
Have you tested virtio-fs before ? Could you share more info if possible?
- is it supported by libvirt-java ?
- does it support hot plug or hot unplug ?

I agree with you that we should consider IPv6 (ip and firewall rules)
in storagefs vm.
cc abhisar.si...@shapeblue.com


Kind regards,
Wei

On Thu, Jun 6, 2024 at 6:43 AM Wido den Hollander
 wrote:
>
>
>
> Op 04/06/2024 om 06:04 schreef Abhisar Sinha:
> > Hi,
> >
> > I would like to propose supporting storage filesystem as a first-class 
> > feature in Cloudstack.
> > The File Share can be associated with one or more guest networks or vpc 
> > tiers and can be used by any VM on the network in a shared manner. It is 
> > designed to be resizable and highly available. This feature can later be 
> > used as integration endpoints with the CSI driver, go-sdk, Terraform, 
> > Ansible and others.
> >
> > The draft functional spec is here : 
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Storage+Filesystem+as+a+First+Class+Feature
> >
> > Looking forward to your comments and suggestions.
> >
>
> I think this is great! Especially the Storage VM. Few things to keep in
> mind:
>
> - Have we thought about passthrough of FileSystems coming from the HV
> and being passed through to the VM [0]
> - The StorageFsVm, can we make sure it supports IPv6 from the start,
> best would be if it. Make sure all the code at least supports this for
> ACLs and such. The VM itself should obtain an IPv6 address when possible
> and open the proper ports in it's firewall
>
> Wido
>
> [0]:
> - https://virtio-fs.gitlab.io/
> - https://chrisirwin.ca/posts/sharing-host-files-with-kvm/
>
>
> > Thanks,
> > Abhisar
> >
> >
> >
> >

Re: ACS 4.16 - Change SystemVM template for CKS

[Wei ZHOU]

See inline

On Tuesday, April 16, 2024, benoit lair  wrote:

> Ok and so there's no interaction with CS for firewalling and public ips
> access par example ?


CAPC automatically adds some lb rules and firewall rules for the k8s
apiserver.
To support k8s services with Type=LoadBalancer, you can deploy
https://github.com/apache/cloudstack-kubernetes-provider


getting it in a vpc tier for internal dmz use ?


No. vpc is not supported.
Refer to
https://github.com/kubernetes-sigs/cluster-api-provider-cloudstack/issues/314



> Le mar. 16 avr. 2024 à 11:12, Wei ZHOU  a écrit :
>
> > Hi benoit,
> >
> > You can try CAPC, it should work with 4.16
> > https://github.com/kubernetes-sigs/cluster-api-provider-cloudstack
> >
> > You need a local kind cluster to manage the CAPC clusters. They are
> > not managed by CloudStack.
> >
> >
> > -Wei
> >
> > On Fri, Apr 12, 2024 at 2:43 PM benoit lair 
> wrote:
> > >
> > > Hi Wei,
> > >
> > > upgrading from 4.16 to 4.19 will be a huge work for me
> > > I have to test vpc/shared network, vrrp vpc with public lb Netscaler
> and
> > > withou it on several VPCs, i added support for VPX 12 and VPX 13 on it
> > with
> > > a nginx middleware rewriting rules from CS
> > > I am on xcp-ng 8.2.1
> > > i kept during years with a CS 4.3, restarting from 4.16, i would like
> > this
> > > time to keep LTS in production
> > > Is there a specific upgrade path to respect ? a specific process to
> > observe
> > > ? what rollback mechanism is possible ?
> > >
> > > For my K8S needs, I would like to upgrade it, but it was looking first
> > for
> > > a preproduction K8s working on 1.28 in order integrating CI/CD
> pipelines
> > > So this would not too be a problem upgrading CS after installing a k8s
> > > cluster for CI/CD
> > >
> > > Rohit was talking about CAPC, i can use it independently of the version
> > of
> > > ACS i use ?
> > >
> >
>

Re: ACS 4.16 - Change SystemVM template for CKS

[Wei ZHOU]

Hi benoit,

You can try CAPC, it should work with 4.16
https://github.com/kubernetes-sigs/cluster-api-provider-cloudstack

You need a local kind cluster to manage the CAPC clusters. They are
not managed by CloudStack.


-Wei

On Fri, Apr 12, 2024 at 2:43 PM benoit lair  wrote:
>
> Hi Wei,
>
> upgrading from 4.16 to 4.19 will be a huge work for me
> I have to test vpc/shared network, vrrp vpc with public lb Netscaler and
> withou it on several VPCs, i added support for VPX 12 and VPX 13 on it with
> a nginx middleware rewriting rules from CS
> I am on xcp-ng 8.2.1
> i kept during years with a CS 4.3, restarting from 4.16, i would like this
> time to keep LTS in production
> Is there a specific upgrade path to respect ? a specific process to observe
> ? what rollback mechanism is possible ?
>
> For my K8S needs, I would like to upgrade it, but it was looking first for
> a preproduction K8s working on 1.28 in order integrating CI/CD pipelines
> So this would not too be a problem upgrading CS after installing a k8s
> cluster for CI/CD
>
> Rohit was talking about CAPC, i can use it independently of the version of
> ACS i use ?
>

Re: ACS 4.16 - Change SystemVM template for CKS

[Wei ZHOU]

28MB/9.28MB
> > 175a472c5f77: Loading layer
> > [==>] 299B/299B
> > a8764e32e9fe: Loading layer
> > [==>] 613B/613B
> > Loaded image: weaveworks/weave-npc:2.8.1
> > net.bridge.bridge-nf-call-iptables = 1
> > [init] Using Kubernetes version: v1.28.4
> > [preflight] Running pre-flight checks
> > error execution phase preflight: [preflight] Some fatal errors occurred:
> > [ERROR CRI]: container runtime is not running: output:
> > time="2024-04-11T15:33:26Z" level=fatal msg="validate service connection:
> > validate CRI v1 runtime API for endpoint
> > \"unix:///var/run/containerd/containerd.sock\": rpc error: code =
> > Unimplemented desc = unknown service runtime.v1.RuntimeService"
> > , error: exit status 1
> > [preflight] If you know what you are doing, you can make a check non-fatal
> > with `--ignore-preflight-errors=...`
> > To see the stack trace of this error execute with --v=5 or higher
> > [init] Using Kubernetes version: v1.28.4
> > [preflight] Running pre-flight checks
> > error execution phase preflight: [preflight] Some fatal errors occurred:
> > [ERROR CRI]: container runtime is not running: output:
> > time="2024-04-11T15:33:26Z" level=fatal msg="validate service connection:
> > validate CRI v1 runtime API for endpoint
> > \"unix:///var/run/containerd/containerd.sock\": rpc error: code =
> > Unimplemented desc = unknown service runtime.v1.RuntimeService"
> > , error: exit status 1
> > [preflight] If you know what you are doing, you can make a check non-fatal
> > with `--ignore-preflight-errors=...`
> > To see the stack trace of this error execute with --v=5 or higher
> > [init] Using Kubernetes version: v1.28.4
> > [preflight] Running pre-flight checks
> > error execution phase preflight: [preflight] Some fatal errors occurred:
> > [ERROR CRI]: container runtime is not running: output:
> > time="2024-04-11T15:33:27Z" level=fatal msg="validate service connection:
> > validate CRI v1 runtime API for endpoint
> > \"unix:///var/run/containerd/containerd.sock\": rpc error: code =
> > Unimplemented desc = unknown service runtime.v1.RuntimeService"
> > , error: exit status 1
> > [preflight] If you know what you are doing, you can make a check non-fatal
> > with `--ignore-preflight-errors=...`
> > To see the stack trace of this error execute with --v=5 or higher
> > Error: kubeadm init failed!
> >
> >
> >
> >
> >
> > Le jeu. 11 avr. 2024 à 17:19, Wei ZHOU  a écrit :
> >
> >> Hi,
> >>
> >> Please refer to
> >> https://github.com/apache/cloudstack/issues/8681#issuecomment-1999083241
> >>
> >> The containerd in 4.16/4.17 sysyemvm template is too old.
> >>
> >> -Wei
> >>
> >>
> >> On Thursday, April 11, 2024, benoit lair  wrote:
> >>
> >> > Hi Rohit,
> >> >
> >> > I already tested with different iso from cloudstack from CKS repos,
> >> > It is ok with ACS 4.16 with community iso 1.23.3 but it fails from
> >> 1.24.0
> >> > and following others versions
> >> >
> >> > I tried to do an upgrade from 1.23.3 with 1.24.0, it fails,
> >> > I tried to bootstrap a k8s cluster with 1.24.0, also with 1.25 or 1.27.3
> >> > and 1.28.4
> >> >
> >> > Last try, i tested k8s community iso 1.25.0
> >> > in CS UI it saying   "Create Kubernetes Cluster k8s-cks-cl16 in
> >> progress"
> >> > and it fails
> >> > If i try to ssh on control node with VR_Pub_IP port 
> >> > i have nothing in execution
> >> >
> >> > If i try manual install :
> >> > core@k8s-cks-cl16-control-18eccd0c12c:~$ sudo
> >> /opt/bin/setup-kube-system
> >> > mount: /mnt/k8sdisk: /dev/sr0 already mounted on /mnt/k8sdisk.
> >> > Installing binaries from /mnt/k8sdisk/
> >> > 5b1fa8e3e100: Loading layer
> >> > [==>]  803.8kB/803.8kB
> >> > 39c831b1aa26: Loading layer
> >> > [==>]  26.25MB/26.25MB
> >> > Loaded image: apache/cloudstack-kubernetes-autoscaler:latest
> >> > 417cb9b79ade: Loading layer
> >> > [==>]  657.7kB/657.7kB
> &

Re: ACS 4.16 - Change SystemVM template for CKS

[Wei ZHOU]

Hi,

Please refer to
https://github.com/apache/cloudstack/issues/8681#issuecomment-1999083241

The containerd in 4.16/4.17 sysyemvm template is too old.

-Wei


On Thursday, April 11, 2024, benoit lair  wrote:

> Hi Rohit,
>
> I already tested with different iso from cloudstack from CKS repos,
> It is ok with ACS 4.16 with community iso 1.23.3 but it fails from 1.24.0
> and following others versions
>
> I tried to do an upgrade from 1.23.3 with 1.24.0, it fails,
> I tried to bootstrap a k8s cluster with 1.24.0, also with 1.25 or 1.27.3
> and 1.28.4
>
> Last try, i tested k8s community iso 1.25.0
> in CS UI it saying   "Create Kubernetes Cluster k8s-cks-cl16 in progress"
> and it fails
> If i try to ssh on control node with VR_Pub_IP port 
> i have nothing in execution
>
> If i try manual install :
> core@k8s-cks-cl16-control-18eccd0c12c:~$ sudo /opt/bin/setup-kube-system
> mount: /mnt/k8sdisk: /dev/sr0 already mounted on /mnt/k8sdisk.
> Installing binaries from /mnt/k8sdisk/
> 5b1fa8e3e100: Loading layer
> [==>]  803.8kB/803.8kB
> 39c831b1aa26: Loading layer
> [==>]  26.25MB/26.25MB
> Loaded image: apache/cloudstack-kubernetes-autoscaler:latest
> 417cb9b79ade: Loading layer
> [==>]  657.7kB/657.7kB
> 8d323b160d65: Loading layer
> [==>]  24.95MB/24.95MB
> Loaded image: apache/cloudstack-kubernetes-provider:v1.0.0
> 256bc5c338a6: Loading layer
> [==>]  122.2kB/122.2kB
> df1818f16337: Loading layer
> [==>]  14.71MB/14.71MB
> Loaded image: registry.k8s.io/coredns/coredns:v1.9.3
> bd8a70623766: Loading layer
> [==>]  75.78MB/75.78MB
> c88361932af5: Loading layer
> [==>] 508B/508B
> Loaded image: kubernetesui/dashboard:v2.7.0
> 0b031aac6569: Loading layer
> [==>]804kB/804kB
> cc0597072b83: Loading layer
> [==>]  1.076MB/1.076MB
> 5a8045f731fc: Loading layer
> [==>]  90.58MB/90.58MB
> f5a5ef1a005f: Loading layer
> [==>]  1.188MB/1.188MB
> 5cf3bfe5417d: Loading layer
> [==>]  8.506MB/8.506MB
> Loaded image: registry.k8s.io/etcd:3.5.4-0
> 8d7366c22fd8: Loading layer
> [==>]  804.1kB/804.1kB
> 7d5f5bba7c45: Loading layer
> [==>]  694.9kB/694.9kB
> 8154c9483a6c: Loading layer
> [==>]  32.72MB/32.72MB
> Loaded image: registry.k8s.io/kube-apiserver:v1.25.0
> c5f1a47b47bc: Loading layer
> [==>]  29.76MB/29.76MB
> Loaded image: registry.k8s.io/kube-controller-manager:v1.25.0
> e4d19dd12df2: Loading layer
> [==>]  7.631MB/7.631MB
> ba3637ccd78a: Loading layer
> [==>]  12.63MB/12.63MB
> Loaded image: registry.k8s.io/kube-proxy:v1.25.0
> 026969d859f7: Loading layer
> [==>]  14.29MB/14.29MB
> Loaded image: registry.k8s.io/kube-scheduler:v1.25.0
> d01384fea991: Loading layer
> [==>]  19.74MB/19.74MB
> bcec7eb9e567: Loading layer
> [==>] 530B/530B
> Loaded image: kubernetesui/metrics-scraper:v1.0.8
> 961e93cda9dd: Loading layer
> [==>]307kB/307kB
> Loaded image: registry.k8s.io/pause:3.8
> 1b3ee35aacca: Loading layer
> [==>]  2.796MB/2.796MB
> 17d89e2a5199: Loading layer
> [==>]  7.425MB/7.425MB
> 148b94859892: Loading layer
> [==>]8.1MB/8.1MB
> dbea472c1ced: Loading layer
> [==>]  4.376MB/4.376MB
> e81f1a367c17: Loading layer
> [==>] 131B/131B
> 351848f6b295: Loading layer
> [==>]  8.216MB/8.216MB
> Loaded image: weaveworks/weave-kube:latest
> b20f7ff12b24: Loading layer
> [==>]  727.9kB/727.9kB
> 1d49e386162e: Loading layer
> [==>]  9.281MB/9.281MB
> 20145eeac146: Loading layer
> [==>] 297B/297B
> d4cc72748587: Loading layer
> [==>] 600

Re: New Committer: Kiran Chavala

[Wei ZHOU]

Congratulations Kiran !

On Tue, Apr 9, 2024 at 7:46 AM Rohit Yadav  wrote:
>
> The Project Management Committee (PMC) for Apache CloudStack
> has invited Kiran Chavala (kiranchavala) to become a committer and
> we are pleased to announce that they have accepted.
>
> Kiran has been a long time CloudStack contributor and has created
> over a hundred issues on Github. Being a committer enables easier
> contribution to the project and enable better productivity.
>
> Please join me in congratulating Kiran!
>
> Regards.

Re: [VOTE] Release Apache CloudStack CloudMonkey 6.4.0 - RC1

[Wei ZHOU]

+1 (binding)

Tested zone creation, vm and volume , CKS life cycles.

-Wei

On Thu, Mar 21, 2024 at 11:39 AM Rohit Yadav  wrote:
>
> Hi All,
>
> I've created a v6.4.0 release of CloudMonkey, with the following
> artifacts up for a vote:
>
> Git Branch and commit SHA:
> https://github.com/apache/cloudstack-cloudmonkey/commit/df65df7cfe331c5af5d39743717e3d58df921a48
>
> Commit:
> df65df7cfe331c5af5d39743717e3d58df921a48
>
> GitHub pre-release (contains changelog,
> artifacts/binaries to test, checksums/usage details):
> https://github.com/apache/cloudstack-cloudmonkey/releases/tag/6.4.0
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/cloudmonkey-6.4.0/
>
> PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884)
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> The vote will be open until 27th March, 2024.
>
> 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 the reason why)
>
> Convenience binaries are available from here:
> https://github.com/apache/cloudstack-cloudmonkey/releases/tag/6.4.0
>
> Regards.

Re: [PROPOSE] ACS 4.18.2.0

[Wei ZHOU]

Hi João,

Unfortunately yes, there are SOME other security issues. The PMC is
working on the fixes.

I suggest we postpone the 4.18.2.0 release, otherwise we most likely
will have a 4.18.2.1 release.


-Wei

On Tue, Mar 12, 2024 at 1:21 PM João Jandre Paraquetti
 wrote:
>
> Hi Wei,
>
> Are you referring to #8729? If so, it was marked as critical (a few
> minutes ago); therefore, as I announced yesterday: "From now onward, we
> will only accept critical/blocker issues or any stabilization fixes" we
> are still accepting fixes for critical/blocker issues, and we will not
> release the RC until #8729 is fixed; same for #8745. Thus, we can keep
> the freeze anyway. Or is there other security issues that I'm missing?
>
> Best regards,
> João Jandre
>
> On 3/12/24 08:45, Wei ZHOU wrote:
> > Hi João,
> >
> > As you might know, we/community are working on some security issues.
> > Please hold on.
> >
> > -Wei
> >
> > On Mon, Mar 11, 2024 at 7:19 PM João Jandre Paraquetti
> >  wrote:
> >> Hi all,
> >>
> >> I would like to announce the code freeze of the 4.18 branch now.
> >>   From now onward, we will only accept critical/blocker issues or any
> >> stabilization fixes. We have 70 open items in the 4.18.2.0 milestone [1]
> >> at the moment. Most of them will be moved to the next milestone.
> >> Currently, there is one critical issue [1]. Which has an open PR to fix
> >> the same. I count on your support on working towards cutting RC1 in the
> >> coming week.
> >>
> >> Regards,
> >> João Jandre
> >>
> >> [1] https://github.com/apache/cloudstack/milestone/29
> >> [2] https://github.com/apache/cloudstack/issues/8745
> >>
> >> On 2/8/24 16:06, João Jandre Paraquetti wrote:
> >>> Hi, Rohit, all
> >>>
> >>> I don't see any critical problems that should be addressed ASAP on the
> >>> 4.18 branch; therefore, there should be no problem with postponing
> >>> 4.18.2 a little bit. We still have several issues targeted at 4.18.2
> >>> that have yet to be addressed, so a couple more weeks before the
> >>> freeze could be good.
> >>>
> >>> Yes, I still want to be the RM for 4.18.2. I triaged all the issues a
> >>> couple of weeks ago and removed/added some issues to the milestone as
> >>> I deemed necessary, but as Rohit said, if anyone has any issues/PRs
> >>> they want in 4.18.2, please ping me so we can discuss/address any
> >>> concerns.
> >>>
> >>> That being said, here's the updated schedule I propose:
> >>>
> >>> - Until the second week of March: accept bug fixes and minor
> >>> improvements;
> >>> - Third week of March: accept only blocker and critical bug fixes,
> >>> aiming to stabilize the branch;
> >>> - End of March: start cutting RCs, vote, and finish release work.
> >>>
> >>> Best regards,
> >>>
> >>> João Jandre
> >>>
> >>> On 2/8/24 03:22, Rohit Yadav wrote:
> >>>> Hi Joao, all,
> >>>>
> >>>> Given we’re only now more available after the major 4.19 release to
> >>>> work on other releases, could we reconsider the timeline and come up
> >>>> with an updated plan.
> >>>>
> >>>> I think we should target early March to give us some space to work on
> >>>> the issues and PRs. Joao - I’m assuming you still want to be RM for
> >>>> the release, have you triaged the current issues and PRs to identify
> >>>> the must haves and good to haves for 4.18.2 ? And anyone else have
> >>>> any must have issues and PRs they want in 4.18?
> >>>>
> >>>> Regards.
> >>>>
> >>>> Regards.
> >>>> 
> >>>> From: João Jandre Paraquetti 
> >>>> Sent: Monday, December 11, 2023 6:18:34 PM
> >>>> To: dev@cloudstack.apache.org 
> >>>> Subject: Re: [PROPOSE] ACS 4.18.2.0
> >>>>
> >>>> I think we can push a week or two earlier on the proposed schedule, it
> >>>> would look something like this:
> >>>>
> >>>>  - From now till the final week of January (1.5 months): accept bug
> >>>> fixes and minor improvements
> >>>>  - First week of February: accept only blocker and critical bug
> >>>>

Re: [PROPOSE] ACS 4.18.2.0

[Wei ZHOU]

Hi João,

As you might know, we/community are working on some security issues.
Please hold on.

-Wei

On Mon, Mar 11, 2024 at 7:19 PM João Jandre Paraquetti
 wrote:
>
> Hi all,
>
> I would like to announce the code freeze of the 4.18 branch now.
>  From now onward, we will only accept critical/blocker issues or any
> stabilization fixes. We have 70 open items in the 4.18.2.0 milestone [1]
> at the moment. Most of them will be moved to the next milestone.
> Currently, there is one critical issue [1]. Which has an open PR to fix
> the same. I count on your support on working towards cutting RC1 in the
> coming week.
>
> Regards,
> João Jandre
>
> [1] https://github.com/apache/cloudstack/milestone/29
> [2] https://github.com/apache/cloudstack/issues/8745
>
> On 2/8/24 16:06, João Jandre Paraquetti wrote:
> > Hi, Rohit, all
> >
> > I don't see any critical problems that should be addressed ASAP on the
> > 4.18 branch; therefore, there should be no problem with postponing
> > 4.18.2 a little bit. We still have several issues targeted at 4.18.2
> > that have yet to be addressed, so a couple more weeks before the
> > freeze could be good.
> >
> > Yes, I still want to be the RM for 4.18.2. I triaged all the issues a
> > couple of weeks ago and removed/added some issues to the milestone as
> > I deemed necessary, but as Rohit said, if anyone has any issues/PRs
> > they want in 4.18.2, please ping me so we can discuss/address any
> > concerns.
> >
> > That being said, here's the updated schedule I propose:
> >
> > - Until the second week of March: accept bug fixes and minor
> > improvements;
> > - Third week of March: accept only blocker and critical bug fixes,
> > aiming to stabilize the branch;
> > - End of March: start cutting RCs, vote, and finish release work.
> >
> > Best regards,
> >
> > João Jandre
> >
> > On 2/8/24 03:22, Rohit Yadav wrote:
> >> Hi Joao, all,
> >>
> >> Given we’re only now more available after the major 4.19 release to
> >> work on other releases, could we reconsider the timeline and come up
> >> with an updated plan.
> >>
> >> I think we should target early March to give us some space to work on
> >> the issues and PRs. Joao - I’m assuming you still want to be RM for
> >> the release, have you triaged the current issues and PRs to identify
> >> the must haves and good to haves for 4.18.2 ? And anyone else have
> >> any must have issues and PRs they want in 4.18?
> >>
> >> Regards.
> >>
> >> Regards.
> >> 
> >> From: João Jandre Paraquetti 
> >> Sent: Monday, December 11, 2023 6:18:34 PM
> >> To: dev@cloudstack.apache.org 
> >> Subject: Re: [PROPOSE] ACS 4.18.2.0
> >>
> >> I think we can push a week or two earlier on the proposed schedule, it
> >> would look something like this:
> >>
> >> - From now till the final week of January (1.5 months): accept bug
> >> fixes and minor improvements
> >> - First week of February: accept only blocker and critical bug
> >> fixes,
> >> aiming to stabilize the branch.
> >> - Second week of February: start cutting RCs, vote and finish
> >> release
> >> work.
> >>
> >> What do you think?
> >>
> >> Best regards,
> >> João Jandre.
> >>
> >> On 12/9/23 17:22, Rohit Yadav wrote:
> >>> +1
> >>>
> >>> Given, 4.18 branch is benefitting from maintenance work already, I
> >>> wouldn't mind if you want to push it earlier to even say end of Jan,
> >>> and target release in Feb 2024.
> >>>
> >>>
> >>> Regards.
> >>>
> >>> 
> >>> From: João Jandre Paraquetti 
> >>> Sent: Friday, December 8, 2023 23:32
> >>> To: dev@cloudstack.apache.org 
> >>> Subject: [PROPOSE] ACS 4.18.2.0
> >>>
> >>> Hi all,
> >>>
> >>> As suggested on the 4.20.0.0 discussion thread (see
> >>> https://lists.apache.org/thread/nyoddmwydz2t59hsfs7gf0vozlf7n434), I'd
> >>> like to propose the release of version 4.18.2.0 with myself as the RM,
> >>> here's a rough timeline:
> >>>
> >>> - From now till the second week of February (2 months): accept bug
> >>> fixes and minor improvements
> >>> - Third week of February: accept only blocker and critical bug
> >>> fixes,
> >>> aiming to stabilize the branch.
> >>> - End of February: start cutting RCs, vote and finish release work.
> >>>
> >>> We currently have 7 open PRs [1] and 51 open issues [2] with
> >>> 4.18.2.0 as
> >>> milestone, I believe the above timeline should give enough time to
> >>> solve
> >>> all concerns. In case anyone wants to include a bug fix or a pull
> >>> request in 4.18.2.0 milestone, please mention me (JoaoJandre) on
> >>> github.
> >>>
> >>> If anyone has any suggestions, please voice them.
> >>>
> >>> [1]:
> >>> https://github.com/apache/cloudstack/pulls?q=is%3Apr+milestone%3A4.18.2.0+is%3Aopen
> >>>
> >>> [2]:
> >>> https://github.com/apache/cloudstack/issues?q=is%3Aopen+is%3Aissue+milestone%3A4.18.2.0
> >>>
> >>>
> >>> Best regards,
> >>> João Jandre
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>

Re: [PROPOSE] upgrade paths for 4.19 and 20

[Wei ZHOU]

agree.

Moreover, we should try to avoid the new upgrade path for 4.xx.2 release.

-Wei


On Friday, March 8, 2024, Rohit Yadav  wrote:

> I think it would be most likely that we work towards releasing 4.19.1
> before 4.20.0. Then, it would be sensible to have 4.19.0 -> 4.19.1 ->
> 4.20.0 upgrade path.
>
>
> Regards.
>
>
>
>
> 
> From: Daan Hoogland 
> Sent: Friday, March 8, 2024 14:50
> To: dev 
> Subject: [PROPOSE] upgrade paths for 4.19 and 20
>
> devs,
> currently we have an upgrade path for 4.19.0.0 to 4.19.1.0 in the 4.19
> branch
> in the main branch we have a 4.19.0.0 to (4.)20.0.0 upgrade path
> merging fails because of this and allowing either or both in main will
> cause main to fail (at least after upgrading)
> If we are sure that 4.19.1 will be release and will be released before
> 20 we can move the main upgrade path to be from 4.19.1 to 20 (never
> mind the 4. or not)
> If we do not release a 4.19.1 (first) we will have to move the path
> back to originate from 4.19.0
>
> Is this a sane strategy for now?
>
> If no-one objects I'll do the forward merge after the weekend.
>
>
> --
> Daan
>

Re: CSEUG - September, Germany

[Wei ZHOU]

Great!

Thanks Swen!

-Wei


On Tuesday, March 5, 2024, Ivet Petrova  wrote:

> Hi all,
>
> Will be Frankfurt. Swen from proIO is really excited to help us organise,
> so we have somebody on place to support, which is really cool.
>
> Best regards,
>
>
>
>
> On 1 Mar 2024, at 11:06, Wido den Hollander  wrote:
>
>
>
> Op 28/02/2024 om 16:29 schreef Ivet Petrova:
> Hi all,
> I would like to propose to organise the CSEUG next meeting on September
> 12th in Germany.
> I already had a few informal conversations with community members in
> Germany, who are willing to help.
> Do you all think the date is OK and we can meet there?
>
> Works for me on 12-09. Just wondering, Germany is big, which city are we
> looking at?
>
> Frankfurt? Berlin? München? Düsseldorf? :-)
>
> Wido
>
> I consider the usual formal of half day talks and will need 5-6 speakers
> on place.
> Best regards,
>
>
>

Re: new committer: Vishesh Jindal (vishesh)

[Wei ZHOU]

Congratulations Vishesh!



On Monday, February 26, 2024, Daan Hoogland  wrote:

> 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: Issue https://github.com/apache/cloudstack/issues/8280 with 4.19.0

[Wei ZHOU]

You can test the nightly build on your testing environment.
https://download.cloudstack.org/testing/nightly/

-Wei


On Thursday, February 22, 2024, Rahul Rai  wrote:

> Thanks for the update, Wei.
>
> Can we expect the latest rpms including these changes or have to wait for
> 4.19.1 release ?
>
> I sincerely apologize if I am missing any facts or additional information.
>
> On Wed, Feb 21, 2024 at 11:16 PM Wei ZHOU  wrote:
>
> > It is already in 4.19 and main branch.
> >
> > -Wei
> >
> > On Thursday, February 22, 2024, Rahul Rai 
> wrote:
> >
> > > Hi Team,
> > >
> > > I have experienced the same error with rhel 9 kvm with UEFI enabled
> > > instance.
> > >
> > > I see that the code was merged with 4.18. Can we expect that to be
> merged
> > > in 4.19 as well?
> > >
> > > https://github.com/apache/cloudstack/pull/8282
> > >
> > > Thanks
> > > Rahul
> > >
> >
>

Re: Issue https://github.com/apache/cloudstack/issues/8280 with 4.19.0

[Wei ZHOU]

It is already in 4.19 and main branch.

-Wei

On Thursday, February 22, 2024, Rahul Rai  wrote:

> Hi Team,
>
> I have experienced the same error with rhel 9 kvm with UEFI enabled
> instance.
>
> I see that the code was merged with 4.18. Can we expect that to be merged
> in 4.19 as well?
>
> https://github.com/apache/cloudstack/pull/8282
>
> Thanks
> Rahul
>

Re: [PROPOSE] RM for 4.19.1.0

[Wei ZHOU]

Great. Go ahead Suresh !


-Wei

On Mon, 12 Feb 2024 at 12:50, 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
>
>
>
>

Re: Discussion: CloudStack upgrade to JRE17 and Debian12/python3

[Wei ZHOU]

Hi Rohit,

Thanks. I will revert the changes then. If the users think 512MB will lead
to large memory consumption, they can
- Create a System Offering
- Update global setting router.service.offering to the uuid of the new
offering.


-Wei


On Fri, 9 Feb 2024 at 16:15, Rohit Yadav  wrote:

> I would advise we should move to 512 MiB.
>
> Regards.
>
>
>
>
>
> ------
> *From:* Wei ZHOU 
> *Sent:* Friday, February 9, 2024 4:14:06 PM
> *To:* Rohit Yadav ; dev <
> dev@cloudstack.apache.org>
> *Subject:* Re: Discussion: CloudStack upgrade to JRE17 and
> Debian12/python3
>
> Hi Rohit,
>
> I tested the VRs of a VPC (with 2 tiers, LB, PF, etc) with different
> memory sizes. 384MB memory looks ok.
>
> (1) 384 MB
>
> root@r-601-VM:~# free -m
>totalusedfree  shared  buff/cache
> available
> Mem: 331 222  39   0 144
>   109
> Swap:242   0 242
>
> (2) 320MB
>
> root@r-603-VM:~# free -m
>totalusedfree  shared  buff/cache
> available
> Mem: 267 214  45   0  80
>53
> Swap:242   0 242
>
> (3) 512MB
>
> root@r-604-VM:~# free -m
>totalusedfree  shared  buff/cache
> available
> Mem: 457 214  63   0 256
>   242
> Swap:242   0 242
>
>
>
>
> On Thu, 8 Feb 2024 at 15:15, Rohit Yadav 
> wrote:
>
> Thanks Wei.
>
> I think VR should be set to 512 (if memory consuming is above 300MB). SSVM
> and CPVM aren’t they already at 512-1024 MiB?
>
> Regards.
>
>
>
>
>
> --
> *From:* Nux 
> *Sent:* Thursday, February 8, 2024 2:50:11 PM
> *To:* dev@cloudstack.apache.org 
> *Cc:* Wei ZHOU 
> *Subject:* Re: Discussion: CloudStack upgrade to JRE17 and
> Debian12/python3
>
> +1 option 2 (Debian12).
>
> I think we need to do a bit longer term testing before we decide on the
> new RAM size for the VR.
> 384MB might be good to boot, but the slightest memory leak or a
> temporarily spiky conntrack table could derail it.
> ..But yeah, need to be conscious of the overall memory overhead in large
> clouds.
>
> On 2024-02-08 07:44, Wei ZHOU wrote:
> > Hi Rohit,
> >
> > Thanks for your reply.
> >
> > Indeed the memory consumption could be an issue, especially for the
> > users
> > who have thousands of virtual routers.
> >
> > I have tested the debian12 systemvm template several times. Every time
> > I
> > get an error "kernel panic"  if the memory is 256MiB (the current
> > memory
> > size of the default system offering for virtual routers).
> > I have tested 320MiB, 384MiB, and 512 MiB. The VRs seem good. For
> > stability, I have updated the PR to change the memory size of the
> > default
> > offering of virtual routers from 256 MiB to 384 MiB.
> >
> > The current default memory size of system vms (CPVM, SSVM) is 512 MiB,
> > so
> > they will not be impacted.
> > Hope it has less impact on users.
> >
> >
> > -Wei
> >
> >
> > On Thu, 8 Feb 2024 at 08:30, Rohit Yadav 
> > wrote:
> >
> >> Hi Wei, all,
> >>
> >> Thanks for the thread, I've no objections to either of the options,
> >> but
> >> option2 is preferred as Debian 11 security will EOL mid of this year.
> >> So,
> >> if not in 4.20, eventually we'll need to migrate systemvmtemplate base
> >> OS
> >> to Debian 12 at some point in future.
> >>
> >> The bigger implication for users will be doubling of their memory
> >> consumption in their env for VRs.
> >>
> >>
> >> Regards.
> >>
> >>
> >>
> >>
> >> 
> >> From: Wei ZHOU 
> >> Sent: Tuesday, February 6, 2024 17:33
> >> To: dev ; users
> >> 
> >> Subject: Discussion: CloudStack upgrade to JRE17 and Debian12/python3
> >>
> >> Hi all,
> >>
> >> My colleagues and I are working on upgrading CloudStack to support the
> >> more
> >> recent JRE version, python version and Debian version for the systemvm
> >> template.
> >> We already have made some changes, if you are interested, please
> >> review the
> >> pull request: https://github.com/apache/cloudstack/pull/8497
> >>
> >>

Re: Discussion: CloudStack upgrade to JRE17 and Debian12/python3

[Wei ZHOU]

Hi Rohit,

I tested the VRs of a VPC (with 2 tiers, LB, PF, etc) with different memory
sizes. 384MB memory looks ok.

(1) 384 MB

root@r-601-VM:~# free -m
   totalusedfree  shared  buff/cache
available
Mem: 331 222  39   0 144
  109
Swap:242   0 242

(2) 320MB

root@r-603-VM:~# free -m
   totalusedfree  shared  buff/cache
available
Mem: 267 214  45   0  80
   53
Swap:242   0 242

(3) 512MB

root@r-604-VM:~# free -m
   totalusedfree  shared  buff/cache
available
Mem: 457 214  63   0 256
  242
Swap:242   0 242




On Thu, 8 Feb 2024 at 15:15, Rohit Yadav  wrote:

> Thanks Wei.
>
> I think VR should be set to 512 (if memory consuming is above 300MB). SSVM
> and CPVM aren’t they already at 512-1024 MiB?
>
> Regards.
>
>
>
>
>
> --
> *From:* Nux 
> *Sent:* Thursday, February 8, 2024 2:50:11 PM
> *To:* dev@cloudstack.apache.org 
> *Cc:* Wei ZHOU 
> *Subject:* Re: Discussion: CloudStack upgrade to JRE17 and
> Debian12/python3
>
> +1 option 2 (Debian12).
>
> I think we need to do a bit longer term testing before we decide on the
> new RAM size for the VR.
> 384MB might be good to boot, but the slightest memory leak or a
> temporarily spiky conntrack table could derail it.
> ..But yeah, need to be conscious of the overall memory overhead in large
> clouds.
>
> On 2024-02-08 07:44, Wei ZHOU wrote:
> > Hi Rohit,
> >
> > Thanks for your reply.
> >
> > Indeed the memory consumption could be an issue, especially for the
> > users
> > who have thousands of virtual routers.
> >
> > I have tested the debian12 systemvm template several times. Every time
> > I
> > get an error "kernel panic"  if the memory is 256MiB (the current
> > memory
> > size of the default system offering for virtual routers).
> > I have tested 320MiB, 384MiB, and 512 MiB. The VRs seem good. For
> > stability, I have updated the PR to change the memory size of the
> > default
> > offering of virtual routers from 256 MiB to 384 MiB.
> >
> > The current default memory size of system vms (CPVM, SSVM) is 512 MiB,
> > so
> > they will not be impacted.
> > Hope it has less impact on users.
> >
> >
> > -Wei
> >
> >
> > On Thu, 8 Feb 2024 at 08:30, Rohit Yadav 
> > wrote:
> >
> >> Hi Wei, all,
> >>
> >> Thanks for the thread, I've no objections to either of the options,
> >> but
> >> option2 is preferred as Debian 11 security will EOL mid of this year.
> >> So,
> >> if not in 4.20, eventually we'll need to migrate systemvmtemplate base
> >> OS
> >> to Debian 12 at some point in future.
> >>
> >> The bigger implication for users will be doubling of their memory
> >> consumption in their env for VRs.
> >>
> >>
> >> Regards.
> >>
> >>
> >>
> >>
> >> 
> >> From: Wei ZHOU 
> >> Sent: Tuesday, February 6, 2024 17:33
> >> To: dev ; users
> >> 
> >> Subject: Discussion: CloudStack upgrade to JRE17 and Debian12/python3
> >>
> >> Hi all,
> >>
> >> My colleagues and I are working on upgrading CloudStack to support the
> >> more
> >> recent JRE version, python version and Debian version for the systemvm
> >> template.
> >> We already have made some changes, if you are interested, please
> >> review the
> >> pull request: https://github.com/apache/cloudstack/pull/8497
> >>
> >> Here are what we want to achieve in CloudStack 4.20
> >>
> >> *1. Upgrade CloudStack to run with JRE17.*
> >>
> >> Currently we use JRE11 to build the CloudStack packages starting in
> >> 2020.
> >> CloudStack mgmt servers/usage/kvm agents run with JRE11 as well.
> >> However,
> >> JRE11 is EOL in September 2023 [1].
> >> In CloudStack 4.20, we will build CloudStack using JRE11 (because old
> >> 4.17/4.18/4/19 systemvm template do not have JRE17 installed) , but
> >> enforce
> >> user to install JRE17 on mgmt server and kvm hosts when upgrade to
> >> CloudStack 4.20
> >> It requires a lot of changes to build CloudStack using JRE17, so it
> >> will be
> >> mostly like done in Cl

Re: Discussion: CloudStack upgrade to JRE17 and Debian12/python3

[Wei ZHOU]

Hi Rohit,

Thanks for your reply.

Indeed the memory consumption could be an issue, especially for the users
who have thousands of virtual routers.

I have tested the debian12 systemvm template several times. Every time I
get an error "kernel panic"  if the memory is 256MiB (the current memory
size of the default system offering for virtual routers).
I have tested 320MiB, 384MiB, and 512 MiB. The VRs seem good. For
stability, I have updated the PR to change the memory size of the default
offering of virtual routers from 256 MiB to 384 MiB.

The current default memory size of system vms (CPVM, SSVM) is 512 MiB, so
they will not be impacted.
Hope it has less impact on users.


-Wei


On Thu, 8 Feb 2024 at 08:30, Rohit Yadav  wrote:

> Hi Wei, all,
>
> Thanks for the thread, I've no objections to either of the options, but
> option2 is preferred as Debian 11 security will EOL mid of this year. So,
> if not in 4.20, eventually we'll need to migrate systemvmtemplate base OS
> to Debian 12 at some point in future.
>
> The bigger implication for users will be doubling of their memory
> consumption in their env for VRs.
>
>
> Regards.
>
>
>
>
> 
> From: Wei ZHOU 
> Sent: Tuesday, February 6, 2024 17:33
> To: dev ; users 
> Subject: Discussion: CloudStack upgrade to JRE17 and Debian12/python3
>
> Hi all,
>
> My colleagues and I are working on upgrading CloudStack to support the more
> recent JRE version, python version and Debian version for the systemvm
> template.
> We already have made some changes, if you are interested, please review the
> pull request: https://github.com/apache/cloudstack/pull/8497
>
> Here are what we want to achieve in CloudStack 4.20
>
> *1. Upgrade CloudStack to run with JRE17.*
>
> Currently we use JRE11 to build the CloudStack packages starting in 2020.
> CloudStack mgmt servers/usage/kvm agents run with JRE11 as well. However,
> JRE11 is EOL in September 2023 [1].
> In CloudStack 4.20, we will build CloudStack using JRE11 (because old
> 4.17/4.18/4/19 systemvm template do not have JRE17 installed) , but enforce
> user to install JRE17 on mgmt server and kvm hosts when upgrade to
> CloudStack 4.20
> It requires a lot of changes to build CloudStack using JRE17, so it will be
> mostly like done in CloudStack 4.21 or later.
>
>
> *2. Upgrade CloudStack VR to use python3*
>
> python2 is currently used in CloudStack VR, which is already EOL in 2020
> [2]. We must migrate to python3 as soon as possible.
> All python scripts used in CloudStack VR will be migrated to python3.
> If you use a Debian11 systemvm template (4.17/4.18/4.19), you need to
> recreate or patch the System VMs and Virtual routers after upgrading to
> CloudStack 4.20.
> If you choose to patch a System VM and Virtual router, two packages will be
> installed: python-is-python3 and python3-netaddr
>
>
> *3. Upgrade CloudStack VR to Debian12*
>
> The more recent operating system provides more features and security. This
> is not urgent as Debian11 will be supported until 2026 [3].
> We have tested the Debian12 systemvm templates, and found only two issues
> - OpenSSL has been upgraded from 1.1.0 to 3.0 in Debian12. Some
> algorithms are deprecated. We have to set "@SECLEVEL=0" in apache2 config
> and "PubkeyAcceptedAlgorithms=+ssh-rsa" to sshd config to support some old
> SSH keys and certificates.
> - The current default memory size (256MB) of virtual routers is not big
> enough. The Debian document says 780MB memory is required [4]. We have
> tested that 512MB/384MB memory is enough. It also works if memory is 320MB.
> But with 256MB, we got "kernel panic" when system VMs/VRs start.
>
> The memory upgrade should not be a problem for most users. If users have
> thousands of virtual routers, they might need to add more memory.
> The new debian12 template might have an impact on CKS (cloudstack
> kubernetes service).  Until now, we have not found any issue in our testing
> with multiple hypervisors (ubuntu22/20, rocky8/alma8/ol8, alma9/ol9,
> xenserver-71, vmware 67u3/70u3/80)
>
>
> What's your opinion on the following two options ?
>
> - Option 1: Upgrade to JRE17 and python3 (still use Debian11)
> - Option 2: Upgrade to JRE17 and python3 and Debian12
>
> Thank you !
>
>
>
> [1]
> https://www.oracle.com/be/java/technologies/java-se-support-roadmap.html
> [2] https://www.python.org/doc/sunset-python-2/
> [3] https://wiki.debian.org/LTS
> [4] https://www.debian.org/releases/bookworm/amd64/ch02s05.en.html
>

Re: [ANNOUNCEMENT] Apache CloudStack 4.19.0.0 LTS Release

[Wei ZHOU]

Great news !


-Wei

On Tue, 6 Feb 2024 at 12:37, Abhishek Kumar  wrote:

> The Apache Software Foundation and the Apache CloudStack Project Announces
> Apache® CloudStack® v4.19.
>
> Apache CloudStack 4.19 is the most recent release of the cloud management
> platform. It comes as a product of extensive contributions from the
> development community and is a LTS release, guaranteeing ongoing
> maintenance and support for a period of 18 months
>
> The 4.19 release contains 314 new features, improvements and bug fixes
> since 4.18, 26 of these being major features.
>
> Some of the highlighted features include:
>
> - VMware to KVM Migration
>
> - KVM Import
>
> - CloudStack Object Storage
>
> - CloudStack DRS
>
> - VNF Appliances Support
>
> - Scheduled Instance Lifecycle Operations
>
> - OAuth 2 Authentication
>
> - CloudStack Snapshot Copy
>
> The full list of new features can be found in the project release notes at:
> https://docs.cloudstack.apache.org/en/4.19.0.0/releasenotes
>
>
> The CloudStack documentation includes upgrade instructions from previous
> versions of Apache CloudStack, and can be found at:
> https://docs.cloudstack.apache.org/en/4.19.0.0/upgrading
>
> The official installation, administration and API documentation for each of
> the releases are available on our documentation page:
> https://docs.cloudstack.apache.org/en/4.19.0.0/installguide
>
> Downloads
>
> The official source code for the 4.19.0.0 release can be downloaded from
> our downloads page: https://cloudstack.apache.org/downloads.html
>
> In addition to the official source code release, individual contributors
> have also made convenience binaries available on the Apache CloudStack
> download page, and can be found at:
>
> - https://download.cloudstack.org/el/7/
>
> - https://download.cloudstack.org/el/8/
>
> - https://download.cloudstack.org/el/9/
>
> - https://download.cloudstack.org/ubuntu/dists/
>
> - https://www.shapeblue.com/cloudstack-packages/
>
>
> Regards,
>
> Abhishek
>

Re: new website is life

[Wei ZHOU]

great !
looks much better


-Wei

On Wed, 7 Feb 2024 at 09:23, Daan Hoogland  wrote:

> People,
> we brought the new website. Please all have a look at
> https://cloudstack.apache.org
>
> thanks for any feedback
>
> --
> Daan
>

Discussion: CloudStack upgrade to JRE17 and Debian12/python3

[Wei ZHOU]

Hi all,

My colleagues and I are working on upgrading CloudStack to support the more
recent JRE version, python version and Debian version for the systemvm
template.
We already have made some changes, if you are interested, please review the
pull request: https://github.com/apache/cloudstack/pull/8497

Here are what we want to achieve in CloudStack 4.20

*1. Upgrade CloudStack to run with JRE17.*

Currently we use JRE11 to build the CloudStack packages starting in 2020.
CloudStack mgmt servers/usage/kvm agents run with JRE11 as well. However,
JRE11 is EOL in September 2023 [1].
In CloudStack 4.20, we will build CloudStack using JRE11 (because old
4.17/4.18/4/19 systemvm template do not have JRE17 installed) , but enforce
user to install JRE17 on mgmt server and kvm hosts when upgrade to
CloudStack 4.20
It requires a lot of changes to build CloudStack using JRE17, so it will be
mostly like done in CloudStack 4.21 or later.


*2. Upgrade CloudStack VR to use python3*

python2 is currently used in CloudStack VR, which is already EOL in 2020
[2]. We must migrate to python3 as soon as possible.
All python scripts used in CloudStack VR will be migrated to python3.
If you use a Debian11 systemvm template (4.17/4.18/4.19), you need to
recreate or patch the System VMs and Virtual routers after upgrading to
CloudStack 4.20.
If you choose to patch a System VM and Virtual router, two packages will be
installed: python-is-python3 and python3-netaddr


*3. Upgrade CloudStack VR to Debian12*

The more recent operating system provides more features and security. This
is not urgent as Debian11 will be supported until 2026 [3].
We have tested the Debian12 systemvm templates, and found only two issues
- OpenSSL has been upgraded from 1.1.0 to 3.0 in Debian12. Some
algorithms are deprecated. We have to set "@SECLEVEL=0" in apache2 config
and "PubkeyAcceptedAlgorithms=+ssh-rsa" to sshd config to support some old
SSH keys and certificates.
- The current default memory size (256MB) of virtual routers is not big
enough. The Debian document says 780MB memory is required [4]. We have
tested that 512MB/384MB memory is enough. It also works if memory is 320MB.
But with 256MB, we got "kernel panic" when system VMs/VRs start.

The memory upgrade should not be a problem for most users. If users have
thousands of virtual routers, they might need to add more memory.
The new debian12 template might have an impact on CKS (cloudstack
kubernetes service).  Until now, we have not found any issue in our testing
with multiple hypervisors (ubuntu22/20, rocky8/alma8/ol8, alma9/ol9,
xenserver-71, vmware 67u3/70u3/80)


What's your opinion on the following two options ?

- Option 1: Upgrade to JRE17 and python3 (still use Debian11)
- Option 2: Upgrade to JRE17 and python3 and Debian12

Thank you !



[1] https://www.oracle.com/be/java/technologies/java-se-support-roadmap.html
[2] https://www.python.org/doc/sunset-python-2/
[3] https://wiki.debian.org/LTS
[4] https://www.debian.org/releases/bookworm/amd64/ch02s05.en.html

Re: [VOTE] Apache CloudStack 4.19.0.0 RC4

[Wei ZHOU]

+1 (binding)

Tested several environments

- rocky8 (mgmt) + rocky8 (host), advanced zone. No issues found.
- ubuntu22 (mgmt) + ubuntu22 (host), advanced zone. No issues found.
- rocky8 (mgmt) + vmware80, advanced zone. No issues found.
- rocky8 (mgmt) + vmware80U1 (not supported officially), advanced zone.
confirmed the issue still exists:
https://github.com/apache/cloudstack/issues/7572
- rocky8 (mgmt) + xcp-ng81 (host), advanced zone. There are some smoke test
failures, none seems critical:
https://github.com/apache/cloudstack/issues/8586
- ubuntu22 (mgmt) + ubuntu22 (host), advanced zone with SG. Found two
non-critical issues: https://github.com/apache/cloudstack/issues/8585 and
https://github.com/apache/cloudstack/issues/8595
- ol9 (mgmt) + ol9 (host), advanced zone with SG. same as above



-Wei

On Mon, 29 Jan 2024 at 07:58, 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
>

Re: [VOTE] go life with new website(design)

[Wei ZHOU]

+1 (binding)



在 2024年2月1日星期四，Daan Hoogland  写道：

> LS,
>
> I am not sure this is still needed after all the discussions
> before,but I would like to start a lazy consent vote threat anyway
> there are some non-blocking rest points mentioned and we can
> administer those in the repo for the site [1]
>
> so without further ado;
> Do we want to go life with the website as staged in
> cloudstack.staged.apache.org
>
> +1 yes
> 0 no opinion (no reaction suffices as well)
> -1 no (please state reasons
>
>
> [1] https://github.com/apache/cloudstack-www/issues/new/choose
>

Re: Introduction and Greetings

[Wei ZHOU]

Welcome Abhisar !

-Wei

On Wed, 31 Jan 2024 at 13:42, Abhisar Sinha 
wrote:

> Hi All,
>
> I have background in Storage as a developer at NetApp India, and I have
> recently joined Shapeblue as a Software Engineer.
> I am excited to be joining the CloudStack community and looking forward to
> interacting with the community and contributing to the project.
>
> Thanks and Regards,
> Abhisar
>
>
>
>

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

[Wei ZHOU]

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
:1: DeprecationWarning: 'cgi' is deprecated and slated for removal
in Python 3.13

For the API changes you mentioned, we could try the similar
- in version X, add new APIs, mark the old APIs as deprecated
- tell users the old APIs will be removed in version Y, please use new APIs
instead.
- in version Y, remove the old APIs.

This can be done in each major/minor release. No need to wait for 5.0.


-Wei

On Fri, 26 Jan 2024 at 18:51, Guto Veronezi  wrote:

> Exactly, so you understand now why we must discuss what we intend.
> Although, incompatibilities are needed sometimes so we can evolve,
> leaving old ways and deprecated technologies and techniques in the past.
>
> *The main point is: *we have to understand the technical reasons for the
> proposal and what we expect from it before deciding anything.
>
> Best regards,
> Daniel Salvador (gutoveronezi)
>
>
>

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

[Wei ZHOU]

Hi Daniel,

The website/repository you mentioned was originally by a person, after
CloudStack 2.x/3.x was released. Is there a decision we must/should follow ?

If you look around, most OS/software do not follow it.  iOS/Android?
Ubuntu/Debian/RHEL/Windows ? or Chrome/Firefox ? or kvm/vmware/xenserver ?

By the way, the article is incorrect. Softwares must keep backward
compatibility as much as possible.


-Wei

On Fri, 26 Jan 2024 at 17:32, Guto Veronezi  wrote:

> Wei,
>
> Currently, ACS follows the semantic version [1], which specifies that
> introducing incompatibilities requires a new MAJOR version; therefore,
> the few changes I mentioned would already require a new MAJOR version,
> as they would generate incompatibilities. Also, remember that they are
> some examples; there is a lot more to do. Adding functionalities in a
> backward compatible manner, like we have been doing, requires only the
> MINOR version change. Therefore, we have to understand the technical
> reasons for the proposal and what we expect from it before deciding
> anything.
>
> Best regards,
> Daniel Salvador (gutoveronezi)
>
> [1] https://semver.org/
>
> On 1/26/24 09:44, Wei ZHOU wrote:
> > Hi Daniel,
> >
> > These are not big changes. You can fix them in some major/minor
> > releases, if you like.
> >
> > I think we will not have a 5.0 release. If so, why not remove "4." from
> the
> > version which is useless at all.
> >
> > Kind regards,
> > Wei
> >
> >
> > On Thu, 25 Jan 2024 at 15:52, Guto Veronezi 
> wrote:
> >
> >> Hello guys,
> >>
> >> It is nice that we are discussing this topic; however, what is the
> >> point? Is it just a semantic change? Or we will be able to introduce
> >> changes that cause incompatibility between versions (although some
> >> incompatibilities are already introduced even when they should not)? By
> >> the way, I already have in mind some changes that would cause
> >> incompatibilities between versions; some of they are:
> >>
> >> - unifying duplicated APIs, like the "list*Metrics" APIs; it should be a
> >> single parameter in the existing API, not a whole new API;
> >> - renaming misleading APIs, like "createCondition" and others from the
> >> AutoScale group that are not intuitive;
> >> - standardize the APIs' response names, vide PR #7022 [1];
> >> - and so many other disruptive changes.
> >>
> >> If it is just a semantic change, then it does not make sense. We would
> >> just make a show off to the community, but nothing would change at all.
> >>
> >> What are the technical reasons between the proposal?
> >>
> >> Best regards,
> >> Daniel Salvador (gutoveronezi)
> >>
> >> [1] https://github.com/apache/cloudstack/pull/7022
> >>
> >>
> >> On 1/24/24 09:45, Wido den Hollander wrote:
> >>>
> >>> Op 24/01/2024 om 10:47 schreef Daan Hoogland:
> >>>> personally I don't like the months too much. They tie us down to a
> >>>> release schedule that we have proven not to be able to maintain. a
> >>>> year as number restricts us to just one major release that year, i.e.
> >>>> only one moment for new integrations or major features. S I am for the
> >>>> more liberal 20.x and if we make a second one some year we can freely
> >>>> add a number.
> >>>>
> >>> Our mails just crossed :-) Timing!
> >>>
> >>> Does .MM tie you down to a specific schedule? You can release
> >>> whenever you want, right? The version depends on when you release.
> >>>
> >>> But I'm ok with just going with an number. 24, then 25, then 26, etc.
> >>> Something else then 4.x for ever.
> >>>
> >>> Wido
> >>>
> >>>> On Wed, Jan 24, 2024 at 12:27 AM Wei ZHOU 
> >> wrote:
> >>>>> Yes, the ubuntu version naming is the best in my opinion.
> >>>>> Other than the version naming, we need to decide the frequency of
> major
> >>>>> releases and minor releases, which version will be LTS, how long the
> >>>>> LTS/normal version will be supported, etc.
> >>>>>
> >>>>> Maybe a vote in the dev/users/pmc mailing list?
> >>>>>
> >>>>>
> >>>>>
> >>>>> 在 2024年1月23日星期二，Nicolas Vazquez 
> >>>>> 写道：
> >>>>>
> >>>>>>

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

[Wei ZHOU]

Hi Daniel,

These are not big changes. You can fix them in some major/minor
releases, if you like.

I think we will not have a 5.0 release. If so, why not remove "4." from the
version which is useless at all.

Kind regards,
Wei


On Thu, 25 Jan 2024 at 15:52, Guto Veronezi  wrote:

> Hello guys,
>
> It is nice that we are discussing this topic; however, what is the
> point? Is it just a semantic change? Or we will be able to introduce
> changes that cause incompatibility between versions (although some
> incompatibilities are already introduced even when they should not)? By
> the way, I already have in mind some changes that would cause
> incompatibilities between versions; some of they are:
>
> - unifying duplicated APIs, like the "list*Metrics" APIs; it should be a
> single parameter in the existing API, not a whole new API;
> - renaming misleading APIs, like "createCondition" and others from the
> AutoScale group that are not intuitive;
> - standardize the APIs' response names, vide PR #7022 [1];
> - and so many other disruptive changes.
>
> If it is just a semantic change, then it does not make sense. We would
> just make a show off to the community, but nothing would change at all.
>
> What are the technical reasons between the proposal?
>
> Best regards,
> Daniel Salvador (gutoveronezi)
>
> [1] https://github.com/apache/cloudstack/pull/7022
>
>
> On 1/24/24 09:45, Wido den Hollander wrote:
> >
> >
> > Op 24/01/2024 om 10:47 schreef Daan Hoogland:
> >> personally I don't like the months too much. They tie us down to a
> >> release schedule that we have proven not to be able to maintain. a
> >> year as number restricts us to just one major release that year, i.e.
> >> only one moment for new integrations or major features. S I am for the
> >> more liberal 20.x and if we make a second one some year we can freely
> >> add a number.
> >>
> >
> > Our mails just crossed :-) Timing!
> >
> > Does .MM tie you down to a specific schedule? You can release
> > whenever you want, right? The version depends on when you release.
> >
> > But I'm ok with just going with an number. 24, then 25, then 26, etc.
> > Something else then 4.x for ever.
> >
> > Wido
> >
> >> On Wed, Jan 24, 2024 at 12:27 AM Wei ZHOU 
> wrote:
> >>>
> >>> Yes, the ubuntu version naming is the best in my opinion.
> >>> Other than the version naming, we need to decide the frequency of major
> >>> releases and minor releases, which version will be LTS, how long the
> >>> LTS/normal version will be supported, etc.
> >>>
> >>> Maybe a vote in the dev/users/pmc mailing list?
> >>>
> >>>
> >>>
> >>> 在 2024年1月23日星期二，Nicolas Vazquez 
> >>> 写道：
> >>>
> >>>> I like this idea as well, even if its .MM or YY.MM.
> >>>>
> >>>> Would we want to define delivery months for releases similar to
> >>>> Ubuntu .04
> >>>> and .10?
> >>>>
> >>>> Regards,
> >>>> Nicolas Vazquez
> >>>> 
> >>>> From: Nux 
> >>>> Sent: Tuesday, January 23, 2024 6:11 PM
> >>>> To: dev@cloudstack.apache.org 
> >>>> Cc: Wei ZHOU 
> >>>> Subject: Re: [PROPOSAL] version naming : drop the 4.
> >>>>
> >>>> An interesting proposition, I like it.
> >>>> It would also relieve us from having to come up with any over-the-top
> >>>> feature or change for a major version change.
> >>>>
> >>>> On 2024-01-23 14:49, Wido den Hollander wrote:
> >>>>> We could look at Ubuntu, and other projects, and call it 2025.01
> >>>>> if we
> >>>>> release it in Jan 2025.
> >>>>>
> >>>>> A great post on the website, mailinglists and social media could
> >>>>> explain the change in versioning, but that the code doesn't change
> >>>>> that
> >>>>> much.
> >>>>>
> >>>>> Project has matured, etc, etc.
> >>>>
> >>>>
> >>>>
> >>>>
> >>
> >>
> >>
>

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

[Wei ZHOU]

Hi Daan,

Can you start a vote with options , for example ?

- No version naming change
- option A
- option B
- option C
- other options


On Wed, 24 Jan 2024 at 13:11, Daan Hoogland  wrote:

> If I start a vote it will be to adjust to the semantic versioning
> system. I do not approve of the ubuntu scheme, sorry. I will probably
> -0 just to get us moving forward but I think it is not the best for
> us. So I'll wait a few and start a vote if no-one else did before me.
>
> On Wed, Jan 24, 2024 at 12:48 PM Wido den Hollander
>  wrote:
> >
> >
> >
> > Op 24/01/2024 om 00:27 schreef Wei ZHOU:
> > > Yes, the ubuntu version naming is the best in my opinion.
> > > Other than the version naming, we need to decide the frequency of major
> > > releases and minor releases, which version will be LTS, how long the
> > > LTS/normal version will be supported, etc.
> > >
> > > Maybe a vote in the dev/users/pmc mailing list?
> > >
> >
> > I think that's a good decision.
> >
> > @ Daan: Do you want to start one?
> >
> > I'd prefer the .MM release schedule. We just need a good (blog)post
> > to explain the new versioning.
> >
> > Wido
> >
> > >
> > >
> > > 在 2024年1月23日星期二，Nicolas Vazquez  写道：
> > >
> > >> I like this idea as well, even if its .MM or YY.MM.
> > >>
> > >> Would we want to define delivery months for releases similar to
> Ubuntu .04
> > >> and .10?
> > >>
> > >> Regards,
> > >> Nicolas Vazquez
> > >> 
> > >> From: Nux 
> > >> Sent: Tuesday, January 23, 2024 6:11 PM
> > >> To: dev@cloudstack.apache.org 
> > >> Cc: Wei ZHOU 
> > >> Subject: Re: [PROPOSAL] version naming : drop the 4.
> > >>
> > >> An interesting proposition, I like it.
> > >> It would also relieve us from having to come up with any over-the-top
> > >> feature or change for a major version change.
> > >>
> > >> On 2024-01-23 14:49, Wido den Hollander wrote:
> > >>> We could look at Ubuntu, and other projects, and call it 2025.01 if
> we
> > >>> release it in Jan 2025.
> > >>>
> > >>> A great post on the website, mailinglists and social media could
> > >>> explain the change in versioning, but that the code doesn't change
> that
> > >>> much.
> > >>>
> > >>> Project has matured, etc, etc.
> > >>
> > >>
> > >>
> > >>
> > >
>
>
>
> --
> Daan
>

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

[Wei ZHOU]

Yes, the ubuntu version naming is the best in my opinion.
Other than the version naming, we need to decide the frequency of major
releases and minor releases, which version will be LTS, how long the
LTS/normal version will be supported, etc.

Maybe a vote in the dev/users/pmc mailing list?



在 2024年1月23日星期二，Nicolas Vazquez  写道：

> I like this idea as well, even if its .MM or YY.MM.
>
> Would we want to define delivery months for releases similar to Ubuntu .04
> and .10?
>
> Regards,
> Nicolas Vazquez
> 
> From: Nux 
> Sent: Tuesday, January 23, 2024 6:11 PM
> To: dev@cloudstack.apache.org 
> Cc: Wei ZHOU 
> Subject: Re: [PROPOSAL] version naming : drop the 4.
>
> An interesting proposition, I like it.
> It would also relieve us from having to come up with any over-the-top
> feature or change for a major version change.
>
> On 2024-01-23 14:49, Wido den Hollander wrote:
> > We could look at Ubuntu, and other projects, and call it 2025.01 if we
> > release it in Jan 2025.
> >
> > A great post on the website, mailinglists and social media could
> > explain the change in versioning, but that the code doesn't change that
> > much.
> >
> > Project has matured, etc, etc.
>
>
>
>

Re: CentOS 7 is reaching EOL

[Wei ZHOU]

Hi Lucian,

I think what Vishesh meant is removing the support of CentOS 7 as a
management server or kvm host.

-Wei

On Tue, 23 Jan 2024 at 22:07, Nux  wrote:

> I would not be so hasty. I am sure there are still CentOS 5 instances in
> existence somewhere, similarly I think CentOS 7 will not go down without
> a fight.
> I'm not saying to never kill support for it, but I'd leave it maybe 1-2
> more releases. Corporate users especially will take a lot of time to
> move...
>
> /imho
>
> On 2024-01-23 16:27, Vishesh Jindal wrote:
> > Hi all
> >
> > While working on a PR[1] to upgrade JRE, I noticed that CentOS 7 is
> > reaching end of life on 30 June, 2024 [2].
> >
> > Should we remove support for CentOS 7 after 4.19 is released? Because
> > by the time 4.20 is out, CentOS 7 would already have reached its EOL
> > and IMO it doesn't make sense to maintain support for it.
> >
> > Regards,
> > Vishesh
> >
> >
> > Ref:
> > [1] https://github.com/apache/cloudstack/pull/8438
> > [2] https://www.redhat.com/en/topics/linux/centos-linux-eol
>

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

[Wei ZHOU]

+1 with 20.0

5.0 sounds like a leap with lots of significant changes. Unfortunately it
has not been discussed what needs to be done.
20.0 (or 24.0) looks better.

Wei

On Mon, 22 Jan 2024 at 12:01, Daan Hoogland  wrote:

> João,
> I think we should not consider 5.0, but go to 20,0 that is more in
> line with what we've actually been doing (semantic versioning from the
> second digit)
>
> On Mon, Jan 22, 2024 at 11:53 AM Nux  wrote:
> >
> > LGTM!
> >
> > On 2024-01-19 19:19, João Jandre Paraquetti wrote:
> > > Hi all,
> > >
> > > I agree that our current versioning schema doesn't make much sense, as
> > > "minors" introduce pretty big features; even backward incompatibilities
> > > are introduced in minor versions sometimes.
> > >
> > > As the current plan is to have 4.20 by June, I think we should stick to
> > > it and still have the next "minor", and make it the last minor version
> > > of the major 4. After so much time in the same major version, we should
> > > plan something relevant before changing it, and June 2024 is a bit of a
> > > tight schedule for that.
> > >
> > > I think that we should plan to move to version 5.0.0, we could set the
> > > release date to the end of 2024 or the start (January) of 2025; by
> > > doing that, we have plenty of time for planning and developing amazing
> > > features for version 5, while also preparing a cleanup of our current
> > > APIs. For instance, we are working on the following major developments:
> > > KVM differential snapshots/backups without needing extra software;
> > > theme management system (white label portal for ACS); native
> > > snapshot/backup for VMware (without needing Veeam) to make it similar
> > > to what ACS does with XenServer and KVM; Operators backup (which are
> > > different from end-user backups); and many other items.
> > >
> > > What do you guys think?
> > >
> > > Best regards,
> > > João Jandre.
> > >
> > > On 1/19/24 10:39, Daan Hoogland wrote:
> > >> devs, PMC,
> > >>
> > >> as we are closing in on 4.19 I want to propose that we drop the 4. in
> > >> our versioning scheme. We've been discussing 5 but no real initiatives
> > >> have been taken. Nowadays big features go into our "minor"
> > >> dot-releases. In my opinion this warrants promoting those version to
> > >> the status of major and dropping the 4..
> > >>
> > >> technically this won't be an issue as 20 > 4 and out upgrade scheme
> > >> supports a step like that.
> > >>
> > >> any thoughts?
> > >>
>
>
>
> --
> Daan
>

Re: [VOTE] Apache CloudStack 4.19.0.0 RC2

[Wei ZHOU]

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
>

Re: [VOTE] Apache CloudStack 4.19.0.0 RC2

[Wei ZHOU]

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
>

Re: new PMC member Harikrishna Patnala

[Wei ZHOU]

Congratulations Hari !

-Wei

On Mon, 15 Jan 2024 at 10:25, Daan Hoogland  wrote:

> users and dev,
>
> The PMC have invited Harikrishna to join their ranks and he has
> gracefully accepted. Please join me in congratulating Hari.
>
> --
> Daan
>

Re: New committer: Alexandre Mattioli

[Wei ZHOU]

Congratulations Alex !
Well deserved !

-Wei

On Wed, 10 Jan 2024 at 23:28, Nux  wrote:

> All,
>
> The Project Management Committee (PMC) for Apache CloudStack
> has invited Alexandre Mattioli to become a committer and we are pleased
> to announce that they have accepted.
>
> Alex has been instrumental in many features present today in Cloudstack,
> with a focus on networking and VMWare:
> - IPv6 static routing
> - Edge Zones
> - Autoscaling with VR
> - VNF appliances
> - VMWare NSX support
> - Tungsten Fabric / OpenSDN
> - Backup & recovery framework
> - VLAN trunking and security policies in ESX
> and so on.
>
>
> Please join me in congratulating Alex!
>
>

Re: new committer: João Jandre Paraquetti

[Wei ZHOU]

Congratulations João !
Well done

-Wei

On Mon, 18 Dec 2023 at 13:48, Daan Hoogland  wrote:

> 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
>

Re: New Object Storage - Huawei OBS

[Wei ZHOU]

Hi Wido,

I just tested your branch, it looks ok (
https://github.com/wido/cloudstack/commits/ceph-object-store).

I got an error which is because I input invalid host/keys

2023-12-15 19:07:22,313 DEBUG [o.a.c.s.d.l.CephObjectStoreLifeCycleImpl]
(qtp775386112-17:ctx-9be6ad79 ctx-b4cdcdd0) (logid:3a8340e9) Error while
initializing Ceph RGW Object Store: IOException
2023-12-15 19:07:22,313 DEBUG [c.c.s.StorageManagerImpl]
(qtp775386112-17:ctx-9be6ad79 ctx-b4cdcdd0) (logid:3a8340e9) Failed to add
object store: Error while initializing Ceph RGW Object Store. Invalid
credentials or URL
java.lang.RuntimeException: Error while initializing Ceph RGW Object Store.
Invalid credentials or URL
at
org.apache.cloudstack.storage.datastore.lifecycle.CephObjectStoreLifeCycleImpl.initialize(CephObjectStoreLifeCycleImpl.java:87)
at
com.cloud.storage.StorageManagerImpl.discoverObjectStore(StorageManagerImpl.java:3777)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)


-Wei

On Fri, 15 Dec 2023 at 17:18, Wido den Hollander  wrote:

>
>
> Op 15/12/2023 om 13:54 schreef Wei ZHOU:
> > Hi Wido,
> >
> > It looks you need a file like
> >
> https://github.com/apache/cloudstack/blob/main/plugins/storage/object/simulator/src/main/resources/META-INF/cloudstack/storage-object-simulator/spring-storage-object-simulator-context.xml
> >
>
> Tnx. But that didn't solve it. The module seems to load according to the
> mgmt server log, but I can't add the storage. Exception is the same.
>
> Wido
>
> > -Wei
> >
> > On Fri, 15 Dec 2023 at 13:40, Wido den Hollander  >
> > wrote:
> >
> >>
> >>
> >> On 12/15/23 09:41, Ronald Feicht wrote:
> >>> Hi Kishan,
> >>>
> >>>
> >>> when I add my module to client/pom.xml I get the following error and
> >> http://192.168.17.252:8080/client/ returns "HTTP ERROR 503 Service
> >> Unavailable" because of the following exception:
> >>>
> >>> [WARNING] Failed startup of context
> o.e.j.m.p.JettyWebAppContext@1df8ea34
> >>
> {/client,file:///opt/cloudstack-huawei-obs/client/target/classes/META-INF/webapp/,UNAVAILABLE}{file:///opt/cloudstack-huawei-obs/client/target/classes/META-INF/webapp/}
> >>> java.lang.NullPointerException
> >>>   at
> >>
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$1.with
> >> (DefaultModuleDefinitionSet.java:104)
> >>>   at
> >>
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
> >> (DefaultModuleDefinitionSet.java:263)
> >>>   at
> >>
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
> >> (DefaultModuleDefinitionSet.java:268)
> >>>   at
> >>
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
> >> (DefaultModuleDefinitionSet.java:268)
> >>>   at
> >>
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
> >> (DefaultModuleDefinitionSet.java:268)
> >>>   at
> >>
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
> >> (DefaultModuleDefinitionSet.java:268)
> >>>   at
> >>
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
> >> (DefaultModuleDefinitionSet.java:268)
> >>>   at
> >>
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule
> >> (DefaultModuleDefinitionSet.java:251)
> >>>   at
> >>
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.startContexts
> >> (DefaultModuleDefinitionSet.java:96)
> >>>   at
> >>
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load
> >> (DefaultModuleDefinitionSet.java:79)
> >>>   at
> >>
> org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules
> >> (ModuleBasedContextFactory.java:37)
> >>>   at
> >> org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init
> >> (CloudStackSpringContext.java:70)
> >>>   at
> >>
> org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.
> >> (CloudStackSpringContext.java:57)
> >>>   at
> >>
> org.apache.cloudstack.spring.module.factory.Clo

Re: New Object Storage - Huawei OBS

[Wei ZHOU]

(Launcher.java:225)
> >  at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> >  at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> >
> > But the directory exists and is not empty:
> >
> > [root@cloudstack-centos cloudstack-huawei-obs]# ll
> /opt/cloudstack-huawei-obs/client/target/classes/META-INF/webapp/
> > total 4
> > drwxr-xr-x. 2 root root   21 Dec 14 12:17 WEB-INF
> > -rw-r--r--. 1 root root 1135 Dec 14 12:17 index.html
> > drwxr-xr-x. 3 root root   39 Dec 14 12:17 .
> > drwxr-xr-x. 4 root root   87 Dec 14 12:17 ..
> > [root@cloudstack-centos cloudstack-huawei-obs]# ll
> /opt/cloudstack-huawei-obs/client/target/classes/META-INF/webapp/WEB-INF/
> > total 4
> > -rw-r--r--. 1 root root 2694 Dec 14 12:17 web.xml
> > drwxr-xr-x. 2 root root   21 Dec 14 12:17 .
> > drwxr-xr-x. 3 root root   39 Dec 14 12:17 ..
> >
> > Because of that error I had removed my plugin from client/pom.xml again
> and then afterwards http://192.168.17.252:8080/client/ worked.
> > So, I now understand that my plugin must by part of client/pom.xml but
> then I receive the same exception mentioned above - how do I fix that?
> >
> >
> > Mit freundlichen Grüßen
> > R. Feicht
> >
> > sc synergy GmbH
> > Hilgestrasse 14 | 55294 Bodenheim | Deutschland
> > Fon: +49 6135 71691 - 000 | Fax: +49 6135 71691 - 299
> http://www.scsynergy.com | ronald.fei...@scsynergy.com Sitz der
> Gesellschaft Bodenheim, HRB 8830, Amtsgericht Mainz, Geschäftsführer:
> Christian Reichert
> >
> >
> > 
> > From: Slavka Peleva 
> > Sent: Thursday, December 14, 2023 11:37
> > To: dev@cloudstack.apache.org
> > Subject: Re: New Object Storage - Huawei OBS
> >
> > Hi Ronald,
> >
> > In the logs, you can find all the modules that are loaded like:
> >
> > ```
> > 2023-12-14 12:28:21,480 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Module Hierarchy: storage
> > 2023-12-14 12:28:21,480 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Module Hierarchy:   baremetal-storage
> > 2023-12-14 12:28:21,480 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Module Hierarchy:
> > server-alert-adapter-storage
> > 2023-12-14 12:28:21,480 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Module Hierarchy:   server-storage
> > 2023-12-14 12:28:21,480 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Module Hierarchy:   server-template-adapter
> > 2023-12-14 12:28:21,480 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Module Hierarchy:   storage-allocator
> > 2023-12-14 12:28:21,480 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Module Hierarchy:   storage-image-default
> > 2023-12-14 12:28:21,480 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Module Hierarchy:   storage-image-s3
> > 2023-12-14 12:28:21,480 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Module Hierarchy:   storage-image-swift
> > 2023-12-14 12:28:21,480 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Module Hierarchy:   storage-object-minio
> > 2023-12-14 12:28:21,480 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Module Hierarchy:   storage-object-simulator
> > 2023-12-14 12:28:21,480 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Module Hierarchy:   storage-volume-cloudbyte
> > 2023-12-14 12:28:21,480 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Module Hierarchy:   storage-volume-datera
> > 2023-12-14 12:28:21,480 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Module Hierarchy:   storage-volume-default
> > 2023-12-14 12:28:21,480 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Module Hierarchy:
>  storage-volume-flasharray
> > 2023-12-14 12:28:21,480 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Module Hierarchy:   storage-volume-linstor
> > 2023-12-14 12:28:21,480 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Module Hierarchy:   storage-volume-primera
> > 2023-12-14 12:28:21,480 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:

Re: New Object Storage - Huawei OBS

[Wei ZHOU]

Is the module added to client/pom.xml ?

-Wei

On Thu, 14 Dec 2023 at 10:51, Ronald Feicht 
wrote:

> Hi,
>
> I am trying to write an Object Storage plugin for Huawei OBS using Minio
> as example. I added my plugin code to the plugins/storage/object/
> directory, added my plugin into plugins/pom.xml and added the string
> 'Huawei OBS' to AddObjectStorage.vue for the dropdown in the UI. But when I
> select that dropdown entry and click "Save" in the UI the following
> exception is thrown:
> com.cloud.exception.InvalidParameterValueException: can't find object
> store provider: Huawei OBS
> at
> com.cloud.storage.StorageManagerImpl.discoverObjectStore(StorageManagerImpl.java:3743)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
> at
> org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:107)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
> at
> com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:52)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
> at
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215)
> at com.sun.proxy.$Proxy119.discoverObjectStore(Unknown Source)
> at
> org.apache.cloudstack.api.command.admin.storage.AddObjectStoragePoolCmd.execute(AddObjectStoragePoolCmd.java:117)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:172)
> at com.cloud.api.ApiServer.queueCommand(ApiServer.java:782)
> at com.cloud.api.ApiServer.handleRequest(ApiServer.java:603)
> at
> com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:347)
> at com.cloud.api.ApiServlet$1.run(ApiServlet.java:154)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
> at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:151)
> at com.cloud.api.ApiServlet.doGet(ApiServlet.java:105)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> org.eclipse.jetty.servlet.ServletHolder$NotAsyncServlet.service(ServletHolder.java:1386)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617)
> at
> org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:226)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:545)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:590)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1610)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1300)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:485)
> at
> org.eclipse.jetty.server.session.SessionHandler

Re: You're in developer mode, please build and run UI using npm. when building CloudStack from source

[Wei ZHOU]

Hi,

I think you need to at first make sure the management service has been
started successfully. You can check it by "curl
http://localhost:8080/client/api";
If it does not work, please check vmops.log to see what's wrong.

For the error "ENOSPC: System limit for number of file watchers reached",
you can search it on google and get some advice.

-Wei

On Wed, 13 Dec 2023 at 14:05,  wrote:

> I found this in /var/log/mysqld.log
> "2023-12-13T13:01:40.388380Z 3 [Note] Aborted connection 3 to db:
> 'cloud' user: 'cloud' host: 'localhost' (Got an error reading
> communication packets)"
>
> Since this error can have a multitude of causes I would be grateful for
> any hints to point me in the correct direction.
>
> On 12/12/23 08:42, Ronald Feicht wrote:
> >
> > Hi,
> >
> >
> > no, I do not see any errors like the one you mentioned, only a lot of
> > errors like this from "npm serve run":
> >
> > Error from chokidar (/opt/cloudstack/ui/src/views/storage): Error:
> > ENOSPC: System limit for number of file watchers reached, watch
> > '/opt/cloudstack/ui/src/views/storage/RecurringSnapshotVolume.vue'
> >
> >
> > The IP has changed due to DHCP and a reboot of the virtual machine -
> > it is now http://192.168.17.252 <http://192.168.17.252>:8080.
> >
> >
> > I do not see any _relevant_ error in vmops.log, but maybe the errors
> > in there are actually crucial and I just fail to recognize this fact?
> > I have attached the file to this email.
> >
> >
> > Mit freundlichen Grüßen
> > R. Feicht
> >
> > *sc synergy GmbH*
> > Hilgestrasse 14 | 55294 Bodenheim | Deutschland
> > Fon: +49 6135 71691 - 000 | Fax: +49 6135 71691 - 299
> > http://www.scsynergy.com | ronald.fei...@scsynergy.com
> > Sitz der Gesellschaft Bodenheim, HRB 8830, Amtsgericht Mainz,
> > Geschäftsführer: Christian Reichert
> >
> >
> > 
> > *From:* Pearl d'Silva 
> > *Sent:* Monday, December 11, 2023 16:56
> > *To:* dev@cloudstack.apache.org
> > *Subject:* Re: You're in developer mode, please build and run UI using
> > npm. when building CloudStack from source
> > Hi,
> >
> > Do you see any error like:
> >
> > Proxy error: Could not proxy request
> > /client/api/?command=listIdps&response=json from 192.168.xx.xx:5050 to
> > http://xx.xx.xx.xx:8080.
> > See https://nodejs.org/api/errors.html#errors_common_system_errors for
> > more information (ECONNREFUSED).
> >
> > If so, can you please verify the IP of the Management server, in your
> > initial email you mentioned the address to be:
> > http://192.168.17.225:8080/client/ but the IP placed in .env.local is
> > http://192.168.17.252:8080 (unless the IP was changed)
> >
> > Regards,
> >
> >
> > 
> > From: Wei ZHOU 
> > Sent: December 11, 2023 9:03 AM
> > To: dev@cloudstack.apache.org 
> > Subject: Re: You're in developer mode, please build and run UI using
> > npm. when building CloudStack from source
> >
> > Hi,
> >
> > You can access vmops.log to get some logs.
> >
> >
> > -Wei
> >
> >
> > On Mon, 11 Dec 2023 at 14:49, Ronald Feicht 
> > wrote:
> >
> > > Hi,
> > >
> > > I can now open the UI on port 5050, but when I try to log in I get
> > > "Login Failed".  I had done these steps previously with no error
> > messages:
> > > 1. mvn -Pdeveloper,systemvm clean install
> > > 2. mvn -P developer -pl developer -Ddeploydb
> > > output:
> > > > WARNING: Provided file does not exist:
> > > /opt/cloudstack/developer/../utils/conf/db.properties.override
> > > > WARNING: Provided file does not exist:
> > > /opt/cloudstack/developer/developer-prefill.sql.override
> > > > Initializing database=cloud with host=localhost port=3306
> > > username=cloud password=cloud
> > > > Running query: drop database if exists `cloud`
> > > > Running query: create database `cloud`
> > > > Running query: CREATE USER IF NOT EXISTS cloud@
> `localhost`
> > > identified by 'cloud'
> > > > Running query: CREATE USER IF NOT EXISTS cloud@`%`
> > > identified by 'cloud'
> > > > Running query: GRANT ALL ON cloud.* to 'cloud'@
> `local

Re: new committer Vladimir Petrov

[Wei ZHOU]

Congratulations Vladi !

-Wei

On Tue, 12 Dec 2023 at 10:52, Daan Hoogland  wrote:

> 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: You're in developer mode, please build and run UI using npm. when building CloudStack from source

[Wei ZHOU]

Hi,

You can access vmops.log to get some logs.


-Wei


On Mon, 11 Dec 2023 at 14:49, Ronald Feicht 
wrote:

> Hi,
>
> I can now open the UI on port 5050, but when I try to log in I get
> "Login Failed".  I had done these steps previously with no error messages:
> 1. mvn -Pdeveloper,systemvm clean install
> 2. mvn -P developer -pl developer -Ddeploydb
> output:
> > WARNING: Provided file does not exist:
> /opt/cloudstack/developer/../utils/conf/db.properties.override
> > WARNING: Provided file does not exist:
> /opt/cloudstack/developer/developer-prefill.sql.override
> > Initializing database=cloud with host=localhost port=3306
> username=cloud password=cloud
> > Running query: drop database if exists `cloud`
> > Running query: create database `cloud`
> > Running query: CREATE USER IF NOT EXISTS cloud@`localhost`
> identified by 'cloud'
> > Running query: CREATE USER IF NOT EXISTS cloud@`%`
> identified by 'cloud'
> > Running query: GRANT ALL ON cloud.* to 'cloud'@`localhost`
> > Running query: GRANT ALL ON cloud.* to 'cloud'@`%`
> > Initializing database=cloud_usage with host=localhost
> port=3306 username=cloud password=cloud
> > Running query: drop database if exists `cloud_usage`
> > Running query: create database `cloud_usage`
> > Running query: CREATE USER IF NOT EXISTS cloud@`localhost`
> identified by 'cloud'
> > Running query: CREATE USER IF NOT EXISTS cloud@`%`
> identified by 'cloud'
> > Running query: GRANT ALL ON cloud_usage.* to
> 'cloud'@`localhost`
> > Running query: GRANT ALL ON cloud_usage.* to 'cloud'@`%`
> > Processing SQL file at
> /opt/cloudstack/developer/target/db/create-schema.sql
> > Processing SQL file at
> /opt/cloudstack/developer/target/db/create-schema-premium.sql
> > Processing SQL file at
> /opt/cloudstack/developer/target/db/templates.sql
> > Processing SQL file at
> /opt/cloudstack/developer/developer-prefill.sql
> > Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
> 3. mvn -pl :cloud-client-ui jetty:run
> 4. Then I did what is written here
> https://github.com/apache/cloudstack/tree/main/ui#cloudstack-ui
>  with echo 'CS_URL=http://192.168.17.252:8080' > .env.local
> 5. opened http://192.168.17.252:5050 in Firefox
> 6. entered "admin" for Username and "password" for Password, leaving
> "Domain" empty
> 7. pressed "Login" and received "Login Failed" (firewalld is disabled)
>
> What am I doing wrong?
>
>
> On 12/4/23 15:37, Pearl d'Silva wrote:
> > Hi,
> >
> > Once you've setup CloudStack and built the UI following the steps
> mentionedhttps://github.com/apache/cloudstack/tree/main/ui#cloudstack-ui
> , you'd be able to access the UI at port 5050.
> >
> > Regards,
> > Pearl
> > 
> > From: Ronald Feicht
> > Sent: December 4, 2023 9:32 AM
> > To:dev@cloudstack.apache.org  
> > Subject: You're in developer mode, please build and run UI using npm.
> when building CloudStack from source
> >
> > Hi,
> >
> > I have followed
> >
> https://docs.cloudstack.apache.org/en/4.18.1.0/developersguide/developer_guide.html
> > to build CloudStack 4.19 from source but when I connect to
> > http://192.168.17.225:8080/client/  I only get
> >
> > "You're in developer mode, please build and run UI using npm."
> >
> > I built the UI using npm, but that did not change anything. What am I
> > doing wrong?
> >
> >
> >
> >
> >
>
> --
> *sc synergy GmbH*
> Hilgestrasse 14 | 55294 Bodenheim | Deutschland
> Fon: +49 6135 71691 - 000 | Fax: +49 6135 71691 - 299
> http://www.scsynergy.com | ronald.fei...@scsynergy.com
> Sitz der Gesellschaft Bodenheim, HRB 8830, Amtsgericht Mainz,
> Geschäftsführer: Christian Reichert

Re: 4.20 plans

[Wei ZHOU]

+1

I think it would be good to start as the RM of a minor release to better
understand the role as a RM.

Kind regards,
Wei

On Fri, 8 Dec 2023 at 11:55, Rohit Yadav  wrote:

> Hi João,
>
> Glad to hear about your interests and I will fully support your effort to
> release manage the next major release 4.20.
>
> In fact you can also help us with 4.18.2.0 maintenance release which will
> be relatively low-effort release and in doing so you can learn the
> logistics of release management and access to Github and CI/CD (including
> BO), learning how to update websites (project and docs) and pre/post
> release work on a low-effort basis.
>
> I like your proposed timeline, for 4.20, free by end of May, would allow
> 4-5 months of development work. And I think that would be beneficial for
> the community to have two major releases in a year, with 4.20 release in
> end ~H1 '24, possibly a 4.21 in end ~H2 '24.
>
> I've jotted my notes on becoming a release manager here, that could help
> you:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/%5BDRAFT%5D+How+to+Become+a+CloudStack+Release+Manager
> (I welcome any/all PMCs to review this)
>
>
> Recently, I had also written my thoughts on growing in the community
> generally: (again, PMCs are welcome to review this - for now these are just
> my thoughts)
>
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/%5BDRAFT%5D+How+to+Become+a+Committer
>
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/%5BDRAFT%5D+How+to+Become+a+PMC+Member
>
>
> Regards.
>
> 
> From: João Jandre Paraquetti 
> Sent: Wednesday, December 6, 2023 17:57
> To: dev@cloudstack.apache.org 
> Subject: Re: 4.20 plans
>
> Hello all,
>
> We have quite a few new interesting features prepared for 4.20; there's
> the log4j PR, that we plan on merging as soon as 4.19 is released. We
> also have a few big PRs to be opened for 4.20:
> - Refactoring of the quota UI;
> - New feature to allow users to create custom UI themes and apply them
> to domains, user accounts, and internet DNS themes that are used to
> access the ACS MS;
> - Differential volume snapshots/backups for KVM;
> - And some more extensions that we are preparing here.
>
> Therefore, I'd like to propose myself as the release manager of
> 4.20.0.0, if none objects. I'd be guided by Daniel, who has recently
> been added to the PMC; any others who are willing to help would be
> welcome too. Here's the rough schedule I propose:
>
> - On the third week of May, we freeze the main branch. That means any
> feature must be in by the second week of May. Only accept
> critical/blocker issues until June.
> - As early as possible in June, cut 4.20.0.0 RC1 and further RCs if
> necessary, start/conclude vote, and finish release work.
>
> Best regards,
> João Jandre
>
> On 12/5/23 13:18, Daan Hoogland wrote:
> > devs,
> >
> > Other than we all have great new plans for integrations and other
> > features for 4.20 and we have about 300 issues to solve, There are
> > some platform issues that need addressing. So far I can think of
> > - the outstanding logging PR
> > - java 11 is out of support and we'll need to support a higher version
> >
> > I think we must address these as soon as we have a release.
> > Are there any other issues to address?
> >
>
>
>
>

Re: [VOTE] Adopt Github Discusssions as Users Forum

[Wei ZHOU]

+1 (binding)

I think it is very nice to QA

-Wei


On Mon, 4 Dec 2023 at 09: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
> us...@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.
>
>
>
>

Re: new committer Bryan Lima

[Wei ZHOU]

Congratulations Bryan !

-Wei

On Thu, 30 Nov 2023 at 10:07, Daan Hoogland  wrote:

> 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: new PMC member: Abhishek Kumar

[Wei ZHOU]

Congratulations Abhishek!



在 2023年11月23日星期四，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: Resize root disk from windows vm

[Wei ZHOU]

You can try cloudbase-init for windows. Normally we use cloud-init for
linux vms.

-Wei

On Thu, 28 Sept 2023 at 08:51, Technology Mail 
wrote:

> *Hello,*
>
> I am follow below step, I am not sure am I right or wrong.
>
> 01. Check volume name from vm : https://prnt.sc/2PYYgOn9bQdA
> 02. Then going to volume root : https://prnt.sc/-_vPmrdHDsCz
> 03. Then Resize volume : 100 (previous is 50GB)
> then click *OK*
> 04. now start vm
> 05. I see not change my root disk after login windows vm. But I see
> added 50GB disk is unallocated.
> 06. If I use disk management and extend this unallocated disk, Then
> resize my full root disk.
>
> But my question is :
>
> Can I resize my root disk without step 06? (I want to just I resize my
> root disk using volume from UI and restart vm)
>
> Another question is : same process for linux vm or other?
>
> --
>
> *Thanks & Regards.*
>
> *Support Admin*
>
> 
>
> *Facebook  | Twitter
>  | YouTube
>  | LinkedIn
> *
>
> *Address : *116/1 West Malibagh, D. I. T Road
>
> Dhaka-1217, Bangladesh
>
> *Mob :* +88 01716915504
>
> *Email :* support.ad...@technologyrss.com
>
> *Web :* www.technologyrss.com
>

Re: [DISCUSS] Upgrading Mockito & phasing out powermock

[Wei ZHOU]

Good job Vishesh !

-Wei

On Tue, 26 Sept 2023 at 13:51, Vishesh Jindal 
wrote:

> Hi all,
>
> I wanted to update everyone that powermock is completely removed from main
> branch now. Thank you everyone for helping out on this.
>
> Regards,
> Vishesh
>
> 
> From: Kishan Kavala 
> Sent: Friday, June 9, 2023 1:30 PM
> To: dev@cloudstack.apache.org 
> Subject: RE: [DISCUSS] Upgrading Mockito & phasing out powermock
>
> +1
> Agree with the approach, Vishesh.
>
>
>
>
>
>
>
> -Original Message-
> From: Wei ZHOU 
> Sent: Tuesday, June 6, 2023 8:11 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] Upgrading Mockito & phasing out powermock
>
> lgtm. go ahead Vishesh.
>
> -Wei
>
>
> On Tue, 6 Jun 2023 at 14:17, Vishesh Jindal 
> wrote:
>
> > Hi all,
> >
> > I am working on upgrading Mockito's version & phasing out powermock.
> > For new maven modules, I would request all to use Mockito's mockStatic
> > instead of Powermock.
> >
> > Why?
> > Powermock's last release was on Nov 2, 2020. The project seems to have
> > been abandoned. Powermock has compatibility issues with Mockito's
> > latest version as well.
> >
> > How?
> > The only usage for PowerMock I could see in code was for mocking
> > static methods. Since Mockito v3.4.0, it has the capability to mock
> static methods.
> > I plan to migrate tests to Mockito's mockStatic instead of PowerMock.
> > This will have to be done module by module and will take some time.
> >
> > I have prepared a PR here:
> > https://github.com/apache/cloudstack/pull/7577
> >
> > This PR upgrades mockito from v3.2.4 to v3.12.4 and removes the usage
> > of PowerMock from utils module.
> >
> >
> > Let me know if you have any questions/concerns.
> >
> > Regards,
> > Vishesh
> >
> >
> >
> >
> >
>

[ANNOUNCEMENT] Apache CloudStack LTS Maintenance Release 4.18.1.0

[Wei ZHOU]

The Apache CloudStack project is pleased to announce the release of
CloudStack 4.18.1.0.

The CloudStack 4.18.1.0 release is a maintenance release as part of
its 4.18.x LTS branch and contains around 200 fixes and
improvements since the CloudStack 4.18.0.0 release. Some of the
highlights include:

- Support Managed User Data in AutoScale VM groups
- Support CKS (CloudStack Kubernetes Cluster) in VPC tiers
- Support for VMware 8.0.0.x
- Several Hypervisor (VMware, KVM, XenServer) fixes and improvements
- Several UI fixes and improvements
- Several Network (L2, VXLAN, etc) fixes and improvements
- Several System VM (CPVM, SSVM) fixes and improvements
- Improve Solidfire storage plugin integration on VMware
- Support volume migration in ScaleIO/PowerFlex within and across
ScaleIO/PowerFlex storage clusters
- Volume encryption support for StorPool
- Fix CloudStack upgrade with some MySQL versions
- Fix guest OSes and guest OS mappings in CloudStack database


CloudStack LTS branches are supported for 18 months and will receive
updates for the first 12 months and only security updates in the last
6 months.

Apache CloudStack is an integrated Infrastructure-as-a-Service (IaaS)
software platform that allows users to build feature-rich public and
private cloud environments. CloudStack includes an intuitive user
interface and rich API for managing the compute, networking, software,
and storage resources. The project became an Apache top-level project
in March, 2013.

More information about Apache CloudStack can be found at:
https://cloudstack.apache.org/

# Documentation

What's new in CloudStack 4.18.1.0:
https://docs.cloudstack.apache.org/en/4.18.1.0/releasenotes/about.html

The 4.18.1.0 release notes include a full list of issues fixed, as
well as upgrade instructions from previous versions of Apache
CloudStack, and can be found at:
https://docs.cloudstack.apache.org/en/4.18.1.0/releasenotes/

The official installation, administration, and API documentation for
each of the releases are available on our documentation page:
https://docs.cloudstack.apache.org/

# Downloads

The official source code for the 4.18.1.0 release can be downloaded
from our downloads page:
https://cloudstack.apache.org/downloads.html

In addition to the official source code release, individual
contributors have also made convenience binaries available on the
Apache CloudStack download page, and can be found at:

https://download.cloudstack.org/el/7/
https://download.cloudstack.org/el/8/
https://download.cloudstack.org/ubuntu/dists/
https://www.shapeblue.com/packages/

[VOTE][RESULT] Apache CloudStack 4.18.1.0 (RC3)

[Wei ZHOU]

Hi all,

After more than 72hrs the vote for CloudStack 4.18.1.0 *passes* with
5 PMC + 1 non-PMC votes.

+1 (PMC / binding)
Rohit Yadav
Nux (Lucian)
Boris Stoyanov
Nicolas Vazquez
Wei Zhou

+1 (non binding)
Harikrishna Patnala

0
none

-1
none

Thanks to everyone participating.

I will now prepare the release announcement to go out after 24 hours to
give the mirrors time to catch up.

-Wei


On Thu, 7 Sept 2023 at 10:34, Wei ZHOU  wrote:

> Hi all,
>
> I've created a 4.18.1.0-RC3, with the following artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230907T0850
> Commit: 4bdff06acd3630180f85ffe2f54add972607bbb4
>
> Source release (checksums and signatures are available at the following
> location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/
>
> PGP release keys (signed using 1503DFE7C8226103):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> 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)
>

Re: [VOTE] Apache CloudStack 4.18.1.0 (RC3)

[Wei ZHOU]

+1 (binding)

- Kicked trillian tests with various combinations of management server OS
and hypervisors. all looks ok.
- Tested manually on some environments (different OSes, NFS, advanced zone
w/wo SG, vlan/vxlan isolation)

-Wei



On Thu, 7 Sept 2023 at 10:34, Wei ZHOU  wrote:

> Hi all,
>
> I've created a 4.18.1.0-RC3, with the following artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230907T0850
> Commit: 4bdff06acd3630180f85ffe2f54add972607bbb4
>
> Source release (checksums and signatures are available at the following
> location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/
>
> PGP release keys (signed using 1503DFE7C8226103):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> 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)
>

Re: [VOTE] Apache CloudStack 4.18.1.0 (RC3)

[Wei ZHOU]

Hi all,

This vote will be closed on Tuesday, 12th September.

Please feel free to share your thoughts, testing results, issues, etc.
Thanks !

-Wei

On Thu, 7 Sept 2023 at 10:34, Wei ZHOU  wrote:

> Hi all,
>
> I've created a 4.18.1.0-RC3, with the following artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230907T0850
> Commit: 4bdff06acd3630180f85ffe2f54add972607bbb4
>
> Source release (checksums and signatures are available at the following
> location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/
>
> PGP release keys (signed using 1503DFE7C8226103):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> 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)
>

Re: [VOTE] Apache CloudStack 4.18.1.0 (RC3)

[Wei ZHOU]

Hi all,

You can find the (unofficial) packages at
http://download.cloudstack.org/testing/4.18.1.0-RC20230907T0850/ for your
convenience.

Kind regards
Wei




On Thu, 7 Sept 2023 at 10:34, Wei ZHOU  wrote:

> Hi all,
>
> I've created a 4.18.1.0-RC3, with the following artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230907T0850
> Commit: 4bdff06acd3630180f85ffe2f54add972607bbb4
>
> Source release (checksums and signatures are available at the following
> location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/
>
> PGP release keys (signed using 1503DFE7C8226103):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> 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)
>

[VOTE] Apache CloudStack 4.18.1.0 (RC3)

[Wei ZHOU]

Hi all,

I've created a 4.18.1.0-RC3, with the following artifacts up for a vote:

Git Branch and Commit SH:
https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230907T0850
Commit: 4bdff06acd3630180f85ffe2f54add972607bbb4

Source release (checksums and signatures are available at the following
location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/

PGP release keys (signed using 1503DFE7C8226103):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

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)

Re: [VOTE] Apache CloudStack 4.18.1.0 (RC2)

[Wei ZHOU]

Hi all,

Thanks a lot for your testing, Rohit, Hari, Lucian, Nicolas and Bobby.

Unfortunately Rohit found a critical issue that live migration failed
between kvm hosts with local storage pools:
https://github.com/apache/cloudstack/issues/7942
We have proposed a fix: https://github.com/apache/cloudstack/pull/7945

I will create RC3 when the fix is verified and merged. The issue impacts
kvm hosts with local storage only.

-Wei


On Fri, 1 Sept 2023 at 09:39, Wei ZHOU  wrote:

> Hi all,
>
> I've created a 4.18.1.0-RC2, with the following artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230901T0817
> Commit: 0e7f7d42f0ec68a360fafa7de21ea06577ed032c
>
> Source release (checksums and signatures are available at the following
> location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/
>
> PGP release keys (signed using 1503DFE7C8226103):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> 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)
>

Re: [VOTE] Apache CloudStack 4.18.1.0 (RC2)

[Wei ZHOU]

+1 (binding)

Tested the upgrade from 4.16.1, 4.17.2 and 4.18.0, checked guest OS mappings
Manually tested vm operations with various OSes: rocky8, alma8, ubuntu22,
vmware8.0c
Kicked smoke tests with various OSes: centos7, rocky8, ubuntu22,
vmware70u3, vmware80. All look ok, except 2 test failures with CKS which we
have seen in some PRs.

-Wei

On Fri, 1 Sept 2023 at 09:39, Wei ZHOU  wrote:

> Hi all,
>
> I've created a 4.18.1.0-RC2, with the following artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230901T0817
> Commit: 0e7f7d42f0ec68a360fafa7de21ea06577ed032c
>
> Source release (checksums and signatures are available at the following
> location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/
>
> PGP release keys (signed using 1503DFE7C8226103):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> 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)
>

Re: [VOTE] Apache CloudStack 4.18.1.0 (RC2)

[Wei ZHOU]

Hi all,

Just a reminder, the vote will be closed tomorrow.

Kind regards,
Wei

On Fri, 1 Sept 2023 at 09:39, Wei ZHOU  wrote:

> Hi all,
>
> I've created a 4.18.1.0-RC2, with the following artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230901T0817
> Commit: 0e7f7d42f0ec68a360fafa7de21ea06577ed032c
>
> Source release (checksums and signatures are available at the following
> location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/
>
> PGP release keys (signed using 1503DFE7C8226103):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> 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)
>

Re: [VOTE] Apache CloudStack 4.18.1.0 (RC2)

[Wei ZHOU]

Hi all,

You can find the (unofficial) packages at
http://download.cloudstack.org/testing/4.18.1.0-RC20230901T0817/ for your
convenience.

Kind regards
Wei


On Fri, 1 Sept 2023 at 09:39, Wei ZHOU  wrote:

> Hi all,
>
> I've created a 4.18.1.0-RC2, with the following artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230901T0817
> Commit: 0e7f7d42f0ec68a360fafa7de21ea06577ed032c
>
> Source release (checksums and signatures are available at the following
> location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/
>
> PGP release keys (signed using 1503DFE7C8226103):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> 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)
>

[VOTE] Apache CloudStack 4.18.1.0 (RC2)

[Wei ZHOU]

Hi all,

I've created a 4.18.1.0-RC2, with the following artifacts up for a vote:

Git Branch and Commit SH:
https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230901T0817
Commit: 0e7f7d42f0ec68a360fafa7de21ea06577ed032c

Source release (checksums and signatures are available at the following
location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/

PGP release keys (signed using 1503DFE7C8226103):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

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)

Re: [VOTE] Apache Cloudstack 4.18.1.0

[Wei ZHOU]

Hi all,

This vote has to be closed, as we found a critical issue that the
direct-download template cannot be registered for KVM.
Please get more information at
https://github.com/apache/cloudstack/issues/7929

-Wei


On Tue, 29 Aug 2023 at 09:56, Wei ZHOU  wrote:

> Hi all,
>
> I've created a 4.18.1.0-RC1, with the following artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230828T2026
> Commit: ff402faff06667e6e819eaee037400ed2005d5d2
>
> Source release (checksums and signatures are available at the following
> location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/
>
> PGP release keys (signed using 1503DFE7C8226103):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> 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)
>

Re: [VOTE] Apache Cloudstack 4.18.1.0

[Wei ZHOU]

Hi all,

Packages have been built and uploaded to
https://download.cloudstack.org/testing/4.18.1.0-RC20230828T2026/

-Wei


On Tue, 29 Aug 2023 at 09:56, Wei ZHOU  wrote:

> Hi all,
>
> I've created a 4.18.1.0-RC1, with the following artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230828T2026
> Commit: ff402faff06667e6e819eaee037400ed2005d5d2
>
> Source release (checksums and signatures are available at the following
> location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/
>
> PGP release keys (signed using 1503DFE7C8226103):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> 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)
>

[VOTE] Apache Cloudstack 4.18.1.0

[Wei ZHOU]

Hi all,

I've created a 4.18.1.0-RC1, with the following artifacts up for a vote:

Git Branch and Commit SH:
https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230828T2026
Commit: ff402faff06667e6e819eaee037400ed2005d5d2

Source release (checksums and signatures are available at the following
location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/

PGP release keys (signed using 1503DFE7C8226103):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

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)

Re: [PROPOSE] ACS 4.18.1.0 release

[Wei ZHOU]

Hi all,

The code freeze date of 4.18.1.0 release is due.

Please find all closed issues and merged PRs at
https://github.com/apache/cloudstack/issues?q=is%3Aissue+milestone%3A4.18.1.0+is%3Aclosed
https://github.com/apache/cloudstack/pulls?page=1&q=is%3Apr+milestone%3A4.18.1.0+is%3Aclosed

I will create RC1 and build packages for you to test.

-Wei

On Mon, 21 Aug 2023 at 13:48, Wei ZHOU  wrote:

> Hi all,
>
> In the last weeks, we have merged a few bug fixes into the 4.18 branch. We
> are still working on remaining bug fixes and reviewing pull requests.
>
> 22 pull requests are open for review:
> https://github.com/apache/cloudstack/pulls?q=is%3Aopen+is%3Apr+milestone%3A4.18.1.0
>
> 51 issues are open (including 2 critical , 15 major, 33 minor issues):
> https://github.com/apache/cloudstack/issues?q=is%3Aopen+is%3Aissue+milestone%3A4.18.1.0
>
> *The code freeze time of 4.18.1.0 will be 12:00pm UTC (1pm BST, 2pm CEST),
> 28th August*.  The open pull requests and issues after code
> freeze will be moved to 4.18.2.0 milestone.
>
> -Wei
>
>
>
> On Wed, 2 Aug 2023 at 03:22, Wei ZHOU  wrote:
>
>> Hi all,
>>
>> Here is an update of Apache CloudStack 4.18.1.0 release:
>>
>> There are some open PRs and issues on github:
>>
>> 37 pull requests are open for review:
>> https://github.com/apache/cloudstack/pulls?q=is%3Aopen+is%3Apr+milestone%3A4.18.1.0
>>
>> 66 issues are open (including 1 BLOCKER, 1 critical , 18 major, 39 minor
>> issues):
>> https://github.com/apache/cloudstack/issues?q=is%3Aopen+is%3Aissue+milestone%3A4.18.1.0
>>
>>
>> We are busy with them. The processes need to be postponed for 2-4 weeks.
>>
>>
>> -Wei
>>
>>
>>
>>
>> On Thu, 4 May 2023 at 10:34, Wei ZHOU  wrote:
>>
>>> Hi all,
>>>
>>> Currently CloudStack 4.18.0.0 is the latest LTS release. There are some
>>> bugs and pull requests with 4.18.0.0 [1], including the fix for the upgrade
>>> issue if users use MySQL 5.6 and 5.7.
>>>
>>> I would like to propose the release of 4.18.1.0 and the timeline
>>>
>>> - from now till the end of July (3 months): accept bug fixes and minor
>>> improvements [2]
>>> - first week in Aug: stablisation efforts, accept only blocker and
>>> critical bug fixes.
>>> - Aug: start cutting RCs, vote and finish release work.
>>>
>>> I will push myself as the release manager (RM) of 4.18.1.0, if nobody
>>> objects.
>>> In case anyone wants to include a bug fix or a pull request in 4.18.1.0
>>> milestone, please mention me (weizhouapache) on github.
>>>
>>> [1] https://github.com/apache/cloudstack/milestone/27
>>> [2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS
>>>
>>>
>>> Any suggestions ?
>>>
>>> Kind regards,
>>> Wei
>>>
>>

Re: Unable to add host error ACS

[Wei ZHOU]

Hi,

If libvirtd does not work, please fix it before adding the host to
cloudstack.

You can check the output of `systemctl status libvirtd` or `journalctl -xeu
libvirtd`


-Wei

On Mon, 28 Aug 2023 at 08:56, Technology Mail 
wrote:

> Thank you so much!,
> I followed your mansion step but error is same, Please see my MGMT
> server error like below:
>
>

Re: new committer: John Bampton

[Wei ZHOU]

Congratulations John !

-Wei

On Fri, 25 Aug 2023 at 12:51, Daan Hoogland  wrote:

> The Project Management Committee (PMC) for Apache CloudStack
> has invited Jown Bampton to become a committer and we are pleased
> to announce that they have accepted.
>
> John is mostly active on CI and build specific issues.
>
>
> please join me in welcoming John to the project
>
> --
> Daan
>

Re: new committer: Sina Kashipazha

[Wei ZHOU]

Congratulations Sina !

-Wei

On Fri, 25 Aug 2023 at 12:53, Daan Hoogland  wrote:

> The Project Management Committee (PMC) for Apache [PROJECT]
>
> has invited Sina Kashipazha to become a committer and we are pleased
> to announce that they have accepted.
>
> Sina has been active as a contributor in several ways; code, testing,
> talks, documentation
>
> Please join me in welcoming Sina
>

Re: new PMC member: Daniel Salvador

[Wei ZHOU]

Congratulations Daniel !

-Wei

On Fri, 25 Aug 2023 at 12:56, Daan Hoogland  wrote:

> The Project Management Committee (PMC) for Apache [PROJECT]
> has invited Daniel Salvador to become a PMC member and we are pleased
> to announce that they have accepted.
>
> Daniel has contributed in the past and has shown effort to make the
> project run smoothly
>
> please join me in congratulating Daniel
>

Re: [PROPOSE] ACS 4.18.1.0 release

[Wei ZHOU]

Hi all,

In the last weeks, we have merged a few bug fixes into the 4.18 branch. We
are still working on remaining bug fixes and reviewing pull requests.

22 pull requests are open for review:
https://github.com/apache/cloudstack/pulls?q=is%3Aopen+is%3Apr+milestone%3A4.18.1.0

51 issues are open (including 2 critical , 15 major, 33 minor issues):
https://github.com/apache/cloudstack/issues?q=is%3Aopen+is%3Aissue+milestone%3A4.18.1.0

*The code freeze time of 4.18.1.0 will be 12:00pm UTC (1pm BST, 2pm CEST),
28th August*.  The open pull requests and issues after code freeze will be
moved to 4.18.2.0 milestone.

-Wei



On Wed, 2 Aug 2023 at 03:22, Wei ZHOU  wrote:

> Hi all,
>
> Here is an update of Apache CloudStack 4.18.1.0 release:
>
> There are some open PRs and issues on github:
>
> 37 pull requests are open for review:
> https://github.com/apache/cloudstack/pulls?q=is%3Aopen+is%3Apr+milestone%3A4.18.1.0
>
> 66 issues are open (including 1 BLOCKER, 1 critical , 18 major, 39 minor
> issues):
> https://github.com/apache/cloudstack/issues?q=is%3Aopen+is%3Aissue+milestone%3A4.18.1.0
>
>
> We are busy with them. The processes need to be postponed for 2-4 weeks.
>
>
> -Wei
>
>
>
>
> On Thu, 4 May 2023 at 10:34, Wei ZHOU  wrote:
>
>> Hi all,
>>
>> Currently CloudStack 4.18.0.0 is the latest LTS release. There are some
>> bugs and pull requests with 4.18.0.0 [1], including the fix for the upgrade
>> issue if users use MySQL 5.6 and 5.7.
>>
>> I would like to propose the release of 4.18.1.0 and the timeline
>>
>> - from now till the end of July (3 months): accept bug fixes and minor
>> improvements [2]
>> - first week in Aug: stablisation efforts, accept only blocker and
>> critical bug fixes.
>> - Aug: start cutting RCs, vote and finish release work.
>>
>> I will push myself as the release manager (RM) of 4.18.1.0, if nobody
>> objects.
>> In case anyone wants to include a bug fix or a pull request in 4.18.1.0
>> milestone, please mention me (weizhouapache) on github.
>>
>> [1] https://github.com/apache/cloudstack/milestone/27
>> [2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS
>>
>>
>> Any suggestions ?
>>
>> Kind regards,
>> Wei
>>
>

Re: [PROPOSE] ACS 4.18.1.0 release

[Wei ZHOU]

Hi all,

Here is an update of Apache CloudStack 4.18.1.0 release:

There are some open PRs and issues on github:

37 pull requests are open for review:
https://github.com/apache/cloudstack/pulls?q=is%3Aopen+is%3Apr+milestone%3A4.18.1.0

66 issues are open (including 1 BLOCKER, 1 critical , 18 major, 39 minor
issues):
https://github.com/apache/cloudstack/issues?q=is%3Aopen+is%3Aissue+milestone%3A4.18.1.0


We are busy with them. The processes need to be postponed for 2-4 weeks.


-Wei




On Thu, 4 May 2023 at 10:34, Wei ZHOU  wrote:

> Hi all,
>
> Currently CloudStack 4.18.0.0 is the latest LTS release. There are some
> bugs and pull requests with 4.18.0.0 [1], including the fix for the upgrade
> issue if users use MySQL 5.6 and 5.7.
>
> I would like to propose the release of 4.18.1.0 and the timeline
>
> - from now till the end of July (3 months): accept bug fixes and minor
> improvements [2]
> - first week in Aug: stablisation efforts, accept only blocker and
> critical bug fixes.
> - Aug: start cutting RCs, vote and finish release work.
>
> I will push myself as the release manager (RM) of 4.18.1.0, if nobody
> objects.
> In case anyone wants to include a bug fix or a pull request in 4.18.1.0
> milestone, please mention me (weizhouapache) on github.
>
> [1] https://github.com/apache/cloudstack/milestone/27
> [2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS
>
>
> Any suggestions ?
>
> Kind regards,
> Wei
>

Re: [DISCUSS] Upgrading Mockito & phasing out powermock

[Wei ZHOU]

lgtm. go ahead Vishesh.

-Wei


On Tue, 6 Jun 2023 at 14:17, Vishesh Jindal 
wrote:

> Hi all,
>
> I am working on upgrading Mockito's version & phasing out powermock. For
> new maven modules, I would request all to use Mockito's mockStatic instead
> of Powermock.
>
> Why?
> Powermock's last release was on Nov 2, 2020. The project seems to have
> been abandoned. Powermock has compatibility issues with Mockito's latest
> version as well.
>
> How?
> The only usage for PowerMock I could see in code was for mocking static
> methods. Since Mockito v3.4.0, it has the capability to mock static methods.
> I plan to migrate tests to Mockito's mockStatic instead of PowerMock. This
> will have to be done module by module and will take some time.
>
> I have prepared a PR here: https://github.com/apache/cloudstack/pull/7577
>
> This PR upgrades mockito from v3.2.4 to v3.12.4 and removes the usage of
> PowerMock from utils module.
>
>
> Let me know if you have any questions/concerns.
>
> Regards,
> Vishesh
>
>
>
>
>

Re: Kubernetes Cluster goes to error state

[Wei ZHOU]

Hi,

I have just tested CKS on rocky8, it worked well.

ISO: https://download.cloudstack.org/cks/setup-1.26.0.iso
Offering: 2CPU, 2GB RAM
Network: new isolated network
HA: no

-Wei

On Fri, 2 Jun 2023 at 15:47, Stanley Burkee 
wrote:

> Hi Guys,
>
> After making some changes to the network side. Now I am seeing the
> following error on the GUI
>
> *Failed to setup Kubernetes cluster : k8test in usable state as unable to
> provision API endpoint for the cluster*
>
> *K8test is the name of the cluster I have provisioned.*
>
> Any idea why I am seeing this error ?
>
> Thanks for your help.
>
> Regards
>
> Stanley Burkee
>
> On Fri, Jun 2, 2023 at 10:02 AM Katie F.  wrote:
>
> > On Thu, Jun 1, Reiwa 5 at 1:56 PM Stanley Burkee <
> stanley.bur...@gmail.com
> > >
> > wrote:
> >
> > > Hi Wei,
> > >
> > > Apologies for the late response.
> > >
> > > The hypervisor I am using is KVM( Rocky Linux 8.7). The ISO I am using
> is
> > > Cloudstack Kubernetes ISO v 1.26..
> > >
> > > The ISO OS details are given below
> > >
> > >
> > >
> > > Thank you!
> > >
> > >
> > >
> > >
> > >
> > > *Cloudstack Release 4.18.0 Wed 28 Dec 2022 09:45:19 AM
> > > UTCPRETTY_NAME="Debian GNU/Linux 11 (bullseye)"NAME="Debian
> > > GNU/Linux"VERSION_ID="11"VERSION="11
> > > (bullseye)"VERSION_CODENAME=bullseyeID=debianHOME_URL="
> > > https://www.debian.org/
> > > <https://www.debian.org/>"SUPPORT_URL="https://www.debian.org/support
> > > <https://www.debian.org/support>"BUG_REPORT_URL="
> > https://bugs.debian.org/
> > > <https://bugs.debian.org/>"*
> > >
> > > The screenshot links are given below
> > >
> > >
> > >
> >
> https://drive.google.com/file/d/14lsRuwOvMrbhfJ3X6IniNnU6VuVFTK1r/view?usp=sharing
> > >
> > > Please let me know if anything else is required from my side.
> > >
> > >
> > > Regards
> > >
> > >
> > > Stanley Burkee
> > >
> > >
> > > On Thu, Jun 1, 2023 at 5:36 PM Wei ZHOU  wrote:
> > >
> > > > Hi,
> > > >
> > > > It would be good to share more details. For example, the OS
> > distribution
> > > > and version, Kubernetes version, cni/crictl/weavenet/dashboard
> > versions,
> > > > etc
> > > >
> > > > -Wei
> > > >
> > > > On Thu, 1 Jun 2023 at 13:57, Stanley Burkee <
> stanley.bur...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi Guys,
> > > > >
> > > > > Whenever I am trying to create a Kubernetes cluster, it goes to an
> > > error
> > > > > state. Upon further troubleshooting the issue, I am getting the
> > > following
> > > > > error in the logs
> > > > >
> > > > >
> > > > > *2023-06-01 11:29:34,934 WARN  [c.c.k.c.u.KubernetesClusterUtil]
> > > > > (API-Job-Executor-74:ctx-d6a69feb job-3792 ctx-73da73b0)
> > > (logid:94112eed)
> > > > > API endpoint for Kubernetes cluster : k8s2 not
> > > > > availablejavax.net.ssl.SSLHandshakeException: Remote host
> terminated
> > > the
> > > > > handshake*
> > > > >
> > > > > I am using Cloudstack 4.18 on KVM.
> > > > >
> > > > > Any help would be appreciated.
> > > > >
> > > > > Thanks.
> > > > >
> > > > > Regards
> > > > >
> > > > > Stanley Burkee
> > > > >
> > > >
> > >
> > --
> > Kathleen Foos
> >
>

Re: Kubernetes Cluster goes to error state

[Wei ZHOU]

Hi,

Did you build the K8s ISO or download from
https://download.cloudstack.org/cks/ ?

-Wei

On Thu, 1 Jun 2023 at 19:57, Stanley Burkee 
wrote:

> Hi Wei,
>
> Apologies for the late response.
>
> The hypervisor I am using is KVM( Rocky Linux 8.7). The ISO I am using is
> Cloudstack Kubernetes ISO v 1.26..
>
> The ISO OS details are given below
>
>
>
>
>
>
>
>
>
> *Cloudstack Release 4.18.0 Wed 28 Dec 2022 09:45:19 AM
> UTCPRETTY_NAME="Debian GNU/Linux 11 (bullseye)"NAME="Debian
> GNU/Linux"VERSION_ID="11"VERSION="11
> (bullseye)"VERSION_CODENAME=bullseyeID=debianHOME_URL="
> https://www.debian.org/
> <https://www.debian.org/>"SUPPORT_URL="https://www.debian.org/support
> <https://www.debian.org/support>"BUG_REPORT_URL="https://bugs.debian.org/
> <https://bugs.debian.org/>"*
>
> The screenshot links are given below
>
>
> https://drive.google.com/file/d/14lsRuwOvMrbhfJ3X6IniNnU6VuVFTK1r/view?usp=sharing
>
> Please let me know if anything else is required from my side.
>
>
> Regards
>
>
> Stanley Burkee
>
>
> On Thu, Jun 1, 2023 at 5:36 PM Wei ZHOU  wrote:
>
> > Hi,
> >
> > It would be good to share more details. For example, the OS distribution
> > and version, Kubernetes version, cni/crictl/weavenet/dashboard versions,
> > etc
> >
> > -Wei
> >
> > On Thu, 1 Jun 2023 at 13:57, Stanley Burkee 
> > wrote:
> >
> > > Hi Guys,
> > >
> > > Whenever I am trying to create a Kubernetes cluster, it goes to an
> error
> > > state. Upon further troubleshooting the issue, I am getting the
> following
> > > error in the logs
> > >
> > >
> > > *2023-06-01 11:29:34,934 WARN  [c.c.k.c.u.KubernetesClusterUtil]
> > > (API-Job-Executor-74:ctx-d6a69feb job-3792 ctx-73da73b0)
> (logid:94112eed)
> > > API endpoint for Kubernetes cluster : k8s2 not
> > > availablejavax.net.ssl.SSLHandshakeException: Remote host terminated
> the
> > > handshake*
> > >
> > > I am using Cloudstack 4.18 on KVM.
> > >
> > > Any help would be appreciated.
> > >
> > > Thanks.
> > >
> > > Regards
> > >
> > > Stanley Burkee
> > >
> >
>

Re: Kubernetes Cluster goes to error state

[Wei ZHOU]

Hi,

It would be good to share more details. For example, the OS distribution
and version, Kubernetes version, cni/crictl/weavenet/dashboard versions, etc

-Wei

On Thu, 1 Jun 2023 at 13:57, Stanley Burkee 
wrote:

> Hi Guys,
>
> Whenever I am trying to create a Kubernetes cluster, it goes to an error
> state. Upon further troubleshooting the issue, I am getting the following
> error in the logs
>
>
> *2023-06-01 11:29:34,934 WARN  [c.c.k.c.u.KubernetesClusterUtil]
> (API-Job-Executor-74:ctx-d6a69feb job-3792 ctx-73da73b0) (logid:94112eed)
> API endpoint for Kubernetes cluster : k8s2 not
> availablejavax.net.ssl.SSLHandshakeException: Remote host terminated the
> handshake*
>
> I am using Cloudstack 4.18 on KVM.
>
> Any help would be appreciated.
>
> Thanks.
>
> Regards
>
> Stanley Burkee
>

Re: Introductions

[Wei ZHOU]

Welcome Ayush !

-Wei

On Fri, 26 May 2023 at 06:53, Ayush Pandey  wrote:

> Hi Everyone,
>
> I am Ayush Pandey, joining the community for a project as part of Google
> Summer of code 2023. I will be working with my mentor Nicolas Vazquez on
> "Extend Import-Export Instances to the KVM Hypervisor"
> https://github.com/apache/cloudstack/issues/7127
>
> I am really looking forward to collaborating with and learning from this
> amazing community.
>
> Thank you,
> Regards,
> Ayush Pandey
>

Re: [VOTE] CloudStack Project Blog Migration

[Wei ZHOU]

+1 (binding)

Great job @Rohit Yadav 

-Wei



On Wed, 17 May 2023 at 10:58, Rohit Yadav  wrote:

> All,
>
> The ASF-infra had announced a hard deadline [0][1] to decommission our
> project’s Roller based blog [3] on the 31st May 2023.
>
> For the blog migration, ASF-infra has exported CloudStack blog posts
> from the current Roller’s database-backed infra to markdown files.
> These were put together in cloudstack-www repository’s
> docusauras-staging branch [2] with Docusauras used as a
> static-site-generator and a GitHub Actions workflow to automate
> publishing a staging site for your testing and review [4].
>
> The staging site that migrates both the website and blog isn’t
> completely ready to meet the hard deadline, so this vote is proposed
> for only migrating the blog before the deadline and continue efforts
> to migrate to a new website [2][4] when we're ready in the near
> future.
>
> The following is put for voting:
>
> 1. By the end of 31st May ’23, ASF-infra will decommission the project
> blog at https://blogs.apache.org/cloudstack and for now we proceed
> with only the blog migration before this deadline.
>
> 2. The old blog URL/pages from
> https://blogs.apache.org/cloudstack/ will be
> redirected to https://cloudstack.apache.org/blog/.
> This will be done by the ASF-infra.
>
> 3. The blog content is copied to the "content/blog" directory of the
> asf-site branch in the https://github.com/apache/cloudstack-www
> repository [6], published at https://cloudstack.apache.org/blog/.
>
> The vote will be open until we reach a lazy consensus.
>
> 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 the reason why)
>
> [0] https://markmail.org/message/o5pse33cgriebsrg
> [1] https://lists.apache.org/thread/hfhzochhmqhd32tclgc47d5nk90jxmb2
> [2] https://github.com/apache/cloudstack-www/tree/docusaurus-staging/blog
> [3] https://blogs.apache.org/cloudstack/
> [4] https://cloudstack.staged.apache.org/
> [5] https://cloudstack.apache.org/bylaws.html
> [6]
> https://github.com/apache/cloudstack-www/commit/651ec3ad9a3f524a5ce1bb9d6943856f57e638e3
>
> Regards.
>

Re: [GitHub] [cloudstack] hpepper opened a new issue, #7533: Cloudstack 4.18 HTTP 503 Error on Ubuntu 22.04

[Wei ZHOU]

Hi,

Have you setup the database for cloudstack?

cloudstack-setup-databases

-Wei



On Sunday, 14 May 2023, hpepper (via GitHub)  wrote:

>
> hpepper opened a new issue, #7533:
> URL: https://github.com/apache/cloudstack/issues/7533
>
>
># ISSUE TYPE
>
> * Other
>
># COMPONENT NAME
>
>Web access fails
>
># CLOUDSTACK VERSION
>
>* cloudstack-management: 4.18.0.0
>
># CONFIGURATION
>
>
># OS / ENVIRONMENT
>
>* OS: Ubuntu 22.04.2 LTS
>* mysqld --version: /usr/sbin/mysqld  Ver 8.0.33-0ubuntu0.22.04.1 for
> Linux on x86_64 ((Ubuntu))
>
>
>
># SUMMARY
>
>Did a new installation of cloudstack on a new minimal Ubuntu
> installation.
>Following the instructions in [4.18.0.0 installation](http://docs.
> cloudstack.apache.org/en/4.18.0.0/installguide/index.html#
> general-installation)
>
>HTTP ERROR 503 Service Unavailable
>
>
>URI: | /client/
>-- | --
>503
>Service Unavailable
>-
>
>##
>
>* minimal install of Ubuntu 22.04
>* Install cloudstack as per the manuel, except for the iptables part
>
>~~~
>May 13 15:36:51 cloudstack java[6754]: INFO  
> [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> (main:null) (logid:) Loading module context [system] from URL
> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.>
>May 13 15:36:51 cloudstack java[6754]: INFO  
> [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> (main:null) (logid:) Loading module context [system] from URL
> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.>
>May 13 15:36:51 cloudstack java[6754]: INFO  
> [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> (main:null) (logid:) Loading module context [system] from URL
> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.>
>May 13 15:36:51 cloudstack java[6754]: INFO  
> [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> (main:null) (logid:) Loading module context [system] from URL
> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.>
>May 13 15:36:51 cloudstack java[6754]: WARNING: An illegal reflective
> access operation has occurred
>May 13 15:36:51 cloudstack java[6754]: WARNING: Illegal reflective
> access by net.sf.cglib.core.ReflectUtils$1 (file:/usr/share/cloudstack-
> management/lib/cloudstack-4.18.0.0.jar) to method java.lang.ClassLoader.>
>May 13 15:36:51 cloudstack java[6754]: WARNING: Please consider
> reporting this to the maintainers of net.sf.cglib.core.ReflectUtils$1
>May 13 15:36:51 cloudstack java[6754]: WARNING: Use
> --illegal-access=warn to enable warnings of further illegal reflective
> access operations
>May 13 15:36:51 cloudstack java[6754]: WARNING: All illegal access
> operations will be denied in a future release
>May 13 15:36:52 cloudstack java[6754]: INFO  [c.c.u.d.T.Transaction]
> (main:null) (logid:) Is Data Base High Availiability enabled? Ans : false
>May 13 15:36:56 cloudstack java[6754]: ERROR [c.c.u.d.Merovingian2]
> (main:null) (logid:) Unable to get a new db connection
>May 13 15:36:56 cloudstack java[6754]: java.sql.
> SQLNonTransientConnectionException: Could not create connection to
> database server. Attempted reconnect 3 times. Giving up.
>May 13 15:36:56 cloudstack java[6754]: at
> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(
> SQLError.java:110)
>May 13 15:36:56 cloudstack java[6754]: at
> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
>May 13 15:36:56 cloudstack java[6754]: at
> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:89)
>~~~
>
># EXPECTED RESULTS
>
>Getting access to the Cloudstack web UI.
>
># ACTUAL RESULTS
>
>~~~
>HTTP ERROR 503 Service Unavailable
>
>
>URI: | /client/
>-- | --
>503
>Service Unavailable
>-
>~~~
>
>~~~
>systemctl status cloudstack-management
>● cloudstack-management.service - CloudStack Management Server
> Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
> enabled; vendor preset: enabled)
> Active: active (running) since Sat 2023-05-13 23:45:02 UTC; 1h
> 4min ago
>   Main PID: 881 (java)
>  Tasks: 37 (limit: 4571)
> Memory: 1.1G
>CPU: 50.660s
> CGroup: /system.slice/cloudstack-management.service
> └─881 /usr/bin/java -Djava.security.properties=/
> etc/cloudstack/management/java.security.ciphers -Djava.awt.headless=true
> -Dcom.sun.management.jmxremote=false -Xmx2G -XX:+UseParallelGC
> -XX:MaxGCPaus>
>
>May 13 23:45:23 cloudstack java[881]: at org.eclipse.jetty.util.
> component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>May 13 23:45:23 cloudstack java[881]: at org.eclipse.jetty.util.
> component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>May 13 23:45:23 cloudstack java[881]: at
> org.eclipse.jetty.server.Server.start(Server.java:423)
>May 13

Re: [PROPOSE] ACS 4.18.1.0 release

[Wei ZHOU]

Thanks all.

Since there is no objection, I will act as the 4.18.1.0 release manager.

I have noticed many bug fix PRs are targeted to the main branch, if the
authors want to merge it into 4.18.1.0, please rebase with 4.18 and change
the target branch to 4.18. All commits in the 4.18 branch will be
fast-forward merged into the main branch.

Thanks in advance for all your work on 4.18.1.0 !

Kind regards,
Wei



On Sat, 6 May 2023 at 07:57, Suresh Kumar Anaparti <
sureshkumar.anapa...@gmail.com> wrote:

> +1, Good luck Wei!
>
> Regards,
> Suresh
>
> On Thu, May 4, 2023 at 2:04 PM Wei ZHOU  wrote:
> >
> > Hi all,
> >
> > Currently CloudStack 4.18.0.0 is the latest LTS release. There are some
> > bugs and pull requests with 4.18.0.0 [1], including the fix for the
> upgrade
> > issue if users use MySQL 5.6 and 5.7.
> >
> > I would like to propose the release of 4.18.1.0 and the timeline
> >
> > - from now till the end of July (3 months): accept bug fixes and minor
> > improvements [2]
> > - first week in Aug: stablisation efforts, accept only blocker and
> critical
> > bug fixes.
> > - Aug: start cutting RCs, vote and finish release work.
> >
> > I will push myself as the release manager (RM) of 4.18.1.0, if nobody
> > objects.
> > In case anyone wants to include a bug fix or a pull request in 4.18.1.0
> > milestone, please mention me (weizhouapache) on github.
> >
> > [1] https://github.com/apache/cloudstack/milestone/27
> > [2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS
> >
> >
> > Any suggestions ?
> >
> > Kind regards,
> > Wei
>

Re: [ANNOUNCE] Cloudmonkey 6.3.0 Release

[Wei ZHOU]

Great news.

Great job Bobby! Thanks.

-Wei

On Tuesday, 9 May 2023, Boris Stoyanov  wrote:

> We are pleased to announce the release of Apache CloudStack Cloudmonkey
> 6.3.0, the latest version of the popular command-line interface tool for
> managing Apache CloudStack environments.
>
> Cloudmonkey 6.3.0 comes packed with several new features, enhancements,
> and bug fixes to make it even more robust and reliable. Some of the key
> highlights of this release include:
>
> Add support for ARM64 Darwin/OSX build in Makefile
> Autocompletion on storage pool related APIs
> Enable profile information passing through commandline
> Profile caching improvements and bugfixes
> Fix: reuse cmk's CLI params to call piped cmd
> Maintenance changes - github actions/travis migration, dependencies
> upgrades,
> Various bug fixes
> Fixes handling of invalid timeout value
> Fixes csv output
>
> Cloudmonkey 6.3.0 is available for download now from the Apache CloudStack
> website. For more information on the release, including a full list of new
> features and bug fixes, please refer to the release notes.
>
>
> Downloads and Documentation  The official source code for CloudMonkey
> v6.3.0 can be downloaded from http://cloudstack.apache.org/downloads.html.
>
> CloudMonkey's usage details are documented at https://github.com/apache/
> cloudstack-cloudmonkey/wiki
>
> We encourage all CloudStack users to upgrade to Cloudmonkey 6.3.0 to take
> advantage of the latest features and improvements. As always, we welcome
> feedback and contributions from the community to help make Cloudmonkey even
> better.
>
> Thank you for your continued support of Apache CloudStack Cloudmonkey.
>
>
>
>
>

[PROPOSE] ACS 4.18.1.0 release

[Wei ZHOU]

Hi all,

Currently CloudStack 4.18.0.0 is the latest LTS release. There are some
bugs and pull requests with 4.18.0.0 [1], including the fix for the upgrade
issue if users use MySQL 5.6 and 5.7.

I would like to propose the release of 4.18.1.0 and the timeline

- from now till the end of July (3 months): accept bug fixes and minor
improvements [2]
- first week in Aug: stablisation efforts, accept only blocker and critical
bug fixes.
- Aug: start cutting RCs, vote and finish release work.

I will push myself as the release manager (RM) of 4.18.1.0, if nobody
objects.
In case anyone wants to include a bug fix or a pull request in 4.18.1.0
milestone, please mention me (weizhouapache) on github.

[1] https://github.com/apache/cloudstack/milestone/27
[2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS


Any suggestions ?

Kind regards,
Wei