Network selection specifically for Hosting provider

[Ranjit Jadhav]

Hello guys,

We are using Xenserver for host and configured Isolated Network . but
we are facing the following issues

1) One IP gets reserved for source-nat per user

2) How can we assign secondary IP to the instance.

There are a few more issues/queries related to the network.

Thanks and Regards,
Ranjit

Problems Configuring GloboDNS

[R R]

Hi all,

I am trying to setup GloboDNS so as to later integrate with cloudstack. I
have been following the github documentation from globocom. I have been
experiencing so many problems as the repo is old. Mostly package problems.
Ruby and rails is very new to me.

Does any one have the guide to configure GloboDNS other than this github
repo? If you could send me few links to articles or videos, that would be
great.

Thanks and regards
Rishabh

ACS 4.15.1 / XCP-NG 8.2

[benoit lair]

Hello,

I am trying to scale up a Debian VM from 4Go to 8Go ram
I ran into the following error :

2021-10-19 15:33:05,803 DEBUG [c.c.h.x.r.w.x.CitrixScaleVmCommandWrapper]
(DirectAgent-156:ctx-62880cee) (logid:e5db9099) Catch exception
com.cloud.utils.exception.CloudRuntimeException when scaling VM:i-2-83-VM
due to com.cloud.utils.exception.CloudRuntimeException: Cannot scale up the
vm because of memory constraint violation: 0 <=
memory-static-min(4294967296) <= memory-dynamic-min(8589934592) <=
memory-dynamic-max(8589934592) <= memory-static-max(4294967296)

Any ideas ?

Regards, Benoit Lair

Re: Linstor storage plugin

[benoit lair]

Hi Slavka,

I see

@PMC Would it be possible to have Linstor for Xcp-NG ?

Thanks a lot
Regards Benoit

Le mar. 19 oct. 2021 à 12:36, Slavka Peleva 
a écrit :

> Hi Benoit,
>
> According to the Linstor
> <
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Linstor+storage+plugin#Linstorstorageplugin-Hypervisorssupported
> >
> documentation of the plugin, the supported hypervisor is KVM.
>
> Best regards,
> Slavka
>
> On Tue, Oct 19, 2021 at 1:17 PM benoit lair  wrote:
>
> > Hello Guys,
> >
> > Will this new feature be available with xcp-ng ?
> >
> > Regards, Benoit
> >
>

[GitHub] [cloudstack-www] rhtyd merged pull request #85: Update users.html.markdown

[GitBox]

rhtyd merged pull request #85:
URL: https://github.com/apache/cloudstack-www/pull/85


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: Linstor storage plugin

[Slavka Peleva]

Hi Benoit,

According to the Linstor

documentation of the plugin, the supported hypervisor is KVM.

Best regards,
Slavka

On Tue, Oct 19, 2021 at 1:17 PM benoit lair  wrote:

> Hello Guys,
>
> Will this new feature be available with xcp-ng ?
>
> Regards, Benoit
>

Linstor storage plugin

[benoit lair]

Hello Guys,

Will this new feature be available with xcp-ng ?

Regards, Benoit

Re: Linstor volume storage plugin

[benoit lair]

Hello René,

Does this plugin will work with XCP-NG Hypervisor ?

Regards, Benoit

Le jeu. 11 févr. 2021 à 09:47, Rene Peinthor  a
écrit :

> Hi!
>
> I'm currently working on a volume storage plugin for cloudstack, but got a
> bit stuck on a few design things of cloudstack.
>
> So I started with adding a `cloud-plugin-storage-volume-linstor` plugin and
> implemented the
> LifeCycle, Provider, Listener and Driver.
> I'm able to add it as primary storage with my own Provider from the UI, but
> as I understood
> you can't directly create a volume within this storage pool, it is rather
> decided by the allocator/placer.
> As I still have another Primary storage driver (NFS) new volumes will get
> created there, but
> I can migrate storage to Linstor from there.
> That is when I found out that cloudstack also has a StorageAdaptor on the
> agent side and it looks
> like the agent side only has very limited info about the storage pool and
> only gets the name(uuid).
>
> Linstor is a shared storage, so BLOCK volumes can/will be provided on all
> nodes that are
> part of the Linstor cluster and for Linstor, it would be enough to control
> the creation/deletion
> of volumes from the management server, actions on the agent side would only
> be needed for
> migrating volumes to another storage pool or copy volumes within Linstor if
> the backend storage doesn't support snapshots.
>
> So do you have any guidelines on how I should add the Linstor storage?
>
> I guess I could create the Linstor pool as `managed` and store the storage
> pool info in some config file,
> but it seems to be unnecessary and I wouldn't really want to control the
> Linstor cluster also
> from the agents.
>
> My idea would be that only the management server talks to Linstor and
> agents should only be used, for e.g. copying data between volumes or
> convert image formats.
>
> Best regards,
> Rene
>

Re: [cloudstack-go] sdk releasing

[Rohit Yadav]

Hi All, cc PL

I thought to check with the community for any objections, following PL's 
approach for ACS 4.15.2 we've created:
https://github.com/apache/cloudstack-go/releases/tag/v2.11.0

Explicit testing/voting may not be necessary as it's largely autogenerated 
against API of an ACS release and further it doesn't serve purpose in itself 
but currently used by the CloudStack k8s provider and terrraform provider which 
will be tested/voted against (indirectly testing/voting these projects will 
also validate/test the go-sdk).

Unless there are any objections, do we agree to tag the cloudstack-go repo with 
tags against ACS releases using the approach PL started?


Regards.


From: Rohit Yadav 
Sent: Wednesday, September 8, 2021 13:49
To: Pierre-Luc Dion ; dev 
Subject: Re: [cloudstack-go] sdk releasing

+1

That makes sense. In the go-sdk we've a generator that consumes the listApis 
output of a ACS release and generates the library - 
https://github.com/apache/cloudstack-go/tree/main/generate

I suppose for every ACS release, we can update go-sdk with release-specific API 
list, test it, release and tag it. Even automate this?

I would say - no need to vote it unless the SDK is manually changed. Since it 
is used with the k8s provider or the terraform provider so tags on go-sdk may 
go in-line with tags/release of these users.

Regards.


From: Pierre-Luc Dion 
Sent: Friday, August 27, 2021 17:57
To: Rohit Yadav ; dev 
Subject: [cloudstack-go] sdk releasing

I've messing around with cloudstack-go

Did a fix that rohit merged yesturday for hostsservices, but this fix will only 
work for acs4.15, I'd like to fix it for previous acs version too, but look 
like the version of the SDK depend on acs version;

Example; for the hostservices, the host attribute managementserverid is a UUID 
in 4.15, but an integer in an older version of xenserver. This breaks the 
structs,or map, we must have some other similar issue.

so I'd like to help on creating a tag or version of the SDK so they would match 
acs version target,
ie: SDK version = v4.15-0; where the last digit would define the sdk version or 
increase with fixes.
Current versioning in use = https://github.com/apache/cloudstack-go/releases

The issue I'm expecting to face is if we create a release , let's say v4.15-0 
from main branch today, if we want to create v4.14.0, it will not be possible 
from the main branch because we need to revert the last commit but also fix 
hostservices.

Here are a bunch of questions I have:
1. Should we create a branch for older ACS versions  and keep main for latest 
fixes and future releases ?
2. Do we need to vote for such changes?
3. Does such releases could impact other Go projects that use this one, such as 
terraform and kubernetes drivers?
4. Should we provide similar versioning on our kubernetes driver?





 

Re: [VOTE] Apache Cloudstack 4.16.0.0 RC1

[Rohit Yadav]

I've built and uploaded convenience packages here:
https://download.cloudstack.org/testing/41600-RC1/

Few notes:

  *   The Debian changelog has an issue to build deb pkgs I had to replace 
"lun" with "Mon" and "oct" with "Oct", this is needed when not using the 
packaging/build-deb.sh script but when people run "dpkg-buildpackage -uc -us 
-b" to build deb packages
  *   GPG keys and checksums are okay
  *   With 4.16, registering systemvmtemplate prior to upgrade is no longer 
required

Regards.


From: Nicolas Vazquez 
Sent: Monday, October 18, 2021 23:55
To: dev@cloudstack.apache.org ; users 

Subject: [VOTE] Apache Cloudstack 4.16.0.0 RC1

Hi All,

I have created a 4.16.0.0 release (RC1) with the following artefacts up for 
testing and a vote:

Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.16.0.0-RC20211018T1454
Commit: 506f8a8269551acb9b07b029da0f9e4fe858d150

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

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

The vote will be open until 21st October 2021, 21.00 CET (72h).

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)

4.16.0.0 System VM templates are available from here:
https://download.cloudstack.org/systemvm/4.16/


Regards,

Nicolas Vazquez