Re: CloudFest Promo Code for Free Registrations

[Ivet Petrova]

Hey David, are you planning to join the event?


 

> On 16 Feb 2024, at 1:38, David Amorín  wrote:
> 
> 18-21 de Marzo
> 
> David Amorín
> 
> david.amo...@jotelulu.com  | 
> jotelulu.com
> 
> This message and the attached documents are confidential and are addressed 
> exclusively to the referenced recipient. If it is not and you have received 
> this email in error, please notify me by this means and proceed to delete it. 
> In accordance with what is available in current regulations, you are informed 
> that the personal data included in this communication will be processed by 
> JOTELULU  (responsible for the Treatment) with the purpose of managing 
> professional communications, and that they will not be transferred to third 
> parties except obligation lawful or with your consent. The legitimizing basis 
> of the treatment is your consent or compliance with the contractual 
> relationship. You can exercise your rights of access, rectification, 
> portability and deletion of data, as well as those of limitation and 
> opposition through d...@jotelulu.com or by written 
> communication.
> 
> Message produced and distributed by JOTELULU. © 2023, JOTELULU. All rights 
> reserved.
> 
> 
> 
> From: Ivet Petrova 
> Sent: Wednesday, January 24, 2024 10:56:27 AM
> To: us...@cloudstack.apache.org ; dev 
> 
> Subject: CloudFest Promo Code for Free Registrations
> 
> Caution: This email has been originated from the outside of the organization, 
> Do not click links or open attachments unless you recognize the sender and 
> know the content is safe.
> 
> 
> Hi all,
> 
> I am happy to announce that for a second year, CloudStack will be exhibiting 
> at CloudFest - biggest cloud expo in Europe.
> I would like to share a code for free registration for our community members: 
> c3SY3Zu2
> 
> You can register here: https://registration.cloudfest.com/?code=c3SY3Zu2
> 
> Also, I am searching for volunteers who would like to support the project at 
> the booth.
> We already have a few people from ShapeBlue and Wido will be also at the 
> event. So is there anybody who would like to participate as booth staff?
> 
> Best regards,
> 
> 
> 
> 

Re: [PR] Update SDKs [cloudstack-terraform-provider]

[via GitHub]

CodeBleu commented on PR #71:
URL: 
https://github.com/apache/cloudstack-terraform-provider/pull/71#issuecomment-1947788692

   If there is going to be SDK updates, why not just go to the [Terraform 
Plugin 
Framework](https://developer.hashicorp.com/terraform/plugin/framework/migrating)
 instead?


-- 
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: [PR] Add docs for new resources [cloudstack-terraform-provider]

[via GitHub]

rohityadavcloud commented on PR #81:
URL: 
https://github.com/apache/cloudstack-terraform-provider/pull/81#issuecomment-1946338552

   @DaanHoogland I'm not sure, they never had license headers 
(https://github.com/apache/cloudstack-terraform-provider/tree/main/website/docs/r)
 and I'm not sure if adding those would somehow break the docs/website at 
https://registry.terraform.io/providers/cloudstack/cloudstack/latest/docs


-- 
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: [PR] Enable cloud-init without any aid from ds-identify [cloudstack-documentation]

[via GitHub]

blueorangutan commented on PR #383:
URL: 
https://github.com/apache/cloudstack-documentation/pull/383#issuecomment-1946295034

   QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/383. 
(QA-JID 213)


-- 
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: [PR] Enable cloud-init without any aid from ds-identify [cloudstack-documentation]

[via GitHub]

blueorangutan commented on PR #383:
URL: 
https://github.com/apache/cloudstack-documentation/pull/383#issuecomment-1946293190

   @weizhouapache a Jenkins job has been kicked to build the document. I'll 
keep you posted as I make progress.


-- 
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: [PR] Enable cloud-init without any aid from ds-identify [cloudstack-documentation]

[via GitHub]

weizhouapache commented on PR #383:
URL: 
https://github.com/apache/cloudstack-documentation/pull/383#issuecomment-1946292430

   @blueorangutan docbuild


-- 
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: [PR] Add docs for new resources [cloudstack-terraform-provider]

[via GitHub]

DaanHoogland commented on PR #81:
URL: 
https://github.com/apache/cloudstack-terraform-provider/pull/81#issuecomment-1946160312

   just a side note , do these docs need apache license statements?


-- 
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: [PR] Add docs for new resources [cloudstack-terraform-provider]

[via GitHub]

CodeBleu commented on PR #81:
URL: 
https://github.com/apache/cloudstack-terraform-provider/pull/81#issuecomment-1946153613

   Thanks @rohityadavcloud. I figured it was better than nothing.     We can 
always go back and tweak it if needed.


-- 
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: [PROPOSAL] version naming : drop the 4.

[Rohit Yadav]

(+ users)

All,

Generally speaking, any versioning/styling change can be perceived as a big or 
concerning change by users (those existing or new ones trying/adopting). So, we 
must get our message across properly and correctly.

I'm not for or against cosmetics change in versioning, but I'm really keen if 
we want to discuss if we can use this opportunity to streamline our LTS 
release, improve how we upgrade CloudStack (i.e relook at our DB/upgrade 
approach), make releases more linear and faster (avoid forking branches for 
example), and try to change new defaults and drop some old API/arch things 
(such as default API response type to json, but largely be backward 
compatible). Some of these suggestions may be too large an undertaking and make 
not be worth it.


Overall, I've no objections if the consensus is to drop the "4." version 
prefix. I also want to hear from our users if they've any feedback for us.


Regards.

 



From: Guto Veronezi 
Sent: Tuesday, February 13, 2024 18:34
To: dev@cloudstack.apache.org 
Subject: Re: [PROPOSAL] version naming : drop the 4.

Daan,

As we still plan to introduce disruptive changes (in a cautious and
structured way) in the major versions, all my concerns are met; I do not
have further technical reasons to keep the "4.".

Best regards,
Daniel Salvador (gutoveronezi)

On 2/12/24 11:55, Daan Hoogland wrote:
> bump,
> @Daniel Salvador is there any technical reason to keep the 4? any
> reason why there must be a 5 instead of a 21, 22 or 23? We are
> maintaining 4 number semantic versioning for no reason, as I see it.
>
> On Tue, Jan 30, 2024 at 12:02 PM Daan Hoogland  
> wrote:
>> Daniel, "technical" reasons for dropping the 4 are all in the field of
>> social engineering. In practice (as I think Wei also described) we are
>> already treating the "minor" version number as major version. Since
>> 4.0 or 4.1 (don´t remember) there has been renewed talk of a 5 , but
>> never enough reason and or commitment to make it real. We could argue
>> about it a lot.
>>
>> so
>> ¨¨¨
>> The main point is: *we have to understand the technical reasons for
>> the proposal and what we expect from it before deciding anything.
>> ¨¨¨
>> The most important point is that we expect that people understand that
>> we treat the number that now seems to be "minor" as major release
>> numbers.
>>
>>
>> On Fri, Jan 26, 2024 at 7:42 PM Wei ZHOU  wrote:
>>> Hi Daniel,
>>>
>>> If we are discussing 5.0, I would have the same concern as you.
>>> What we are discussing is dropping 4.x. The fact is, we will never release
>>> 5.0 (anyone disagree ?)
>>> In this case, the major version 4.x becomes useless.
>>> If we compare 4.20.0/4.21.0 with 20.0/21.0, it is obvious which is better.
>>> IMHO due to the similar reason, the Java version has been changed from 1.x
>>> to java 1.7/1.8 (=java 7/8) then to java 11/14/17.
>>> of course there will be some issues if semantic changes, I think it is
>>> under control.
>>>
>>>
>>>
>>> Regarding the compatibility, I think we can change the APIs gradually.
>>> I noticed the following recently when I tested VR upgrade to
>>> debian12/python3
>>>
>>> root@r-431-VM:~# python
>>> Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] on linux
>>> Type "help", "copyright", "credits" or "license" for more information.
>> import cgi
>>> :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)



>>
>>
>> --
>> Daan
>
>

Re: [PR] Improves service offering resource [cloudstack-terraform-provider]

[via GitHub]

rohityadavcloud commented on PR #64:
URL: 
https://github.com/apache/cloudstack-terraform-provider/pull/64#issuecomment-1945840699

   @fabiomatavelli can you help review/resolve the conflict?


-- 
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: [PR] Add docs for new resources [cloudstack-terraform-provider]

[via GitHub]

rohityadavcloud merged PR #81:
URL: https://github.com/apache/cloudstack-terraform-provider/pull/81


-- 
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: [PR] Fix: zone data source not returning Id [cloudstack-terraform-provider]

[via GitHub]

rohityadavcloud merged PR #80:
URL: https://github.com/apache/cloudstack-terraform-provider/pull/80


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