[GitHub] [cloudstack-www] rohityadavcloud commented on pull request #96: Initial migration of blog posts and images

[via GitHub]

rohityadavcloud commented on PR #96:
URL: https://github.com/apache/cloudstack-www/pull/96#issuecomment-1432904289

   Thanks for replying @christ I think that should not happen as the permalink 
is renamed as `slug` in the docusauras website.
   For example for the blog post 
https://beautiful-pastelito-4eb422.netlify.app/blog/meet-apache-cloudstack-at-kubecon
  is same as 
https://blogs.apache.org/cloudstack/entry/meet-apache-cloudstack-at-kubecon 
(except the domain and some path). The `slug` is the permalink for this 
migrated post as seen at the markdown file here 
https://raw.githubusercontent.com/shapeblue/cloudstack-www/docusaurus-staging/blog/2023-02-10-meet-apache-cloudstack-at-kubecon.md
   
   @christ could you advise if ASF/infra has any deadline on blog migration, 
could it wait until May '23 end?



-- 
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: [DISCUSSION] Name confirmation before Destructive and unrecoverable actions

[Sina Kashipazha]

Daan, I created the following PR, it don't allow users to delete themselves.

https://github.com/apache/cloudstack/pull/7242



--- Original Message ---
On Wednesday, February 15th, 2023 at 14:34, Sina Kashipazha 
 wrote:


> 

> 

> 

> 

> Yes, they shouldn't be allowed to delete themselves. I'm totally agree with 
> that.
> 

> We can add this extra step as well, before users remove something valuable 
> like volume or network, etc.
> 

> 

> --- Original Message ---
> On Wednesday, February 15th, 2023 at 14:09, Daan Hoogland 
> daan.hoogl...@gmail.com wrote:
> 

> 

> 

> > again Sina, I think the users should never be allowed to delete themselves.
> > What is the use of such an action?
> 

> > On Wed, Feb 15, 2023 at 12:28 PM Sina Kashipazha
> > s.kashipa...@protonmail.com.invalid wrote:
> 

> > > I agree that it is not as pressing as it looks, but the consequences are
> > > high if users remove their account. In some setup, their VM will be 
> > > deleted
> > > immediately for ever.
> 

> > > Cause the network, VPS, account and many more deletion actions are look
> > > the same user will not read the confirmation pop up :-)
> 

> > > The proposed extra step that asks users to input the account name will
> > > prevent accident.
> 

> > > --- Original Message ---
> > > On Wednesday, February 15th, 2023 at 10:17 AM, Wei ZHOU <
> > > ustcweiz...@gmail.com> wrote:
> 

> > > > Agree with Daan
> 

> > > > -Wei
> 

> > > > On Wednesday, 15 February 2023, Daan Hoogland daan.hoogl...@gmail.com
> 

> > > > wrote:
> 

> > > > > seems ok, but I do not see the use case as pressing. I´d rather say
> > > > > that a
> > > > > user should not be able to destroy their own account.
> 

> > > > > On Tue, Feb 14, 2023 at 3:32 PM Sina Kashipazha
> > > > > s.kashipa...@protonmail.com.invalid wrote:
> 

> > > > > > Hey guys,
> 

> > > > > > Cloudstack users can delete their account accidentally and lock
> > > > > > themselves
> > > > > > from accessing the CloudStack panel. A link to an account placed
> > > > > > next to
> > > > > > ISO, template, VM and other entities in CloudStack's UI. If 
> > > > > > customers
> > > > > > doesn't paying attention, they would click on the account link
> > > > > > instead of
> > > > > > the link to the entity they want (vm, template, ISO etc.) Then, if
> > > > > > they
> > > > > > had
> > > > > > wanted to delete that entity, they would press delete button without
> > > > > > realising they were on the account page, and press Confirm.
> 

> > > > > > I'm suggesting to add an extra step before deletion. In that step
> > > > > > users
> > > > > > must write the account name, unless otherwise they can't confirm
> > > > > > deletion.
> > > > > > Github, like many other applications asks you to write down the
> > > > > > entity's
> > > > > > name before DESTRUCTIVE and UNRECOVERABLE actions.
> 

> > > > > > I've also created the following issue in Github:
> > > > > > https://github.com/apache/cloudstack/issues/7219
> 

> > > > > > Please let me know your thoughts about the proposal.
> 

> > > > > > Kind regards,
> > > > > > Sina
> 

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

> > --
> > Daan

signature.asc
Description: OpenPGP digital signature

Re: [4.18][RELEASE] RC1 up for vote

[João Jandre Paraquetti]

+1

Tested VM creation, migration, deletion, scaling, VM restart, VM 
snapshot and restore from snapshot.
Tested volume creation, attach, detach, migration, deletion, volume 
snapshot and restore from snapshot.
Tested registering a k8s ISO and creating a k8s cluster using the 
community ISO 1.24.0, also tested basic operations using k8s.


Best regards,
João Jandre (JoaoJandre)

On 15/02/2023 04:49, Daan Hoogland wrote:

Rohit, I started building them and they should be ready but I haven´t made
them publicly available yet. I'll look at that today

On Wed, Feb 15, 2023 at 2:46 AM Rohit Yadav 
wrote:


Thanks Daan, are there convenience packages available somewhere we can
test?

Regards.

Regards.

From: Wei ZHOU 
Sent: Wednesday, February 15, 2023 1:05:43 AM
To: us...@cloudstack.apache.org ;
dev@cloudstack.apache.org 
Subject: Re: [4.18][RELEASE] RC1 up for vote

Thanks Daan.

The docker image of cloudstack-simulator for 4.18.0.0-RC1 can be found at

https://hub.docker.com/repository/docker/apache/cloudstack-simulator/general

-Wei




On Tue, 14 Feb 2023 at 10:31, Daan Hoogland 
wrote:


Hi All,

I've created a 4.18.0.0 release candidate, with the following
artifacts up for a vote:

Git Branch and Commit
SH:


https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.18.0.0-RC20230214T0955

Commit: c3a27df15a535d877b34a10564651fffb032f756

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

PGP release keys (signed using
):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)


--
Daan

Re: [4.18][RELEASE] RC1 up for vote

[Nicolas Vazquez]

Hi all,

Unfortunately I have to vote -1, found the console access was not working for 
XCPng/Xen, staying Connecting indefinitely. Have produced a fix for it: 
https://github.com/apache/cloudstack/pull/7243

Regards,
Nicolas Vazquez


From: João Jandre Paraquetti 
Date: Thursday, 16 February 2023 at 17:21
To: us...@cloudstack.apache.org , 
dev@cloudstack.apache.org 
Subject: Re: [4.18][RELEASE] RC1 up for vote
+1

Tested VM creation, migration, deletion, scaling, VM restart, VM
snapshot and restore from snapshot.
Tested volume creation, attach, detach, migration, deletion, volume
snapshot and restore from snapshot.
Tested registering a k8s ISO and creating a k8s cluster using the
community ISO 1.24.0, also tested basic operations using k8s.

Best regards,
João Jandre (JoaoJandre)

On 15/02/2023 04:49, Daan Hoogland wrote:
> Rohit, I started building them and they should be ready but I haven´t made
> them publicly available yet. I'll look at that today
>
> On Wed, Feb 15, 2023 at 2:46 AM Rohit Yadav 
> wrote:
>
>> Thanks Daan, are there convenience packages available somewhere we can
>> test?
>>
>> Regards.
>>
>> Regards.
>> 
>> From: Wei ZHOU 
>> Sent: Wednesday, February 15, 2023 1:05:43 AM
>> To: us...@cloudstack.apache.org ;
>> dev@cloudstack.apache.org 
>> Subject: Re: [4.18][RELEASE] RC1 up for vote
>>
>> Thanks Daan.
>>
>> The docker image of cloudstack-simulator for 4.18.0.0-RC1 can be found at
>>
>> https://hub.docker.com/repository/docker/apache/cloudstack-simulator/general
>>
>> -Wei
>>
>>
>>
>>
>> On Tue, 14 Feb 2023 at 10:31, Daan Hoogland 
>> wrote:
>>
>>> Hi All,
>>>
>>> I've created a 4.18.0.0 release candidate, with the following
>>> artifacts up for a vote:
>>>
>>> Git Branch and Commit
>>> SH:
>>>
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.18.0.0-RC20230214T0955
>>> Commit: c3a27df15a535d877b34a10564651fffb032f756
>>>
>>> Source release (checksums and signatures are available at the following
>>> location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.0.0/
>>>
>>> PGP release keys (signed using
>>> ):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)
>>>
>>>
>>> --
>>> Daan
>>>
>

 

Re: [DISCUSSION] Name confirmation before Destructive and unrecoverable actions

[Harikrishna Patnala]

I agree with Sina to some extent as he mentioned in the PR, we should not allow 
deleting the own user account from UI alteast. I tried deleting the user where 
I logged in, it immediately kicked me out of the logged in session.

Daan, we are already not allowing a normal user to delete their own account. 
This case is for the root/resource/domain admin accounts.

Regards,
Harikrishna

On 16/02/23, 8:53 PM, "Sina Kashipazha"  
wrote:

Daan, I created the following PR, it don't allow users to delete themselves.

https://github.com/apache/cloudstack/pull/7242



--
 

- Original Message ---
On Wednesday, February 15th, 2023 at 14:34, Sina Kashipazha 
mailto:s.kashipa...@protonmail.com.inva>LID> 
wrote:


>

>

>

>

> Yes, they shouldn't be allowed to delete themselves. I'm totally agree with 
> that.
>

> We can add this extra step as well, before users remove something valuable 
> like volume or network, etc.
>

>

> --- Original Message ---
> On Wednesday, February 15th, 2023 at 14:09, Daan Hoogland 
> daan.hoogl...@gmail.com wrote:
>

>

>

> > again Sina, I think the users should never be allowed to delete themselves.
> > What is the use of such an action?
>

> > On Wed, Feb 15, 2023 at 12:28 PM Sina Kashipazha
> > s.kashipa...@protonmail.com.invalid
> >  wrote:
>

> > > I agree that it is not as pressing as it looks, but the consequences are
> > > high if users remove their account. In some setup, their VM will be 
> > > deleted
> > > immediately for ever.
>

> > > Cause the network, VPS, account and many more deletion actions are look
> > > the same user will not read the confirmation pop up :-)
>

> > > The proposed extra step that asks users to input the account name will
> > > prevent accident.
>

> > > --- Original Message ---
> > > On Wednesday, February 15th, 2023 at 10:17 AM, Wei ZHOU <
> > > ustcweiz...@gmail.com> wrote:
>

> > > > Agree with Daan
>

> > > > -Wei
>

> > > > On Wednesday, 15 February 2023, Daan Hoogland 
> > > > daan.hoogl...@gmail.com
>

> > > > wrote:
>

> > > > > seems ok, but I do not see the use case as pressing. I´d rather say
> > > > > that a
> > > > > user should not be able to destroy their own account.
>

> > > > > On Tue, Feb 14, 2023 at 3:32 PM Sina Kashipazha
> > > > > s.kashipa...@protonmail.com.invalid
> > > > >  wrote:
>

> > > > > > Hey guys,
>

> > > > > > Cloudstack users can delete their account accidentally and lock
> > > > > > themselves
> > > > > > from accessing the CloudStack panel. A link to an account placed
> > > > > > next to
> > > > > > ISO, template, VM and other entities in CloudStack's UI. If 
> > > > > > customers
> > > > > > doesn't paying attention, they would click on the account link
> > > > > > instead of
> > > > > > the link to the entity they want (vm, template, ISO etc.) Then, if
> > > > > > they
> > > > > > had
> > > > > > wanted to delete that entity, they would press delete button without
> > > > > > realising they were on the account page, and press Confirm.
>

> > > > > > I'm suggesting to add an extra step before deletion. In that step
> > > > > > users
> > > > > > must write the account name, unless otherwise they can't confirm
> > > > > > deletion.
> > > > > > Github, like many other applications asks you to write down the
> > > > > > entity's
> > > > > > name before DESTRUCTIVE and UNRECOVERABLE actions.
>

> > > > > > I've also created the following issue in Github:
> > > > > > https://github.com/apache/cloudstack/issues/7219
>

> > > > > > Please let me know your thoughts about the proposal.
>

> > > > > > Kind regards,
> > > > > > Sina
>

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

> > --
> > Daan

[GitHub] [cloudstack-documentation] kiranchavala commented on a diff in pull request #304: Added sample ssh commands to connect to Control and Worker node

[via GitHub]

kiranchavala commented on code in PR #304:
URL: 
https://github.com/apache/cloudstack-documentation/pull/304#discussion_r1109405418


##
source/plugins/cloudstack-kubernetes-service.rst:
##
@@ -153,6 +153,20 @@ A new network offering named 
DefaultNetworkOfferingforKubernetesService has been
- Multi-control nodes, HA cluster can be created for Kubernetes version 
1.16 and above only.
- While creating multi-control nodes, HA cluster over a shared network, an 
external load-balancer must be manually setup. This load-balancer should have 
port-forwarding rules for SSH, Kubernetes API server access. Service assumes 
SSH access to cluster nodes is available from port  to ( + cluster node 
count -1). Similarly, for API access 6443 must be forwarded to control nodes. 
Over the CloudStack isolated network these rules are automatically provisioned.
 
+.. parsed-literal::
+
+   Example to ssh into the Control node and worker node
+
+   Control node
+
+   ssh -i  -p  cloud@
+   
+   Worker node
+   
+   ssh -i  -p 2223 cloud@

Review Comment:
   @DaanHoogland 
   Thanks, the formatting looks good now 



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